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] gdb: sim: merge the sysroot update logic together Date: Wed, 24 Jun 2015 15:57:00 -0000 [thread overview] Message-ID: <87d1b30944783ae0efb49236c6d872d775a37417@kwanyin> (raw) *** TEST RESULTS FOR COMMIT 87d1b30944783ae0efb49236c6d872d775a37417 *** Author: Mike Frysinger <vapier@gentoo.org> Branch: master Commit: 87d1b30944783ae0efb49236c6d872d775a37417 gdb: sim: merge the sysroot update logic together Initialize the local sysroot fully before we start using it. This keeps it all a bit simpler.
next reply other threads:[~2015-06-24 15:57 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-24 15:57 sergiodj+buildbot [this message] 2015-06-24 16:14 ` Failures on AIX-POWER7-plain, branch master sergiodj+buildbot 2015-06-24 16:33 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2015-06-24 19:16 ` Failures on Debian-i686, " sergiodj+buildbot 2015-06-24 19:32 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot 2015-06-24 20:10 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot 2015-06-24 20:30 ` Failures on Debian-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2015-06-24 21:26 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot 2015-06-24 22:15 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-06-24 22:37 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-06-24 23:41 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot 2015-06-25 0:34 ` Failures on Fedora-i686, " sergiodj+buildbot 2015-06-25 1:22 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2015-06-25 2:04 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2015-06-25 2:26 ` 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=87d1b30944783ae0efb49236c6d872d775a37417@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).