Created attachment 401792 [details]
configure log on amd64
The latest update to stunnel-5.14 fails with the following error message:
>>> Emerging (1 of 1) net-misc/stunnel-5.14::gentoo
>>> Jobs: 0 of 1 complete, 1 running Load avg: 0.08, 0.03, 0.05*** Error in `/usr/lib
/gcc/i686-pc-linux-gnu/4.8.3/../../../../i686-pc-linux-gnu/bin/ld': corrupted double-linked list: 0x
>>> Jobs: 0 of 1 complete, 1 running Load avg: 0.00, 0.01, 0.05^C
Looks like the stunnel build triggers an error in the toolchain, see http://lists.opensuse.org/opensuse-bugs/2015-02/msg03775.html
A plain "configure" without ebuild and portage involved fails with the same error message on x86.
A plain "configure" on amd64 does not exhibit the error.
Created attachment 401794 [details]
build.log from the failing ebuild
The SUSE mailing list posting leads to their bug tracker, which in turn mentions https://sourceware.org/bugzilla/show_bug.cgi?id=16428 with patches. These were presumably merged into 2.25. Maybe stabilize .25 or backport those to 2.24?
I updated to binutils-2.25 and stunnel emerges without problems. Looks like a bintuilts update is the way to solve this.
Very much like bug 512734. Killing the ld process allows stunnel to finish building.
(In reply to Dirk Olmes from comment #1)
> Created attachment 401794 [details]
> build.log from the failing ebuild
The relevant lines are:
hecking if i686-pc-linux-gnu-gcc PIC flag -fPIC -DPIC works... yes
checking if i686-pc-linux-gnu-gcc static flag -static works... sandbox:stop caught signal 2 in pid 11680
sandbox:stop signal already caught and busy still cleaning up!
This is a dup of bug #533862 downstream and was dealt with upstream at
*** This bug has been marked as a duplicate of bug 533862 ***