rdlibtool --silent --tag=CXX --mode=link --silent /usr/bin/x86_64-pc-linux-gnu-g++ -Wl,-O1 -Wl,--as-needed -Wl,--defsym=__gentoo_check_ldflags__=0 -shared Makefile dkid.lo dkinfo.lo dkcommctx.lo docker-fd.lo ../pluglib.lo dkid.h dkinfo.h dkcommctx.h docker-fd.h -o docker-fd.la -rpath /usr/lib64 -module -export-dynamic -avoid-version dkid.h:30:10: fatal error: bacula.h: No such file or directory 30 | #include "bacula.h" | ^~~~~~~~~~ compilation terminated. ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_no-multilib-20210331-001544 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10.2.0 * clang version 11.1.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/11/bin /usr/lib/llvm/11 11.1.0 Python 3.8.8 Available Ruby profiles: (none found) Available Rust versions: [1] rust-1.50.0 * The following VMs are available for generation-2: *) AdoptOpenJDK 8.282_p08 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 system-vm timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Thu Apr 1 20:27:01 UTC 2021 emerge -qpvO app-backup/bacula [ebuild N ] app-backup/bacula-9.6.7 USE="acl batch-insert ipv6 readline sqlite ssl tcpd -X -bacula-clientonly -bacula-nodir -bacula-nosd -examples (-libressl) -logwatch -mysql -postgres -qt5 -static -vim-syntax"
Created attachment 696843 [details] emerge-info.txt
Created attachment 696846 [details] app-backup:bacula-9.6.7:20210401-203625.log
Created attachment 696849 [details] emerge-history.txt
Created attachment 696852 [details] environment
Created attachment 696855 [details] etc.portage.tar.bz2
Created attachment 696858 [details] logs.tar.bz2
Created attachment 696861 [details] temp.tar.bz2
Possibly slibtool related given how.. weird this mis?
No idea about the original issue which I have not reproduced, but I fixed what slibtool issues I did find in the referenced PR. I have not yet received a confirmation e-mail for their bug tracker so maybe someone else can try to upstream the patch?
Closed in favor of bug 790140 which actually reflects the errors I am seeing. This specific issue perhaps was already fixed somewhere else?