patch to make --enable-cpp the default
Zack Weinberg
zack@rabi.columbia.edu
Mon May 31 20:56:00 GMT 1999
On Sat, 08 May 1999 06:43:17 -0600, Jeffrey A Law wrote:
>
> In message < 199905072012.WAA02529@quatramaran.ens.fr >you write:
> > In article < 199905051503.LAA23102@blastula.phys.columbia.edu > you write:
> >
> > >which I submitted under the assumption that --enable-cpp was already
> > >the default, and which should not have gone in if we weren't going to
> > >make it the default. Right now, `ln -s PREFIX/lib/gcc-lib/T/V/cpp
> > >/bin/cpp' gets you a /bin/cpp with no predefined macros at all and
> > >which does not recognize -undef. That will break Imake and probably
> > >other things as well. This is true for both cccp and cpplib.
> >
> > This *does* break other things as well. Imake was not was prompted my
> > initial posting of problems with respect to cccp.
>The whole point behind providing the cpp wrapper was to make imake and related
>friends happy *and* still be able to provide an ANSI clean namespace if
>requested.
Precisely. Therefore we need to have the cpp wrapper installed by default,
otherwise people will continue to symlink gcc-lib/T/V/cpp into a public
binary directory, which will not work anymore. At the very least, it needs
to be a documented --enable option, not a sekrit one.
I consider this to be release critical.
zw
More information about the Gcc-patches
mailing list