It appears that the options to build only static libraries or only shared
libraries are still not in the 1.3 branch of libtool. They exist in the
multi-language/tagged branch.
This is going to be a problem for NT and AIX, unless they've fixed them to
use different library names for static and shared libraries. On both NT and
AIX, the same suffix is used for both static and shared libraries. The
normal libtool behavior is to build both static and shared when a platform
supports both. On NT and AIX this will result in unusable libraries because
the static and shared code will overwrite each other as compilation and
linking progress.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Kurt D. Zeilenga
> Sent: Monday, October 02, 2000 1:32 PM
> To: Howard Chu
> Cc: [EMAIL PROTECTED]
> Subject: RE: libtool update likely breaks modules...
>
>
> At 01:13 PM 10/2/00 -0700, Howard Chu wrote:
> >Yuck. You're probably right, I'll have to see what's changed in libtool
> >1.3.5.
> >I believe the "--only-static" flag has been renamed in 1.3.5, we have to
> >find
> >out what they're calling it now.
>
> Did you hack 1.3.3? CVSweb seems to indicate you did...
>
>
> >> -----Original Message-----
> >> From: [EMAIL PROTECTED]
> >> [mailto:[EMAIL PROTECTED]]On Behalf Of Kurt D. Zeilenga
> >> Sent: Monday, October 02, 2000 1:02 PM
> >> To: [EMAIL PROTECTED]
> >> Subject: libtool update likely breaks modules...
> >>
> >>
> >> I assume the libtool update will breaks modules...
> >> Those desiring module support likely should sort
> >> out necessary changes...
> >>
> >> Kurt
> >>
>
