From: Paul Smith <psmith@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: GDB with python support: which version of Python?
Date: Fri, 31 May 2013 05:49:00 -0000 [thread overview]
Message-ID: <1369979331.4119.19.camel@homebase> (raw)
In-Reply-To: <20130531044006.GB4395@adacore.com>
On Fri, 2013-05-31 at 08:40 +0400, Joel Brobecker wrote:
> > I'm trying to build a portable version of GDB, with Python support, that
> > I can use on many different (GNU/Linux) systems. It's frustrating
> > because Python versions are all over the place: every distro you use, it
> > seems like, has a different not-completely-compatible version.
>
> Forcing static libraries might work on GNU/Linux systems, but
> we've found it to be unworkable in general.
Interesting; what kinds of problems did you have?
> Here is what we do at AdaCore: we build and install GDB inside
> GDB's prefix,
I assume you mean build and install _Python_ inside GDB's prefix?
> and use that to configure GDB. You can then ship
> the entire GDB install, including Python. As long as the Python
> path is inside the GDB prefix, GDB should be locating the Python
> install fine (unless the user has the PYTHONHOME environment
> variable set, in which case I believe it overrides GDB's default
> behavior).
But don't you have to set LD_LIBRARY_PATH or something to find the
libpython.so, if you link dynamically? I guess this could be done with
a gdb wrapper script of some kind. Or, is the installation not
relocatable (it must always be installed in the same place)? Our
installation needs to be relocatable.
This is an interesting idea, though, I'll look into it.
next prev parent reply other threads:[~2013-05-31 5:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 22:04 Paul Smith
2013-05-31 0:04 ` Paul_Koning
2013-05-31 4:40 ` Joel Brobecker
2013-05-31 5:49 ` Paul Smith [this message]
2013-05-31 6:00 ` Joel Brobecker
2013-05-31 10:18 ` Pedro Alves
2013-05-31 20:23 ` Joseph S. Myers
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=1369979331.4119.19.camel@homebase \
--to=psmith@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb@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