Executable memory: some apps that work on RH9 don't on FC1

[Mike A. Harris]

On Mon, 17 Nov 2003, Neal D. Becker wrote:

>> If a program say takes address of a nested function, GCC knows it needs
>> executable stack and arranges things automatically.
>> Otherwise, either an object file can be marked as needing executable
>> stack (with -Wa,--execstack; at least one such object will make the whole
>> shared library or binary requiring executable stack), or during link
>> time with -Wl,-z,execstack or after it using execstack(8) utility.
                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> The defaults are such that programs and/or libraries compiled/linked
>> on <= RHL9 are always assumed to potentially require executable stack,
>> but if you build a new program on FC1, you really need to tell the
>> toolchain about it.
>>
>
>Is it possible to mark executables, without requiring relinking?



-- 
Mike A. Harris