This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: objc (current snapshot) doesn't compile
- To: Jeffrey A Law <law at cygnus dot com>
- Subject: Re: objc (current snapshot) doesn't compile
- From: "Rod m. Stewart" <stewart at nexus dot carleton dot ca>
- Date: Sun, 25 Apr 1999 15:55:24 -0400 (EDT)
- cc: Marc Espie <Marc dot Espie at liafa dot jussieu dot fr>, Marc Espie <espie at quatramaran dot ens dot fr>, bero at microsoft dot sucks dot eu dot org, egcs-bugs at egcs dot cygnus dot com
On Fri, 23 Apr 1999, Jeffrey A Law wrote:
> In message <19990422002250.A22743@liafa1.liafa.jussieu.fr>you write:
> > Looking at bison log, the only significant change between 1.25 and 1.27
> > is a re-numbering of tokens, so that they now start at 257 as advertized.
> >
> > So there are two basic possibilities: either objc-parse was the only parser
> > that was rebuilt, in which case it's quite normal it broke (since C/objc
> > parsing are VERY tightly linked), or egcs somehow came out to rely on that
> > bison bug...
> >
> > I don't have any machine in a decent state to check either conjecture
> > right away... Jeff, which version of bison is used these days ?
> My machine seems to have bison-1.25. I suspect that's probably what most
> of the Cygnus folks have.
>
> Hopefully we're just out of sync in the repo and not depending on any
> bug/feature of bison-1.25 that is not in bison-1.27.
Incidently, this now appears to fixed (Tue Apr 20 23:38:58 1999
gcc/Changelog entry). Well I can now build the latest egcs using
bison-1.27, no more crashes in objc.
I have other problems, but I'm willing to blame most of the them on my
build environment. And hopefully I can convince dejagnu to build on one
of my arm boxes this afternoon.
Thanks,
-Rms