From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: 7.2 branch, configure problem, --with-python
Date: Tue, 27 Jul 2010 15:30:00 -0000 [thread overview]
Message-ID: <1280244591.2661.104.camel@hactar> (raw)
In-Reply-To: <4C4E1E0F.80309@vmware.com>
On Mon, 2010-07-26 at 16:45 -0700, Michael Snyder wrote:
> Hey folks, I'm having a problem attempting to build the release branch
> on a 32 bit RHEL5 system. I've used "--with-python=xyz" to point to a
> local install directory, but configure tells me it wasn't found.
>
> The exact same configuration worked fine in version 7.1.
>
> This is my configure command:
> CFLAGS=-g \
> LDFLAGS="-Wl,-R/build/toolchain/lin32/ncurses-5.5/lib
> -Wl,-R/build/toolchain/lin32/expat-1.95.8/lib
> -Wl,-R/build/toolchain/lin32/python-2.5/lib
> -Wl,-R/build/toolchain/lin32/zlib-1.2.3-3/lib \
> $(srcdir)/configure --with-python=/build/toolchain/lin32/python-2.5
>
> ... and this is the error message:
>
> checking for python2.5... no
> configure: error: no usable python found at
> /build/toolchain/lin32/python-2.5
> make[1]: *** [configure-gdb] Error 1
You're getting lots of "undefined reference to `__ctype_b'" errors when
statically linking with libpython2.5.a. I've never seen such error
myself, but it looks like that it is related to using old versions of
glibc (like version 2.3 or so). E.g., see:
http://lists.debian.org/debian-glibc/2002/10/msg00340.html
http://lists.debian.org/debian-glibc/2002/10/msg00093.html
configure is trying to compile a trivial Python application using:
gcc -o conftest -g -DVMWARE_VMKGDB
-I/build/toolchain/lin32/python-2.5/include
-I/build/toolchain/lin32/python-2.5/include
-Wl,-R/build/toolchain/lin32/ncurses-5.5/lib
-Wl,-R/build/toolchain/lin32/expat-1.95.8/lib
-Wl,-R/build/toolchain/lin32/python-2.5/lib
-Wl,-R/build/toolchain/lin32/zlib-1.2.3-3/lib conftest.c -lncurses -lz
-lm -L/build/toolchain/lin32/python-2.5/lib/python2.5/config
-lpthread -ldl -lutil -lm -lpython2.5 >&5
Which (apart from the -Wl,-R options) look harmless to me.
My initial impression is that there's something fishy with your
libpython2.5.a. I don't know why GDB 7.1 and GDB 7.2 would differ here.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2010-07-27 15:30 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 23:45 Michael Snyder
2010-07-27 15:30 ` Thiago Jung Bauermann [this message]
2010-07-27 17:17 ` Michael Snyder
2010-07-27 17:25 ` Jan Kratochvil
2010-07-28 0:30 ` Michael Snyder
2010-07-28 16:15 ` Tom Tromey
2010-07-28 16:56 ` Michael Snyder
2010-07-28 17:20 ` Joel Brobecker
2010-07-28 17:27 ` Michael Snyder
2010-07-28 17:37 ` Joel Brobecker
2010-07-28 17:59 ` Michael Snyder
2010-07-28 18:08 ` Joel Brobecker
2010-07-28 18:10 ` Michael Snyder
2010-07-28 18:15 ` Michael Snyder
2010-07-28 19:59 ` Michael Snyder
2010-07-28 21:32 ` Joel Brobecker
2010-07-28 18:19 ` Joel Brobecker
2010-07-28 18:23 ` Michael Snyder
2010-07-28 18:27 ` Joel Brobecker
2010-07-28 19:58 ` Michael Snyder
2010-07-28 20:02 ` Michael Snyder
2010-07-28 20:07 ` Michael Snyder
2010-07-28 20:21 ` Michael Snyder
2010-07-28 21:36 ` Joel Brobecker
2010-07-28 22:56 ` Michael Snyder
2010-07-29 15:28 ` Joel Brobecker
2010-07-29 17:37 ` Michael Snyder
2010-07-29 17:52 ` Michael Snyder
2010-07-29 18:41 ` Joel Brobecker
2010-07-29 18:49 ` Michael Snyder
2010-07-29 19:05 ` Joel Brobecker
2010-07-29 19:31 ` Michael Snyder
2010-07-29 21:32 ` Joel Brobecker
2010-07-29 21:45 ` Michael Snyder
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=1280244591.2661.104.camel@hactar \
--to=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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