bug-libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Bugs or what?


From: Jin Zhou
Subject: Bugs or what?
Date: Wed, 11 Dec 2002 16:13:34 -0800

Hi there,

    I downloaded libtool 1.4.3 source code and trying to install it on Soalris8 and Tru64 V5.1. The "configure" and "make" run smoothly, but "make check" has some interesting outputs.

   For Tru64 V5.1, I have some "unresolved symbol name" errors, but still all tests have passed succesfully.
........
PASS: demo-exec.test
PASS: demo-inst.test
PASS: hardcode.test
578531:/home/kansas/vb/Ctech/jinz/playzone/libtool-1.4.3/demo/.libs/lt-hell: /sbin/loader: Error: /home/kansas/vb/Ctech/jinz/playzone/libtool-1.4.3/demo/.libs/lt-hell: symbol "nothing" unresolved
578531:/home/kansas/vb/Ctech/jinz/playzone/libtool-1.4.3/demo/.libs/lt-hell: /sbin/loader: Fatal Error: Load of "/home/kansas/vb/Ctech/jinz/playzone/libtool-1.4.3/demo/.libs/lt-hell" failed: Unresolved symbol name
PASS: build-relink.test
PASS: noinst-link.test
PASS: demo-unst.test
PASS: depdemo-shared.test
PASS: depdemo-make.test
PASS: depdemo-exec.test
PASS: depdemo-inst.test
581377:/home/kansas/vb/Ctech/jinz/playzone/libtool-1.4.3/depdemo/.libs/lt-depdemo: /sbin/loader: Error: libl4.so.0: symbol "var_l3" unresolved
581377:/home/kansas/vb/Ctech/jinz/playzone/libtool-1.4.3/depdemo/.libs/lt-depdemo: /sbin/loader: Fatal Error: Load of "/home/kansas/vb/Ctech/jinz/playzone/libtool-1.4.3/depdemo/.libs/lt-depdemo" failed: Unresolved symbol name
PASS: build-relink2.test
.......
.......
===================
All 83 tests passed
===================

   For Solaris8, I don't see any errors, except that one test failed.
.......
.......
PASS: demo-inst.test
FAIL: hardcode.test
PASS: build-relink.test
.......
.......
====================
1 of 83 tests failed
====================

   Then I run the hardcode.test individually and got these outputs:
% hardcode.test
=== Running hardcode.test
= Running make hardcode in ../demo
You may ignore any linking errors from the following command:
cc -g  -o hc-direct main.o ./.libs/libhello.so  -lm -R/export/home/vb/Ctech/jinz/playzone/libtool-1.4.3/tests/_inst/lib || echo unsupported > hc-direct
cc -g  -o hc-libflag main.o -R/export/home/vb/Ctech/jinz/playzone/libtool-1.4.3/demo/.libs -L/export/home/vb/Ctech/jinz/playzone/libtool-1.4.3/tests/_inst/lib -lhello  -lm
You may ignore any linking errors from the following command:
LD_LIBRARY_PATH=./.libs cc -g  -o hc-libpath main.o -lhello  -lm -R/export/home/vb/Ctech/jinz/playzone/libtool-1.4.3/tests/_inst/lib || echo unsupported > hc-libpath
cc -g  -o hc-minusL main.o -L./.libs -lhello  -lm -R/export/home/vb/Ctech/jinz/playzone/libtool-1.4.3/tests/_inst/lib || echo unsupported > hc-minusL
= Finding libtool.m4's guesses at hardcoding values
= Searching for hardcoded library directories in each program
.libs was hardcoded in `hc-direct', which fooled libtool
.libs was hardcoded in `hc-libflag', as libtool expected
.libs was hardcoded in `hc-libpath', which fooled libtool
.libs was hardcoded in `hc-minusL', which fooled libtool

   By the way, I'm not using gcc, I'm using the C compiler bought from SUN and DEC+Compaq+HP. In addition, I do not have even any error message during "make".

   My question are:
   1) Can we ignore the erros on Tru64 and just go ahead install libtool on Tru64 V5.1 since libtool passes all 83 tests?
   2) What's wrong with libtool on Solari8?

   Thanks

   Jin
 
 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]