From: gdb-buildbot@sergiodj.net
To: gdb-patches@sourceware.org
To: gdb-patches@sourceware.org, Luis Machado <luis.machado@linaro.org>
Subject: Breakage on builder Ubuntu-Aarch64-m64, revision 39f34d7b64ee76e07b82a3e57800905d249d8005
Date: Thu, 12 Dec 2019 12:54:00 -0000 [thread overview]
Message-ID: <E1ifNyi-0002Gq-Az@gdb-buildbot.osci.io> (raw)
In-Reply-To: <39f34d7b64ee76e07b82a3e57800905d249d8005-master-breakage@gdb-build>
Unfortunately it seems that there is a breakage on GDB.
Commit title: 'Fix unused function error'
Revision: 39f34d7b64ee76e07b82a3e57800905d249d8005
You can find more details below:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+++ The full log is too big to be posted here.
+++ These are the last 100 lines of it.
mkdir -p -- unittests/.deps
mkdir -p -- guile/.deps
/bin/bash ../../binutils-gdb/gdb/../mkinstalldirs nat/.deps
LEX ada-lex.c
mkdir -p -- python/.deps
YACC ada-exp.c
mkdir -p -- target/.deps
mkdir -p -- nat/.deps
YACC c-exp.c
YACC cp-name-parser.c
YACC d-exp.c
YACC f-exp.c
CXX f-lang.o
CXX f-typeprint.o
CXX f-valprint.o
/work/ubuntu-aarch64-m64/build/gdb/../../binutils-gdb/gdb/c-exp.y: warning: 42 shift/reduce conflicts [-Wconflicts-sr]
/work/ubuntu-aarch64-m64/build/gdb/../../binutils-gdb/gdb/c-exp.y: warning: 53 reduce/reduce conflicts [-Wconflicts-rr]
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
CXX gdbsupport/scoped_mmap.o
CXX gdbsupport/selftest.o
CXX gdbsupport/signals-state-save-restore.o
CXX gdbsupport/signals.o
CXX gdbsupport/tdesc.o
CXX gdbsupport/thread-pool.o
CXX gdbsupport/xml-utils.o
CXX gdbtypes.o
CXX glibc-tdep.o
CXX gnu-v2-abi.o
CXX gnu-v3-abi.o
YACC go-exp.c
CXX go-lang.o
CXX go-typeprint.o
../../binutils-gdb/gdb/gdbsupport/thread-pool.c:44:1: error: 'DIAGNOSTIC_IGNORE_UNUSED_FUNCTION' does not name a type; did you mean 'DIAGNOSTIC_IGNORE_STRINGOP_TRUNCATION'?
DIAGNOSTIC_IGNORE_UNUSED_FUNCTION
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DIAGNOSTIC_IGNORE_STRINGOP_TRUNCATION
../../binutils-gdb/gdb/gdbsupport/thread-pool.c: In member function 'void gdb::thread_pool::thread_function()':
../../binutils-gdb/gdb/gdbsupport/thread-pool.c:142:52: error: invalid conversion from 'int (*)(pthread_t, const char*) throw () {aka int (*)(long unsigned int, const char*) throw ()}' to 'void (*)(const char*)' [-fpermissive]
set_thread_name (pthread_setname_np, "gdb worker");
^
../../binutils-gdb/gdb/gdbsupport/thread-pool.c:57:1: note: initializing argument 1 of 'void set_thread_name(void (*)(const char*), const char*)'
set_thread_name (void (*set_name) (const char *), const char *name)
^~~~~~~~~~~~~~~
CXX go-valprint.o
Makefile:1660: recipe for target 'gdbsupport/thread-pool.o' failed
make[2]: *** [gdbsupport/thread-pool.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/work/ubuntu-aarch64-m64/build/gdb'
Makefile:9229: recipe for target 'all-gdb' failed
make[1]: *** [all-gdb] Error 2
make[1]: Leaving directory '/work/ubuntu-aarch64-m64/build'
Makefile:851: recipe for target 'all' failed
make: *** [all] Error 2
program finished with exit code 2
elapsedTime=168.672371
next prev parent reply other threads:[~2019-12-12 12:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 12:17 Oh dear. I regret to inform you that commit 39f34d7b64ee76e07b82a3e57800905d249d8005 might be unfortunate gdb-buildbot
2019-12-12 12:17 ` Breakage on builder Solaris11-sparcv9-m64, revision 39f34d7b64ee76e07b82a3e57800905d249d8005 gdb-buildbot
2019-12-12 12:19 ` Breakage on builder Solaris11-amd64-m64, " gdb-buildbot
2019-12-12 12:54 ` gdb-buildbot [this message]
2019-12-12 12:57 ` Breakage on builder Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-buildbot
2019-12-12 12:59 ` Breakage on builder Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
2019-12-13 8:26 ` Breakage on builder Fedora-i686, " gdb-buildbot
2019-12-13 8:27 ` Breakage on builder Fedora-x86_64-cc-with-index, " gdb-buildbot
2019-12-13 8:29 ` Breakage on builder Fedora-x86_64-m32, " gdb-buildbot
2019-12-13 8:31 ` Breakage on builder Fedora-x86_64-m64, " gdb-buildbot
2019-12-13 8:33 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2019-12-13 8:34 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2019-12-13 8:43 ` Breakage on builder Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2019-12-13 8:51 ` Breakage on builder 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=E1ifNyi-0002Gq-Az@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).