During stablisation tests, both versions failed one test out of 124 tests. The test in particular was tests/demo-hardcode.test Adding both logs with this report.
Created attachment 253113 [details] emerge --info =sys-devel/libtool-2.2.6b
Created attachment 253115 [details] /var/tmp/portage/sys-devel/libtool-2.2.6b/temp/build.log
Created attachment 253117 [details] emerge --info =sys-devel/libtool-2.2.10
Created attachment 253119 [details] /var/tmp/portage/sys-devel/libtool-2.2.10/temp/build.log
This happens on amd64 as well in libtool-2.4.
This test passed fine when I manually built and ran the tests so it has something to do with how Portage runs the tests.
Log of failing test: FAIL: tests/demo-hardcode.test (exit: 1) ======================================== demo-hardcode.test: === Running demo-hardcode.test demo-hardcode.test: === Running `make hardcode' in demo You may ignore any linking errors from the following command: x86_64-pc-linux-gnu-gcc -march=native -O3 -pipe -ggdb3 -fstack-protector-all -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -o hc-direct main.o ./.libs/libhello.so -ldl -lm -Wl,-rpath -Wl,/var/tmp/portage/sys-devel/libtool-2.4/work/libtool-2.4/_inst-demo/lib || echo unsupported > hc-direct x86_64-pc-linux-gnu-gcc -march=native -O3 -pipe -ggdb3 -fstack-protector-all -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -o hc-libflag main.o -Wl,-rpath -Wl,/var/tmp/portage/sys-devel/libtool-2.4/work/libtool-2.4/tests/demo/.libs -L/var/tmp/portage/sys-devel/libtool-2.4/work/libtool-2.4/_inst-demo/lib -lhello -ldl -lm You may ignore any linking errors from the following command: LD_LIBRARY_PATH=./.libs x86_64-pc-linux-gnu-gcc -march=native -O3 -pipe -ggdb3 -fstack-protector-all -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -o hc-libpath main.o -lhello -ldl -lm -Wl,-rpath -Wl,/var/tmp/portage/sys-devel/libtool-2.4/work/libtool-2.4/_inst-demo/lib || echo unsupported > hc-libpath /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lhello collect2: ld returned 1 exit status x86_64-pc-linux-gnu-gcc -march=native -O3 -pipe -ggdb3 -fstack-protector-all -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -o hc-minusL main.o -L./.libs -lhello -ldl -lm -Wl,-rpath -Wl,/var/tmp/portage/sys-devel/libtool-2.4/work/libtool-2.4/_inst-demo/lib || echo unsupported > hc-minusL demo-hardcode.test: === 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 `hc-libpath' was not linked properly, as libtool expected .libs was hardcoded in `hc-minusL', which fooled libtool
Log of passing test (manually built) for comparison: PASS: tests/demo-hardcode.test (exit: 0) ======================================== demo-hardcode.test: === Running demo-hardcode.test demo-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 -ldl -lm -Wl,-rpath -Wl,/home/brantgurga/libtool-2.4/_inst-demo/lib || echo unsupported > hc-direct gcc -g -O2 -o hc-libflag main.o -Wl,-rpath -Wl,/home/brantgurga/libtool-2.4/tests/demo/.libs -L/home/brantgurga/libtool-2.4/_inst-demo/lib -lhello -ldl -lm You may ignore any linking errors from the following command: LD_LIBRARY_PATH=./.libs gcc -g -O2 -o hc-libpath main.o -lhello -ldl -lm -Wl,-rpath -Wl,/home/brantgurga/libtool-2.4/_inst-demo/lib || echo unsupported > hc-libpath /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lhello collect2: ld returned 1 exit status gcc -g -O2 -o hc-minusL main.o -L./.libs -lhello -ldl -lm -Wl,-rpath -Wl,/home/brantgurga/libtool-2.4/_inst-demo/lib || echo unsupported > hc-minusL demo-hardcode.test: === 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 `hc-libpath' was not linked properly, as libtool expected .libs was not hardcoded in `hc-minusL', as libtool expected
what about the testsuite.log ?
Created attachment 255671 [details] full test-suite.log I've attached the full test-suite.log as requested.
seems to be fixed w/libtool-2.4.x which is stable now
