New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unknown section type: %progbits #65
Comments
Duh? This is indeed super weird. We can work around it using autoconf magic, but this is pretty annoying. |
http://www.gentoo.org/proj/en/hardened/gnu-stack.xml#doc_chap6 lists a second alternative, compiling with |
That sounds like a better option. Still.. #if statements not working is worrying. Can anybody running Gentoo check that the |
The relevant command from
Now it turns out there's the following subtlety, from http://stackoverflow.com/a/7190511:
Thus we want to call
Still, the |
Good catch. Hope it will work on case-insensitive filesystems as well. Let's give it a shot. |
Can you try with the current git master? |
It compiles as expected, fixed! |
Neat! And good to know! Thanks a lot for your report! |
The stack markings introduced in #60 lead to a compilation failure on OS X 10.8 using GCC 4.7 from MacPorts, with the following error:
This is rather odd given it's wrapped in an
#if
as follows:Neither of the two
defined
hold true.The text was updated successfully, but these errors were encountered: