Summary: | net-misc/stunnel fails configure on x86 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dirk Olmes <dirk.olmes> |
Component: | Current packages | Assignee: | Anthony Basile <blueness> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | gentoo, infoman1985 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
configure log on amd64
build.log from the failing ebuild |
Description
Dirk Olmes
2015-04-22 11:47:11 UTC
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 https://sourceware.org/bugzilla/show_bug.cgi?id=16428 *** This bug has been marked as a duplicate of bug 533862 *** |