From: Paul Smith <psmith@gnu.org>
To: GDB Development <gdb@sourceware.org>
Subject: Running without Python
Date: Mon, 28 Oct 2013 20:43:00 -0000 [thread overview]
Message-ID: <1382993004.3496.79.camel@pdsdesk> (raw)
I had a naive hope that if I built my own GDB (7.6) with Python support,
then I needed to copy it to another system to do some debugging (because
my code is compiled with GCC 4.8.1 and the other system doesn't have a
new-enough GDB to debug the new object file format) where that other
system didn't have an appropriate Python, that my GDB would still work.
Like, GDB would try to dlopen() the Python library, discover it wasn't
available, shrug, and continue on letting me debug using "classic"
commands with just some minor grumbling.
But, it pretty much just stops:
$ my-gdb
Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
ImportError: No module named site
$
Any thoughts about this? I guess I need to build GDB twice, once with
Python for those systems that can use it and once without for those
systems that don't have it. Is there any interest in making this work
"better"?
Cheers!
next reply other threads:[~2013-10-28 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 20:43 Paul Smith [this message]
2013-10-28 20:53 ` Tom Tromey
2013-10-28 21:17 ` Paul Smith
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=1382993004.3496.79.camel@pdsdesk \
--to=psmith@gnu.org \
--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