[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
autoconf 2.65: AC_PROG_F77 code executed though in a test that is always
From: |
Vincent Lefevre |
Subject: |
autoconf 2.65: AC_PROG_F77 code executed though in a test that is always false |
Date: |
Fri, 5 Feb 2010 14:51:25 +0100 |
User-agent: |
Mutt/1.5.20-6038-vl-r30587 (2010-02-01) |
I'm forwarding this bug...
I can reproduce it under Mac OS X (with autoconf 2.65).
Note that this is a regression. On a Debian/stable (lenny) machine
with autoconf 2.61-8, there is no such problem.
On 2010-02-05 14:14:56 +0100, Vincent Lefevre wrote:
> Package: autoconf
> Version: 2.65-3
> Severity: normal
>
> In MPFR, we had in configure.in:
>
> if test -n "$variable_indefinie" ; then
> AC_PROG_CXX([g++])
> AC_PROG_F77([g77])
> AC_PROG_CXXCPP
> fi
>
> This doesn't seem to be forbidden according to the autoconf
> documentation. Even though the test
>
> test -n "$variable_indefinie"
>
> is always false, the configure script checks for the GNU Fortran 77
> compiler.
>
> To reproduce the problem:
>
> $ svn checkout svn://scm.gforge.inria.fr/svn/mpfr/address@hidden mpfr
> $ cd mpfr
> $ autoreconf -i
> $ ./configure
>
> In the configure output:
>
> checking for g77... no
> checking for xlf... no
> checking for f77... no
> checking for frt... no
> checking for pgf77... no
> checking for cf77... no
> checking for fort77... no
> checking for fl32... no
> checking for af77... no
> checking for xlf90... no
> checking for f90... no
> checking for pgf90... no
> checking for pghpf... no
> checking for epcf90... no
> checking for gfortran... no
> checking for g95... no
> checking for xlf95... no
> checking for f95... no
> checking for fort... no
> checking for ifort... no
> checking for ifc... no
> checking for efc... no
> checking for pgf95... no
> checking for lf95... no
> checking for ftn... no
> checking whether we are using the GNU Fortran 77 compiler... no
>
> But if one replaces
>
> AC_PROG_F77([g77])
>
> by
>
> dnl AC_PROG_F77([g77])
>
> and rerun "autoreconf -i" and ./configure, the above lines are
> no longer there. There seems to be a similar problem for:
>
> AC_PROG_CXX([g++])
--
Vincent Lefèvre <address@hidden> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)
- autoconf 2.65: AC_PROG_F77 code executed though in a test that is always false,
Vincent Lefevre <=