Created attachment 318710 [details] emerge fail log =dev-libs/mpfr-3.1.1 fails tests with clang-3.1-r4, latest stable =dev-libs/mpfr-3.0.1_p4 passes tests, I didn't test intermediates.
According to the attached log, this bug depends on the use of the gold linker: /usr/bin/x86_64-pc-linux-gnu-ld: internal error in relocate_tls, at /var/tmp/portage/sys-devel/binutils-2.22-r1/work/binutils-2.22/gold/x86_64.cc:3187 clang: error: linker command failed with exit code 1 (use -v to see invocation) The tests pass fine with the default ld.bfd linker. My fault for setting up the VM with ld.gold in the first place.
(In reply to comment #1) > According to the attached log, this bug depends on the use of the gold > linker: > > /usr/bin/x86_64-pc-linux-gnu-ld: internal error in relocate_tls, at > /var/tmp/portage/sys-devel/binutils-2.22-r1/work/binutils-2.22/gold/x86_64. > cc:3187 > clang: error: linker command failed with exit code 1 (use -v to see > invocation) > > The tests pass fine with the default ld.bfd linker. My fault for setting up > the VM with ld.gold in the first place. I've just tested ld.gold with current gcc, and tests seem to run fine. It may be a clang+gold problem then.
Just tested: dev-libs/mpfr-3.1.2-r1 builds fine with clang-3.4.2 and gold linker and passes tests just fine (binutils-2.23.2).
I retested with clang 3.7.1-r100 and clang-3.8_rc1-r100, ld.gold from binutils-2.25.1-r1 (latest stable): mpfr-3.1.3_p4 compiles and passes tests. I see that binutils-2.22-r1 is still in tree and stable, but considering the age of that release (late 2011) I guess most users will have upgraded by now, and the bug can be closed as OBSOLETE.
If it works with current stable binutils, that is indeed quite enough, thanks for checking!
