From: Joel Brobecker <brobecker@adacore.com>
To: Michel METZGER <michel.metzger@st.com>
Cc: gdb@sourceware.org
Subject: Re: Failed to compile GDB 7.2 with python support
Date: Thu, 30 Sep 2010 04:14:00 -0000 [thread overview]
Message-ID: <20100930041438.GA2988@adacore.com> (raw)
In-Reply-To: <5B4CE209869C6A4797F5FAA0B348F0A0D9E83E2E74@SAFEX1MAIL1.st.com>
[added gdb@sourceware.org back so that everyone can follow the
discussion and any suggestion that might emerge]
> It prints
>
> -lpthread -ldl -lutil -lm -lpython2.6
It's all coming back to me, now. I was thinking of a discussion
we had with MichaelS, but in fact, it was something I already
found earlier:
http://www.sourceware.org/ml/gdb-patches/2010-07/msg00168.html
http://www.sourceware.org/ml/gdb-patches/2010-08/msg00047.html
(you are facing issue #1)
You're facing that problem because you built python with --enable-shared.
The problem is indeed in the python-config.py script, which we copied
from the Python sources. And the bad news is that fixing it is far
from trivial - and it gets worse when one starts considering MacOS
and Windows.
Unless you are interested in hacking that script to make it work,
I suspect the simplest is to add the -L yourself (through LDFLAGS).
Or hack the python-config.py script to add it for you. Whichever
is simplest in your case.
--
Joel
next prev parent reply other threads:[~2010-09-30 4:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 20:30 Michel METZGER
2010-09-29 20:37 ` Mathew Yeates
2010-09-29 20:37 ` Joel Brobecker
[not found] ` <5B4CE209869C6A4797F5FAA0B348F0A0D9E83E2E74@SAFEX1MAIL1.st.com>
2010-09-30 4:14 ` Joel Brobecker [this message]
2010-09-30 20:07 ` Michel METZGER
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=20100930041438.GA2988@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=michel.metzger@st.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