This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: killing STDC_0_IN_SYSTEM_HEADERS
- To: Alexandre Oliva <oliva at lsd dot ic dot unicamp dot br>
- Subject: Re: killing STDC_0_IN_SYSTEM_HEADERS
- From: Zack Weinberg <zack at rabi dot columbia dot edu>
- Date: Thu, 06 Jan 2000 01:56:58 -0500
- cc: Joern Rennecke <amylaar at cygnus dot co dot uk>, gcc at gcc dot gnu dot org
On 05 Jan 2000 18:16:03 -0200, Alexandre Oliva wrote:
>On Dec 29, 1999, Joern Rennecke <amylaar@cygnus.co.uk> wrote:
>
>>> This is a nasty hack which appears to be required only by Solaris. I would
>>> like to kill it and deal with the problem in fixincludes instead. Thoughts
>?
>
>> The more files are copied and changed by fixincludes, the less
>> likely a single installation of gcc for a group of computers with
>> slightly different OS versions will work.
>
>But this hasn't work on Solaris for quite a long time, so I'd rather
>go for it.
I am not sure what you mean by "hasn't worked." The code (in cpplib,
anyway) functions, and the headers on Solaris do require this hack. I just
object to the hack on aesthetic reasons. We deal with all other problems of
this nature in fixincludes; why not this one?
An alternative option would be to move the definition of __STDC__ into the
specs. Then Solaris could override it to be zero unless -ansi. This has
the advantage of being exactly what the native compiler does, instead of
this weird 1 sometimes, 0 sometimes arrangement.
zw