[prev in list] [next in list] [prev in thread] [next in thread]
List: autoconf-bug
Subject: Re: testsuite.log
From: Noah Misch <noah () cs ! caltech ! edu>
Date: 2005-07-17 4:50:32
Message-ID: 20050717045032.GD13529 () orchestra ! cs ! caltech ! edu
[Download RAW message or body]
On Thu, Jul 14, 2005 at 05:07:07PM -0500, tlvogl@rockwellcollins.com wrote:
> After configuring, making and trying to test autoconf 2.58 (using the same
> version of automake (1.9.2) as another project that required autoconf 2.58
> or greater...), I received the following testsuite.log file and a message
> with a request to send it to this email.
Please use Autoconf 2.59 instead. It will not affect your test suite results,
but it is definitely the better version.
> 2. tools.at:92: 2. Syntax of the Perl scripts (tools.at:92): FAILED (tools.at:104)
This is fixed in CVS as of 2003-12-29.
> 3. tools.at:118: testing ...
> tools.at:126: autom4te --language=m4sugar script.4s -o script
> tools.at:134: autom4te --language=m4sugar script.4s -o script
> stderr:
> script.4s:1: /bin/m4: Cannot open foo: No such file or directory
> autom4te: /bin/m4 failed with exit status: 1
> tools.at:134: exit code was 0, expected 1
> 3. tools.at:118: 3. autom4te cache (tools.at:118): FAILED (tools.at:134)
Weird. What is the output of `/bin/m4 --version'?
> 24. base.at:29: testing ...
> base.at:60: autoconf
> --- /dev/null Thu Jul 14 20:46:02 2005
> +++ /home/tlvogl/apps/autoconf-2.58/tests/testsuite.dir/at-stderr Thu Jul 14 \
> 14:48:39 2005 @@ -0,0 +1 @@
> +autom4te: cannot lock autom4te.cache/requests with mode 2 (perhaps you are running \
> make -j on a lame NFS client?): Invalid argument 24. base.at:29: 24. AC_REQUIRE: \
> topological sort (base.at:29): FAILED (base.at:60)
This causes most of the test failures. Why does your Perl flock(file, LOCK_EX)
return EINVAL on a file below the Autoconf build directory?
Thanks for the report.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic