From: "René Berber" <rene.berber@gmail.com>
To: cygwin@cygwin.com
Subject: Re: libtool with mingw hangs building openocd in func_convert_core_msys_to_w32
Date: Mon, 28 Jun 2021 09:49:01 -0500 [thread overview]
Message-ID: <5578086f-6ac4-70c3-cc74-fe813faac879@gmail.com> (raw)
In-Reply-To: <SN6PR13MB4269FAC268C274507EC43A7EE5039@SN6PR13MB4269.namprd13.prod.outlook.com>
On 6/28/2021 8:56 AM, Dietmar May via Cygwin wrote:
> Thanks for submitting the bug report.
>
>> I can now see what may be a duplicate report under:
>>
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=10949
>>
>> responding that //c is deliberate so MSYS does not convert a posix path,
>> so in the Cygwin Mingw build case, the response may be "Don't Do That"!
>
> I just re-installed msys2 and tried a few things, with interesting result.
>
> First, "ls /usr//bin" as well as "ls /usr/////bin" complete successfully
> under both cygwin and msys2, demonstrating slash compaction.
>
> However, "ls //usr/bin" hangs, as both apparently evaluate the leading
> // as a server path.
Well documented here:
https://cygwin.com/cygwin-ug-net/using.html#unc-paths
> For testing libtool's construct, I tried:
>
> $ cmd //c echo hello
> hello
>
> which works, and this, which doesn't:
>
> $ cmd /c echo hello
>
> Microsoft Windows [Version 10.0.blah]
> (c) Microsoft Corporation. All rights reserved.
>
> C:\msys64\home\myname>
Your example seems to be inverted, the first form doesn't work, the
second does with the same results you show (but inverted).
It would be better if you document how you executed those commands,
we're assuming a mintty terminal running a bash shell, but I haven't
followed all your messages and it might be a cmd window; results
shouldn't change anyway, but for completeness sake.
> Interestingly,
>
> ls //c
>
> hangs under msys2 (as well as cygwin),
Expected as the documentation link describes, //c is taken as a path to
a server, you already knew that.
> whereas
>
> cmd //c
>
> does not; so it almost seems like msys2 has a hack to recognize that
> cmd.exe is being invoked ...
No, wrong, cmd is getting an argument which it interprets as it seems
fit, no hack there. The same applies to the ls example before, ls
receives an argument which is expected to be a path, nothing strange.
> However, both of the following also complete successfully under msys2,
> WITHOUT the double-slash hack:
>
> $ cmd /c "echo hello"
> hello
>
> $ cmd "/c" "echo hello"
> hello
>
> Both seem preferable to bad syntax.
>
> Of course, there's always the question of why libtool is using cmd.exe
> instead of /bin/echo, which seems to work just fine ...
>
> $ /bin/echo "hello world"
> hello world
--
R.Berber
next prev parent reply other threads:[~2021-06-28 14:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 13:56 Dietmar May
2021-06-28 14:49 ` René Berber [this message]
[not found] <1f91bcfb-374f-7985-5b4e-c6e323de3cd8@outlook.com>
2021-06-28 16:29 ` Dietmar May
2021-06-28 17:06 ` Jonathan Yong
2023-07-25 16:19 ` Evgeny Grin
[not found] <355a97ed-2076-6756-8a5f-227e44537136@outlook.com>
2021-06-25 20:46 ` Dietmar May
2021-06-26 19:17 ` Brian Inglis
2021-06-27 2:38 ` Dietmar May
2021-06-27 20:23 ` Brian Inglis
2021-06-27 22:00 ` Brian Inglis
-- strict thread matches above, loose matches on Subject: below --
2021-06-25 14:34 Dietmar May
2021-06-25 15:27 ` Jonathan Yong
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=5578086f-6ac4-70c3-cc74-fe813faac879@gmail.com \
--to=rene.berber@gmail.com \
--cc=cygwin@cygwin.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).