Summary: | dev-libs/libbsd-0.5.2 - configure: error: missing required GNU .init_array section support (-flto caused?) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Craig Andrews <candrews> |
Component: | [OLD] Library | Assignee: | Freedesktop bugs <freedesktop-bugs> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | toolchain |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
dev-libs:libbsd-0.5.2:20130611-000515.log
config.log |
Description
Craig Andrews
2013-06-11 00:17:27 UTC
Created attachment 350718 [details]
dev-libs:libbsd-0.5.2:20130611-000515.log
Works fine here with latest gcc on 64bit. It says: !!! Please attach the following file when seeking support: !!! /var/tmp/portage/dev-libs/libbsd-0.5.2/work/libbsd-0.5.2/config.log * ERROR: dev-libs/libbsd-0.5.2 failed (configure phase): * econf failed Created attachment 350724 [details]
config.log
I don't see any compile errors, but the ./conftest is resulting '1' instead of '0' like it should. And I see you have "lto" enabled which prints this at sys-devel/gcc emerge: * LTO support is still experimental and unstable. Any bug reports * about LTO that do not include an upstream patch will be closed as * invalid. So I'm thinking this is miscompiled binary caused by -flto It is, and so we don't care. Take it upstream. (In reply to Ryan Hill from comment #5) > It is, and so we don't care. Take it upstream. You're right - I'm sincerely apologize for wasting everyone's time. I should have disabled lto and re-tested before reporting this issue. |