[sr #110901] libtool hangs indefinitely on windows when used in msys due to cmd.exe call bug

Ileana Dumitrescu <[email protected]> Tue, 20 Aug 2024 10:16:44 -0400 (EDT)

Newsgroups	gmane.comp.gnu.libtool.general
Message-ID	<[email protected]>

Follow-up Comment #4, sr #110901 (group libtool):

This is a similar report to both of the following:
  https://debbugs.gnu.org/cgi/bugreport.cgi?bug=49246
  https://debbugs.gnu.org/cgi/bugreport.cgi?bug=10949

Maybe an update to libtool's documentation should be made, since this has been
recurring? A minor revision of the quote below should be helpful in
doc/notes.texi:

[comment #2 comment #2:]
> When starting any program under MSYS (and MSYS2), the MSYS[2] checks whether
the lunched program is linked with msys-*.dll. 
> If program is linked with this DLL then the program expects POSIX-like
environment so no path translation is performed.
> If program is not linked with this DLL then the program is native Windows
binary, which expects native Windows paths. In such case the MSYS[2] scans all
arguments for POSIX-like paths and converts all of them to Windows native
paths. The problem is that all Windows drives are mounted as single letter in
the root so the path like "/d/path/file" should be translated into
"D:/path/file", while "/c" is translated into "C:/"
> To prevent this translation double slash could be used. Double slash is
replaced with single slash.

An update to documentation and/or libtool could also be made for the variable
MSYS2_ARG_CONV_EXCL, but I am not sure...


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/support/?110901>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

signature.asc (application/pgp-signature, 228 B)