Build of egcs-971114 again fails with `C function `doublehypot(double, double)' conflicts with ...'
Toon Moene
toon@moene.indiv.nluug.nl
Wed Nov 19 16:32:00 GMT 1997
I changed the include order in config/nextstep.h to:
{ GPLUSPLUS_INCLUDE_DIR, 1, 1 }, \
{ GPLUSPLUS_INCLUDE_DIR "/ansi", 1, 1 }, \
{ GPLUSPLUS_INCLUDE_DIR "/bsd", 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 }, \
....
Unfortunately, that is not even useless, it's incorrect
(GPLUSPLUS_INCLUDE_DIR has nothing to do with my problem). The
point is that GCC_INCLUDE_DIR doesn't exist yet at the moment the
build of libraries/libstdc++ goes wrong and this list assumes it
does.
This is passed as GCC_INCLUDE_DIR (quoting the Makefile):
% grep GCC_INCLUDE gcc/Makefile
-DGCC_INCLUDE_DIR=\"$(libsubdir)/include\" \
libsubdir is $(libdir)/gcc-lib/$(target_alias)/$(version)
libdir is ${exec_prefix}/lib
and exec_prefix is ${prefix} is /usr/test.
This means that as-is, on m68k-next-nextstep3, you can only build
libraries/libstdc++ once the compiler is installed, and not half
way.
Unfortunately, I am not a hacker of Makefiles, nor a wizard of
autoconf, so I'll drop the ball right here.
HTH,
Toon.
"Fortran is our Forte"
More information about the Gcc
mailing list