From: Doug Evans <dje@google.com>
To: Joel Brobecker <brobecker@adacore.com>,
Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] ignore PYTHONHOME environment variable.
Date: Sat, 15 Jan 2011 09:17:00 -0000 [thread overview]
Message-ID: <AANLkTikf7JZPOVpS6RdP5OdT2LAW6xwk_E_XoANvng9A@mail.gmail.com> (raw)
In-Reply-To: <20110113205504.GL2504@adacore.com>
On Thu, Jan 13, 2011 at 12:55 PM, Joel Brobecker <brobecker@adacore.com> wrote:
> Given the lack of support and the resistance from Jan, this patch is
> withdrawn. (I think that's a mistake! :-P)
fwiw, I like GDB_PYTHONHOME. I'd rather not punt on this.
I'm not sure I completely understand the objections to something like
the following:
if GDB_PYTHONHOME provided
use it
elseif PYTHONHOME provided
use it
else
use default
endif
That way a user can provide a PYTHONHOME and gdb will use it. But if
it is incompatible with the python that gdb is using, they can still
have PYTHONHOME - they just need to set GDB_PYTHONHOME too.
next prev parent reply other threads:[~2011-01-15 7:56 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
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 [this message]
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=AANLkTikf7JZPOVpS6RdP5OdT2LAW6xwk_E_XoANvng9A@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