From: Terry Guo <flameroc@gmail.com>
To: Tim Sander <tim@krieglstein.org>
Cc: gdb@sourceware.org
Subject: Re: OT: Re: Is it possible to statically link python into gdb?
Date: Wed, 25 Jun 2014 09:00:00 -0000 [thread overview]
Message-ID: <CAGbRaL65KDHL4Ab2x=TMcd0=M_RDtFL70Xyt_NMOWG1WydF4gw@mail.gmail.com> (raw)
In-Reply-To: <1728408.r4D3qvlyjx@dabox>
On Wed, Jun 25, 2014 at 4:32 PM, Tim Sander <tim@krieglstein.org> wrote:
> Hi Terry
>> Very appreciate your help. Indeed the python that is statically linked
>> into gdb needs other modules to run correctly. I now worked around
>> this issue by following steps:
>>
>> 1). build and install python 2.7 in dynamic way (produced the
>> libpython2.7.so instead of libpython2.7.a). This python is installed
>> to my own path instead of system path.
>> 2). unset the variable PYTHONHOME and then export
>> PYTHONHOME=MY-OWN-PATH:/usr, then configure, build and install gdb.
>> 3). now copy the gdb to other machine, everything works fine. The only
>> requirement is user will need to install libpython2.7 in their
>> machine.
>>
>> I admit that I have to make a compromise here. I am delivering gdb to
>> my customer and my expectation is that they can use my gdb with python
>> support no matter there is python in their system and no matter the
>> version of their installed python. After a lot of attempts, I think I
>> can't reach my expectation. I guess I have to live with my above
>> workaround.
> Its good you found a workable solution.
>
> I think i have seen your name on the
> https://launchpad.net/gcc-arm-embedded? Is your work on this related? It would
> be really nice to have a python enabled gdb in this toolchain.
>
> I am working on the baremetal plugin for qtcreator. With 3.1, qtcreator has a
> dependecy on a python enabled gdb. It would be really great if there would be
> a ready to use toolchain for this to use for embedded development with
> qtcreator.
>
> Best regards
> Tim
You are right. It's me. Hopefully we will enable this feature in
upcoming 4.9 based release.
BR,
Terry
next prev parent reply other threads:[~2014-06-25 9:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-21 3:01 Terry Guo
2014-06-23 13:49 ` Tim Sander
2014-06-23 15:48 ` Paul_Koning
2014-06-25 1:47 ` Terry Guo
2014-06-25 8:32 ` OT: " Tim Sander
2014-06-25 9:00 ` Terry Guo [this message]
2014-06-25 14:37 ` Joel Brobecker
2014-06-25 14:58 ` Hector Oron
2014-06-25 15:17 ` Joel Brobecker
2014-06-25 15:29 ` Hector Oron
2014-07-01 17:00 ` Tom Tromey
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='CAGbRaL65KDHL4Ab2x=TMcd0=M_RDtFL70Xyt_NMOWG1WydF4gw@mail.gmail.com' \
--to=flameroc@gmail.com \
--cc=gdb@sourceware.org \
--cc=tim@krieglstein.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