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] [GDBserver] Move arm-linux.o and arm-get-next-pcs.o to arch/ Date: Tue, 17 Oct 2017 13:53:00 -0000 [thread overview] Message-ID: <e675d1703fbdec643ec42aa67b9720cb199f4375@gdb-build> (raw) *** TEST RESULTS FOR COMMIT e675d1703fbdec643ec42aa67b9720cb199f4375 *** Author: Yao Qi <yao.qi@linaro.org> Branch: master Commit: e675d1703fbdec643ec42aa67b9720cb199f4375 [GDBserver] Move arm-linux.o and arm-get-next-pcs.o to arch/ gdb/gdbserver: 2017-10-17 Yao Qi <yao.qi@linaro.org> * configure.srv: Rename arm-linux.o with arch/arm-linux.o. Rename arm-get-next-pcs.o with arch/arm-get-next-pcs.o.
next reply other threads:[~2017-10-17 13:53 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-10-17 13:53 sergiodj+buildbot [this message] 2017-10-17 13:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2017-10-17 13:53 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2017-10-17 14:07 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2017-10-17 14:22 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2017-10-17 14:31 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-10-17 14:55 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2017-10-19 14:27 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2017-10-19 14:41 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2017-10-19 15:00 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2017-10-19 15:09 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2017-10-19 15:22 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-10-19 15:48 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-10-19 15:50 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " 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=e675d1703fbdec643ec42aa67b9720cb199f4375@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).