/usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib64/libunwind-x86_64.so: error adding symbols: file in wrong format collect2: error: ld returned 1 exit status ninja: build stopped: subcommand failed. * ERROR: sci-libs/ceres-solver-2.0.0::gentoo failed (compile phase): * ninja -v -j3 -l0 failed ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop-j3_abi32+64_debug-20210729-185806 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-11.2.0 * clang version 12.0.1 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/12/bin /usr/lib/llvm/12 12.0.1 Python 3.9.6 Available Ruby profiles: (none found) Available Rust versions: [1] rust-bin-1.53.0 * The following VMs are available for generation-2: 1) JamVM JDK 2.0.0 [jamvm] *) AdoptOpenJDK 8.292_p10 [openjdk-bin-8] Available Java Virtual Machines: [1] jamvm [2] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.10.4 HEAD of ::gentoo commit 7e88391f67e5d81c9183ae3e9ef48bb700a70f17 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Wed Aug 4 23:52:21 2021 +0000 2021-08-04 23:52:20 UTC emerge -qpvO sci-libs/ceres-solver [ebuild N ] sci-libs/ceres-solver-2.0.0 USE="openmp schur -cxsparse -doc -examples -gflags -lapack -sparse -test" ABI_X86="32 (64) (-x32)"
Created attachment 730226 [details] emerge-info.txt
Created attachment 730228 [details] emerge-history.txt
Created attachment 730230 [details] environment
Created attachment 730232 [details] etc.portage.tar.bz2
Created attachment 730234 [details] logs.tar.bz2
Created attachment 730236 [details] sci-libs:ceres-solver-2.0.0:20210805-005558.log
Created attachment 730238 [details] temp.tar.bz2
I was curious and checked if the problem was gone on v2.1.0, but it still happens there.
It's the multilib x86 portion of the build that fails due to presence of the 64-bit libunwind ; USE="-abi_x86_32" builds.
The unwind issue is brought indirectly by glog, whose glog-config.cmake simply does: find_dependency (Unwind 1.6.2) and uses its own FindUnwind which was broken until https://github.com/google/glog/pull/769/files#diff-d4308e6c6735dd82d755ac06d881951f963438a1929f6fca82a5593d8b15083bR55 (not tagged yet). I suggest to include a glog patch?