From: Alexandre Oliva (oliva@dcc.unicamp.br)
Date: Tue Jan 26 1999 - 23:28:06 EST
On Jan 27, 1999, Godmar Back <gback@cs.utah.edu> wrote:
> So even the current libtool version, once integrated in Kaffe, will
> only tell me this warning:
>> *** Warning: inter-library dependencies are not known to be supported.
>> *** All declared inter-library dependencies are being dropped.
> and not what the actual missing dependencies are? I'm confused...
Yes, the actual dependencies will be the ones listed in the libtool
command line.
> Only if I'm running on a system with shared libraries that requires
> me to do so should I have to declare that libbar defines 'f' when
> building libfoo
Or if you plan on dlopening that library without dlopening its
dependencies first.
> Why does libtool require me to say where I want to take 'f' from if
> that *only* applies to static libraries?
It does not require this, but, if you do, libtool verifies that the
library dependencies you have specified can be satisfied at library
creation time, or if they have to be postponed to program linking
time.
> Libtool, however, by adding the object modules of a "dependent"
> library to the object modules of the library referencing it in the
> way defined in 1, attempts to simulate the way shared libraries are
> linked for static libraries.
It only does that for convenience libraries, and then, it does it for
both shared and static libraries. object modules of inconvenience :-)
libraries are never copied into another library (except when libtool
is allowed to pass static libraries in the link command line of a
shared library and the shared library linker copies some of its object
modules into the shared library on its own)
--
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