From: <Paul_Koning@Dell.com>
To: <psmith@gnu.org>
Cc: <gdb@sourceware.org>
Subject: Re: GDB with python support: which version of Python?
Date: Fri, 31 May 2013 00:04:00 -0000 [thread overview]
Message-ID: <C75A84166056C94F84D238A44AF9F6AD033FF86D@AUSX10MPC103.AMER.DELL.COM> (raw)
In-Reply-To: <1369951459.3295.229.camel@pdsdesk>
On May 30, 2013, at 6:04 PM, 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?
>
> I see from the README that the "oldest version of Python supported by
> GDB is 2.4". Is there a _recommended_ version of Python? 2.7? 3.x?
> Something else?
My personal favorite is 3.latest, but for those who want Python 2, I'd say 2.latest (i.e., 2.7). But it's really more a matter of what you have installed. If you can most easily install some other version, or you have other libraries that need a particular Python version, then that would decide things.
I've built gdb for pretty much all the 2.x and 3.x versions supported; it's all easy.
paul
next prev parent reply other threads:[~2013-05-31 0:04 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 [this message]
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
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=C75A84166056C94F84D238A44AF9F6AD033FF86D@AUSX10MPC103.AMER.DELL.COM \
--to=paul_koning@dell.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