From: gdb-buildbot@sergiodj.net
To: gdb-patches@sourceware.org
To: gdb-patches@sourceware.org, Christian Biesinger <cbiesinger@google.com>
Subject: Breakage on builder Fedora-x86_64-m64, revision ab7d13f07027e6232a21448ef51f0a52a96738a9
Date: Tue, 10 Dec 2019 19:30:00 -0000 [thread overview]
Message-ID: <E1ielDM-00043P-OO@gdb-buildbot.osci.io> (raw)
In-Reply-To: <ab7d13f07027e6232a21448ef51f0a52a96738a9-master-breakage@gdb-build>
Unfortunately it seems that there is a breakage on GDB.
Commit title: 'Replace the remaining uses of strerror with safe_strerror'
Revision: ab7d13f07027e6232a21448ef51f0a52a96738a9
You can find more details below:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+++ The full log is too big to be posted here.
+++ These are the last 100 lines of it.
CXX cp-namespace.o
/home/gdb-buildbot-2/fedora-x86-64-2/fedora-x86-64/build/gdb/../../binutils-gdb/gdb/cp-name-parser.y: warning: fix-its can be applied. Rerun with option '--update'. [-Wother]
CXX cp-support.o
CXX cp-valprint.o
CXX cris-linux-tdep.o
CXX cris-tdep.o
CXX csky-linux-tdep.o
CXX csky-tdep.o
CXX ctfread.o
YACC d-exp.c
CXX d-lang.o
CXX d-namespace.o
CXX d-valprint.o
CXX dbxread.o
CXX dcache.o
CXX debug.o
CXX dicos-tdep.o
CXX dictionary.o
CXX disasm-selftests.o
CXX disasm.o
CXX dtrace-probe.o
CXX dummy-frame.o
CXX dwarf-index-cache.o
CXX dwarf-index-common.o
CXX dwarf-index-write.o
CXX dwarf2-frame-tailcall.o
CXX dwarf2-frame.o
CXX dwarf2expr.o
CXX dwarf2loc.o
CXX dwarf2read.o
CXX elfread.o
CXX eval.o
CXX event-loop.o
CXX event-top.o
CXX exceptions.o
CXX exec.o
CXX expprint.o
CXX extension.o
YACC f-exp.c
CXX f-lang.o
CXX f-typeprint.o
CXX f-valprint.o
CXX fbsd-tdep.o
CXX filename-seen-cache.o
CXX filesystem.o
CXX findcmd.o
CXX findvar.o
CXX fork-child.o
CXX frame-base.o
CXX frame-unwind.o
CXX frame.o
CXX frv-linux-tdep.o
CXX frv-tdep.o
CXX ft32-tdep.o
CXX gcore.o
CXX gdb-demangle.o
CXX gdb_bfd.o
CXX gdb_obstack.o
CXX gdb_regex.o
CXX gdbarch-selftests.o
CXX gdbarch.o
CXX gdbsupport/agent.o
CXX gdbsupport/btrace-common.o
CXX gdbsupport/buffer.o
CXX gdbsupport/cleanups.o
CXX gdbsupport/common-debug.o
CXX gdbsupport/common-exceptions.o
CXX gdbsupport/common-inferior.o
CXX gdbsupport/common-regcache.o
CXX gdbsupport/common-utils.o
CXX gdbsupport/environ.o
CXX gdbsupport/errors.o
CXX gdbsupport/fileio.o
CXX gdbsupport/filestuff.o
CXX gdbsupport/format.o
CXX gdbsupport/gdb-dlfcn.o
CXX gdbsupport/gdb_tilde_expand.o
CXX gdbsupport/gdb_vecs.o
CXX gdbsupport/job-control.o
CXX gdbsupport/netstuff.o
CXX gdbsupport/new-op.o
CXX gdbsupport/pathstuff.o
CXX gdbsupport/print-utils.o
CXX gdbsupport/ptid.o
CXX gdbsupport/rsp-low.o
CXX gdbsupport/run-time-clock.o
CXX gdbsupport/safe-strerror.o
../../binutils-gdb/gdb/gdbsupport/safe-strerror.c:38:1: error: char* select_strerror_r(char*, char*) defined but not used [-Werror=unused-function]
38 | select_strerror_r (char *res, char *)
| ^~~~~~~~~~~~~~~~~
cc1plus: all warnings being treated as errors
make[2]: *** [Makefile:1660: gdbsupport/safe-strerror.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/home/gdb-buildbot-2/fedora-x86-64-2/fedora-x86-64/build/gdb'
make[1]: Leaving directory '/home/gdb-buildbot-2/fedora-x86-64-2/fedora-x86-64/build'
make[1]: *** [Makefile:9230: all-gdb] Error 2
make: *** [Makefile:852: all] Error 2
program finished with exit code 2
elapsedTime=277.314775
next prev parent reply other threads:[~2019-12-10 19:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 19:28 Oh dear. I regret to inform you that commit ab7d13f07027e6232a21448ef51f0a52a96738a9 might be unfortunate gdb-buildbot
2019-12-10 19:28 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, revision ab7d13f07027e6232a21448ef51f0a52a96738a9 gdb-buildbot
2019-12-10 19:28 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2019-12-10 19:28 ` Breakage on builder Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-buildbot
2019-12-10 19:29 ` Breakage on builder Solaris11-sparcv9-m64, " gdb-buildbot
2019-12-10 19:30 ` gdb-buildbot [this message]
2019-12-10 19:31 ` Breakage on builder Fedora-x86_64-m32, " gdb-buildbot
2019-12-10 19:31 ` Breakage on builder Fedora-x86_64-cc-with-index, " gdb-buildbot
2019-12-10 19:31 ` Breakage on builder Solaris11-amd64-m64, " gdb-buildbot
2019-12-10 19:31 ` Breakage on builder Ubuntu-Aarch64-m64, " gdb-buildbot
2019-12-10 19:32 ` Breakage on builder Fedora-i686, " gdb-buildbot
2019-12-10 19:33 ` Breakage on builder Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
2019-12-10 19:35 ` Breakage on builder Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
2019-12-10 19:35 ` Breakage on builder Fedora-x86_64-w64-mingw32, " gdb-buildbot
2019-12-10 19:37 ` Breakage on builder Fedora-x86_64-native-gdbserver-m32, " 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=E1ielDM-00043P-OO@gdb-buildbot.osci.io \
--to=gdb-buildbot@sergiodj.net \
--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