Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
	 "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: FYI: update for Python 2.7
Date: Wed, 28 Jul 2010 17:06:00 -0000	[thread overview]
Message-ID: <4C506398.6090901@vmware.com> (raw)
In-Reply-To: <m3vd80rjml.fsf@fleche.redhat.com>

I'm no expert in this stuff, but don't we need a new 2.7 entry in
this region of configure.ac?

   if test "${have_python_config}" = yes; then
     python_version=`echo " ${python_libs} " \
                          | sed -e 's,^.* 
-l\(python[[0-9]]*[[.]][[0-9]]*\) .*$,\
\1,'`
     case "${python_version}" in
     python*)
       AC_TRY_LIBPYTHON(${python_version}, have_libpython,
                        ${python_includes}, ${python_libs})
       ;;
     *)
       AC_MSG_ERROR([unable to determine python version from 
${python_libs}])
       ;;
     esac
   elif test "${have_python_config}" != failed; then
     if test "${have_libpython}" = no; then
       AC_TRY_LIBPYTHON(python2.6, have_libpython,
                        ${python_includes}, "${python_libs} -lpython2.6")
     fi
     if test ${have_libpython} = no; then
       AC_TRY_LIBPYTHON(python2.5, have_libpython,
                        ${python_includes}, "${python_libs} -lpython2.5")
     fi
     if test ${have_libpython} = no; then
       AC_TRY_LIBPYTHON(python2.4, have_libpython,
                        ${python_includes}, "${python_libs} -lpython2.4")
     fi
   fi


  reply	other threads:[~2010-07-28 17:06 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 [this message]
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=4C506398.6090901@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.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