From: Dietmar May <dietmar.may@outlook.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:56:41 -0400 [thread overview]
Message-ID: <SN6PR13MB4269FAC268C274507EC43A7EE5039@SN6PR13MB4269.namprd13.prod.outlook.com> (raw)
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.
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>
Interestingly,
ls //c
hangs under msys2 (as well as cygwin),
whereas
cmd //c
does not; so it almost seems like msys2 has a hack to recognize that
cmd.exe is being invoked ...
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
> On 2021-06-27 14:23, Brian Inglis wrote:
>>> Which you don't need to change if you configure properly, as JonY
>>> replied on the list to your earlier post:
>>
>>>> On 2021-06-25 09:27, Jonathan Yong via Cygwin wrote:
>>>>> Don't set --build, you are building on Cygwin, not MSYS.
>>
>>> Jonathan Yong is correct - removing --build allows make to complete
>>> without error using the unmodified ltmain.sh > There's still the
>>> issue of generating a call to cmd.exe with an
>>> invalid switch (//c), which will cause it to hang indefinitely if
>>> ever invoked.
>> > The risk of breaking anything by fixing this seems like nil.
>>
>> The issue exists in the package libtool upstream:
>>
>> https://git.savannah.gnu.org/cgit/libtool.git/tree/build-aux/ltmain.in#n963
>>
>>
>> I submitted a bug report with link to this thread and patch to the
>> upstream package maintainers; I will post any responses received.
>
next reply other threads:[~2021-06-28 13:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 13:56 Dietmar May [this message]
2021-06-28 14:49 ` René Berber
[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=SN6PR13MB4269FAC268C274507EC43A7EE5039@SN6PR13MB4269.namprd13.prod.outlook.com \
--to=dietmar.may@outlook.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).