public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] gdbserver: Fix whitespace configure.srv damage for `i[34567]86-*-mingw*'
Date: Wed, 29 Jan 2020 20:47:00 -0000 [thread overview]
Message-ID: <287c844a33a4d3b513bce17165158dd5fb2d820c@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 287c844a33a4d3b513bce17165158dd5fb2d820c ***
commit 287c844a33a4d3b513bce17165158dd5fb2d820c
Author: Maciej W. Rozycki <macro@wdc.com>
AuthorDate: Wed Jan 29 18:26:15 2020 +0000
Commit: Maciej W. Rozycki <macro@wdc.com>
CommitDate: Wed Jan 29 18:26:15 2020 +0000
gdbserver: Fix whitespace configure.srv damage for `i[34567]86-*-mingw*'
Fix fallout from commit 42cd72aa0279 ("gdbserver: Make `make TAGS'
actually work") add a missing newline to configure.srv for
`i[34567]86-*-mingw*'.
gdb/gdbserver/
* configure.srv <i[34567]86-*-mingw*>: Fix whitespace damage.
diff --git a/gdb/gdbserver/ChangeLog b/gdb/gdbserver/ChangeLog
index 3b88a9b901..9bc965a36b 100644
--- a/gdb/gdbserver/ChangeLog
+++ b/gdb/gdbserver/ChangeLog
@@ -1,3 +1,7 @@
+2020-01-29 Maciej W. Rozycki <macro@wdc.com>
+
+ * configure.srv <i[34567]86-*-mingw*>: Fix whitespace damage.
+
2020-01-29 Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
* configure.srv (powerpc*-*-linux*): Use srv_tgtobj in second
diff --git a/gdb/gdbserver/configure.srv b/gdb/gdbserver/configure.srv
index f0ab14f7c3..dba0733f1d 100644
--- a/gdb/gdbserver/configure.srv
+++ b/gdb/gdbserver/configure.srv
@@ -124,7 +124,8 @@ case "${target}" in
srv_mingwce=yes
;;
i[34567]86-*-mingw*) srv_regobj=""
- srv_tgtobj="x86-low.o nat/x86-dregs.o win32-low.o" srv_tgtobj="${srv_tgtobj} win32-i386-low.o"
+ srv_tgtobj="x86-low.o nat/x86-dregs.o win32-low.o"
+ srv_tgtobj="${srv_tgtobj} win32-i386-low.o"
srv_tgtobj="${srv_tgtobj} arch/i386.o"
srv_mingw=yes
;;
next reply other threads:[~2020-01-29 20:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 20:47 gdb-buildbot [this message]
2020-01-29 21:05 ` Failures on Fedora-x86_64-cc-with-index, branch master gdb-buildbot
2020-01-29 21:28 ` Failures on Fedora-x86_64-m32, " gdb-buildbot
2020-01-29 21:49 ` Failures on Fedora-x86_64-m64, " gdb-buildbot
2020-01-29 22:01 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2020-01-29 22:08 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2020-01-29 22:56 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-buildbot
2020-01-30 0:03 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
2020-01-30 0:23 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2020-01-30 0:49 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-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=287c844a33a4d3b513bce17165158dd5fb2d820c@gdb-build \
--to=gdb-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).