darlinghq/darling-gdb
1
0
Fork 0
mirror of https://github.com/darlinghq/darling-gdb.git synced 2024-11-24 20:49:43 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

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

Browse Source 
* Makefile.in (all-gcc): Run ld/ld-new if necessary.
This commit is contained in:
H.J. Lu 2000-03-10 20:50:45 +00:00
parent 09b59ee380
commit 1b26604121
2 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ChangeLog
View File

@ -1,3 +1,7 @@
2000-03-10 H.J. Lu <hjl@gnu.org>
* Makefile.in (all-gcc): Run ld/ld-new if necessary.
Fri Mar 3 18:44:08 2000 Andrew Cagney <cagney@b1.cygnus.com> Fri Mar 3 18:44:08 2000 Andrew Cagney <cagney@b1.cygnus.com>
* Makefile.in (taz): Set PACKAGE to TOOL when not defined. * Makefile.in (taz): Set PACKAGE to TOOL when not defined.

11
Makefile.in
View File

@ -1414,6 +1414,17 @@ $(INSTALL_X11_MODULES): installdirs
# gcc is the only module which uses GCC_FLAGS_TO_PASS. # gcc is the only module which uses GCC_FLAGS_TO_PASS.
.PHONY: all-gcc .PHONY: all-gcc
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 \ @if [ -f ./gcc/Makefile ] ; then \
r=`pwd`; export r; \ r=`pwd`; export r; \
s=`cd $(srcdir); pwd`; export s; \ s=`cd $(srcdir); pwd`; export s; \