From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Add gdb_libdir/python-<version> in front of Python search path.
Date: Fri, 21 May 2010 16:01:00 -0000 [thread overview]
Message-ID: <20100521155415.GU3019@adacore.com> (raw)
In-Reply-To: <AANLkTiktQWpMfjWakzeJkHMZd2MEfS0rphPhdBS1nhTs@mail.gmail.com>
> I think(!) this is a better approach. Could be wrong of course. :-)
> I think adding one directory to sys.path is insufficient, and from
> what I've read it seems like Py_SetProgramName is the preferred
> solution to this problem.
ISTM for your research (thank you!) that not only is this a better
solution, but most likely the only really viable solution. We're going
to have to go with ${gdb_libdir=<prefix>/lib/gdb}/python/lib/python2.6.
> This patch doesn't currently handle your case, where the relationship
> between the location of python and gdb at build time is different than
> at runtime. I think the solution to that is another config parameter
> to specify where to find python at run time. Currently, when given a
> path, --with-python specifies where to find python at build time, and,
> for now, also at runtime.
> I can create another patch to add this new option
> (--with-python-libdir or some such) if you think it's worth pursuing.
I think we can work around it, by simply making sure that python is
already installed at desired location relative to the prefix used
for configuration. In any case, if I need the extra option, I can
take care of that part.
> Regardless of whether --with-python-libdir is useful to add to the FSF
> tree, I think the attached patch is worthy.
I agree.
> 2010-05-21 Doug Evans <dje@google.com>
>
> Allow python to find its files if moved from original location.
> * acinclude.m4 (GDB_AC_DEFINE_RELOCATABLE): New function.
> (GDB_AC_WITH_DIR): Call it.
> * configure.ac: If a path is provided to --with-python,
> define WITH_PYTHON_PATH.
> * config.in: Regenerate.
> * configure: Regenerate.
> * defs.h (python_libdir): Declare.
> * main.c (python_libdir): Define.
> (captured_main): Initialize python_libdir.
> * python/python.c (_initialize_python): If configured with
> --with-python=/path, call Py_SetProgramName to make sure python
> can find its libraries and modules.
I read the patch as carefully as I could, and nothing jumped out.
--
Joel
next prev parent reply other threads:[~2010-05-21 15:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 18:40 Add LIBDIR/gdb/python-<version> to " 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 [this message]
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
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=20100521155415.GU3019@adacore.com \
--to=brobecker@adacore.com \
--cc=dje@google.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