mirror of
https://sourceware.org/git/binutils-gdb.git
synced 2024-11-27 03:51:15 +08:00
2000-03-10 H.J. Lu <hjl@gnu.org>
* Makefile.in (all-gcc): Backed out the last change.
This commit is contained in:
parent
1b26604121
commit
042c8311c7
@ -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.
|
||||
|
11
Makefile.in
11
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; \
|
||||
|
Loading…
Reference in New Issue
Block a user