| 1 |
On Friday 17 December 2010 14:55:03 Thomas Kahle wrote: |
| 2 |
> On 14:22 Fri 17 Dec , Christopher Schwan wrote: |
| 3 |
> > Mpir's configure scripts looks like its adding "-Wl,-z,noexecstack" if it |
| 4 |
> > detects a gcc+x86/amd64 configuration - so I guess noexecstack should |
| 5 |
> > work out of the box. If it does not I would consider this as broken. |
| 6 |
> |
| 7 |
> Yes, I saw that. The configure method fails directly, it just does *not* |
| 8 |
> add the ldflag (at least when configure is run by portage). |
| 9 |
> |
| 10 |
> I also tried to add "-Wl,-z,noexecstack" via append-ldflags, and it is |
| 11 |
> indeed appended as visible in the compile output, but the exec stacks |
| 12 |
> are still there and the QA warning comes up, so I guess we can consider |
| 13 |
> this broken and stick with your solution of patching the asm (which sill |
| 14 |
> works fine) |
| 15 |
|
| 16 |
Did you read http://www.gentoo.org/proj/en/hardened/gnu-stack.xml ? The |
| 17 |
document proposes a slightly different approach for assembler files: |
| 18 |
|
| 19 |
append-flags -Wa,--noexecstack |
| 20 |
|
| 21 |
Which tells the assembler to use --nostack (instead of telling the linker to |
| 22 |
use -z,noexecstack). |
| 23 |
|
| 24 |
> |
| 25 |
> Cheers, |
| 26 |
> Thomas |
| 27 |
|
| 28 |
Cheers, |
| 29 |
Christopher |
Archives