# -*- compilation -*- 79. archive-in-archive.at:27: testing static library contains static library ... libtool: compile: x86_64-gentoo-linux-musl-gcc -O2 -pipe -march=x86-64 -frecord-gcc-switches -fno-diagnostics-color -fmessage-length=0 -c foo.c -fPIC -DPIC -o .libs/foo.o libtool: compile: x86_64-gentoo-linux-musl-gcc -O2 -pipe -march=x86-64 -frecord-gcc-switches -fno-diagnostics-color -fmessage-length=0 -c foo.c -o foo.o >/dev/null 2>&1 libtool: compile: x86_64-gentoo-linux-musl-gcc -O2 -pipe -march=x86-64 -frecord-gcc-switches -fno-diagnostics-color -fmessage-length=0 -c bar.c -fPIC -DPIC -o .libs/bar.o libtool: compile: x86_64-gentoo-linux-musl-gcc -O2 -pipe -march=x86-64 -frecord-gcc-switches -fno-diagnostics-color -fmessage-length=0 -c bar.c -o bar.o >/dev/null 2>&1 libtool: link: x86_64-gentoo-linux-musl-ar cr .libs/libfoo.a foo.o libtool: link: x86_64-gentoo-linux-musl-ranlib .libs/libfoo.a libtool: link: ( cd ".libs" && rm -f "libfoo.la" && ln -s "../libfoo.la" "libfoo.la" ) libtool: install: cp .libs/libfoo.lai /var/tmp/portage/sys-devel/libtool-2.4.7/work/libtool-2.4.7/tests/testsuite.dir/079/libfoo.la libtool: install: cp .libs/libfoo.a /var/tmp/portage/sys-devel/libtool-2.4.7/work/libtool-2.4.7/tests/testsuite.dir/079/libfoo.a libtool: install: chmod 644 /var/tmp/portage/sys-devel/libtool-2.4.7/work/libtool-2.4.7/tests/testsuite.dir/079/libfoo.a libtool: install: x86_64-gentoo-linux-musl-ranlib /var/tmp/portage/sys-devel/libtool-2.4.7/work/libtool-2.4.7/tests/testsuite.dir/079/libfoo.a libtool: finish: PATH="/var/tmp/portage/sys-devel/libtool-2.4.7/work/libtool-2.4.7/tests:/usr/lib/portage/python3.10/ebuild-helpers/xattr:/usr/lib/portage/python3.10/ebuild-helpers:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/sbin" ldconfig -n /var/tmp/portage/sys-devel/libtool-2.4.7/work/libtool-2.4.7/tests/testsuite.dir/079 Unimplemented option: -n ---------------------------------------------------------------------- Libraries have been installed in: /var/tmp/portage/sys-devel/libtool-2.4.7/work/libtool-2.4.7/tests/testsuite.dir/079 If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the '-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the 'LD_LIBRARY_PATH' environment variable during execution - add LIBDIR to the 'LD_RUN_PATH' environment variable during linking - use the '-Wl,-rpath -Wl,LIBDIR' linker flag - have your system administrator run these commands: - have your system administrator add LIBDIR to '/etc/ld.so.conf' See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. ---------------------------------------------------------------------- ./archive-in-archive.at:51: $LIBTOOL --mode=link --tag=CC --tag=disable-shared $CC $CFLAGS $LDFLAGS \ -o libbar.la bar.lo $libfoo -version-info 1:0:0 -rpath $thisdir stderr: stdout: *** Warning: Linking the shared library libbar.la against the *** static library libfoo.a is not portable! libtool: link: x86_64-gentoo-linux-musl-ar cr .libs/libbar.a libfoo.a bar.o libtool: link: x86_64-gentoo-linux-musl-ranlib .libs/libbar.a libtool: link: ( cd ".libs" && rm -f "libbar.la" && ln -s "../libbar.la" "libbar.la" ) ./archive-in-archive.at:54: $LIBTOOL --mode=install cp libbar.la $thisdir stderr: Unimplemented option: -n stdout: libtool: install: cp .libs/libbar.lai /var/tmp/portage/sys-devel/libtool-2.4.7/work/libtool-2.4.7/tests/testsuite.dir/079/libbar.la libtool: install: cp .libs/libbar.a /var/tmp/portage/sys-devel/libtool-2.4.7/work/libtool-2.4.7/tests/testsuite.dir/079/libbar.a libtool: install: chmod 644 /var/tmp/portage/sys-devel/libtool-2.4.7/work/libtool-2.4.7/tests/testsuite.dir/079/libbar.a libtool: install: x86_64-gentoo-linux-musl-ranlib /var/tmp/portage/sys-devel/libtool-2.4.7/work/libtool-2.4.7/tests/testsuite.dir/079/libbar.a libtool: finish: PATH="/var/tmp/portage/sys-devel/libtool-2.4.7/work/libtool-2.4.7/tests:/usr/lib/portage/python3.10/ebuild-helpers/xattr:/usr/lib/portage/python3.10/ebuild-helpers:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/sbin" ldconfig -n /var/tmp/portage/sys-devel/libtool-2.4.7/work/libtool-2.4.7/tests/testsuite.dir/079 ---------------------------------------------------------------------- Libraries have been installed in: /var/tmp/portage/sys-devel/libtool-2.4.7/work/libtool-2.4.7/tests/testsuite.dir/079 If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the '-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the 'LD_LIBRARY_PATH' environment variable during execution - add LIBDIR to the 'LD_RUN_PATH' environment variable during linking - use the '-Wl,-rpath -Wl,LIBDIR' linker flag - have your system administrator run these commands: - have your system administrator add LIBDIR to '/etc/ld.so.conf' See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. ---------------------------------------------------------------------- ./archive-in-archive.at:57: $AR -t $libbar | $GREP $libfoo stderr: stdout: libfoo.a ./archive-in-archive.at:57: exit code was 0, expected 1 79. archive-in-archive.at:27: 79. static library contains static library (archive-in-archive.at:27): expected failure (archive-in-archive.at:57)