I've discovered something which is only a problem when doing a
CC='gcc -mno-cygwin' compile - namely, that the new wrapper executables do
execv("/bin/bash",...), which quite obviously, msvcrt doesn't understand.
cygwin-target(or mingw-target) libtool does not work at all unless you
have a reasonably complete posix environment -- ditto autoconf,
automake, etc. In fact, this was the entire reason for the Earnie's
MSYS fork of cygwin: he wanted the autotools to work, but he wanted the
environment to give the "right" answers for a non-cygwin, ming-ish
system, while a "real" cygwin platform does not do that.Now, I don't think that many people do weird cross-compile tricks, and this
issue probably should not block a new Cygwin release of libtool, but I just
wanted to raise the issue. I can't think of any good solution to it, either.
There's no solution because there's no problem. cygwin-target libtool
is only supported on posixy systems. (I could even say that libtool, in
general, only works on posixy systems, but there's probably some gotcha
corner case I don't know about.)