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-w64-mingw32, revision b231e86ac9608056ea837e24d42a878927f5787a
Date: Mon, 18 Nov 2019 04:43:00 -0000 [thread overview]
Message-ID: <E1iWYsK-0006pH-16@gdb-buildbot.osci.io> (raw)
In-Reply-To: <b231e86ac9608056ea837e24d42a878927f5787a-master-breakage@gdb-build>
Unfortunately it seems that there is a breakage on GDB.
Commit title: 'Use strerror_r in safe_strerror if available'
Revision: b231e86ac9608056ea837e24d42a878927f5787a
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 corefile.o
CXX corelow.o
CXX cp-abi.o
YACC cp-name-parser.c
CXX cp-namespace.o
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 demangle.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 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_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/mingw-strerror.o
CXX gdbsupport/netstuff.o
../../binutils-gdb/gdb/gdbsupport/mingw-strerror.c:32:1: error: ambiguating new declaration of 'char* safe_strerror(int)'
safe_strerror (int errnum)
^~~~~~~~~~~~~
In file included from ../../binutils-gdb/gdb/gdbsupport/common-defs.h:122,
from ../../binutils-gdb/gdb/gdbsupport/mingw-strerror.c:20:
../../binutils-gdb/gdb/gdbsupport/common-utils.h:113:20: note: old declaration 'const char* safe_strerror(int)'
extern const char *safe_strerror (int);
^~~~~~~~~~~~~
make[2]: *** [Makefile:1642: gdbsupport/mingw-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-mingw32/build/gdb'
make[1]: Leaving directory '/home/gdb-buildbot-2/fedora-x86-64-2/fedora-x86-64-mingw32/build'
make[1]: *** [Makefile:8917: all-gdb] Error 2
make: *** [Makefile:859: all] Error 2
program finished with exit code 2
elapsedTime=386.703022
prev parent reply other threads:[~2019-11-18 4:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 4:43 Oh dear. I regret to inform you that commit b231e86ac9608056ea837e24d42a878927f5787a might be unfortunate gdb-buildbot
2019-11-18 4:43 ` gdb-buildbot [this message]
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=E1iWYsK-0006pH-16@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