On Wed, Jan 17, 2001 at 06:35:36AM -0500, Rick Scott wrote:
> For the Xm lib you have
>
> -L../lib/Xm-2.0/.libs -lXm
>
> followed by
>
> ../../../lib/Xm-2.0/.libs/libXm.so
>
> So if the first -L isn't correct, which appears to be the case, then the link
> is picking up an installed version, from the -lXm. I think only the full path
> to the .so should be in there.
Ah, perhaps I got it now.
Here's my libMrm.la (2.0):
# libMrm.la - a libtool library file
# Generated by ltmain.sh - GNU libtool 1.3.4 (1.385.2.196 1999/12/07 21:47:57)
#
# Please DO NOT delete this file!
# It is necessary for linking the library.
# The name that we can dlopen(3).
dlname=''
# Names of this library.
library_names='libMrm.so.2.0.0 libMrm.so libMrm.so'
# The name of the static archive.
old_library=''
# Libraries that this one depends upon.
dependency_libs=' -L/home/mai/lib -L../../lib/Xm-2.0/.libs -lXm'
# Version information for libMrm.
current=2
age=0
revision=0
# Is this an already installed library?
installed=no
# Directory that this library needs to be installed in:
libdir='/home/mai/LessTif/Motif2.0/lib'
Note the -L../../lib/Xm-2.0/.libs, this is a relative path triggered
by Makefile.am (my working copy; CVS is even worse) ecerpt:
libMrm_la_LIBADD = -L$(top_builddir)/lib/Xm-2.0/.libs -lXm
The problem is that the dependency that libtool&friends generate out of
it contains the relative path, while need an absolute one!?
top_builddir is a relative variable on my system (like "../.."),
only top_srcdir is an absolute one.
--
Alexander Mai
[EMAIL PROTECTED]
