/bin/sh ../libtool --tag=CXX --mode=link x86_64-pc-linux-gnu-g++ -fopenmp -O2 -pipe -march=native -std=c++11 -Wextra -Wall -Wsign-promo -Woverloaded-virtual -Wendif-labels -Wno-unused -Wno-deprecated -Wno-long-long -Wno-parentheses -fno-nonansi-builtins -mieee-fp -fno-strict-aliasing -iquote . -DNDEBUG -pthread -Wl,-O1 -Wl,--as-needed -o VAAL0_5 VAAL0_5.o libVAAL.a libtool: link: x86_64-pc-linux-gnu-g++ -fopenmp -O2 -pipe -march=native -std=c++11 -Wextra -Wall -Wsign-promo -Woverloaded-virtual -Wendif-labels -Wno-unused -Wno-deprecated -Wno-long-long -Wno-parentheses -fno-nonansi-builtins -mieee-fp -fno-strict-aliasing -iquote . -DNDEBUG -pthread -Wl,-O1 -o VAAL0_5 VAAL0_5.o -Wl,--as-needed libVAAL.a -pthread -fopenmp /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lieee collect2: error: ld returned 1 exit status make[2]: *** [Makefile:891: VAAL0_5] Error 1 make[2]: Leaving directory '/var/tmp/portage/sci-biology/vaal-46233-r2/work/vaal-46233/src' ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-no-multilib-hardened_test_20180215-173621 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.6.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv sci-biology/vaal
Created attachment 519756 [details] emerge-info.txt
Created attachment 519758 [details] emerge-history.txt
Created attachment 519760 [details] environment
Created attachment 519762 [details] etc.portage.tbz2
Created attachment 519764 [details] logs.tbz2
Created attachment 519766 [details] sci-biology:vaal-46233-r2:20180216-114706.log
Created attachment 519768 [details] temp.tbz2
This is caused by -mieee-fp, which makes gcc link (errorneously) to libieee.a ... libieee.a was already an empty archive in the last versions, and the behaviour of -mieee-fp is default now on linux (not from gcc side, but from glibc side). So this is a mess-up / bad interaction between glibc and gcc. See also https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84829 I'm going to patch that compiler flag out of the package; shouldnt hurt. Long run we need the patches from above bug backported into gcc.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c24d4349f4e48f2a8aeda81be28d40e91d979f40 commit c24d4349f4e48f2a8aeda81be28d40e91d979f40 Author: Andreas K. Hüttel <dilfridge@gentoo.org> AuthorDate: 2018-09-29 20:33:49 +0000 Commit: Andreas K. Hüttel <dilfridge@gentoo.org> CommitDate: 2018-09-29 20:34:30 +0000 sci-biology/vaal: Add build fix for glibc 2.27 Closes: https://bugs.gentoo.org/647878 Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org> Package-Manager: Portage-2.3.49, Repoman-2.3.10 sci-biology/vaal/files/vaal-46233-libieee.patch | 12 ++++++++++++ sci-biology/vaal/vaal-46233-r2.ebuild | 3 ++- 2 files changed, 14 insertions(+), 1 deletion(-)
