From: Jonathan Yong <10walls@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 17:06:57 +0000 [thread overview]
Message-ID: <2354976f-cdee-8ad4-c7db-06c52000dd16@gmail.com> (raw)
In-Reply-To: <SN6PR13MB42697EC6467C4B92D1F8F757E5039@SN6PR13MB4269.namprd13.prod.outlook.com>
On 6/28/21 4:29 PM, Dietmar May via Cygwin wrote:
> It seems evident that msys2 is performing slash escaping - ie. 2
> consecutive slashes are consolidated into a single slash (rather like
> quote escaping in various languages - eg. SQL, CSV, C#, YAML)
> recursively (ie. repeatedly) during argument evaluation.
>
> Again, why not simply change this to a form that works without the slash
> hackery?
>
MSYS2 is NOT MSYS NOR a continuation, it is developed by separate groups.
MSYS was based off an ancient Cygwin fork from the 1.3 days, while MSYS2
started life from Cygwin 1.7.
MSYS has been around for a long time, and is heavily used by the
original mingw.org mingw distribution. Libtool is catered to work with
MSYS simply because it has been around far longer than MSYS2.
I'd say if anything, libtool needs to check if it is on MSYS2 or MSYS
and then work appropriately. MSYS2 should be treated as close as
possible to Cygwin.
next prev parent reply other threads:[~2021-06-28 17:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1f91bcfb-374f-7985-5b4e-c6e323de3cd8@outlook.com>
2021-06-28 16:29 ` Dietmar May
2021-06-28 17:06 ` Jonathan Yong [this message]
2023-07-25 16:19 ` Evgeny Grin
2021-06-28 13:56 Dietmar May
2021-06-28 14:49 ` René Berber
[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=2354976f-cdee-8ad4-c7db-06c52000dd16@gmail.com \
--to=10walls@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).