issue about building windows version of gdb with python support

[Tom Tromey]

>>>>> ">" == Asm gmail <asmwarrior@gmail.com> writes:

>> Today, I have build a gdb.exe with python support under windows(i'm
>> using TDMMinGW 4.5 dw2 version, I use the latest gdb snapshot 7.1.5
>> 20100613, python 2.6.5).
[...]
>> E:\XXXX\python this is the root folder.
>> Then E:\XXXX\python\include, this is the header directory.
>> Then, the lib foldee was: E:\XXXX\python\libs        (please note that
>> the path name is"libs" not lib.)

Hmm, I would have thought that the python-config.py stuff (in
gdb/python/) would do the right thing here.

What is the output on your machine when you run that with --ldflags?
I'm wondering if configure is somehow falling through to the old code,
or if Python itself is somehow misconfigured, or if it is an upstream
Python bug.

Even if it is a Python bug, maybe we can work around it somehow.

Tom