public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@redhat.com To: gdb-testers@sourceware.org Subject: [binutils-gdb] [OBV] Fix build -- missing ';' Date: Mon, 23 Mar 2015 20:51:00 -0000 [thread overview] Message-ID: <c53ed7cf577806c9d7d658dec5b70b2de00ec825@kwanyin> (raw) *** TEST RESULTS FOR COMMIT c53ed7cf577806c9d7d658dec5b70b2de00ec825 *** Author: Keith Seitz <keiths@redhat.com> Branch: master Commit: c53ed7cf577806c9d7d658dec5b70b2de00ec825 [OBV] Fix build -- missing ';' bfd/ChangeLog * elfnn-aarch64.c (_bfd_aarch64_create_or_find_stub_sec): Add missing ';'.
next reply other threads:[~2015-03-23 19:16 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-23 20:51 sergiodj+buildbot [this message] 2015-03-23 20:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2015-03-23 23:52 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot 2015-03-24 0:46 ` Failures on Debian-x86_64-m64, " sergiodj+buildbot 2015-03-24 1:09 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot 2015-03-24 1:17 ` Failures on Debian-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2015-03-24 1:29 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-03-24 1:33 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot 2015-03-24 1:37 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot 2015-03-24 7:16 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2015-03-24 8:00 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2015-03-24 8:04 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-03-24 8:20 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2015-03-24 8:32 ` Failures on Fedora-x86_64-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=c53ed7cf577806c9d7d658dec5b70b2de00ec825@kwanyin \ --to=sergiodj+buildbot@redhat.com \ --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).