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: Brian Ford <ford at vss dot fsi dot com>
- Subject: Re: killing STDC_0_IN_SYSTEM_HEADERS
- From: Alexandre Oliva <oliva at lsd dot ic dot unicamp dot br>
- Date: 06 Jan 2000 19:15:47 -0200
- Cc: Zack Weinberg <zack at rabi dot columbia dot edu>, Joern Rennecke <amylaar at cygnus dot co dot uk>, gcc at gcc dot gnu dot org
- References: <Pine.GSO.4.10.10001061436290.4781-100000@eos>
On Jan 6, 2000, Brian Ford <ford@vss.fsi.com> wrote:
> On 6 Jan 2000, Alexandre Oliva wrote:
>> Building gcc on one version of Solaris and using it on another. Many
>> people have faced problems after upgrading to Solaris 7, trying to use
>> GCC built on Solaris 2.6.
> That is funny. We've been doing just that for seven months or so now
> without problems.
It seems that my information is just outdated. gcc 2.7.* would
present problems for almost any network-related application, because
lots of headers were `fixinclude'd, and they ended up incompatible
with those that did not have to be fixed, and were picked from
/usr/include, regardless of OS version. gcc 2.8.* wouldn't fixinclude
on Solaris, so it didn't have this problem, and gcc 2.95.* fixes just
a few files, which makes the possibility of incompatibilities
negligible.
So I withdraw my comment that it doesn't work. It just used not to
work, but it seems to have been fixed now.
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{lsd.ic.unicamp.br,guarana.{org,com}} aoliva@{acm,computer}.org
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them