From: Alexandre Oliva (oliva@dcc.unicamp.br)
Date: Tue Jan 26 1999 - 13:52:15 EST
On Jan 26, 1999, Godmar Back <gback@cs.utah.edu> wrote:
> *** Warning: libtool could not satisfy all dependencies of module libnative
> *** Therefore, instead of creating a dynamic module that would not run,
> *** libtool will create a static module. As long as the dlopening
> *** application is linked with the -dlopen flag, this should be enough.
> Is this something we need to be concerned about?
No, because we do use -dlopen properly when we link Kaffe.
> How do I find out what the unsatisfied dependencies are?
In systems that partially support inter-library dependencies, libtool
will a warning message for each dependency it can't satisfy. In the
case of FreeBSD2-aout, libtool assumes no inter-library dependencies
are supported, so if any libraries are specified as dependencies,
static modules will be built. I'd love to learn this is wrong and we
can actually create shared modules, but I won't have time for
experimenting this until next week. Godmar (or anyone else, for that
matter), if you feel like giving it a try, just search for freebsd-*
in ltconfig and try some other definition for deplibs_check_method.
If it works, it will probably be similar in form to the one in
freebsd-elf*.
> Also, is libtool talking about its fancy notion of interlibrary
> dependencies or is this plain symbol dependencies that would normally
> lead to unresolved symbol errors?
It's inter-library dependencies that might lead to unresolved symbol
errors at dlopening time.
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva aoliva@{acm.org}
oliva@{dcc.unicamp.br,gnu.org,egcs.cygnus.com,samba.org}
Universidade Estadual de Campinas, SP, Brasil
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:49 EDT