public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-patches@sourceware.org
To: gdb-patches@sourceware.org, Tom Tromey <tromey@adacore.com>
Subject: Breakage on builder Fedora-i686, revision 93689ce91271bf88580a2d035a466479c16f4e71
Date: Wed, 22 Apr 2020 05:37:08 -0400	[thread overview]
Message-ID: <E1jRBoa-00017z-2Q@gdb-buildbot.osci.io> (raw)
In-Reply-To: <93689ce91271bf88580a2d035a466479c16f4e71-master-breakage@gdb-build>

Unfortunately it seems that there is a breakage on GDB.

Commit title: 'Handle complex error type in read_base_type'
Revision: 93689ce91271bf88580a2d035a466479c16f4e71

You can find more details below:

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


+++ The full log is too big to be posted here.
+++ These are the last 100 lines of it.

/home/gdb-buildbot-2/fedora-x86-64-2/fedora-i686/build/gdb/../../binutils-gdb/gdb/cp-name-parser.y:34.1-12: warning: deprecated directive, use %define api.pure [-Wdeprecated]
   34 | %pure-parser
      | ^~~~~~~~~~~~
/home/gdb-buildbot-2/fedora-x86-64-2/fedora-i686/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    debuginfod-support.o
  CXX    dicos-tdep.o
  CXX    dictionary.o
  CXX    disasm-selftests.o
  CXX    disasm.o
  CXX    dtrace-probe.o
  CXX    dummy-frame.o
  CXX    dwarf2/abbrev.o
  CXX    dwarf2/attribute.o
  CXX    dwarf2/comp-unit.o
  CXX    dwarf2/dwz.o
  CXX    dwarf2/expr.o
  CXX    dwarf2/frame-tailcall.o
  CXX    dwarf2/frame.o
  CXX    dwarf2/index-cache.o
  CXX    dwarf2/index-common.o
  CXX    dwarf2/index-write.o
  CXX    dwarf2/leb.o
  CXX    dwarf2/line-header.o
  CXX    dwarf2/loc.o
  CXX    dwarf2/macro.o
  CXX    dwarf2/read.o
  CXX    dwarf2/section.o
  CXX    dwarf2/stringify.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    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
  CXX    go-valprint.o
  CXX    guile/guile.o
  CXX    h8300-tdep.o
  CXX    hppa-bsd-tdep.o
  CXX    hppa-linux-tdep.o
  CXX    hppa-nbsd-tdep.o
../../binutils-gdb/gdb/hppa-nbsd-tdep.c: In function void hppanbsd_init_abi(gdbarch_info, gdbarch*):
../../binutils-gdb/gdb/hppa-nbsd-tdep.c:204:3: error: nbsd_init_abi was not declared in this scope; did you mean hppanbsd_init_abi?
  204 |   nbsd_init_abi (info, gdbarch);
      |   ^~~~~~~~~~~~~
      |   hppanbsd_init_abi
make[2]: *** [Makefile:1609: hppa-nbsd-tdep.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/home/gdb-buildbot-2/fedora-x86-64-2/fedora-i686/build/gdb'
make[1]: *** [Makefile:10066: all-gdb] Error 2
make[1]: Leaving directory '/home/gdb-buildbot-2/fedora-x86-64-2/fedora-i686/build'
make: *** [Makefile:854: all] Error 2
program finished with exit code 2
elapsedTime=210.340481

      reply	other threads:[~2020-04-22  9:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-22  9:37 Oh dear. I regret to inform you that commit 93689ce91271bf88580a2d035a466479c16f4e71 might be unfortunate gdb-buildbot
2020-04-22  9:37 ` 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=E1jRBoa-00017z-2Q@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).