This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/32009] [4.3 Regression] building gcc4-4.3.0-20070518 failed on OSX 10.3.9
- From: "andreast at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 21 May 2007 21:39:15 -0000
- Subject: [Bug bootstrap/32009] [4.3 Regression] building gcc4-4.3.0-20070518 failed on OSX 10.3.9
- References: <bug-32009-12313@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from andreast at gcc dot gnu dot org 2007-05-21 22:39 -------
Late night comment, Paolo, I think your patch is fine but it exposed an
inconsitency in using CFLAGS/BOOT_CFLAGS in libgcc.
I could work around the problem with filtering out the mdynamic-no-pic inside
the libgcc Makefile.in.:
Index: Makefile.in
===================================================================
--- Makefile.in (revision 124895)
+++ Makefile.in (working copy)
@@ -204,7 +204,7 @@
# Forcibly remove any profiling-related flags. There is no point
# in supporting profiled bootstrap in this library.
-override CFLAGS := $(filter-out -fprofile-generate -fprofile-use,$(CFLAGS))
+override CFLAGS := $(filter-out -fprofile-generate -fprofile-use
-mdynamic-no-pic,$(CFLAGS))
# CFLAGS first is not perfect; normally setting CFLAGS should override any
# options in LIBGCC2_CFLAGS. But LIBGCC2_CFLAGS may contain -g0, and CFLAGS
It's absolutely the wrong place with the wrong comment. But it's ok for a first
trial.
It smells for me to have an additional var and to pass this one correctly to
all involved consumers.
As said, late night.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32009