summaryrefslogtreecommitdiffstats
path: root/gnu/usr.bin/cc
diff options
context:
space:
mode:
authorru <ru@FreeBSD.org>2007-05-21 12:04:16 +0000
committerru <ru@FreeBSD.org>2007-05-21 12:04:16 +0000
commit686c6f6d3e9a68ce84b9b305c68d5c8056d6b452 (patch)
treef15f8a152a277130536abff76a147a051ed07935 /gnu/usr.bin/cc
parentb41a739b99a026e922996a51b8c36460ac643424 (diff)
downloadFreeBSD-src-686c6f6d3e9a68ce84b9b305c68d5c8056d6b452.zip
FreeBSD-src-686c6f6d3e9a68ce84b9b305c68d5c8056d6b452.tar.gz
Back out the addition of -static to LDFLAGS; I'm pretty confident
that the build failure was caused by a computer/sources date/time mismatch that caused GCC tools to be mistakenly rebuilt again at an inappropriate time during buildworld, re-linking them against new libraries instead of host's installed libraries and thus making them not runnable by the host. Normally they are only built in the early stage of buildworld (build-tools) that links them against shared libraries of the host, but if either the system clock or modification date/time on source files is set incorrectly, make(1) can be foolished into thinking that tools are stale and will rebuild them again, now in the "target" environment which is not suitable for building helper apps that are to be run during buildworld. OK'ed by: kan
Diffstat (limited to 'gnu/usr.bin/cc')
-rw-r--r--gnu/usr.bin/cc/cc_tools/Makefile1
1 files changed, 0 insertions, 1 deletions
diff --git a/gnu/usr.bin/cc/cc_tools/Makefile b/gnu/usr.bin/cc/cc_tools/Makefile
index 55fd64d..38ac590 100644
--- a/gnu/usr.bin/cc/cc_tools/Makefile
+++ b/gnu/usr.bin/cc/cc_tools/Makefile
@@ -3,7 +3,6 @@
.include <bsd.own.mk>
CFLAGS+= -I.
-LDFLAGS+= -static
.include "../Makefile.inc"
OpenPOWER on IntegriCloud