GNU bug report logs -
#41470
Libtool "func_convert_core_msys_to_w32" Hang
Previous Next
To reply to this bug, email your comments to 41470 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-libtool <at> gnu.org
:
bug#41470
; Package
libtool
.
(Sat, 23 May 2020 03:23:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
阿布 <abucomic2015 <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-libtool <at> gnu.org
.
(Sat, 23 May 2020 03:23:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi,
I might have found a (tiny) bug when using libtool (packaged along with
another project, libffi) under Cygwin on Windows 10 (64-bit) and mingw64 to
compile the project: when the command
./libtool -v --tag=CC --mode=link x86_64-w64-mingw32-gcc -O3
-fomit-frame-pointer -fstrict-aliasing -ffast-math -W
all -fexceptions -o libffi_convenience.la src/prep_cif.lo src/types.lo
src/raw_api.lo src/java_raw_api.lo src/closur
es.lo src/x86/ffiw64.lo src/x86/win64.lo
was executed by 'make', the process hangs. After it was re-executed in
debug mode, I found out that the command which caused it to hang was
sed -e 's/[ ]*$//' -e 's|\\\\*|\\|g;s|/|\\|g;s|\\|\\\\|g'
which is in line 964 of build-aux/ltmain.in: instead of having cmd.exe to
exit after the command was executed (the '/c' argument), it remains open
and waiting for the user's input due to the unrecognized argument '//c'.
The problem was fixed after I changed line 963 to
func_convert_core_msys_to_w32_result=`( cmd */c* echo "$1" )
2>/dev/null |
Perhaps you would want to consider fixing the problem?
Regards,
Hongtian Yu
[Message part 2 (text/html, inline)]
This bug report was last modified 4 years and 185 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.