[Buildroot] [PATCH] Config.in: security hardening: disable FORTIFY_SOURCE for gcc < 6
Peter Korsgaard
peter at korsgaard.com
Mon Nov 5 22:17:46 UTC 2018
>>>>> "Matthew" == Matthew Weber <matthew.weber at rockwellcollins.com> writes:
> Romain ,
> On Mon, Nov 5, 2018, 14:07 Romain Naour <romain.naour at gmail.com wrote:
>> As reported in the bug report [1], gcc < 6 doesn't build when
>> FORTIFY_SOURCE is set to 1 or 2. The issue is related to the
>> upstream bug report [2] but the patch fixing the issue for gcc 6
>> has not been backported to earlier gcc versions.
>>
>> Add a dependency on gcc at least version 6 to BR2_FORTIFY_SOURCE_1
>> and BR2_FORTIFY_SOURCE_2.
>>
> Sorry about the HTML email.
> Could this dependency be conditional on if a internal toolchain is used?
Ahh yes, if this is really about *building* gcc, then it should be
depends on !BR2_TOOLCHAIN_BUILDROOT || BR2_TOOLCHAIN_GCC_AT_LEAST_6
--
Bye, Peter Korsgaard
More information about the buildroot
mailing list