Re: Build of egcs-971114 again fails with `C function `doublehypot(double, double)' conflicts with ...'

[Toon Moene <toon@moene.indiv.nluug.nl>]

Yesterday, I wrote:

>  One point to notice is the /usr/test directory in this
>  list, because it's where the headers of the previously
>  installed snapshot are.  I thought this would be harmless,
>  until I removed -rf /usr/test; subsequently the compile
>  of the offending file in .../libstdc++ couldn't find
>  _G_config_ (sp?) - a completely different problem.

Unfortunately, that's not the root of the problem - however, if we  
now look again at the include-file-search-list:

GNU CPP version egcs-2.90.17 971114 (gcc2-970802 experimental)  
(68k, MIT syntax)
#include "..." search starts here:
#include <...> search starts here:
 .
 stl
 ../libio
 /Users/toon/Unix/compilers/egcs-971114/gcc/include
 /usr/local/include
 /NextDeveloper/Headers
 /NextDeveloper/Headers/ansi
 /NextDeveloper/Headers/bsd
 /NextDeveloper/2.0CompatibleHeaders
 /usr/include
 /usr/include/bsd
End of search list.

and compare it with the one in config/nextstep.h:

#undef  INCLUDE_DEFAULTS
#define INCLUDE_DEFAULTS                                \
  {                                                     \
    { GPLUSPLUS_INCLUDE_DIR, 1, 1 },                    \
    { LOCAL_INCLUDE_DIR, 0, 1 },                        \
    { TOOL_INCLUDE_DIR, 0, 1 },                         \
    { GCC_INCLUDE_DIR, 0, 0 },                          \
    /* These are for fixincludes-fixed ansi/bsd headers \
       which wouldn't be found otherwise.               \
       (The use of string catenation here is OK since   \
        NeXT's native compiler is derived from GCC.) */ \
    { GCC_INCLUDE_DIR "/ansi", 0, 0 },                  \
    { GCC_INCLUDE_DIR "/bsd", 0, 0 },                   \
    { "/NextDeveloper/Headers", 0, 0 },                 \
    { "/NextDeveloper/Headers/ansi", 0, 0 },            \
    { "/NextDeveloper/Headers/bsd", 0, 0 },             \
    { "/LocalDeveloper/Headers", 0, 0 },                \
    { "/LocalDeveloper/Headers/ansi", 0, 0 },           \
    { "/LocalDeveloper/Headers/bsd", 0, 0 },            \
    { "/NextDeveloper/2.0CompatibleHeaders", 0, 0 },    \
    { STANDARD_INCLUDE_DIR, 0, 0 },                     \
    { "/usr/include/bsd", 0, 0 },                       \
    { 0, 0, 0 }                                         \
  }

then I definitely get the impression that two lines have to be added:

    { GPLUSPLUS_INCLUDE_DIR "/ansi, 1, 1 },                    \
    { GPLUSPLUS_INCLUDE_DIR "/bsd", 1, 1 },                    \

Of course, this begs the question why this hasn't gone wrong in the  
past ...

Could someone with somewhat more experience on this please comment ?

TIA,
Toon.