From: Ben Elliston <bje@au1.ibm.com>
To: gdb-patches@sourceware.org
Subject: PATCH: fix link error for an all-targets libbfd
Date: Mon, 14 Mar 2005 02:36:00 -0000 [thread overview]
Message-ID: <4234F899.3010500@au.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]
When linking GDB against an "all-targets" version of libopcodes and libbfd, link
errors occur due to calls from opcodes->bfd. Since bfd is a lower level library, it
should be linked after libopcodes. This patch does just that. Okay for mainline?
2005-03-14 Ben Elliston <bje@au.ibm.com>
* Makefile.in (CLIBS): Link libbfd after libopcodes, as it is a
more primitive library.
Index: Makefile.in
===================================================================
RCS file: /home/bje/src-cvs/src/gdb/Makefile.in,v
retrieving revision 1.705
diff -u -p -r1.705 Makefile.in
--- Makefile.in 11 Mar 2005 02:24:20 -0000 1.705
+++ Makefile.in 14 Mar 2005 02:33:42 -0000
@@ -372,7 +372,7 @@ INTERNAL_LDFLAGS = $(CFLAGS) $(GLOBAL_CF
INSTALLED_LIBS=-lbfd -lreadline -lopcodes -liberty \
$(XM_CLIBS) $(TM_CLIBS) $(NAT_CLIBS) $(GDBTKLIBS) @LIBS@ \
-lintl -liberty
-CLIBS = $(SIM) $(BFD) $(READLINE) $(OPCODES) $(INTL) $(LIBIBERTY) \
+CLIBS = $(SIM) $(READLINE) $(OPCODES) $(BFD) $(INTL) $(LIBIBERTY) \
$(XM_CLIBS) $(TM_CLIBS) $(NAT_CLIBS) $(GDBTKLIBS) @LIBS@ \
$(LIBICONV) \
$(LIBIBERTY) $(WIN32LIBS)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next reply other threads:[~2005-03-14 2:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 2:36 Ben Elliston [this message]
2005-03-14 2:49 ` Daniel Jacobowitz
2005-03-14 3:13 ` Ben Elliston
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=4234F899.3010500@au.ibm.com \
--to=bje@au1.ibm.com \
--cc=gdb-patches@sourceware.org \
/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