[Top][All Lists]

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

Re: now getting a build error with coreutils-cvs (Re: coreutils-6.2: var

From: Jim Meyering
Subject: Re: now getting a build error with coreutils-cvs (Re: coreutils-6.2: various runtime problems on Darwin-8.7.0 HFS+ (including attachment this time))
Date: Wed, 27 Sep 2006 00:47:51 +0200

<address@hidden> wrote:

> On 2006-09-25 17:25:01 -0500, <address@hidden> said:
>> I will pull coreutils and gnulib from CVS also and report back.
> Okay I got a fresh clean copy of coreutils+gnulib, ran ./bootstrap,
> complained only a tiny bit about the hu language (smth about 2 or more
> suffixes for this language? I didn't save the output), but otherwise a

harmless.  you can ignore warnings about bad .po files.

> good run.  (Some months ago I did get autoconf-2.60 installed into both
> /usr and /usr/local [never know which is going to be used ;) ].)
> Ran
> ./configure \
> --with-libiconv-prefix=/usr/local \
> --with-libintl-prefix=/usr/local
> (latest stable built & installed of all those).
> Ran make -w and promptly got a bison error:
> [...]
> bison -y   getdate.y
> getdate.y:206: unrecognized: %parse_param
> getdate.y:206:    Skipping to next %
> getdate.y:207: unrecognized: %lex_param
> getdate.y:207:    Skipping to next %
> make[1]: *** [getdate.c] Error 1
> make[1]: Leaving directory
> `/Volumes/MaxFire3/Projects/coreutils_cvs/coreutils/lib'
> make: *** [all-recursive] Error 1
> make: Leaving directory `/Volumes/MaxFire3/Projects/coreutils_cvs/coreutils'
> $ _

Probably because you're not using a new enough version of bison.

> This didn't happen with the 6.2 tarball from the GNU FTP alpha repo or
> with 5.97 as recently as yesterday (so I know Tiger's bison didn't get
> changed ;) shows as GNU bison version 1.28) but we didn't need to run
> ./bootstrap on those non-CVS tarballs (or did we?).


reply via email to

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