Juergen Vigna wrote assert that
> No as Albert Chin explained us recently it is an xforms bug. When
> creating .a libraries they should contain all other needed libraries or
> at least contain the dependencies on them when build.
Stop right there. This would be a really *bad idea* in many instances because
the only known method of doing this on linux is to statically link the library
with .a versions of the other libraries it needs. If the libraries required are
small (like libz) this is not a major problem but if not then I heve real
problems with it. If you take this approach in a multipthreaded apllication you
can end up with multiple version of major mutexes, which is obviously lethal.
FYI I do not think libtool knowns how to pull in all the functions from other
libraries anyway, just assuming you have a static version of everything
required (a dubious assumption these days if you are not using a developer's
box).
> Same for .so libraries which should already contain the dependencies on other
> libraries they need. So LyX should not need to link in Xpm if it is not used
> internally in LyX. So as told already before this is an Xforms bug. As an
> example libqt uses libz internally but we don't have to do our tests and link
> in libz, do we?
Dependencies in shared .so libraries are not a problem because if 5 libraries
list the same dependency you end up loading only some copy of the required
shared librar{y,ies}. This avoids the multiple versions of the same mutex
problem. Also you can share these copies with other programs too, so you need
less memory and disc space :-)
--
Duncan (-:
"software industry, the: unique industry where selling substandard goods is
legal and you can charge extra for fixing the problems."
