> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jeff Trawick
> Sent: 17 April 2002 17:13

> "Sander Striker" <[EMAIL PROTECTED]> writes:
> 
>> Yes, and we should fix it.
> 
> sure
> 
>> This patch works for me.  Not an expert on libtool, so I'd like some feedback.
> 
> As far as I can tell, your patch handles the simple problem #2 but
> leaves the real problem #1 unchanged.

That's probably because I don't have access to the platforms for
which libtool is broken.
 
> If you do libtool --mode=install like we used to do, 
> 
>   LoadModule foo_module modules/mod_foo.so
> 
> won't work on HP-UX, Tru64, AIX (and perhaps some other platforms I
> don't have access to).

I don't think we should break the platforms where libtool --install
works by avoiding it by default.
 
> You'll have to code this on LoadModule
> 
>       modules/libmod_foo.so           (Tru64)
> or
>       modules/mod_foo.sl              (HP-UX)
> or
>       modules/XXX                     (I forget what it was on AIX)
> 
> Not to mention getting stuck with the symbolic links added to the
> modules directory which represent versioning.
> 
> A fairly safe* hack would be:
> 
> 1) look in the .la file and see if the DSO needs to be relinked.  If
>    not, use cp and skip the following steps
> 2) do libtool --install instead of cp
> 3) look in the installed .la for the name that must be passed to
>    dlopen (I think there is such a field) and rename that file in the
>    target directory to what we think a DSO ought to be named
> 4) ignore the extra system-dependent libtool-created files/symlinks in
>    the target directory
> 
> (*only subversion folks suffer with inevitable breakage)
> 
> or, being braver, do this
> 
> 1) always do libtool --install

+1.

> 2) look in installed .la file for the name that must be passed to
>    dlopen and rename that file in the target directory to what we
>    think a DSO ought to be named

But we only need to do that for AIX, Tru64 and HP-UX.

> 3) since this design does libtool --install for every DSO, we need to
>    work hard to zap the extra system-dependent libtool-created
>    files/symlinks in the target directory

But that's not too hard.  We can zap everything not ending with .so,
right?

Sander

Reply via email to