From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2 2/3] configure.ac: add check for python 2.x version
Date: Tue, 15 Apr 2014 11:26:59 +0200 [thread overview]
Message-ID: <20140415092656.GA20567@omega> (raw)
In-Reply-To: <1397553565-1144-3-git-send-email-alex.aring@gmail.com>
Hi,
On Tue, Apr 15, 2014 at 11:19:24AM +0200, Alexander Aring wrote:
> Signed-off-by: Alexander Aring <alex.aring@gmail.com>
> ---
> configure.ac | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/configure.ac b/configure.ac
> index 2a97944..efc67ba 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -304,6 +304,18 @@ AC_ARG_WITH(python, AS_HELP_STRING([--with-python],[name of the python executabl
> AC_PATH_PROGS(PYTHON, python2.7 python2.6 python)
> AC_SUBST(PYTHON)
> ])
> +
> +dnl
> +dnl Check for python 2.x
> +dnl
> +AC_MSG_CHECKING([check for python major version])
> +PYTHON_MAJOR_VERSION=`$PYTHON -c "import sys; print(sys.version_info[[0]])" 2> /dev/null`
> +case "$PYTHON_MAJOR_VERSION" in
> +2) ;;
> +*) AC_MSG_ERROR([we need python version 2.x but found $PYTHON_MAJOR_VERSION.x]) ;;
> +esac
some little note here. I know we don't need a switch case here but it's
good to handle others python major versions in the future.
Then maybe python 4.x is incompatible with python 3.x like the current
situation with python 3.x and python 2.x
- Alex
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-04-15 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 9:19 [ptxdist] [PATCH v2 0/3] ptxdist: check for python 2.x and rename libusbx Alexander Aring
2014-04-15 9:19 ` [ptxdist] [PATCH v2 1/3] libusb: rename libusbx to libusb Alexander Aring
2014-04-15 9:19 ` [ptxdist] [PATCH v2 2/3] configure.ac: add check for python 2.x version Alexander Aring
2014-04-15 9:24 ` Uwe Kleine-König
2014-04-15 9:28 ` Alexander Aring
2014-04-15 9:26 ` Alexander Aring [this message]
2014-04-15 9:19 ` [ptxdist] [PATCH v2 3/3] configure.ac: check for python2 binary as well Alexander Aring
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=20140415092656.GA20567@omega \
--to=alex.aring@gmail.com \
--cc=ptxdist@pengutronix.de \
/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