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

[Michael Snyder <msnyder at vmware dot com>]

Joel Brobecker wrote:
> > I wonder why that changed.  Does your Python come with dynamic
> > libraries?  Did 7.1 choose those instead?  AFAIK we didn't intentionally
> > make any change to prefer static libraries -- I think that would be a
> > bad decision.
>
> Perhaps the linker is not finding the python shared library?
> I think it should.
>
> One thing we should be aware of is that it seems that the Python
> developers themselves made the static libpython the default, and users
> building python need to explicitly request the dynamic libpython for it
> to be built. Maybe python-config.py is skewed that way too (meaning,
> lack of testing with the dynamic version of libpython).

Ahhh... perhaps we're getting warm.

7.2 gdb/config.log links the conftest program with these args:

-L/build/toolchain/lin64/python-2.5/lib/python2.5/config ... -lpython2.5

Whereas the equivalent args in 7.1 config.log are these:

 -L/build/toolchain/lin64/python-2.5/lib -lpython2.5



Notice the -L directory is different.  The first one is where the
static library is stored (7.2), and the second (7.1) is where the
dynamic library is stored.

What I don't know is, who made this change.