I am finding that if I explicitly set CPPFLAGS in my gcc trunk build,
the bootstrap failure disppears however I end up with three instances of
-I/sw/include in many compile lines. This requirement of setting CPPFLAGS
did not exist up to at least 20081016. I suspect this was caused by...
-----------------------------------------------------------------------
r141292 | drow | 2008-10-22 09:30:19 -0400 (Wed, 22 Oct 2008) | 21 lines
./
PR gdb/921
PR gdb/1646
PR gdb/2175
PR gdb/2176
* Makefile.def (flags_to_pass): Add CPPFLAGS_FOR_BUILD and CPPFLAGS.
* Makefile.tpl (BUILD_EXPORTS): Set CPPFLAGS.
(EXTRA_BUILD_FLAGS): Correct typo. Pass CPPFLAGS.
(HOST_EXPORTS): Pass CPPFLAGS.
(CPPFLAGS_FOR_BUILD, CPPFLAGS, CPPFLAGS_FOR_TARGET): Define.
(LDFLAGS_FOR_TARGET): Initialize from configure script.
(EXTRA_TARGET_FLAGS): Set CPPFLAGS.
* Makefile.in, configure: Regenerated.
* configure.ac: Set CPPFLAGS_FOR_TARGET, LDFLAGS_FOR_TARGET,
and CPPFLAGS_FOR_BUILD.
libiberty/
* Makefile.in (CPPFLAGS): Define.
(FLAGS_TO_PASS, COMPILE.c): Add CPPFLAGS.
which now results in the situation where CPPFLAGS is properly set to
-I/sw/include in
the Makefile in libcpp, but is unset in the Makefile at the top build level.
This unset
CPPFLAGS appears to override the setting in the Makefile in the libcpp
subdirectory.
Jack
