Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] ignore PYTHONHOME environment variable.
Date: Tue, 23 Nov 2010 09:29:00 -0000	[thread overview]
Message-ID: <AANLkTiko2FVL+ktF9JTBRedYz_wvsq_eP4rU3rLcOYmF@mail.gmail.com> (raw)
In-Reply-To: <20101123030037.GA19962@host0.dyn.jankratochvil.net>

On Mon, Nov 22, 2010 at 7:00 PM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Tue, 23 Nov 2010 02:03:22 +0100, Joel Brobecker wrote:
>> This is something I hinted during one of our discussion at this year's
>> GCC Summit.
>>
>> If PYTHONHOME is defined in the environment, then Py_SetProgramName
>> does not use the program-name location to find the python library.
>> Instead, it follows the PYTHONHOME, which can cause problems if
>> it points to a different Python installation, particularly if that
>> installation is from a different version of Python.
>
> On standard Fedora 14 ./configure (no python options given) I get:
> #define HAVE_LIBPYTHON2_7 1
> #define HAVE_PYTHON 1
> #define PYTHON_PATH_RELOCATABLE 0
> #define WITH_PYTHON_PATH "/usr"
>
> I am not a Python expect but I believe for GDB linked with the only regular
> system Python $PYTHONHOME should work, even for GDB-Python.
>
> Maybe it should be overriden only for the case of PYTHON_PATH_RELOCATABLE?
> Or maybe only if --with-python=SPECIFIC-PATH has been given?
>
> (I do not have an opinion what it should do in such case, just I think I know
> what it should do in the default system Python case.)

Hi.
I'm not sure I understand the objection.
AIUI, if gdb is linked with the system python then Joel's patch is
essentially a nop
(i.e. PYTHONHOME=/usr would still work).

[Right?]


  reply	other threads:[~2010-11-23  9:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23  1:03 Joel Brobecker
2010-11-23  3:01 ` Jan Kratochvil
2010-11-23  9:29   ` Doug Evans [this message]
2010-11-23 16:31     ` Jan Kratochvil
2010-11-23 16:57       ` Doug Evans
2010-11-23 17:31         ` Joel Brobecker
2010-12-14  7:12           ` Joel Brobecker
2010-12-14  9:27             ` Jan Kratochvil
2010-12-14 10:33               ` Joel Brobecker
2011-01-13 22:57                 ` Joel Brobecker
2011-01-15  9:17                   ` Doug Evans
2011-01-15 11:26                     ` Jan Kratochvil
2011-01-17 10:36                       ` Joel Brobecker
2012-05-18 19:34                 ` Jan Kratochvil
2012-05-28 14:41                   ` Joel Brobecker
2012-05-28 17:30                     ` Jan Kratochvil
2012-05-29 14:54                       ` Joel Brobecker
2012-05-29 15:57                         ` Jan Kratochvil
2012-05-30 14:37                         ` Jan Kratochvil

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=AANLkTiko2FVL+ktF9JTBRedYz_wvsq_eP4rU3rLcOYmF@mail.gmail.com \
    --to=dje@google.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /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