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] Add native target for FreeBSD/arm. Date: Wed, 11 Oct 2017 20:32:00 -0000 [thread overview] Message-ID: <4f9d99066edcefab0e5868d20cb9ddaa7b76da52@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 4f9d99066edcefab0e5868d20cb9ddaa7b76da52 *** Author: John Baldwin <jhb@FreeBSD.org> Branch: master Commit: 4f9d99066edcefab0e5868d20cb9ddaa7b76da52 Add native target for FreeBSD/arm. gdb/ChangeLog: * Makefile.in (ALLDEPFILES): Add arm-fbsd-nat.c. * NEWS: Mention new FreeBSD/arm native configuration. * configure.host: Add arm*-*-freebsd*. * configure.nat: Likewise. * arm-fbsd-nat.c: New file.
next reply other threads:[~2017-10-11 20:32 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-10-11 20:32 sergiodj+buildbot [this message] 2017-10-11 20:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2017-10-11 21:57 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2017-10-11 23:49 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-10-12 0:13 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2017-10-12 1:53 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2017-10-12 2:16 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2017-10-12 2:31 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2017-10-12 2:33 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-10-12 2:45 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-12-13 9:46 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot 2017-12-13 16:12 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot 2017-12-13 22:38 ` Failures on Fedora-ppc64be-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=4f9d99066edcefab0e5868d20cb9ddaa7b76da52@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).