Subject: Re: Report on broken packages, gcc3 on sparc64
To: Martin Husemann <email@example.com>
From: Frederick Bruckman <firstname.lastname@example.org>
Date: 07/17/2003 14:09:29
On Thu, 17 Jul 2003, Martin Husemann wrote:
> On Thu, Jul 17, 2003 at 10:52:46AM -0500, Frederick Bruckman wrote:
> > There's nothing wrong with gcc-3* in that regard. It's well
> > documented, and modern autoconf systems allow for it, using "gcc -E"
> > for the C-preprocessor.
> All fine with me, but then our src/tools tree is broken.
> > export CPP='/usr/pkg/gcc-3.3/bin/cpp -gcc'
> Uhm, that's what I would call a hack. How will things be once gcc3.3.x is
> integrated into the main source tree? Will you still have to set CPP to
> "/usr/bin/cpp -gcc"? Will bsd.*.mk take care of it?
The reason it's an issue is because of "fixincludes" fixing perfectly
reasonable headers by liberally inserting #ifdef __GNUC__. (I guess
they feel that since certain identifiers are "reserved for the
implementation", that means they're reserved for themselves.) I'm
confident that once gcc-3.3.1 is imported, #ifdef __GNUC__ will only
protect use of gcc special features, and not essential parts of the
implementation, so occasional use of naked "cpp" won't hurt anything.