[Top][All Lists]

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

Re: bug with automake 1.6 and autoconf 2.53

From: Alexandre Duret-Lutz
Subject: Re: bug with automake 1.6 and autoconf 2.53
Date: Fri, 7 Jun 2002 20:21:47 +0200
User-agent: Mutt/1.3.28i

On Fri, Jun 07, 2002 at 07:38:31AM -0700, jeff deifik wrote:
> At 09:53 AM 6/7/2002 +0200, you wrote:
> >
> >What does
> >  /usr/ets/bin/m4 --version
> >prints?
> There is no m4 in that directory.

That explains it.  There was one the first time Autoconf was installed.

> Why is automake looking there, the one at /home/jdeifik/bin/m4
> is the first thing in my path.

Autoconf try to use the one it found when it was installed.

> I am reinstalling autoconf right now.
> I was able to run configure on automake without incident.
> I am compiling & running check now.
> Here are the results, with the passing tests omitted:
> FAIL: cond4.test
> FAIL: cond16.test
> FAIL: cond19.test

You can run the testsuite verbosely as follow:

  env TESTS='cond4.test cond16.test cond19.test' VERBOSE=x make -e check
The last time I have seen these failures [*], if was because the testsuite
was running on an NFS filesystem and the NFS server did not have its 
date synchronized with the NFS clients.  I wager this is your case too.

[*] http://sources.redhat.com/ml/bug-automake/2002/msg00618.html
Alexandre Duret-Lutz

reply via email to

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