From: Chris Sutcliffe <ir0nh34d@gmail.com>
To: gdb@sourceware.org
Subject: Re: configure: error: no usable python found
Date: Wed, 03 Mar 2010 16:54:00 -0000 [thread overview]
Message-ID: <2bf229d31003030854v7418caa8qd1cdaa2e0eef37c4@mail.gmail.com> (raw)
In-Reply-To: <m34okx9xqu.fsf@fleche.redhat.com>
> Tom> Could you also paste the command line?
> Chris> The full command line I used was:
>
> Sorry, I wasn't clear.
> I meant the command line used to compile the test program, from config.log.
configure:9438: checking whether to use python
configure:9440: result: /python
configure:9474: checking for python2.6
configure:9489: mingw32-gcc -o conftest.exe -g -O2
-D__USE_MINGW_ACCESS -I/python/include -Wl,--stack,8388608
conftest.c -lm -L/python/lib -lpython2.6 >&5
conftest.c:46:30: error: python2.6/Python.h: No such file or directory
configure:9489: $? = 1
So the include path supplied is correct, however the library path is
wrong, it should be /python/libs (not /python/lib).
| #include "python2.6/Python.h"
This is incorrect though, it should just be '#include "Python.h"'. Is
perhaps the win32 distribution of Python significantly different in
directory structure compared to the 'nix distribution directory
structure?
Chris
--
Chris Sutcliffe
http://emergedesktop.org
http://www.google.com/profiles/ir0nh34d
next prev parent reply other threads:[~2010-03-03 16:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 11:38 Anton Kunze
2010-03-03 11:54 ` Joel Brobecker
2010-03-03 12:54 ` Chris Sutcliffe
2010-03-03 16:06 ` Tom Tromey
2010-03-03 16:25 ` Chris Sutcliffe
2010-03-03 16:27 ` Tom Tromey
2010-03-03 16:54 ` Chris Sutcliffe [this message]
2010-03-03 19:03 ` Tom Tromey
2010-03-04 2:23 ` Chris Sutcliffe
2010-03-04 21:45 ` Tom Tromey
2010-03-03 12:11 ` Andreas Schwab
2010-03-03 13:32 ` Anton Kunze
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=2bf229d31003030854v7418caa8qd1cdaa2e0eef37c4@mail.gmail.com \
--to=ir0nh34d@gmail.com \
--cc=gdb@sourceware.org \
/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