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, Alan Modra <amodra@gmail.com>
Subject: Breakage on builder Fedora-x86_64-m32, revision 09c78487342254de6a4498f8b3aa1f3f1d508898
Date: Thu, 12 Dec 2019 11:09:00 -0000	[thread overview]
Message-ID: <E1ifMLJ-0000ag-1y@gdb-buildbot.osci.io> (raw)
In-Reply-To: <09c78487342254de6a4498f8b3aa1f3f1d508898-master-breakage@gdb-build>

Unfortunately it seems that there is a breakage on GDB.

Commit title: 'Make bfd_get_8 return a bfd_vma like other bfd_get_* functions'
Revision: 09c78487342254de6a4498f8b3aa1f3f1d508898

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    c-varobj.o
  CXX    charset.o
  CXX    cli-out.o
  CXX    cli/cli-cmds.o
  CXX    cli/cli-decode.o
  CXX    cli/cli-dump.o
  CXX    cli/cli-interp.o
  CXX    cli/cli-logging.o
  CXX    cli/cli-option.o
  CXX    cli/cli-script.o
  CXX    cli/cli-setshow.o
  CXX    cli/cli-style.o
  CXX    cli/cli-utils.o
  CXX    coff-pe-read.o
  CXX    coffread.o
  CXX    compile/compile-c-support.o
  CXX    compile/compile-c-symbols.o
  CXX    compile/compile-c-types.o
  CXX    compile/compile-cplus-symbols.o
  CXX    compile/compile-cplus-types.o
  CXX    compile/compile-loc2c.o
  CXX    compile/compile-object-load.o
  CXX    compile/compile-object-run.o
  CXX    compile/compile.o
  CXX    complaints.o
  CXX    completer.o
  CXX    continuations.o
  CXX    copying.o
  CXX    corefile.o
  CXX    corelow.o
  CXX    cp-abi.o
  YACC   cp-name-parser.c
/home/gdb-buildbot/fedora-x86-64-3/fedora-x86-64-m32/build/gdb/../../binutils-gdb/gdb/cp-name-parser.y:34.1-12: warning: POSIX Yacc does not support %pure-parser [-Wyacc]
   34 | %pure-parser
      | ^~~~~~~~~~~~
/home/gdb-buildbot/fedora-x86-64-3/fedora-x86-64-m32/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/fedora-x86-64-3/fedora-x86-64-m32/build/gdb/../../binutils-gdb/gdb/cp-name-parser.y: warning: fix-its can be applied.  Rerun with option '--update'. [-Wother]
  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    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
../../binutils-gdb/gdb/fbsd-tdep.c: In function void fbsd_core_info_proc_status(gdbarch*):
../../binutils-gdb/gdb/fbsd-tdep.c:1435:36: error: format %d expects argument of type int, but argument 2 has type bfd_signed_vma {aka long int} [-Werror=format=]
 1435 |   printf_filtered ("'nice' value: %d\n",
      |                                   ~^
      |                                    |
      |                                    int
      |                                   %ld
  CXX    filesystem.o
cc1plus: all warnings being treated as errors
make[2]: *** [Makefile:1660: fbsd-tdep.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/home/gdb-buildbot/fedora-x86-64-3/fedora-x86-64-m32/build/gdb'
make[1]: *** [Makefile:9230: all-gdb] Error 2
make[1]: Leaving directory '/home/gdb-buildbot/fedora-x86-64-3/fedora-x86-64-m32/build'
make: *** [Makefile:852: all] Error 2
program finished with exit code 2
elapsedTime=177.412435

  parent reply	other threads:[~2019-12-12 11:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 19:56 Oh dear. I regret to inform you that commit 09c78487342254de6a4498f8b3aa1f3f1d508898 might be unfortunate gdb-buildbot
2019-12-11 19:56 ` Breakage on builder Ubuntu-Aarch64-m64, revision 09c78487342254de6a4498f8b3aa1f3f1d508898 gdb-buildbot
2019-12-11 20:02 ` Breakage on builder Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-buildbot
2019-12-11 20:07 ` Breakage on builder Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
2019-12-12 11:02 ` Breakage on builder Fedora-i686, " gdb-buildbot
2019-12-12 11:07 ` Breakage on builder Fedora-x86_64-cc-with-index, " gdb-buildbot
2019-12-12 11:09 ` gdb-buildbot [this message]
2019-12-12 11:13 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2019-12-12 11:16 ` Breakage on builder Fedora-x86_64-m64, " gdb-buildbot
2019-12-12 11:21 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2019-12-12 11:38 ` Breakage on builder Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2019-12-12 11:39 ` 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=E1ifMLJ-0000ag-1y@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).