Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Chris Sutcliffe <ir0nh34d@gmail.com>
To: gdb@sourceware.org
Subject: Re: configure: error: no usable python found
Date: Wed, 03 Mar 2010 12:54:00 -0000	[thread overview]
Message-ID: <2bf229d31003030453k302064caq29a75976637203ba@mail.gmail.com> (raw)
In-Reply-To: <20100303115437.GD15364@adacore.com>

On 3 March 2010 06:54, Joel Brobecker wrote:
>> checking whether to use python... /usr/lib/Python-2.6.4
>> checking for python2.6... no
>> checking for python2.5... no
>> checking for python2.4... no
>> configure: error: no usable python found at /usr/lib/Python-2.6.4
>
> I'd recommend that you check the gdb/config.log file.  Somewhere
> close to the end, before configure dumped its entire environment,
> you should see the compile check that was used to check for python2.6,
> and the error that caused configure discard to 2.6 python install.

I'm having a similar issue trying to build gdb for MinGW using MSYS
with Python support.  I have the official Python 2.6.4 windows version
installed at C:\Python26, which I have mounted at /python within my
MSYS shell.  I configured gdb with 'configure --with-python=/python'.
Looking at the config.log file I see:

| #include "python2.6/Python.h"
| int
| main ()
| {
| Py_Initialize ();
|   ;
|   return 0;
| }

Which is why it's failing, given that Python.h is in /python/include/.
 Is there a way to override where configure is looking for Python.h?

Thank you,

Chris

-- 
Chris Sutcliffe
http://emergedesktop.org
http://www.google.com/profiles/ir0nh34d


  reply	other threads:[~2010-03-03 12: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 [this message]
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
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=2bf229d31003030453k302064caq29a75976637203ba@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