Am 20.02.2014 14:53, schrieb Markos Chandras:
> On 02/20/2014 12:53 PM, Richard Weinberger wrote:
>> On Thu, Feb 20, 2014 at 1:46 PM, Markos Chandras
>> wrote:
>>> On 02/07/2014 05:15 PM, Markos Chandras wrote:
In case the compiler does not support the stack-protector option,
unset
On 02/20/2014 12:53 PM, Richard Weinberger wrote:
On Thu, Feb 20, 2014 at 1:46 PM, Markos Chandras
wrote:
On 02/07/2014 05:15 PM, Markos Chandras wrote:
In case the compiler does not support the stack-protector option,
unset the flag to avoid build failures. Printing a warning is enough
to le
On Thu, Feb 20, 2014 at 1:46 PM, Markos Chandras
wrote:
> On 02/07/2014 05:15 PM, Markos Chandras wrote:
>>
>> In case the compiler does not support the stack-protector option,
>> unset the flag to avoid build failures. Printing a warning is enough
>> to let the user know that this flag will not b
On 02/07/2014 05:15 PM, Markos Chandras wrote:
In case the compiler does not support the stack-protector option,
unset the flag to avoid build failures. Printing a warning is enough
to let the user know that this flag will not be used.
Fixes the following build problem when using a toolchain whic
On 02/07/2014 05:15 PM, Markos Chandras wrote:
In case the compiler does not support the stack-protector option,
unset the flag to avoid build failures. Printing a warning is enough
to let the user know that this flag will not be used.
Fixes the following build problem when using a toolchain whic
In case the compiler does not support the stack-protector option,
unset the flag to avoid build failures. Printing a warning is enough
to let the user know that this flag will not be used.
Fixes the following build problem when using a toolchain which does
not support the -fstack-protector-strong f
6 matches
Mail list logo