From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Add gdb_libdir/python-<version> in front of Python search path.
Date: Thu, 20 May 2010 21:49:00 -0000 [thread overview]
Message-ID: <20100520214647.GG3019@adacore.com> (raw)
In-Reply-To: <20100520212805.GA8617@host0.dyn.jankratochvil.net>
On Thu, May 20, 2010 at 11:28:05PM +0200, Jan Kratochvil wrote:
> On Thu, 20 May 2010 20:40:03 +0200, Joel Brobecker wrote:
> > +\n\
> > +# Put gdb_libdir/python-<version> in the python search path. This allows\n\
> > +# us to provide GDB bundled with its own python runtime (the .py/pyc files).\n\
> > +sys.path.insert(0, gdb.libdir + \"/python-%d.%d\" % (sys.version_info[0],\n\
> > + sys.version_info[1]))\n\
>
> While I do not mind wrt FSF GDB I find this kind of patch as the schoolbook
> example of a distro patch nobody expects to be accepted upstream.
I have to disagree about that ("textbook example" is a little harsh, no?)
- I wouldn't have proposed this idea if I didn't think that it wouldn't
be useful to others. I guess we have to take one step back and decide
whether we want to help users who build binaries like AdaCore does, or
not. I don't think that this is the first time that someone introduces
a patch that helps in that direction, and I don't think we're doing
a disservice to GDB to adding it either. It's not like it's a complicated
and intrusive change...
I'm going to hold off on that for a day or two, see what everyone
thinks. If it has to be kept inside AdaCore, then so be it. But it's
clear, just with Dan's answer, that someone else would benefit from
the code. And code sharing means more time to work on other stuff.
> I could push the same way patch for using gcc44 for specific testcases
> requiring newer gcc, workaround of Red Hat specific kernel incompatibility or
> workaround of upstream ccache bug which you voted for not including in FSF GDB
> http://sourceware.org/ml/gdb-patches/2009-03/msg00026.html
We can revisit the decision. I don't remember the details, but I feel that
the situation was not the same then.
--
Joel
next prev parent reply other threads:[~2010-05-20 21:47 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 [this message]
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
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=20100520214647.GG3019@adacore.com \
--to=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