From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Paul Smith <psmith@gnu.org>
Cc: <gdb@sourceware.org>
Subject: Re: GDB with python support: which version of Python?
Date: Fri, 31 May 2013 20:23:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1305312017320.16006@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1369951459.3295.229.camel@pdsdesk>
On Thu, 30 May 2013, Paul Smith wrote:
> Hi all;
>
> 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.
>
> Plus, I can't find any straightforward way to build GDB with Python
> linked statically to avoid local .so version problems. Seems GDB
> configure doesn't really support this. I'm thinking of pulling a Python
> install without any .so to force static linking. Have others tried
> this?
You can link with a .so copy of Python shipped with the GDB installation
using -Wl,-rpath,$ORIGIN. Unfortunately multiple levels of shell and
makefile interpretation make passing that '$' down a pain; at Mentor we
have a shell variable setting
flags='-Wl,-rpath,'\''\\\$$\$$\\\$$\$$ORIGIN'\''/../'"$pypath"
for this purpose, but the exact levels of quotation required may depend on
exactly how you pass the linker options when configuring GDB. See
<http://sourceware.org/ml/binutils/2009-10/msg00257.html>.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2013-05-31 20:23 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
2013-05-31 6:00 ` Joel Brobecker
2013-05-31 10:18 ` Pedro Alves
2013-05-31 20:23 ` Joseph S. Myers [this message]
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=Pine.LNX.4.64.1305312017320.16006@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=psmith@gnu.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