bug-bison
[Top][All Lists]
Advanced

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

Re: Test 52 failure on AIX, HP-UX, Solaris


From: Joel E. Denny
Subject: Re: Test 52 failure on AIX, HP-UX, Solaris
Date: Tue, 2 Feb 2010 00:42:18 -0500 (EST)
User-agent: Alpine 1.00 (DEB 882 2007-12-20)

On Mon, 1 Feb 2010, Albert Chin wrote:

> On Mon, Feb 01, 2010 at 06:56:03PM -0500, Joel E. Denny wrote:
> > On Mon, 1 Feb 2010, Albert Chin wrote:
> > 
> > > Test 52 fails on AIX, HP-UX, and Solaris:
> > > 52. output.at:159: testing ...
> > > ./output.at:159: VALGRIND_OPTS="$VALGRIND_OPTS --leak-check=summary 
> > > --show-reachable=no"; export VALGRIND_OPTS; bison -o foo.y foo.y
> > > 2c2,3
> > > < 
> > > ---
> > > > /opt/TWWfsw/m414/bin/gm4:/opt/build/bison-2.4.1a/data/yacc.c:694: 
> > > > ERROR: copying inserted file: Broken pipe
> > > > /opt/TWWfsw/m414/bin/gm4: write error
> > > 52. output.at:159: 52. Conflicting output files:  -o foo.y 
> > > (output.at:159): FAILED (output.at:159)
> > > 
> > > We're seeing the same failure on AIX and HP-UX.
> > 
> > I'm pretty sure this means your m4 is broken.  Please confirm that you're 
> > running at least GNU M4 1.4.6.
> 
> We're running 1.4.12.

You're saying that /opt/TWWfsw/m414/bin/gm4, which is mentioned in the 
error message, is GNU M4 1.4.12?

I should point out that M4 in your environment would cause Bison to use a 
different m4 than the one discovered by configure.

Do any other test cases fail?  Attaching a complete tests/testsuite.log 
and config.log might help us debug this.




reply via email to

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