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] libbfd.h and libcoff.h include guards Date: Fri, 18 May 2018 04:54:00 -0000 [thread overview] Message-ID: <0b4395434942ecc6f3006004784d19d9a4fbbf55@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 0b4395434942ecc6f3006004784d19d9a4fbbf55 *** Author: Alan Modra <amodra@gmail.com> Branch: master Commit: 0b4395434942ecc6f3006004784d19d9a4fbbf55 libbfd.h and libcoff.h include guards * libbfd-in.h: Add include guard. * libcoff-in.h: Likewise. * doc/Makefile.am (libbfd.h, libcoff.h): Append another #endif. * doc/Makefile.in: Regenerate. * libbfd.h: Regenerate. * libcoff.h: Regenerate.
next reply other threads:[~2018-05-18 4:50 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-18 4:54 sergiodj+buildbot [this message] 2018-05-18 4:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2018-05-18 5:46 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot 2018-05-18 6:02 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-05-18 6:39 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-05-18 6:39 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2018-05-22 18:43 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-05-22 19:45 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-05-22 20:13 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-05-22 20:44 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-05-22 20:50 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot 2018-07-11 15:49 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, branch master 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=0b4395434942ecc6f3006004784d19d9a4fbbf55@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).