From 042c8311c7af7f75a0508992403372917ed0acee Mon Sep 17 00:00:00 2001 From: "H.J. Lu" Date: Fri, 10 Mar 2000 21:21:16 +0000 Subject: [PATCH] 2000-03-10 H.J. Lu * Makefile.in (all-gcc): Backed out the last change. --- ChangeLog | 4 ++++ Makefile.in | 11 ----------- 2 files changed, 4 insertions(+), 11 deletions(-) diff --git a/ChangeLog b/ChangeLog index 8171336db31..17966a58637 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,7 @@ +2000-03-10 H.J. Lu + + * Makefile.in (all-gcc): Backed out the last change. + 2000-03-10 H.J. Lu * Makefile.in (all-gcc): Run ld/ld-new if necessary. diff --git a/Makefile.in b/Makefile.in index 9eae8e65edc..beab8be4fb1 100644 --- 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; \ -- 2.30.2