This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/37923] [4.4 Regression] CPPFLAGS now unset for stage 1 build of libcpp files.
- From: "howarth at nitro dot med dot uc dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 28 Oct 2008 16:21:52 -0000
- Subject: [Bug bootstrap/37923] [4.4 Regression] CPPFLAGS now unset for stage 1 build of libcpp files.
- References: <bug-37923-11113@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #24 from howarth at nitro dot med dot uc dot edu 2008-10-28 16:21 -------
I still don't understand how the stage1 build of libcpp manages to ignore the
CFLAGS setting in the libccp level Makefile. This would suggest that the stage
1
build of libcpp is entirely handled by the toplevel Makefile and the Makefile
in libcpp is ignored, no? I only see three instance of CPPFLAGS in the libcpp
level Makefile...
CPPFLAGS = -I/sw/include
...
ALL_CFLAGS = $(CFLAGS) $(WARN_CFLAGS) $(INCLUDES) $(CPPFLAGS)
...
COMPILE.base = $(CC) $(DEFS) $(INCLUDES) $(CPPFLAGS) $(ALL_CFLAGS) -c
I don't see how, even if CPPFLAGS is unset at the toplevel, that the setting of
CPPFLAGS is ignored if the libcpp level Makefile is actually being used in the
stage 1 build of libcpp.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37923