From: Sandra Loosemore <sandra.loosemore@siemens.com>
To: Tom Tromey <tom@tromey.com>, Sandra Loosemore <sandra@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 4/5] gdb/testsuite: Disable some tests that are broken on remote Windows host
Date: Fri, 21 Apr 2023 13:33:32 -0600 [thread overview]
Message-ID: <ac9672b4-4f1b-ca0d-63b1-a258018d14f1@siemens.com> (raw)
In-Reply-To: <87y1mlz3rm.fsf@tromey.com>
On 4/21/23 08:52, Tom Tromey wrote:
>>>>>> "Sandra" == Sandra Loosemore <sandra@codesourcery.com> writes:
>
> Sandra> +# The pathnames and shell commands in this test don't work on Windows host.
> Sandra> +if { [is_remote host] && [ishost *-*-mingw*] } {
>
> It belatedly occurred to me to wonder if the "is_remote host" part is needed.
> Like, would this work on native Windows but just not cross Windows?
Is it even possible to run the testsuite on native Windows without being
inside Cygwin or some similar environment? :-S We don't do that here,
anyway -- only Canadian-cross with remote Windows host.
-Sandra
next prev parent reply other threads:[~2023-04-21 19:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 19:30 [PATCH 0/5] gdb/testsuite: Miscellaneous fixes Sandra Loosemore
2023-04-19 19:30 ` [PATCH 1/5] gdb/testsuite: Fix style.exp failures on targets without argc/argv support Sandra Loosemore
2023-04-19 19:30 ` [PATCH 2/5] gdb/testsuite: Fix style.exp failures on targets without libopcodes styling Sandra Loosemore
2023-04-21 14:37 ` Tom Tromey
2023-04-21 19:15 ` Sandra Loosemore
2023-04-19 19:30 ` [PATCH 3/5] gdb/testsuite: Adjust some testcases to allow Windows pathnames Sandra Loosemore
2023-04-21 14:44 ` Tom Tromey
2023-04-21 19:26 ` Sandra Loosemore
2023-04-22 0:11 ` Tom Tromey
2023-04-19 19:30 ` [PATCH 4/5] gdb/testsuite: Disable some tests that are broken on remote Windows host Sandra Loosemore
2023-04-21 14:46 ` Tom Tromey
2023-04-21 14:52 ` Tom Tromey
2023-04-21 19:33 ` Sandra Loosemore [this message]
2023-04-22 0:11 ` Tom Tromey
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=ac9672b4-4f1b-ca0d-63b1-a258018d14f1@siemens.com \
--to=sandra.loosemore@siemens.com \
--cc=gdb-patches@sourceware.org \
--cc=sandra@codesourcery.com \
--cc=tom@tromey.com \
/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).