From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: Add LIBDIR/gdb/python-<version> to Python search path
Date: Thu, 20 May 2010 19:15:00 -0000 [thread overview]
Message-ID: <20100520190347.GE3019@adacore.com> (raw)
In-Reply-To: <20100520185436.GA24123@caradoc.them.org>
> I have a not-as-nice local patch to achieve a similar goal, so I'm in
> favor. But what do you see as the role of GDB_LIBDIR, other than
> this?
I admit that I don't see any other uses for now. I picked libdir
because that seemed to be the appropriate location after reading
the GNU Coding Standards section on the various directories. I should
also give credit to Tom for suggesting it first (on IRC).
> GDB isn't the only program in our distribution that needs an included
> Python, so we're not going to put it in lib/gdb. But it'd be nice to
> have other GDB-private data outside of top-level lib/.
That would argue in favor if adding an extra switch that allows you
to override the python libdir. I can take care of that as part of
this patch set, for sure, if this helps in your case.
--
Joel
next prev parent reply other threads:[~2010-05-20 19:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 18:40 Joel Brobecker
2010-05-20 18:40 ` [PATCH 2/2] Add gdb_libdir/python-<version> in front of " Joel Brobecker
2010-05-20 21:37 ` Jan Kratochvil
2010-05-20 21:49 ` Joel Brobecker
2010-05-20 22:09 ` Jan Kratochvil
2010-05-20 23:03 ` Joel Brobecker
2010-05-21 9:33 ` Doug Evans
2010-05-21 16:01 ` Joel Brobecker
2010-05-21 16:17 ` Tom Tromey
2010-05-21 19:39 ` Doug Evans
2010-05-20 18:54 ` [PATCH 1/2] Add support for --with-gdb-libdir (default: <prefix>/lib/gdb) Joel Brobecker
2010-05-27 15:04 ` Joel Brobecker
2010-05-28 5:27 ` Doug Evans
2010-05-28 16:08 ` Joel Brobecker
2010-05-20 19:03 ` Add LIBDIR/gdb/python-<version> to Python search path Daniel Jacobowitz
2010-05-20 19:15 ` Joel Brobecker [this message]
2010-05-20 19:23 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100520190347.GE3019@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox