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] Regenerate gdbserver/configure
Date: Mon, 16 Oct 2017 10:50:00 -0000 [thread overview]
Message-ID: <5bfda25568c34410129c91042cdfdf10c143edac@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 5bfda25568c34410129c91042cdfdf10c143edac ***
Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 5bfda25568c34410129c91042cdfdf10c143edac
Regenerate gdbserver/configure
4fa7574 (Fix gdb 8.1 Solaris compilation) changes warning.m4 and updates
configure, but gdbserver/configure is not updated.
gdb/gdbserver:
2017-10-16 Yao Qi <yao.qi@linaro.org>
* configure: Regenerated.
next reply other threads:[~2017-10-16 10:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 10:50 sergiodj+buildbot [this message]
2017-10-16 10:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2017-10-16 11:50 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2017-10-16 14:16 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
2017-10-16 14:40 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-10-16 15:04 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-10-18 11:13 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2017-10-18 11:18 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2017-10-18 11:39 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2017-10-18 12:26 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2017-10-18 12:40 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2017-10-18 12:42 ` 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=5bfda25568c34410129c91042cdfdf10c143edac@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: link
Be 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).