2000-03-10 H.J. Lu <hjl@gnu.org>

	* Makefile.in (all-gcc): Backed out the last change.

diff --git a/ChangeLog b/ChangeLog
index 8171336db3159a9bea459bb84c8c7c46864ff03f..17966a58637a80d705772ef9601e171691b84eb1 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2000-03-10  H.J. Lu  <hjl@gnu.org>
+
+       * Makefile.in (all-gcc): Backed out the last change.
+
 2000-03-10  H.J. Lu  <hjl@gnu.org>
 
        * Makefile.in (all-gcc): Run ld/ld-new if necessary.

diff --git a/Makefile.in b/Makefile.in
index 9eae8e65edcc45e11b072b529ef70ffed0e3d461..beab8be4fb1f61ef90eff76c6f38f8a289094122 100644 (file)
--- a/Makefile.in
+++ b/Makefile.in
@@ -1414,17 +1414,6 @@ $(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; \