This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: issue about building windows version of gdb with python support
- From: Tom Tromey <tromey at redhat dot com>
- To: asmwarrior <asmwarrior at gmail dot com>
- Cc: gdb at sourceware dot org
- Date: Wed, 16 Jun 2010 11:36:51 -0600
- Subject: Re: issue about building windows version of gdb with python support
- References: <4C162783.4010706@gmail.com>
- Reply-to: tromey at redhat dot com
>>>>> ">" == 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