From: Christian Biesinger <cbiesinger@google.com>
To: Tom Tromey <tom@tromey.com>
Cc: Simon Marchi <simark@simark.ca>,
Simon Marchi <simon.marchi@efficios.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] testsuite: use cygpath to convert from Unix to Windows paths
Date: Fri, 13 Mar 2020 13:14:40 -0500 [thread overview]
Message-ID: <CAPTJ0XH35jMevMSar-5U68nkGLQ8h4vbpS0Dx-bY_p5R344ikQ@mail.gmail.com> (raw)
In-Reply-To: <87imj8dtns.fsf@tromey.com>
On Fri, Mar 13, 2020 at 12:57 PM Tom Tromey <tom@tromey.com> wrote:
>
> >> Right, using "pwd -W" was exactly what I wanted to propose for this
> >> purpose.
>
> Simon> Ok thanks, I have pushed this version of the patch.
>
> Today I tried something a little weird -- I did a mingw build on Linux
> and then tried to run the gdb.server test cases. Linux can run mingw
> executables via wine...
>
> However this fails with:
>
> ERROR: tcl error sourcing /home/tromey/gdb/build-mingw/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.server/wrapper.exp.
> ERROR: sh: line 0: pwd: -W: invalid option
> pwd: usage: pwd [-LP]
>
> My site.exp says:
>
> set host_triplet i686-w64-mingw32
> set target_alias i686-w64-mingw32
> set target_triplet i686-w64-mingw32
> set build_triplet x86_64-pc-linux-gnu
>
> I guess maybe this is expected, I wonder if there's a clean way to fix
> the problem. Christian suggested maybe we could have a wine board file
> to work around it. Or maybe we could check build_triplet? I'm not sure
> if that would be incorrect in some case.
Just to clarify... it is not enough to just bypass that call for wine.
You do need to convert the linux path to a Windows path, or GDB will
not be able to load the file. So since that translation has to be done
by the testrunner, it has to be aware that you're running GDB under
Wine.
It looks like by default, Z:\ is mapped to /, so /foo should become Z:/foo.
Christian
next prev parent reply other threads:[~2020-03-13 18:15 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 [this message]
2020-03-13 19:11 ` Tom Tromey
2020-05-12 22:44 ` Simon Marchi
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=CAPTJ0XH35jMevMSar-5U68nkGLQ8h4vbpS0Dx-bY_p5R344ikQ@mail.gmail.com \
--to=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).