From: gdb-buildbot@sergiodj.net
To: gdb-patches@sourceware.org
To: gdb-patches@sourceware.org, Kamil Rytarowski <n54@gmx.com>
Subject: Breakage on builder Ubuntu-Aarch64-native-extended-gdbserver-m64, revision 797439622361bc901ed64b398c0d689c97cd8121
Date: Sun, 26 Apr 2020 18:15:03 -0400 [thread overview]
Message-ID: <E1jSpYF-0007EQ-Bk@gdb-buildbot.osci.io> (raw)
In-Reply-To: <797439622361bc901ed64b398c0d689c97cd8121-master-breakage@gdb-build>
Unfortunately it seems that there is a breakage on GDB.
Commit title: 'Add signal number conversions for NetBSD'
Revision: 797439622361bc901ed64b398c0d689c97cd8121
You can find more details below:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+++ The full log is too big to be posted here.
+++ These are the last 100 lines of it.
/bin/bash ../../binutils-gdb/gdb/../mkinstalldirs python/.deps
mkdir -p -- compile/.deps
/bin/bash ../../binutils-gdb/gdb/../mkinstalldirs target/.deps
mkdir -p -- tui/.deps
mkdir -p -- unittests/.deps
/bin/bash ../../binutils-gdb/gdb/../mkinstalldirs nat/.deps
mkdir -p -- guile/.deps
LEX ada-lex.c
YACC ada-exp.c
mkdir -p -- python/.deps
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
YACC go-exp.c
YACC m2-exp.c
CXX m2-lang.o
/work/ubuntu-aarch64-native-extended-gdbserver-m64/build/gdb/../../binutils-gdb/gdb/m2-exp.y: warning: 34 shift/reduce conflicts [-Wconflicts-sr]
/work/ubuntu-aarch64-native-extended-gdbserver-m64/build/gdb/../../binutils-gdb/gdb/c-exp.y: warning: 153 shift/reduce conflicts [-Wconflicts-sr]
/work/ubuntu-aarch64-native-extended-gdbserver-m64/build/gdb/../../binutils-gdb/gdb/c-exp.y: warning: 70 reduce/reduce conflicts [-Wconflicts-rr]
/work/ubuntu-aarch64-native-extended-gdbserver-m64/build/gdb/../../binutils-gdb/gdb/m2-exp.y:301.25-52: warning: rule useless in parser due to conflicts [-Wother]
{ pstate->start_arglist(); }
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
CXX m2-typeprint.o
CXX m2-valprint.o
CXX m32c-tdep.o
CXX m32r-linux-tdep.o
CXX m32r-tdep.o
CXX m68hc11-tdep.o
CXX m68k-bsd-tdep.o
CXX m68k-linux-tdep.o
CXX m68k-tdep.o
CXX machoread.o
CXX macrocmd.o
CXX macroexp.o
CXX macroscope.o
CXX macrotab.o
CXX main.o
CXX maint-test-options.o
CXX maint-test-settings.o
CXX maint.o
CXX mdebugread.o
CXX mem-break.o
CXX memattr.o
CXX memory-map.o
CXX memrange.o
CXX mep-tdep.o
CXX mi/mi-cmd-break.o
CXX mi/mi-cmd-catch.o
CXX mi/mi-cmd-disas.o
CXX mi/mi-cmd-env.o
CXX mi/mi-cmd-file.o
CXX mi/mi-cmd-info.o
CXX mi/mi-cmd-stack.o
CXX mi/mi-cmd-target.o
CXX mi/mi-cmd-var.o
CXX mi/mi-cmds.o
CXX mi/mi-common.o
CXX mi/mi-console.o
CXX mi/mi-getopt.o
CXX mi/mi-interp.o
CXX mi/mi-main.o
CXX mi/mi-out.o
CXX mi/mi-parse.o
CXX mi/mi-symbol-cmds.o
CXX microblaze-linux-tdep.o
CXX microblaze-tdep.o
CXX minidebug.o
CXX minsyms.o
CXX mips-fbsd-tdep.o
CXX mips-linux-tdep.o
CXX mips-nbsd-tdep.o
CXX mips-sde-tdep.o
CXX mips-tdep.o
CXX mips64-obsd-tdep.o
CXX mipsread.o
../../binutils-gdb/gdb/mips-nbsd-tdep.c: In function 'void mipsnbsd_init_abi(gdbarch_info, gdbarch*)':
../../binutils-gdb/gdb/mips-nbsd-tdep.c:359:3: error: expected ';' before 'set_gdbarch_iterate_over_regset_sections'
set_gdbarch_iterate_over_regset_sections
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CXX mn10300-linux-tdep.o
../../binutils-gdb/gdb/mips-nbsd-tdep.c: At global scope:
../../binutils-gdb/gdb/mips-nbsd-tdep.c:119:1: error: 'void mipsnbsd_iterate_over_regset_sections(gdbarch*, void (*)(const char*, int, int, const regset*, const char*, void*), void*, const regcache*)' defined but not used [-Werror=unused-function]
mipsnbsd_iterate_over_regset_sections (struct gdbarch *gdbarch,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1plus: all warnings being treated as errors
Makefile:1609: recipe for target 'mips-nbsd-tdep.o' failed
make[2]: *** [mips-nbsd-tdep.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/work/ubuntu-aarch64-native-extended-gdbserver-m64/build/gdb'
Makefile:10065: recipe for target 'all-gdb' failed
make[1]: *** [all-gdb] Error 2
make[1]: Leaving directory '/work/ubuntu-aarch64-native-extended-gdbserver-m64/build'
Makefile:853: recipe for target 'all' failed
make: *** [all] Error 2
program finished with exit code 2
elapsedTime=113.606056
next prev parent reply other threads:[~2020-04-26 22:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 9:09 Oh dear. I regret to inform you that commit 797439622361bc901ed64b398c0d689c97cd8121 might be unfortunate gdb-buildbot
2020-04-22 9:09 ` Breakage on builder Fedora-x86_64-cc-with-index, revision 797439622361bc901ed64b398c0d689c97cd8121 gdb-buildbot
2020-04-22 9:18 ` Breakage on builder Fedora-x86_64-m32, " gdb-buildbot
2020-04-22 9:25 ` Breakage on builder Fedora-x86_64-m64, " gdb-buildbot
2020-04-22 9:31 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2020-04-22 9:31 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2020-04-22 9:36 ` Breakage on builder Fedora-x86_64-w64-mingw32, " gdb-buildbot
2020-04-23 5:41 ` Breakage on builder Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2020-04-24 0:14 ` Breakage on builder Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
2020-04-26 22:12 ` Breakage on builder Ubuntu-Aarch64-m64, " gdb-buildbot
2020-04-26 22:15 ` gdb-buildbot [this message]
2020-04-26 22:17 ` Breakage on builder Ubuntu-Aarch64-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=E1jSpYF-0007EQ-Bk@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).