From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Michael Snyder <msnyder@vmware.com>,
Mike Frysinger <vapier@gentoo.org>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: FYI: update for Python 2.7
Date: Fri, 30 Jul 2010 15:59:00 -0000 [thread overview]
Message-ID: <m3wrsd6jvz.fsf@fleche.redhat.com> (raw)
In-Reply-To: <AANLkTikxn4nALQa0d7q9vD2iaWCy06nOhmfko6s-AMnF@mail.gmail.com> (Doug Evans's message of "Thu, 29 Jul 2010 17:03:15 -0700")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> I'm happy to do it.
Thanks for the offer, but I went ahead and did it this morning.
Here is what I am checking in.
I am putting it on the 7.2 branch as well.
Tom
2010-07-30 Tom Tromey <tromey@redhat.com>
* configure: Rebuild.
* configure.ac: Add missing case for Python 2.7.
Index: configure.ac
===================================================================
RCS file: /cvs/src/src/gdb/configure.ac,v
retrieving revision 1.127
diff -u -r1.127 configure.ac
--- configure.ac 28 Jul 2010 23:24:57 -0000 1.127
+++ configure.ac 30 Jul 2010 15:58:03 -0000
@@ -622,7 +622,7 @@
dnl yes - Include python support, error if it's missing.
dnl If we find python in $PATH, use it to fetch configure options,
dnl otherwise assume the compiler can find it with no help from us.
-dnl Python 2.6, 2.5, and then 2.4 are tried in turn.
+dnl Python 2.7, 2.6, 2.5, and then 2.4 are tried in turn.
dnl auto - Same as "yes", but if python is missing from the system,
dnl fall back to "no".
dnl /path/to/python/exec-prefix -
@@ -631,7 +631,7 @@
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 Python 2.7, 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 -
@@ -780,6 +780,10 @@
esac
elif test "${have_python_config}" != failed; then
if test "${have_libpython}" = no; then
+ AC_TRY_LIBPYTHON(python2.7, have_libpython,
+ ${python_includes}, "${python_libs} -lpython2.7")
+ fi
+ if test "${have_libpython}" = no; then
AC_TRY_LIBPYTHON(python2.6, have_libpython,
${python_includes}, "${python_libs} -lpython2.6")
fi
prev parent reply other threads:[~2010-07-30 15:59 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
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 [this message]
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=m3wrsd6jvz.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.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