Summary: | =app-portage/eix-0.22.8 files contain writable and executable sections | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
Component: | Current packages | Assignee: | Martin Väth <martin> |
Status: | RESOLVED FIXED | ||
Severity: | QA | CC: | darkside, jlec |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Build log |
Description
Agostino Sarubbo
2011-06-02 11:15:43 UTC
Although it is not obvious, this is a duplicate of bug 364317 Actually it is a gcc-4.6 issue with lto which will hopefully be fixed in gcc-4.6.1 (to check this, I still postpone the next eix release). It appears that the other problem of bug 364317 is fixed in gcc-4.6.1. To my surprise, the executable+writable sections are still reported by scanelf -F '%e %p' /usr/bin/eix This looks like a bug in scanelf to me since readelf -S /usr/bin/eix does not exhibit such sections. In fact, the output of readelf -S seems to be identical, no matter whether -flto is used or not, only scanelf reports a different result with -flto (even if -flto is used only for compiling and not for linking). So unless somebody explains to me that I am misunderstanding something, I will consider this bug as a false positive of portage. I will leave the bug open so that people obtaining the message can find it. For people reading this bug: Please do not leave "me too" messages but only comment if you really have new information. Thank you. Finally, I found time to look into the issue: The problem is that -flto seems to turn on execstack. I believe that this is a bug in gcc-4.6. The solution seems to be to add -Wl,-z,noexecstack to LDFLAGS. At least, eix seems to have no problems with this combination of options, so I doubt that -flto *really* needs execstack. This is now in eix-0.22.10 which I released immediately (some minutes ago). I'll try it Fixed in eix-0.22.10. Closing a eix-0.22.10 is in tree now. |