On Wed, 2 May 2001 17:55:17 +0100, David Starks-Browning wrote:
>Greetings,
>
>I just updated from CVS, to check that my prefix/exec_prefix patches
>didn't cause any grief. So far I seem to be the only one with
>prefix != exec_prefix.
>
>Now I find that "make" fails in lib/Mrm-2.0 when attempting to link libMrm.la:
>
>> Making all in Mrm-2.0
>> make[2]: Entering directory
>`/net/nfs0/vol1/sw/src/lesstif/lesstif-cvs-2001-05-02/i386-linux/lib/Mrm-2.0'
>>
>> [... successful compiles omitted ...]
>>
>> /bin/sh ../../libtool --mode=link gcc -g -Wall -L/sw/arch/lib
>-Wl,-rpath,/sw/arch/lib -o libMrm.la -rpath
/sw/arch/LessTif/Motif2.0/lib -version-info 2:0 Mrm.lo lookup.lo misc.lo
../Xm-2.0/libXm.la
>> libtool: link: error: cannot link shared libraries into libtool libraries
>> make[2]: *** [libMrm.la] Error 1
>> make[2]: Leaving directory
>`/net/nfs0/vol1/sw/src/lesstif/lesstif-cvs-2001-05-02/i386-linux/lib/Mrm-2.0'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory
>`/net/nfs0/vol1/sw/src/lesstif/lesstif-cvs-2001-05-02/i386-linux/lib'
>> make: *** [all-recursive] Error 1
>
>It seems that lib/Mrm-2.0/Makefile.am now has
>
> libMrm_la_LIBADD = ../Xm-2.0/libXm.la
>
>which wasn't there on 26 April, when I last checked that this worked. Suggestions?
Hmm, well yes ... to some extent ...
We are just playing with the recently released GNU libtool (forget the
vesion sorry, came out last week). If you would build from a tarball
you would automatically use the new libtool, building from CVS
uses you local installed one.
So if you can life with some potential unresolved bugs or compatibility
issues (?!) you should install this new version.
---
Alexander Mai
[EMAIL PROTECTED]
