From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: libtool with mingw hangs building openocd in func_convert_core_msys_to_w32
Date: Sun, 27 Jun 2021 14:23:21 -0600 [thread overview]
Message-ID: <22509ec7-3dca-32d0-c594-9b80295dd4f7@SystematicSw.ab.ca> (raw)
In-Reply-To: <SN6PR13MB426988E94E52385A4D227031E5049@SN6PR13MB4269.namprd13.prod.outlook.com>
On 2021-06-26 20:38, Dietmar May via Cygwin wrote:
> On 6/26/2021 3:17 PM, Brian Inglis wrote:
>> On 2021-06-25 14:46, Dietmar May via Cygwin wrote:
>>> The build completes successfully by replacing the "cmd /c | sed"
>>> construct with simply:
>>> func_convert_core_msys_to_w32_result=$1
>>> so no path translation takes place.
>>> The function then becomes:
>>> func_convert_core_msys_to_w32 ()
>>> {
>>> $debug_cmd
>>> func_convert_core_msys_to_w32_result=$1
>>> }
>>>> SUMMARY
>>>> func_convert_core_msys_to_w32 in
>>>> /usr/share/libtool/build-aux/ltmain.sh
>>>> has an extraneous '/' in the call to
>>>> ( cmd //c echo "$1" )
>>>> causing make to hang indefinitely
>>>> when configured with
>>>> --build=x86_64-w64-mingw32 --host=x86_64-w64-mingw32
>> 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.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2021-06-27 20:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2021-06-27 22:00 ` Brian Inglis
[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
2021-06-28 13:56 Dietmar May
2021-06-28 14:49 ` René Berber
-- 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=22509ec7-3dca-32d0-c594-9b80295dd4f7@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).