From: gdb-buildbot@sergiodj.net
To: Jose E. Marchesi <jose.marchesi@oracle.com>, gdb-patches@sourceware.org
Subject: Breakage on builder Fedora-i686, revision fd0de36e274c8141a5dd4579cd04856dc88370da
Date: Thu, 23 May 2019 19:44:00 -0000 [thread overview]
Message-ID: <E1hTtdG-0006WS-Do@kwanyin.sergiodj.net> (raw)
In-Reply-To: <fd0de36e274c8141a5dd4579cd04856dc88370da-master-breakage@gdb-build>
Unfortunately it seems that there is a breakage on GDB.
Commit title: 'bfd: add support for eBPF'
Revision: fd0de36e274c8141a5dd4579cd04856dc88370da
You can find more details below:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Buildslave:
fedora-x86-64-2
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Fedora-i686/builds/12969>
Commit(s) tested:
fd0de36e274c8141a5dd4579cd04856dc88370da
Author(s) (in the same order as the commits):
Jose E. Marchesi <jose.marchesi@oracle.com>
Subject:
bfd: add support for eBPF
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Fedora-i686/fd/fd0de36e274c8141a5dd4579cd04856dc88370da/>
*** Failed to compiled GDB. ***
============================
+++ The full log is too big to be posted here.
+++ These are the last 100 lines of it.
CXX sparc-ravenscar-thread.o
CXX sparc-sol2-tdep.o
CXX sparc-tdep.o
CXX spu-multiarch.o
CXX spu-tdep.o
CXX stabsread.o
CXX stack.o
CXX std-regs.o
CXX stub-termcap.o
CXX symfile-debug.o
CXX symfile-mem.o
CXX symfile.o
CXX symmisc.o
CXX symtab.o
CXX target-dcache.o
CXX target-descriptions.o
CXX target-float.o
CXX target-memory.o
CXX target.o
CXX target/waitstatus.o
CXX test-target.o
CXX thread-iter.o
CXX thread.o
CXX tic6x-linux-tdep.o
CXX tic6x-tdep.o
CXX tid-parse.o
CXX tilegx-linux-tdep.o
CXX tilegx-tdep.o
CXX top.o
CXX tracefile-tfile.o
CXX tracefile.o
CXX tracepoint.o
CXX trad-frame.o
CXX tramp-frame.o
CXX type-stack.o
CXX typeprint.o
CXX ui-file.o
CXX ui-out.o
CXX ui-style.o
CXX unittests/array-view-selftests.o
CXX unittests/child-path-selftests.o
CXX unittests/cli-utils-selftests.o
CXX unittests/common-utils-selftests.o
CXX unittests/copy_bitwise-selftests.o
CXX unittests/environ-selftests.o
CXX unittests/format_pieces-selftests.o
CXX unittests/function-view-selftests.o
CXX unittests/lookup_name_info-selftests.o
CXX unittests/memory-map-selftests.o
CXX unittests/memrange-selftests.o
CXX unittests/mkdir-recursive-selftests.o
CXX unittests/observable-selftests.o
CXX unittests/offset-type-selftests.o
CXX unittests/optional-selftests.o
CXX unittests/parse-connection-spec-selftests.o
CXX unittests/ptid-selftests.o
CXX unittests/rsp-low-selftests.o
CXX unittests/scoped_fd-selftests.o
CXX unittests/scoped_mmap-selftests.o
CXX unittests/scoped_restore-selftests.o
CXX unittests/string_view-selftests.o
CXX unittests/style-selftests.o
CXX unittests/tracepoint-selftests.o
CXX unittests/unpack-selftests.o
CXX unittests/utils-selftests.o
CXX unittests/xml-utils-selftests.o
CXX user-regs.o
CXX utils.o
CXX v850-tdep.o
CXX valarith.o
CXX valops.o
CXX valprint.o
CXX value.o
CXX varobj.o
CXX vax-nbsd-tdep.o
CXX vax-tdep.o
CXX version.o
CXX windows-tdep.o
CXX x86-linux-nat.o
CXX x86-nat.o
CXX x86-tdep.o
CXX xcoffread.o
CXX xml-builtin.o
CXX xml-support.o
CXX xml-syscall.o
CXX xml-tdesc.o
CXX xstormy16-tdep.o
CXX xtensa-config.o
CXX xtensa-linux-tdep.o
CXX xtensa-tdep.o
CXX init.o
CXXLD gdb
/usr/bin/ld: ../bfd/libbfd.a(targets.o):(.rodata+0x1364): undefined reference to `bpf_elf64_le_vec'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:1895: gdb] Error 1
make[1]: *** [Makefile:8793: all-gdb] Error 2
make: *** [Makefile:850: all] Error 2
make[2]: Leaving directory '/home/gdb-buildbot-2/fedora-x86-64-2/fedora-i686/build/gdb'
make[1]: Leaving directory '/home/gdb-buildbot-2/fedora-x86-64-2/fedora-i686/build'
============================
next prev parent reply other threads:[~2019-05-23 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 19:44 Oh dear. I regret to inform you that commit fd0de36e274c8141a5dd4579cd04856dc88370da might be unfortunate gdb-buildbot
2019-05-23 19:44 ` gdb-buildbot [this message]
2019-05-23 21:30 ` Jose E. Marchesi
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=E1hTtdG-0006WS-Do@kwanyin.sergiodj.net \
--to=gdb-buildbot@sergiodj.net \
--cc=gdb-patches@sourceware.org \
--cc=jose.marchesi@oracle.com \
/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