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] gdb/gdbserver: Remove reference to vec-ipa.o
Date: Mon, 21 Oct 2019 20:13:00 -0000 [thread overview]
Message-ID: <00975ff6eb19ea5c14acf354fe3677a68a9e7fa2@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 00975ff6eb19ea5c14acf354fe3677a68a9e7fa2 ***
commit 00975ff6eb19ea5c14acf354fe3677a68a9e7fa2
Author: Andrew Burgess <andrew.burgess@embecosm.com>
AuthorDate: Tue Oct 15 22:00:05 2019 +0100
Commit: Andrew Burgess <andrew.burgess@embecosm.com>
CommitDate: Tue Oct 15 22:01:53 2019 +0100
gdb/gdbserver: Remove reference to vec-ipa.o
This comit:
commit 0dc327459b19e6765c8fe80957f5c8620611628e
Date: Mon Oct 7 16:38:53 2019 +0100
gdb: Remove vec.{c,h} and update code to not include vec.h
Broke the GDB build due to leaving a reference to vec-ipa.o in the
Makefile.in, this file is built from vec.c which has been removed.
I got away with this as I had an old version of the vec-ipa.o file
still in my build tree.
With this commit in place a clean build now completed successfully.
gdb/ChangeLog:
* Makefile.in: Remove references to vec-ipa.o.
Change-Id: I4cf55951158dd7ee8f60cd054311a7c367e1d7bf
diff --git a/gdb/gdbserver/ChangeLog b/gdb/gdbserver/ChangeLog
index 402546b57c..801a66c563 100644
--- a/gdb/gdbserver/ChangeLog
+++ b/gdb/gdbserver/ChangeLog
@@ -1,3 +1,7 @@
+2019-10-15 Andrew Burgess <andrew.burgess@embecosm.com>
+
+ * Makefile.in: Remove references to vec-ipa.o.
+
2019-10-15 Andrew Burgess <andrew.burgess@embecosm.com>
* Makefile.in: Remove references to vec.c.
diff --git a/gdb/gdbserver/Makefile.in b/gdb/gdbserver/Makefile.in
index c83cb3d363..34d8060c25 100644
--- a/gdb/gdbserver/Makefile.in
+++ b/gdb/gdbserver/Makefile.in
@@ -426,7 +426,6 @@ IPA_OBJS = \
gdbsupport/print-utils-ipa.o \
gdbsupport/rsp-low-ipa.o \
gdbsupport/tdesc-ipa.o \
- gdbsupport/vec-ipa.o \
regcache-ipa.o \
remote-utils-ipa.o \
tdesc-ipa.o \
next reply other threads:[~2019-10-21 20:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 20:13 gdb-buildbot [this message]
2019-10-21 20:13 ` Failures on Ubuntu-Aarch64-m64, branch master gdb-buildbot
2019-10-21 21:47 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-buildbot
2019-10-21 22:25 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
2019-10-29 23:29 ` Failures on Fedora-i686, " gdb-buildbot
2019-10-30 0:28 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2019-10-30 0:47 ` Failures on Fedora-x86_64-native-extended-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=00975ff6eb19ea5c14acf354fe3677a68a9e7fa2@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).