[Top][All Lists]

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

Re: autoconf 2.49c AC_CACHE_CHECK failure

From: Nicolas Joly
Subject: Re: autoconf 2.49c AC_CACHE_CHECK failure
Date: Tue, 30 Jan 2001 18:12:48 +0100
User-agent: Mutt/1.2.4i

On Tue, Jan 30, 2001 at 02:59:17PM +0100, Akim Demaille wrote:
> >>>>> "Nicolas" == Nicolas Joly <address@hidden> writes:
> Nicolas> Why do we need both AT_CHECK and AT_CHECK_CONFIGURE calls
> Nicolas> here ?
> Nicolas> AT_CHECK_CONFIGURE([-q], 0, [])
> Right, more beautiful.  Will fix, thanks!

My proposal was to remove the second `AT_CHECK_CONFIGURE' call too,
which produce the failure (sorry if i was unclear). It runs a normal
configure generating the famous `loading site script ...' line.

Extracted for testsuite.log :

Testing suite for GNU Autoconf 2.49d
23. ./base.at:205: testing AC_CACHE_CHECK...
./base.at:212: autoconf --autoconf-dir .. -l $at_srcdir 
./base.at:213: top_srcdir=$top_srcdir ./configure -q
./base.at:215: top_srcdir=$top_srcdir ./configure 
> configure: loading site script /usr/local/share/config.site
./base.at:215: config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

Nicolas Joly

Informatique Scientifique
Institut Pasteur, Paris.

reply via email to

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