What can I do????
 
=== Running hardcode.test
= Running make hardcode in ../demo
You may ignore any linking errors from the following command:
gcc -g -O2  -o hc-direct main.o ./.libs/libhello.so  -lm -Wl,+b
-Wl,/home/rdejes
us/libtool-1.5.24/tests/_inst/lib || echo unsupported > hc-direct
gcc -g -O2  -o hc-libflag main.o -Wl,+b
-Wl,/home/rdejesus/libtool-1.5.24/demo/.
libs -L/home/rdejesus/libtool-1.5.24/tests/_inst/lib -lhello  -lm
You may ignore any linking errors from the following command:
LD_LIBRARY_PATH=./.libs gcc -g -O2  -o hc-libpath main.o -lhello  -lm
-Wl,+b -Wl
,/home/rdejesus/libtool-1.5.24/tests/_inst/lib || echo unsupported >
hc-libpath
gcc -g -O2  -o hc-minusL main.o -L./.libs -lhello  -lm -Wl,+b
-Wl,/home/rdejesus
/libtool-1.5.24/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 not hardcoded in `hc-direct', as libtool expected
.libs was hardcoded in `hc-libflag', as libtool expected
.libs was not hardcoded in `hc-minusL', as libtool expected
FAIL: hardcode.test
 
____________________________________ 
Rafael De Jesus 
S.P. Richards Co.
Voice: 678.309.7040 

 
_______________________________________________
Bug-libtool mailing list
Bug-libtool@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-libtool

Reply via email to