Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
	       "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: FYI: update for Python 2.7
Date: Tue, 27 Jul 2010 16:10:00 -0000	[thread overview]
Message-ID: <m3vd80rjml.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4C4E07F7.4030409@vmware.com> (Michael Snyder's message of "Mon,	26 Jul 2010 15:11:03 -0700")

>>>>> "Michael" == Michael Snyder <msnyder@vmware.com> writes:

Michael> Sorry, --with-python=/build/toolchain/lin32/python-2.6

Michael> Which is of course a local install location.

Try --with-python=/build/toolchain/lin32/python-2.6/bin/python.
I don't think my 2.7 patch changed this, it was an earlier change.

From gdb/configure.ac:

dnl There are several different values for --with-python:
[...]
dnl /path/to/python/exec-prefix -
dnl        Use the python located in this directory.
dnl        If /path/to/python/exec-prefix/bin/python exists, use it to find
dnl        the compilation parameters.  Otherwise use
dnl        -I/path/to/python/exec-prefix/include,
dnl        -L/path/to/python/exec-prefix/lib.
dnl        Python 2.6, 2.5, and then 2.4 are tried in turn.
dnl        NOTE: This case is historical.  It is what was done for 7.0/7.1
dnl        but is deprecated.
dnl /path/to/python/executable -
dnl        Run python-config.py with this version of python to fetch the
dnl        compilation parameters.

Tom


  reply	other threads:[~2010-07-27 16:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 18:23 Tom Tromey
2010-07-26 21:28 ` Michael Snyder
2010-07-26 21:38   ` Mike Frysinger
2010-07-26 22:11     ` Michael Snyder
2010-07-27 16:10       ` Tom Tromey [this message]
2010-07-28 17:06         ` Michael Snyder
2010-07-29 21:04           ` Tom Tromey
2010-07-30  0:03             ` Doug Evans
2010-07-30 15:59               ` Tom Tromey

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=m3vd80rjml.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=vapier@gentoo.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