Re: cvs server: conflicts found in gcc/c-parse.c

[Toon Moene <toon at moene dot indiv dot nluug dot nl>]

  In message <u9d8g8ld0i.fsf@yorick.cygnus.com> Jason Merrill wrote:

  > BTW, how would people feel about removing some of the generated  
files from
  > CVS?  I think it's reasonable to expect people using the CVS  
repository to
  > have bison installed.

and Jeff replied

> I'd vote yes for this :-)

Before I'd give it my vote, I first checked whether bison (and  
flex) build on my m68k-next-nextstep3; a close finish: flex built  
without problems, but I had to use NEXTSTEP's make to build bison,  
as GNU make-3.75 choked on bisons makefile ...  (IOT trap after  
reading in the Makefile, so apparently while interpreting it).

Oh, BTW, it's more clear now why I can't use dejagnu:  Apparently,  
the TCL part of it was never correctly brought under autoconf, as it  
tried to use utimes (with arguments with different types from the  
ones used on NEXTSTEP) and mkfifo, which I also don't have.

And, to take a first shot at another discussion:  binutils  
*doesn't* build on my system, because it doesn't support NEXTSTEP's  
Mach-O format (last time I looked).  So if it is included in the  
egcs distribution, the only thing I can do with it is `rm -rf' :-(

HTH,
Toon.