From: Chris Sutcliffe <ir0nh34d@gmail.com>
To: gdb@sourceware.org
Subject: Re: configure: error: no usable python found
Date: Thu, 04 Mar 2010 02:23:00 -0000 [thread overview]
Message-ID: <2bf229d31003031823t2825f09fu62340b70c22bdcba@mail.gmail.com> (raw)
In-Reply-To: <m34okx6xex.fsf@fleche.redhat.com>
> I don't know; I have never looked at it. If you could come up with a
> configure patch that works for Windows, without breaking Linux, that
> would be helpful. I can test it on Linux for you, if that would help.
I've hacked the configure script to allow for Python support under
Windows, but the source itself is also going to need some fixing up.
I'm working on making the configure script play a little nicer for
both Linux and Windows, but I'm a little stumped on how to make
somethings conditional. The code check itself is fairly straight
forward:
#include "${version}/Python.h"
becomes:
#ifdef WIN32
#include "Python.h"
#else
#include "${version}/Python.h"
#endif
what I'm unclear on is how to make (line 9470):
version=python2.6
conditional on Windows to be:
version=python26
and similarly (line 9456):
python_libs="-L${with_python}/lib"
to conditionally be:
python_libs="-L${with_python}/libs"
on Windows.
Any pointers here would be greatly appreciated.
Thank you,
Chris
--
Chris Sutcliffe
http://emergedesktop.org
http://www.google.com/profiles/ir0nh34d
next prev parent reply other threads:[~2010-03-04 2:23 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
2010-03-03 19:03 ` Tom Tromey
2010-03-04 2:23 ` Chris Sutcliffe [this message]
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=2bf229d31003031823t2825f09fu62340b70c22bdcba@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