Open sav-ix opened 6 years ago
@sav-ix you can try research this.
A possible research from MSYS2 Users side already provided. The remaining part refers to MSYS2 itself and unlikely can be fixed (or rather implemented) by anyone except MSYS2 Developers. Taking into account a date of related libtool commit (1999), it was embedded in its architecture from the beginning, when it was a part of Cygwin.
@sav-ix this warning is not principal and I dont have time and wish to do here anything. If it not done in Cygwin for this years then probably it not easy to do
The only possible fix is to remove the annoying warning from ltmain.in. I ended up here because I was so annoyed I wanted to know how to fix it.
Unfortunately this can not be considered as a fix, or even workaround, since in such case executables unable to find required .dll
binaries and test suite run fails (see Description).
Unfortunately this can not be considered as a fix, or even workaround, since in such case executables unable to find required .dll binaries and test suite run fails (see Description).
Removing the echoed warning in the filtered path doesn't prevent the -no-fast-install
option from being used. It just removes the annoyance that makes it appear to be wrong.
Of course someone would argue that -no-install
option shouldn't be used for MSYS and others that can't support it but then that just convolutes the issue to a broader scale when the problem is already fixed with the test in ltmain.in.
Hello everyone,
For Projects with Autotools-based build system (i.e. GMP, as a sample), builds using mingw-w64 with shared layout throw warnings:
which are a result of related libtool commit.
If in file
ltmain.sh
change:to
warnings not reproduce, build system stop to build
.exe
wrappers for related executables, but they unable to find required.dll
binaries during run:Environment:
Is it possible to make MSYS2 to emulate missing Unix functionality, so executables, built with -no-install flag would be able to find required
.dll
binaries?Best,
Alexander