This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: __STRICT_ANSI__ "fixes" on STDC_0_IN_SYSTEM_HEADERS (solaris) targets
- From: Bruce Korb <bkorb at gnu dot org>
- To: "Kaveh R. Ghazi" <ghazi at caipclassic dot rutgers dot edu>
- Cc: ebotcazou at libertysurf dot fr, gcc at gcc dot gnu dot org
- Date: Sun, 01 Oct 2006 10:25:20 -0700
- Subject: Re: __STRICT_ANSI__ "fixes" on STDC_0_IN_SYSTEM_HEADERS (solaris) targets
- References: <200610011600.k91G0YLu009761@caipclassic.rutgers.edu>
- Reply-to: bkorb at gnu dot org
Kaveh R. Ghazi wrote:
Thoughts on fixing it?
Blech! :-)
However I believe since fixincludes moved to the top level directory
we're no longer looking in the target headers and getting that
definition and thus the __STRICT_ANSI__ changes are always applied,
even when they're not supposed to be.
Am I reading the situation correctly?
I don't know. We only have a couple of Solaris platforms where I
work and they (mostly) aren't configured to build anything. This
means it isn't easy for me to chase this down. I would hazard a
guess, though, that the change is at least innocuous or there would
have been complaints by now. :) Anyway, is there a way to determine
the setting for STDC_0_IN_SYSTEM_HEAD at run time, since not for
compile time? That'd fix it.
Thanks - Bruce