Max Bowsher wrote:
ARGH. This defeats the whole purpose of the policy change -- and it
is a policy change driven by the libtool development
I've been hunting for the relevant threads on the libtool list - can't find
them. Can anyone offer URLs or search terms that would help?
I think it was actually described in the code/comments/changelogs/NEWS
or somesuch. But if you're really curious, ask on the libtool list.
I'm sure one of the PowersThatBe will clue us all in.
I think that in some cases, libtool tries to do too much. I've run into a
number of cases which would have just worked if libtool had passed the
arguments to gcc without modification, but it insists on filtering stuff in
complex ways. For example, gcc -print-search-dirs doesn't admit to searching
/usr/lib/w32api, so any attempt to link with a w32api library when
cross-compiling with -mno-cygwin (which means the Cygwin-specific hack in
libtool.m4 doesn't get activated) fails. Now, admittedly, gcc is probably
wrong in not showing all its search dirs correctly, but sometimes I wish
libtool trusted the compiler more.
mebbe. But that's another discussion.
--Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
