HP/UX 10.20 vanilla <-> gcc-2.95.2
Martin v. Loewis
martin@mira.isdn.cs.tu-berlin.de
Sun Oct 31 23:03:00 GMT 1999
> > You should not need bison for the released gcc; it is needed only when
> > you modify the GCC sources (the bison input in particular).
> At the cost of boring repeat readers, the reason for installing
> bison is in order to be able to install flex so that gcc will not
> misconfigure on account of the lex library being found, even though
> lex is not present. This could be cured by a better configure
> script which actually checks for presence of lex rather than libl,
> or by removing libl before running configure, or by installing the
> lex, which is part of the "ANSI C" extra cost development package.
> I found it more practical to install bison and flex.
Pardon my ignorance. Why, exactly, is it necessary that configure
finds a working lex, when you want to build gcc 2.95.2?
lex/flex is not required for building gcc. In fact, I just removed
flex and lex from my system, and gcc still compiles.
I believe that even the autoconf test could be removed, but that's a
different issue.
Regards,
Martin
More information about the Gcc-bugs
mailing list