Re: Building mingw32 DLLs without -no-undefined?

[Simon Josefsson]

Ralf Wildenhues <address@hidden> writes:

> Hi Simon,
>
> * Simon Josefsson wrote on Tue, Mar 07, 2006 at 03:15:29PM CET:
>> Hi!  I'm able to build a win32 DLL of libidn using libtool and
>> mingw32, but it didn't work with libgsasl.  The difference was that
>> libidn specified a -no-undefined where as libgsasl didn't.  libgsasl
>> depend on libidn, so that is understandable.
>
> Well, if it *specifies* that dependency, then all is well, and it should
> use `-no-undefined'.
>
>> `-no-undefined'
>>      Declare that OUTPUT-FILE does not depend on any other libraries.
>
> `any other' is supposed to mean: any you have not specified on the link
> command line.

Oh, I see.  I read it to mean what it says more literally, i.e., only
use -no-undefined if your library doesn't use any external libraries
at all.  May I suggest changing the wording here?

Thanks!

--- libtool.texi        07 Mar 2006 17:18:54 +0100      1.134.2.15
+++ libtool.texi        07 Mar 2006 17:43:05 +0100      
@@ -1272,9 +1272,11 @@
 used in the build tree, e.g., for testing or generating other files.
 
 @item -no-undefined
-Declare that @var{output-file} does not depend on any other libraries.
-Some platforms cannot create shared libraries that depend on other
-libraries (@pxref{Inter-library dependencies}).
+Declare that @var{output-file} does not depend on any other libraries,
+i.e., after linking it will not have any unresolved symbols.  Some
+platforms cannot create shared libraries that depend on other
+libraries (@pxref{Inter-library dependencies}), and using this
+parameter (when applicable) helps on these platforms.
 
 @item -o @var{output-file}
 Create @var{output-file} from the specified objects and libraries.