From: Michel METZGER <michel.metzger@st.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Failed to compile GDB 7.2 with python support
Date: Wed, 29 Sep 2010 20:30:00 -0000 [thread overview]
Message-ID: <5B4CE209869C6A4797F5FAA0B348F0A0D9E83E2E6B@SAFEX1MAIL1.st.com> (raw)
Hi all,
I tried to compile GDB 7.2 with python support (2.6.6) under Linux and it fails during the configure phase.
Python was compile like with:
> ./configure --prefix=/tmp/python-2.6.6-install --enable-shared make
> make install
And GDB with
> ./configure --with-python=/tmp/python-2.6.6-install
> --prefix=/tmp/gdb-7.2-install make
It fails during the execution of gdb/configure with the following message:
-------------------------------------------------------------
[...]
checking whether to use python... /tmp/python-2.6.6-install/ checking for python2.6... no
configure: error: no usable python found at /tmp/python-2.6.6-install/
make[1]: *** [configure-gdb] Error 1
-------------------------------------------------------------
The gdb/config.log tells me that configure failed to compile a test program to set up python.
From what I understand, the faulty compilation command line is:
--------------------------------------------------------------
[...]
configure:10682: gcc -o conftest -g -O2 -I/tmp/python-2.6.6-install/include -I/tmp/python-2.6.6-install/include conftest.c -lncurses -lz -lm -lpthread -ldl -lutil -lm -lpython2.6 >&5
/usr/bin/ld: cannot find -lpython2.6
[...]
--------------------------------------------------------------
Apparently the -L/tmp/Python-2.6.6-install/lib is missing.
What am I doing wrong?
Best regards,
Michel Metzger.
next reply other threads:[~2010-09-29 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 20:30 Michel METZGER [this message]
2010-09-29 20:37 ` Joel Brobecker
[not found] ` <5B4CE209869C6A4797F5FAA0B348F0A0D9E83E2E74@SAFEX1MAIL1.st.com>
2010-09-30 4:14 ` Joel Brobecker
2010-09-30 20:07 ` Michel METZGER
2010-09-29 20:37 ` Mathew Yeates
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=5B4CE209869C6A4797F5FAA0B348F0A0D9E83E2E6B@SAFEX1MAIL1.st.com \
--to=michel.metzger@st.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