Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tim Sander <tim@krieglstein.org>
To: gdb@sourceware.org, Terry Guo <flameroc@gmail.com>
Subject: Re: Is it possible to statically link python into gdb?
Date: Mon, 23 Jun 2014 13:49:00 -0000	[thread overview]
Message-ID: <56168225.tkKpPXRO26@dabox> (raw)
In-Reply-To: <CAGbRaL5PAaO-NHojLYfSOjZPsPajYGGb0e8FV2qr5g8OEJXqzQ@mail.gmail.com>

Hi Terry
> I am trying to build a gdb with python support which doesn't depend on
> system python at all. I can manage to build python into static library
> like libpython2.7.a, then I can see that this static library is linked
> into gdb. With command ldd, there is no libpython dependence in final
> gdb. So far all good. But when run this gdb on another machine, I ran
> into below errors and gdb can't be initiated:
> 
> Could not find platform independent libraries <prefix>
> Could not find platform dependent libraries <exec_prefix>
> Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
> 
> I am working on Ubuntu x86 machines with gdb from master branch and
> Python 2.7. Could some one please help me? Thanks in advance.
I don't know much about python but might it be that you need the *.py files 
of PYTHONHOME/lib nevertheless to get a running python interpreter?

Best regards
Tim



  reply	other threads:[~2014-06-23 13:49 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 [this message]
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
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=56168225.tkKpPXRO26@dabox \
    --to=tim@krieglstein.org \
    --cc=flameroc@gmail.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