Re: ppc c++ header location oddities

[Franz Sirl <Franz dot Sirl-kernel at lauterbach dot com>]

At 16:43 23.03.99 , Mike Stump wrote:
>> Date: Tue, 23 Mar 1999 16:17:53 +0100
>> To: mrs@wrs.com (Mike Stump)
>> From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
>
>> Under what circumstances is this default set?
>
>Under the circumstance that your /usr has C source files.  Maybe I
>missed the subtly of your question?
>
>> And where can I configure that?
>
> From the manual:
>
>@findex INCLUDE_DEFAULTS
>@item INCLUDE_DEFAULTS
>Define this macro if you wish to override the entire default search path
>for include files.  For a native compiler, the default search path
>usually consists of @code{GCC_INCLUDE_DIR}, @code{LOCAL_INCLUDE_DIR},
>@code{SYSTEM_INCLUDE_DIR}, @code{GPLUSPLUS_INCLUDE_DIR}, and
>@code{STANDARD_INCLUDE_DIR}.  In addition, @code{GPLUSPLUS_INCLUDE_DIR}
>and @code{GCC_INCLUDE_DIR} are defined automatically by @file{Makefile},
>and specify private search areas for GCC.  The directory
>@code{GPLUSPLUS_INCLUDE_DIR} is used only for C++ programs.

Or even better suited seems to be NO_IMPLICIT_EXTERN_C. For x86/m68k-linux 
this is defined in config/linux.h, some other linux-platforms seem to 
define it in config/<platform>/linux.h, probably because it's more work to 
undefine some of the stuff in config/linux.h, than to define the needed 
parts separately.

So what's the better way to implement this for the future? Define 
NO_IMPLICIT_EXTERN_C or include config/linux.h in config/rs6000/linux.h?
I'll prepare a patch for the more common solution then. For the mainline a 
cleanup of config/linux.h maybe wise, some stuff looks quite x86 specific.

Franz.