summaryrefslogtreecommitdiff
path: root/Makefile.in
diff options
context:
space:
mode:
authorH.J. Lu <hjl.tools@gmail.com>2000-03-10 20:50:45 +0000
committerH.J. Lu <hjl.tools@gmail.com>2000-03-10 20:50:45 +0000
commit1b2660412156e2eec0545da6d3d6d7744c39a6ad (patch)
treeb6158e845e8261022c7bf11bdb26f4d5ee4d3796 /Makefile.in
parent09b59ee38099437254e739e8de2e44b98447a4e6 (diff)
downloadbinutils-gdb-1b2660412156e2eec0545da6d3d6d7744c39a6ad.tar.gz
2000-03-10 H.J. Lu <hjl@gnu.org>
* Makefile.in (all-gcc): Run ld/ld-new if necessary.
Diffstat (limited to 'Makefile.in')
-rw-r--r--Makefile.in11
1 files changed, 11 insertions, 0 deletions
diff --git a/Makefile.in b/Makefile.in
index beab8be4fb1..9eae8e65edc 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -1414,6 +1414,17 @@ $(INSTALL_X11_MODULES): installdirs
# gcc is the only module which uses GCC_FLAGS_TO_PASS.
.PHONY: all-gcc
all-gcc:
+ # When configured with --enable-shared, libtool creates a
+ # script in the build directory which automatically relinks
+ # the program to search for shared libraries in the build
+ # directory. However, when ld/ld-new is called the first time
+ # from the new gcc, all the compiler environment variables are
+ # set to use the new gcc. ld/ld-new will use the new gcc to
+ # relink the new linker. It is incorrect. We cannot run
+ # ld/ld-new the first time from the new gcc. It is a very
+ # special case. We deal with it here.
+ -if test -f gcc/Makefile -a -x ld/ld-new -a -x ld/.libs/ld-new; then \
+ ld/ld-new -v >/dev/null 2>&1; fi
@if [ -f ./gcc/Makefile ] ; then \
r=`pwd`; export r; \
s=`cd $(srcdir); pwd`; export s; \