This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: cpplib: Dump __GXX_WEAK__ and __STDC__ with -dM

 > From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
 > Like Zack, I'm not sure this special treatment of Solaris 2 is a good idea.
 > Reducing the number of copies system headers may somewhat reduce the
 > breakage caused by inconsistencies between the system headers on the host
 > gcc is run on versus the fixinclded headers, but it cannot eliminate it,
 > but may just give a false sense of security.  On the other hand, I have
 > just been bitten by Digital UNIX V4.0B fixincluded headers on a V4.0F
 > system and the resulting breakage, so avoiding changes to system headers
 > has important advantages.

And its not just OS *upgrades*.  On Solaris it has been the case that
OS *patches* sometimes also install new copies of system headers to
correct various problems.  If that header was "fixed" by the gcc
bootstrap prior to the patch installation, gcc will never see the

 > See below.  Running this on Solaris 8 gives just the expected differences:
 > no changes to any STDC_0 construct, and many files not fixed at all.
 > 	Rainer
 > Fri Mar  2 18:01:01 2001  Rainer Orth  <ro@TechFak.Uni-Bielefeld.DE>
 > 	* fixinc/inclhack.def (strict_ansi_not, strict_ansi_not_ctd,
 > 	strict_ansi_only): Don't run on Solaris 2.
 > 	* fixinc/fixincl.x: Regenerate.

This looks good to me.

Kaveh R. Ghazi			Engagement Manager / Project Services		Qwest Internet Solutions

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]