Posible Error with libc
Andreas Schwab
schwab@suse.de
Fri Jun 21 13:32:00 GMT 2002
Roland McGrath <roland@frob.com> writes:
|> > Please check for CVS conflict markers. Actually I think this file should
|> > not be in CVS in the first place.
|>
|> It is canonical practice to include bison output files in distributions so
|> as to reduce the number of tools required.
I never suggest to leave it out of the distribution.
|> Keeping the number of necessary
|> build tools to a minimum is especially desireable for libc, which is an
|> early stage of the bootstrap path. We could keep it out of cvs and
|> generate it at make dist time, I suppose.
The file is already autogenerated (if bison exists) during normal build,
which is why the conflicts happen.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
More information about the Libc-alpha
mailing list