Re: 7.2 branch, configure problem, --with-python

[Michael Snyder <msnyder at vmware dot com>]

Joel Brobecker wrote:
> > Hmmm, what if you try configure --with-python=/usr?
> > That will approximate what I'm doing (only with me it's a
> > non-standard install location).
>
> I just rebuilt python-2.7 with --enable-shared and installed it at
> a non-standard location.  And then configured GDB as follow:

Wow, thanks for going to all that effort.

>     % CFLAGS='-g' ~/act/gdb-public/configure --with-python=/t.a/brobecke/python-2.7-shared
>
> And I still see GDB being linked against the python DSO:
>
>     % ldd gdb/gdb
>     libpython2.7.so.1.0 => /t.a/brobecke/python-2.7-shared/lib/libpython2.7.so.1.0 (0x00007f5effa5f000)

Grr, frustrating (for me...)

> For this to work, I did need my python-config.py patch, because
> the compilation command was missing a -L/path/to/python/dso, without
> which the configure check for libpython2.7 would fail.

Right.  I assume you worked out of HEAD?

> In order to understand what is going on, you will probably have to
> dig into your config.log file and see what the configure script is
> doing. I'm starting to think that your python install might be screwed
> or non-standard?

Well, it's screwed in that the static library is linked against an
older glibc, but other than that I think it's ok.  I have the dso at
xyz/python-2.6.1/lib and the static at 
xyz/python-2.6.1/lib/python2.6/config.

But the link command in config.log only points to the static location.
Even with your patch.  Even when I say --with-python=/usr.