public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] Make _bfd_error_handler available outside libbfd Date: Fri, 01 Jun 2018 04:20:00 -0000 [thread overview] Message-ID: <030157d8a65afcc6292a4d3d183b816ed2ff7c57@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 030157d8a65afcc6292a4d3d183b816ed2ff7c57 *** Author: Alan Modra <amodra@gmail.com> Branch: master Commit: 030157d8a65afcc6292a4d3d183b816ed2ff7c57 Make _bfd_error_handler available outside libbfd Needed when building libopcodes.so. bfd/ * bfd.c (_bfd_error_handler): Arrange for this function to be declared in bfd-in2.h. * libbfd-in.h (_bfd_error_handler): Don't declare. * libbfd.h: Regenerate. * bfd-in2.h: Regenerate. opcodes/ * sysdep.h (_bfd_error_handler): Don't declare. * msp430-decode.opc: Include bfd.h. Don't include ansidecl.h here. * rl78-decode.opc: Likewise. * msp430-decode.c: Regenerate. * rl78-decode.c: Regenerate.
next reply other threads:[~2018-06-01 4:15 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-06-01 4:20 sergiodj+buildbot [this message] 2018-06-01 4:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2018-06-01 4:46 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot 2018-06-01 7:46 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-06-05 12:27 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-06-05 12:27 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-06-05 13:46 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot 2018-06-05 13:46 ` Failures on Fedora-x86_64-cc-with-index, branch master sergiodj+buildbot 2018-06-07 6:19 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-06-09 1:44 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+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=030157d8a65afcc6292a4d3d183b816ed2ff7c57@gdb-build \ --to=sergiodj+buildbot@sergiodj.net \ --cc=gdb-testers@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: linkBe 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).