Albert Chin | 1 Feb 17:21

Re: Building bison 2.4.1 in Solaris 8

On Fri, Jan 22, 2010 at 05:45:53PM +0800, Edwin.Joseph-Ortile <at> ubs.com wrote:
> It seems like there is a bug in building bison 2.4.1 in Solaris 8. My
> bison config keeps on failing with the error below:
> 
> Config keeps on failing with the error below:
> 
> config.status: creating etc/bench.pl
> 
> nawk: input record `      print $out "1+...' too long
> 
>  input record number 122
> 
>  source line number 397
> 
> config.status: error: could not create etc/bench.pl
> 
> make: Fatal error: No arguments to build
> 
> Not sure if someone else had encountered this. But in case, could
> someone explain why the error was encountered and how to resolve it
> perhaps?

If you have GNU awk, gawk, make sure it's first in $PATH and
re-configure/rebuild.

--

-- 
albert chin (china <at> thewrittenword.com)

Albert Chin | 1 Feb 17:52

2.4.1a testsuite failures on Solaris 2.7

A few of the tests fail on Solaris 2.7 because libbison.a is not linked
in:
118. calc.at:568: testing ...
./calc.at:568: bison -o calc.c calc.y
./calc.at:568: $CC $CFLAGS $CPPFLAGS $LDFLAGS -o calc calc.c $LIBS
stderr:
Undefined                       first referenced
 symbol                             in file
rpl_fopen                           calc.o
ld: fatal: Symbol referencing errors. No output written to calc
stdout:
./calc.at:568: exit code was 1, expected 0
118. calc.at:568: 118. Calculator  (calc.at:568): FAILED (calc.at:568)

How do I modify the testsuite to link in ../lib/libbison.a?

--

-- 
albert chin (china <at> thewrittenword.com)

Joel E. Denny | 1 Feb 18:54
Favicon

Re: 2.4.1a testsuite failures on Solaris 2.7

On Mon, 1 Feb 2010, Albert Chin wrote:

> A few of the tests fail on Solaris 2.7 because libbison.a is not linked
> in:
> 118. calc.at:568: testing ...
> ./calc.at:568: bison -o calc.c calc.y
> ./calc.at:568: $CC $CFLAGS $CPPFLAGS $LDFLAGS -o calc calc.c $LIBS
> stderr:
> Undefined                       first referenced
>  symbol                             in file
> rpl_fopen                           calc.o
> ld: fatal: Symbol referencing errors. No output written to calc
> stdout:
> ./calc.at:568: exit code was 1, expected 0
> 118. calc.at:568: 118. Calculator  (calc.at:568): FAILED (calc.at:568)
> 
> How do I modify the testsuite to link in ../lib/libbison.a?

Thanks for the report.  In tests/atlocal, please try adding

  $abs_top_builddir/lib/libbison.a

to the value of LIBS.

Albert Chin | 1 Feb 21:06

Test 52 failure on AIX, HP-UX, Solaris

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.

--

-- 
albert chin (china <at> thewrittenword.com)

Joel E. Denny | 1 Feb 23:59
Favicon

Re: 2.4.1a testsuite failures on Solaris 2.7

On Mon, 1 Feb 2010, Albert Chin wrote:

> > Thanks for the report.  In tests/atlocal, please try adding
> > 
> >   $abs_top_builddir/lib/libbison.a
> > 
> > to the value of LIBS.
> 
> Thanks. That worked.

Thanks for confirming.

I pushed the following to branch-2.4.2.  A previous patch already handled 
this on branch-2.5 and master where the problem affected more platforms.

>From d093cf8cbd50c8fa888640b8487e3f517063aa28 Mon Sep 17 00:00:00 2001
From: Joel E. Denny <jdenny <at> clemson.edu>
Date: Mon, 1 Feb 2010 15:54:41 -0500
Subject: [PATCH] tests: link lib/libbison.a for gnulib.

This solves a problem on Solaris 2.7 where the testsuite needs
at least gnulib's rpl_fopen.  Reported by Albert Chin at
<http://lists.gnu.org/archive/html/bug-bison/2010-02/msg00001.html>.
* NEWS (2.4.2): Document.
* tests/atlocal.in (LIBS): As for LDADD in src/Makefile.am, add
lib/libbison.a.
---
 ChangeLog        |   10 ++++++++++
 NEWS             |    3 +++
 tests/atlocal.in |    2 +-
(Continue reading)

Joel E. Denny | 2 Feb 00:56
Favicon

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

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.

Albert Chin | 2 Feb 06:27

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

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.

--

-- 
albert chin (china <at> thewrittenword.com)

Joel E. Denny | 2 Feb 06:42
Favicon

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

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.

(Continue reading)

Joel E. Denny | 2 Feb 07:19
Favicon

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

On Tue, 2 Feb 2010, Joel E. Denny wrote:

> 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 
(Continue reading)


Gmane