On 3/19/2011 6:25 AM, LRN wrote: > I expect to find a lot of libtool-using projects that will require such > hacks or workarounds, because `unrecognized option '-no-undefined'' is > very common.
Ah, but actually -no-undefined should be added by the upstream maintainers, in Makefile.am, to libfoo_la_LDFLAGS. It is a *description* of the library -- which is true regardless of the host platform the library is being built for. It is a claim by the library designer that: "This library, when linked, will not reference any symbols, unless they are defined either in its own source objects or in other explicitly listed dependencies" In order to build a library on win32/cygwin, libtool requires that the library designer assure it of this fact. So, either a library DOES or DOES NOT satisfy the claim: if it doesn't, then it can't be built on windows without massive surgery. If it does, then it does no harm to tell ALL platforms that it does so -- thus, upstream should add -no-undefined to their Makefile.am/libfoo_la_LDFLAGS. This "declaration" is usually NOT passed via an explicit variable statement on the make or configure command line. -- Chuck _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
