[Sablevm-developer] actual build failure not catched (sablevm-nativelib build dep on sablevm-native
Brought to you by:
egagnon
From: Grzegorz P. <gr...@se...> - 2002-09-11 20:52:27
|
Hi! I reported previously, that from sablevm-nativelib source some of the libs are not build sometimes. So I made two builds - one w/o old sablevm-native installed, one - with. And compared build outputs. Here's what I found: --- ./native-installed.out 2002-09-08 22:17:47.000000000 +0200 +++ ./native-uninstalled.out 2002-09-09 00:33:47.000000000 +0200 -/usr/bin/install -c .libs/libjava-io-1.0.4.soT /home/greg/deb-pkgs/sablevm/sablevm-nativelib-1.0.4/debian/libsablevm-native1/usr/lib/sablevm/libjava-io-1.0.4.so -(cd /home/greg/deb-pkgs/sablevm/sablevm-nativelib-1.0.4/debian/libsablevm-native1/usr/lib/sablevm && rm -f libjava-io.so && ln -s libjava-io-1.0.4.so libjava-io.so) -/usr/bin/install -c .libs/libjava-io.lai /home/greg/deb-pkgs/sablevm/sablevm-nativelib-1.0.4/debian/libsablevm-native1/usr/lib/sablevm/libjava-io.la +/usr/bin/ld: cannot find -lclasspath +collect2: ld returned 1 exit status +libtool: install: error: relink `libjava-io.la' with the above command before installing it libtool: install: warning: remember to run `libtool --finish /usr/lib/sablevm' -/usr/bin/install -c .libs/libjava-lang-1.0.4.soT /home/greg/deb-pkgs/sablevm/sablevm-nativelib-1.0.4/debian/libsablevm-native1/usr/lib/sablevm/libjava-lang-1.0.4.so -(cd /home/greg/deb-pkgs/sablevm/sablevm-nativelib-1.0.4/debian/libsablevm-native1/usr/lib/sablevm && rm -f libjava-lang.so && ln -s libjava-lang-1.0.4.so libjava-lang.so) -/usr/bin/install -c .libs/libjava-lang.lai /home/greg/deb-pkgs/sablevm/sablevm-nativelib-1.0.4/debian/libsablevm-native1/usr/lib/sablevm/libjava-lang.la +/usr/bin/ld: cannot find -lclasspath +collect2: ld returned 1 exit status +libtool: install: error: relink `libjava-lang.la' with the above command before installing it libtool: install: warning: remember to run `libtool --finish /usr/lib/sablevm' -/usr/bin/install -c .libs/libjava-net-1.0.4.soT /home/greg/deb-pkgs/sablevm/sablevm-nativelib-1.0.4/debian/libsablevm-native1/usr/lib/sablevm/libjava-net-1.0.4.so -(cd /home/greg/deb-pkgs/sablevm/sablevm-nativelib-1.0.4/debian/libsablevm-native1/usr/lib/sablevm && rm -f libjava-net.so && ln -s libjava-net-1.0.4.so libjava-net.so) -/usr/bin/install -c .libs/libjava-net.lai /home/greg/deb-pkgs/sablevm/sablevm-nativelib-1.0.4/debian/libsablevm-native1/usr/lib/sablevm/libjava-net.la +/usr/bin/ld: cannot find -lclasspath +collect2: ld returned 1 exit status +libtool: install: error: relink `libjava-net.la' with the above command before installing it libtool: install: warning: remember to run `libtool --finish /usr/lib/sablevm' Of course libclasspath is part of just built sablevm-nativelib and in _no case_ should be looked for in /usr/lib ! So I suggest that: 1. Such errors should be catched as errors and not ignored - should stop compilation 2. Some neat trick like LD_LIBRARY_PATH set to directory w/ just builded libclasspath should be used (I'll try it in a minute) (btw. is it portable outside Linux/glibc? no I think) Maybe -L parameter usage would be wiser? Surely. Current situtation is that I need to have sablevm-nativelib installed to be able build new sablevm-nativelib which is unnacceptable. Tell me what you think. GBP PS: The problem with sablevm-n.e.w looking for libs in o.l.d versions if those o.l.d versions were installed during the build - seems to be on similar ground. It seem that sablevm checks in /usr/lib, /usr/lib/sablevm for versions first, instead of own build directories. ATM I need to build conflict w/ sablevm and build depend on libsablevm-native with specified version that coresponds to sablevm version. |