On Thursday, 23. August 2001 23:35, Brian S. Julin wrote:
> Hopefully this is not what Debian wants -- what makes most sense
> for Debian is to build libraries/sublibs that are statically linked
> against everything else (libc/xlib/etc) but still are dynamically
> loaded by a statically linked libggi (which is statically linked to
> libgii/libgg).
>
> That is, assuming a staticly linked library _can_ dlopen (?)
Wow, suddenly lot's of 'static' here. ;-) Hope this is cool.
Debian _policy_ requires static interface libs: libgii.a, libggi.a ...
What you describe is the only correct solution (that is not required).
And, yes, you link with -ldl.
The loading is not the problem. input-stdio crashes when init is
called. Others when gii/demo.c joins inputs.
Some dynamics (for variaty):
There should be no reason why dynamically loaded modules, dynamically
linking to the libs on my system, loaded from a statically linked
program shouldn't work - but i go check now how to build your proposed
statically linked sublibs, may be that's giving the segfaults. Can't
believe, though.
Another issue is that static libs shouldn't be built with -fPIC, but
exactly that happens when simply configuring with --enable-static.
Heading back to the box, martin
