public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Don't link gdb twice against libiberty
Date: Wed, 15 Jan 2020 04:11:00 -0000 [thread overview]
Message-ID: <975f45b7e103929f3ed05d7a4dc71bb5fc320810@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 975f45b7e103929f3ed05d7a4dc71bb5fc320810 ***
commit 975f45b7e103929f3ed05d7a4dc71bb5fc320810
Author: Tom Tromey <tom@tromey.com>
AuthorDate: Wed Jan 8 17:43:29 2020 -0700
Commit: Tom Tromey <tom@tromey.com>
CommitDate: Tue Jan 14 16:25:04 2020 -0700
Don't link gdb twice against libiberty
I noticed that gdb includes libiberty twice in its link line. I don't
think there's a need for this, so this patch removes one of the
references.
gdb/ChangeLog
2020-01-14 Tom Tromey <tom@tromey.com>
* Makefile.in (CLIBS): Remove second use of $(LIBIBERTY).
Change-Id: I43bb7100660867081f937c67ea70ff751c62bbfb
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 7a691092ce..213f2d0395 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2020-01-14 Tom Tromey <tom@tromey.com>
+
+ * Makefile.in (CLIBS): Remove second use of $(LIBIBERTY).
+
2020-01-14 Tom Tromey <tom@tromey.com>
* nat/linux-btrace.c: Don't include <config.h>.
diff --git a/gdb/Makefile.in b/gdb/Makefile.in
index 5f63c617d4..45d1586e85 100644
--- a/gdb/Makefile.in
+++ b/gdb/Makefile.in
@@ -615,7 +615,7 @@ CLIBS = $(SIM) $(READLINE) $(OPCODES) $(BFD) $(LIBCTF) $(ZLIB) \
$(XM_CLIBS) $(GDBTKLIBS) \
@LIBS@ @GUILE_LIBS@ @PYTHON_LIBS@ \
$(LIBEXPAT) $(LIBLZMA) $(LIBBABELTRACE) $(LIBIPT) \
- $(LIBIBERTY) $(WIN32LIBS) $(LIBGNU) $(LIBICONV) \
+ $(WIN32LIBS) $(LIBGNU) $(LIBICONV) \
$(LIBMPFR) $(SRCHIGH_LIBS) $(LIBXXHASH) $(PTHREAD_LIBS)
CDEPS = $(NAT_CDEPS) $(SIM) $(BFD) $(READLINE_DEPS) $(LIBCTF) \
$(OPCODES) $(INTL_DEPS) $(LIBIBERTY) $(CONFIG_DEPS) $(LIBGNU) \
next reply other threads:[~2020-01-15 4:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 4:11 gdb-buildbot [this message]
2020-01-15 4:21 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, branch master gdb-buildbot
2020-01-17 3:07 ` *** COMPILATION FAILED *** Failures on Fedora-i686, branch master *** BREAKAGE *** gdb-buildbot
2020-01-17 3:39 ` Failures on Fedora-x86_64-cc-with-index, branch master gdb-buildbot
2020-01-17 4:01 ` Failures on Fedora-x86_64-m64, " gdb-buildbot
2020-01-17 4:04 ` Failures on Fedora-x86_64-m32, " gdb-buildbot
2020-01-17 4:06 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2020-01-17 4:07 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** gdb-buildbot
2020-01-17 4:10 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch master gdb-buildbot
2020-01-17 4:32 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2020-01-17 4:39 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
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=975f45b7e103929f3ed05d7a4dc71bb5fc320810@gdb-build \
--to=gdb-buildbot@sergiodj.net \
--cc=gdb-testers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).