Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>
Cc: Simon Marchi <simon.marchi@efficios.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] testsuite: use cygpath to convert from Unix to Windows paths
Date: Tue, 12 May 2020 18:44:20 -0400	[thread overview]
Message-ID: <dec761cb-efc6-041c-8551-0352d8fd9601@simark.ca> (raw)
In-Reply-To: <87a74kdq80.fsf@tromey.com>

On 2020-03-13 3:11 p.m., Tom Tromey wrote:
> Tom> Today I tried something a little weird -- I did a mingw build on Linux
> Tom> and then tried to run the gdb.server test cases.  Linux can run mingw
> Tom> executables via wine...
> 
> Tom> However this fails with:
> 
> Tom>     ERROR: tcl error sourcing /home/tromey/gdb/build-mingw/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.server/wrapper.exp.
> Tom>     ERROR: sh: line 0: pwd: -W: invalid option
> Tom>     pwd: usage: pwd [-LP]
> 
> It failed this way on the Windows machine I have access to as well.
> 
> I believe on that machine, I log in to a Cygwin environment, but
> normally I do mingw-hosted builds.  The Cygwin "pwd" doesn't understand -W.

Hey, I missed that somehow, sorry about that.

I think I could implement something where we try multiple methods in sequence:

1. cygpath
2. pwd -W
3. the original regsub that was there prior to this patch

Would this help?

Simon



      reply	other threads:[~2020-05-12 22:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11 18:32 Simon Marchi
2020-03-11 18:40 ` Christian Biesinger
2020-03-11 19:09   ` Simon Marchi
2020-03-11 19:14     ` Eli Zaretskii
2020-03-11 19:26       ` Simon Marchi
2020-03-13 17:57         ` Tom Tromey
2020-03-13 18:14           ` Christian Biesinger
2020-03-13 19:11           ` Tom Tromey
2020-05-12 22:44             ` Simon Marchi [this message]

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=dec761cb-efc6-041c-8551-0352d8fd9601@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@efficios.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