From: Corinna Vinschen <vinschen@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] sim/common/Make-common.in: Correct dependency for LIBDEPS
Date: Tue, 24 May 2005 14:22:00 -0000 [thread overview]
Message-ID: <20050524140827.GA13850@calimero.vinschen.de> (raw)
Hi,
LIBDEPS in sim/common/Make-common.in defines the dependencies used
to figure out what has to be build, while EXTRA_LIBS defines what
libraries are used for building.
The same difference is made for INTLDEPS vs. INTLLIBS. Nevertheless,
LIBDEPS depends on $(INTLLIBS) instead of $(INTLDEPS), which would
be the correct dependency.
The below patch fixes that. Ok to apply?
Corinna
* Make-common.in (LIBDEPS): Correctly use INTLDEPS for dependency
check.
Index: sim/common/Make-common.in
===================================================================
RCS file: /cvs/src/src/sim/common/Make-common.in,v
retrieving revision 1.23
diff -u -p -r1.23 Make-common.in
--- sim/common/Make-common.in 18 May 2005 01:55:46 -0000 1.23
+++ sim/common/Make-common.in 24 May 2005 14:07:57 -0000
@@ -241,7 +241,7 @@ OPCODES_LIB = ../../opcodes/libopcodes.a
INTLLIBS = @INTLLIBS@
INTLDEPS = @INTLDEPS@
CONFIG_LIBS = @LIBS@
-LIBDEPS = $(BFD_LIB) $(OPCODES_LIB) $(INTLLIBS) $(LIBIBERTY_LIB) \
+LIBDEPS = $(BFD_LIB) $(OPCODES_LIB) $(INTLDEPS) $(LIBIBERTY_LIB) \
$(SIM_EXTRA_LIBDEPS)
EXTRA_LIBS = $(BFD_LIB) $(OPCODES_LIB) $(INTLLIBS) $(LIBIBERTY_LIB) \
$(CONFIG_LIBS) $(SIM_EXTRA_LIBS)
--
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat, Inc.
next reply other threads:[~2005-05-24 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 14:22 Corinna Vinschen [this message]
2005-05-24 15:29 ` Daniel Jacobowitz
2005-05-24 15:43 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050524140827.GA13850@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox