automake/libtool question

[Brian Jones]

I'm looking for a suggestion as to the best way to have some common
source code to multiple libraries outside of the directory the library
is made in.  I've tried LIBADD with .lo files and had problems with
libtool resolving that the source file x.c is the same even though the
path to it is different relative to the path when the .lo is created
(ie the ../../ type stuff confused it or something so I get lots of
errors with regards to redefinition of blah).  I've tried
including the source paths into the _la_SOURCES line with
$(top_srcdir)/native/lib/jcl.c for example and automake complains
about source file in a subdirectory is not supported.

So, since I'm using automake 1.4 and libtool 1.3.5 does this mean I
should try upgrading to automake 1.5 and libtool 1.4.2?  The warning
about inter-library dependencies was removed in libtool 1.4.2 info
documentation but no one seemed to bother to provide a clear example
of how to use it for libraries that haven't been installed yet.  I've
avoid the inter-library thing so far because I think that with the way
VMs load the single shared library we specify in our source that
making one shared library dependent on another could be problematic.
Anyone with experience with this?

Brian
-- 
Brian Jones <address@hidden>