Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paul Smith <psmith@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: GDB Development <gdb@sourceware.org>
Subject: Re: Running without Python
Date: Mon, 28 Oct 2013 21:17:00 -0000	[thread overview]
Message-ID: <1382995034.3496.81.camel@pdsdesk> (raw)
In-Reply-To: <87txg19kx9.fsf@fleche.redhat.com>

On Mon, 2013-10-28 at 14:53 -0600, Tom Tromey wrote:
> >>>>> "Paul" == Paul Smith <psmith@gnu.org> writes:
> 
> Paul> But, it pretty much just stops:
> Paul>   $ my-gdb
> Paul>   Could not find platform independent libraries <prefix>
> Paul>   Could not find platform dependent libraries <exec_prefix>
> Paul>   Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
> Paul>   ImportError: No module named site
> Paul>   $
> 
> Paul> Any thoughts about this?  I guess I need to build GDB twice, once with
> Paul> Python for those systems that can use it and once without for those
> Paul> systems that don't have it.  Is there any interest in making this work
> Paul> "better"?
> 
> This should be better in a more recent gdb.  Please try git master.
> We've made it so that if Python initialization fails, then gdb still
> works but disables all the Python functionality.

Is this in 7.6.1, or just master?

> However, we haven't done the dlopen thing.  It's been discussed but I
> think it is difficult to do sanely, and especially difficult to do in a
> way that handles differences between versions of libpython.

That's OK with me, actually, because I've linked python statically so I
don't have to worry about it.  It's just the support .py stuff that's
missing when I copy GDB around.

Cheers!


  reply	other threads:[~2013-10-28 21:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 20:43 Paul Smith
2013-10-28 20:53 ` Tom Tromey
2013-10-28 21:17   ` Paul Smith [this message]
2013-10-29  2:07     ` 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=1382995034.3496.81.camel@pdsdesk \
    --to=psmith@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=tromey@redhat.com \
    /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