Re: libtool uses incorrect module extension (.so instead of .dylib) under Darwin

[Peter O'Gorman]

On Mon, 2006-03-20 at 21:56 +0100, Vincent Lefevre wrote:
> When modules are generated under Darwin (Mac OS X 10.4.5), the
> extension ".so" is always used; I've been told that this comes
> from libtool (there's this problem with Liferea 1.0.8, whose
> tarball has been generated using libtool 1.5.22 Debian 1.5.22-4).
> Unfortunately, the value of G_MODULE_SUFFIX has changed in glib2,
> from what I can see:
> 
> $ grep G_MODULE_SUFFIX `locate /include/glibconfig.h`
> /opt/local/lib/glib-2.0/include/glibconfig.h:#define G_MODULE_SUFFIX "dylib"
> /opt/local/var/db/dports/software/glib2/2.10.1_0/opt/local/lib/glib-2.0/include/glibconfig.h:#define
>  G_MODULE_SUFFIX "dylib"
> /opt/local/var/db/dports/software/glib2/2.8.4_0/opt/local/lib/glib-2.0/include/glibconfig.h:#define
>  G_MODULE_SUFFIX "so"
> /opt/local/var/db/dports/software/glib2/2.8.5_0/opt/local/lib/glib-2.0/include/glibconfig.h:#define
>  G_MODULE_SUFFIX "so"
> /opt/local/var/db/dports/software/glib2/2.8.6_0/opt/local/lib/glib-2.0/include/glibconfig.h:#define
>  G_MODULE_SUFFIX "so"
> 
> and this breaks GTK applications under Mac OS X.
> 

This is a bug with the glib2 package, either upstream or darwinports.
The "correct" extension for loadable bundles on darwin is ".so", for
libraries that can be used as input to ld(1) it is ".dylib".

Peter

signature.asc
Description: This is a digitally signed message part