[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: python-version.patch (Was: Bug in AM_PATH_PYTHON ?)

From: Akim Demaille
Subject: Re: python-version.patch (Was: Bug in AM_PATH_PYTHON ?)
Date: 06 Dec 2001 14:54:30 +0100
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Civil Service)

| >>> "Patrick" == Patrick Guio <address@hidden> writes:
| [...]
|  Patrick> AM_PATH_PYTHON(2)
| [...]
|  Patrick> I am running RH7.2 and have several python
|  Patrick> versions. The default "python" is version 1.5 but
|  Patrick> there are in addition python2 and python2.1 all of
|  Patrick> them coming from rpm's.  The problem is that configure
|  Patrick> does not check all the possibilities as it should do:
| [...]
|  Patrick> checking for python... /usr/bin/python
|  Patrick> checking if Python version >= 2... configure: error: too old
| [...]
|  Patrick> Another comment is that maybe the command python2
|  Patrick> could be tried since some rpms contain the python2
|  Patrick> command.
| The following patch should fix this.
| Akim, I'm almost certain I should not call _AC_EVAL (see the
| last line of the patch) from an Automake macro, but I don't know
| what I should use instead.  All I want is too log the each run
| of python and capture any error message to ease debugging.  I
| don't need the command to be eval'ed.  Is there a public macro
| for this?

Unfortunately, nope :(  I still didn't really make my mind wrt this
issue.   And I don't have much time to devote to Autoconf currently.

If I were you, I would fetch it from Autoconf, and paste it into
Automake as AM_EVAL_LOG or something.  Try to remain independent until
Autoconf made up its mind.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]