[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gnubg] gnubg-020610.tar.gz - bison problems are back
From: |
Jim Segrave |
Subject: |
Re: [Bug-gnubg] gnubg-020610.tar.gz - bison problems are back |
Date: |
Tue, 11 Jun 2002 18:22:04 +0200 |
User-agent: |
Mutt/1.2.5i |
On Tue 11 Jun 2002 (12:11 -0400), Gary Wong wrote:
> On Tue, Jun 11, 2002 at 05:00:59PM +0200, Jim Segrave wrote:
> > Under FreeBSD 4.6 Release Candidate, the snapshot from 10 June 2002
> > does not build with bison 1.34a, but does with bison 1.30l
>
> Thanks for the bug report. I have checked in a patch to the repository
> which should show up in snapshots dated 020611 and later.
>
> > (and the sed expression on line 5995 of configure is still looking for
> > a version number from bison surrounded by whitespace:
> >
> > ac_prog_version=`$INTLBISON --version 2>&1 | sed -n's/^.*GNU Bison .*
> > \([0-9]*\.[0-9.]*\).*$/\1/p'`
> >
> > Should be:
> > ac_prog_version=`$INTLBISON --version 2>&1 | sed -n's/^.*GNU
> > Bison.*\([0-\9]*\.[0-9.]*\).*$/\1/p'`
> >
> > (Fixing this does not fix the problem however)
>
> That part of the configure script is actually gettext code. It has no effect
> unless the gettext source is modified, so it is safe to ignore for gnubg
> purposes. It has been fixed in gettext 0.11.2.
Ok - I didn't know that. I only noticed it when I started looking to
see why gnubg had become 'bison version sensitive'.
--
Jim Segrave address@hidden