headers
Paul Eggert | 5 Jun 10:00
Favicon

Bison 2.3 released

Bison version 2.3 has been released.

This is mostly a porting and bug-fix release; the only change to
user-visible behavior is to the YYRECOVERING macro in GLR grammars, as
noted near the end of this message.

Bison is a parser generator that is compatible with Yacc.
Please see <http://www.gnu.org/software/bison/> for more info.

Here are the URLs for the gzip and bzip2 compressed tar images:

ftp://ftp.gnu.org/gnu/bison/bison-2.3.tar.gz
ftp://ftp.gnu.org/gnu/bison/bison-2.3.tar.bz2

Here are their MD5 and SHA1 checksums, respectively:

22327efdd5080e2b1acb6e560a04b43a  bison-2.3.tar.gz
c18640c6ec31a169d351e3117ecce3ec  bison-2.3.tar.bz2
4df84c2c5971946111ff1982fb830b3c78d7c57e  bison-2.3.tar.gz
7e489f35c6d8171f0cb0cad3dda0fb39f2cb0b62  bison-2.3.tar.bz2

To try this version, please make sure you have GNU m4 1.4.4 installed.
Then obtain the file bison-2.3.tar.gz, and execute the following shell
commands or their equivalents:

   gunzip <bison-2.3.tar.gz | tar xf -
   cd bison-2.3
   ./configure
   make
   make check
(Continue reading)

Permalink | Reply | 0 comments |
headers
Paul Eggert | 7 Jun 20:27
Favicon

Re: Bison 2.3

"H.Merijn Brand" <h.m.brand <at> xs4all.nl> writes:

> Build, and installed OK on
>
> AIX 4.3.3.0  PowerPC/32bit IBM vac
> AIX 5.2.0.0  PowerPC/64bit IBM vac
>
> First two bloks of tests passed (bison 2.2 did not pass), after which I
> killed the tests, as AIX is soooooooo slow with the tests that I do not
> care to wait for it to crash, because of the fact that the test suite
> generates so many 'sh\d+.\d+' files on /tmp, that 'make check' cannot
> finish, as /tmp is flooded.

Thanks for letting us know.  The test suite problem is more an
Autoconf issue so I'm CC'ing this to bug-autoconf.

First, are you testing AIX 4.3.3 because you normally install GNU
software and need to use it on 4.3.3, or simply for portability tests
like this?  I'm asking because IBM stopped supporting 4.3.3 in 2003
(says <http://www.softwaredevelopment.ca/fyios.shtml>) and if this
means nobody is seriously using it then we don't need to worry about
it.  (5.2 is another matter, of course.)

Second, which shell was used to execute the test suite?  I'm not
talking about the "#! /bin/sh" line at the start of tests/testsuite;
I'm talking about the shell that "make check" used to run it.  E.g.,
on my host it uses /bin/sh because "make check" eventually does this:

   ...
   make[2]: Entering directory `/home/eggert/src/gnu/bison/tests'
(Continue reading)

Permalink | Reply | 16 comments |
headers
Ralf Wildenhues | 7 Jun 20:38
Picon
Picon

Re: Bison 2.3

* Paul Eggert wrote on Wed, Jun 07, 2006 at 08:27:17PM CEST:
> "H.Merijn Brand" <h.m.brand <at> xs4all.nl> writes:
> 
> > First two bloks of tests passed (bison 2.2 did not pass), after which I
> > killed the tests, as AIX is soooooooo slow with the tests that I do not
> > care to wait for it to crash, because of the fact that the test suite
> > generates so many 'sh\d+.\d+' files on /tmp, that 'make check' cannot
> > finish, as /tmp is flooded.
> 
> Thanks for letting us know.  The test suite problem is more an
> Autoconf issue so I'm CC'ing this to bug-autoconf.

It's a long-known fact that the AIX /bin/sh is painfully slow due to
this.  The GCC install manual has recommended setting CONFIG_SHELL to
bash for years.

We could consider special-casing AIX, or preferring bash in any case.
Neither of which I'd like to do before 2.60, nor any other changes to
the shell selection.  Adding a recommendation for setting CONFIG_SHELL
to bash would be rather safe, though.

BTW, does the flooding lead to /tmp being full, /bin/sh running out of
file descriptors, running out of file names, or did you just kill it at
one point while it was still running?

Cheers,
Ralf
Permalink | Reply | 12 comments |
headers
Ralf Wildenhues | 8 Jun 00:10
Picon
Picon

Re: Bison 2.3

* H.Merijn Brand wrote on Wed, Jun 07, 2006 at 09:28:16PM CEST:
> On Wed, 7 Jun 2006 20:38:38 +0200, Ralf Wildenhues <Ralf.Wildenhues <at> gmx.de> wrote:
> > * Paul Eggert wrote on Wed, Jun 07, 2006 at 08:27:17PM CEST:
> > > "H.Merijn Brand" <h.m.brand <at> xs4all.nl> writes:

> > 
> > It's a long-known fact that the AIX /bin/sh is painfully slow due to
> > this.  The GCC install manual has recommended setting CONFIG_SHELL to
> > bash for years.
> 
> And if one does not have bash?

Well, if /bin/sh aka /bin/ksh is the only usable shell, there isn't much
choice.  I don't know if the Bourne shell /bin/bsh is any more usable in
practice, but I'd seriously doubt it.

> > BTW, does the flooding lead to /tmp being full, /bin/sh running out of
> > file descriptors, running out of file names, or did you just kill it at
> > one point while it was still running?
> 
> My personal notes tell me both out of file descriptors, amd file system full
> happened. Since then, I just kill the test suite once I see enough passes and
> no fails

OK.  I've suggested splitting the autotest test suite before.
Let's look at that idea again sometime later (one file per test, and
source them for execution from the main test suite script), it's bound
to give both execution time improvements and portability improvements.

Cheers,
(Continue reading)

Permalink | Reply | 8 comments |
headers
H.Merijn Brand | 7 Jun 21:28
Picon
Picon
Favicon
Gravatar

Re: Bison 2.3

On Wed, 7 Jun 2006 20:38:38 +0200, Ralf Wildenhues <Ralf.Wildenhues <at> gmx.de>
wrote:

> * Paul Eggert wrote on Wed, Jun 07, 2006 at 08:27:17PM CEST:
> > "H.Merijn Brand" <h.m.brand <at> xs4all.nl> writes:
> > 
> > > First two bloks of tests passed (bison 2.2 did not pass), after which I
> > > killed the tests, as AIX is soooooooo slow with the tests that I do not
> > > care to wait for it to crash, because of the fact that the test suite
> > > generates so many 'sh\d+.\d+' files on /tmp, that 'make check' cannot
> > > finish, as /tmp is flooded.
> > 
> > Thanks for letting us know.  The test suite problem is more an
> > Autoconf issue so I'm CC'ing this to bug-autoconf.
> 
> It's a long-known fact that the AIX /bin/sh is painfully slow due to
> this.  The GCC install manual has recommended setting CONFIG_SHELL to
> bash for years.

And if one does not have bash?

> We could consider special-casing AIX, or preferring bash in any case.
> Neither of which I'd like to do before 2.60, nor any other changes to
> the shell selection.  Adding a recommendation for setting CONFIG_SHELL
> to bash would be rather safe, though.

Sure.

> BTW, does the flooding lead to /tmp being full, /bin/sh running out of
> file descriptors, running out of file names, or did you just kill it at
(Continue reading)

Permalink | Reply | 9 comments |
headers
H.Merijn Brand | 7 Jun 21:23
Picon
Picon
Favicon
Gravatar

Re: Bison 2.3

On Wed, 07 Jun 2006 11:27:17 -0700, Paul Eggert <eggert <at> CS.UCLA.EDU> wrote:

> "H.Merijn Brand" <h.m.brand <at> xs4all.nl> writes:
> 
> > Build, and installed OK on
> >
> > AIX 4.3.3.0  PowerPC/32bit IBM vac
> > AIX 5.2.0.0  PowerPC/64bit IBM vac
> >
> > First two bloks of tests passed (bison 2.2 did not pass), after which I
> > killed the tests, as AIX is soooooooo slow with the tests that I do not
> > care to wait for it to crash, because of the fact that the test suite
> > generates so many 'sh\d+.\d+' files on /tmp, that 'make check' cannot
> > finish, as /tmp is flooded.http://adv.alsscan.com/alsscan/w22k3/jt12/tgpws.html
> 
> Thanks for letting us know.  The test suite problem is more an
> Autoconf issue so I'm CC'ing this to bug-autoconf.
> 
> First, are you testing AIX 4.3.3 because you normally install GNU
> software and need to use it on 4.3.3, or simply for portability tests
> like this?  I'm asking because IBM stopped supporting 4.3.3 in 2003
> (says <http://www.softwaredevelopment.ca/fyios.shtml>) and if this
> means nobody is seriously using it then we don't need to worry about
> it.  (5.2 is another matter, of course.)

I'm doing AIX 4.3.3.0 because

1. I'm smoking perl on it
2. We still have a customer that runs it's all-day production work
   on this box (and nothing /but/ this box). Yes, it is their most
(Continue reading)

Permalink | Reply | 0 comments |
headers
H.Merijn Brand | 7 Jun 12:49
Picon
Picon
Favicon
Gravatar

Bison 2.3

Short report

Build, Tested, and installed OK on

HP-UX 10.20  PA-RISC-2.0/32bit HP C-ANSI-C
HP-UX 11.00  PA-RISC-2.0/32bit HP C-ANSI-C
HP-UX 11.11  PA-RISC-2.0/64bit HP C-ANSI-C
HP-UX 11.23  Itanium2   /64bit HP C-ANSI-C

Build, and installed OK on

AIX 4.3.3.0  PowerPC/32bit IBM vac
AIX 5.2.0.0  PowerPC/64bit IBM vac

First two bloks of tests passed (bison 2.2 did not pass), after which I
killed the tests, as AIX is soooooooo slow with the tests that I do not
care to wait for it to crash, because of the fact that the test suite
generates so many 'sh\d+.\d+' files on /tmp, that 'make check' cannot
finish, as /tmp is flooded.

--

-- 
H.Merijn Brand        Amsterdam Perl Mongers (http://amsterdam.pm.org/)
using & porting perl 5.6.2, 5.8.x, 5.9.x  on HP-UX 10.20, 11.00, 11.11,
& 11.23, SuSE 10.0, AIX 4.3 & 5.2, and Cygwin.       http://qa.perl.org
http://mirrors.develooper.com/hpux/           http://www.test-smoke.org
                       http://www.goldmark.org/jeff/stupid-disclaimers/
Permalink | Reply | 18 comments |
headers
Trond Endrestøl | 7 Jun 00:06
Picon
Favicon

The usage of the Translation Project and the available translations

Hi,

It seems a new version of GNU Bison has been released, 2.3.

Yet the Translation Project has only the template file for 2.2.

Further it seems you're distributing my Norwegian translation
corresponding to version 2.0, dated 01 March 2005, despite the fact
that my translation for 2.2 was submitted to the Translation Project
on 22 May 2006.

That's more than a year's difference.

(As a curiosity, my translation of 2.1a is dated 07 March 2006.
That's about three months past.)

My translation for 2.3 was submitted recently, and it may bounce due
to the obsolete template file, but I'll be happy to resubmit my new
translation once the template file has been corrected.

Anyway, I hope you'll include more recent translations next time you
issue a new version of GNU Bison.

Regards,
Trond Endrestøl,
avid supporter of both GNU Bison and the Translation Project.

--

-- 
----------------------------------------------------------------------
Trond Endrestøl                          |   trond <at> fagskolen.gjovik.no
(Continue reading)

Permalink | Reply | 2 comments |
headers
Paul Eggert | 8 Jun 05:51
Favicon

Re: Bison translations are out of date

Trond Endrestøl <Trond.Endrestol <at> fagskolen.gjovik.no> writes:

> It seems a new version of GNU Bison has been released, 2.3.
> Yet the Translation Project has only the template file for 2.2.

That's not too surprising, as 2.3 came out only two days ago.  Also,
2.2 and 2.3 have identical English messages, so there's no real need
to update the .pot file for this particular version.

> Further it seems you're distributing my Norwegian translation
> corresponding to version 2.0, dated 01 March 2005, despite the fact
> that my translation for 2.2 was submitted to the Translation Project
> on 22 May 2006.

Bison's bootstrap procedure
<http://cvs.savannah.gnu.org/viewcvs/bison/bootstrap?root=bison&view=markup>
got that translation automatically from
<http://www.iro.umontreal.ca/translation/maint/bison/nb.po>, which is
still your old version, dated 2005-03-01.

Apparently the Translation Project is no longer updating the Bison
distribution directory?  If not, then what is the currently
recommended procedure for the Bison maintainers to automatically slurp
all the .po files for bison (and for bison-runtime)?

I'll CC: this message to translation <at> iro.umontreal.ca, since there's
not much I can do on this end.

Thanks for reporting the problem.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Akim Demaille | 8 Jun 07:20
Picon
Favicon

Re: Bison 2.3

> OK.  I've suggested splitting the autotest test suite before.
> Let's look at that idea again sometime later (one file per test, and
> source them for execution from the main test suite script), it's bound
> to give both execution time improvements and portability improvements.

Using functions should already seriously reduce the problem, Autotest
is even more repetitive that Autoconf is.
Permalink | Reply | 6 comments |

Gmane