diff options
| author | Matt Weber <matthew.weber@rockwellcollins.com> | 2018-09-17 16:21:51 -0500 |
|---|---|---|
| committer | Peter Korsgaard <peter@korsgaard.com> | 2018-10-20 12:53:03 +0200 |
| commit | 394bdd11fc1f741c88c89f0e71571d87a29ab627 (patch) | |
| tree | ae9c2ee26a4809b1846959abccad6f0d0ea60a52 /package/php/php.mk | |
| parent | f10822d151085bcbfecd0ecf2542ac5f5623fd9d (diff) | |
| download | buildroot-394bdd11fc1f741c88c89f0e71571d87a29ab627.tar.gz buildroot-394bdd11fc1f741c88c89f0e71571d87a29ab627.zip | |
BR2_FORTIFY*: toolchain wrapper limitation note
A note is added to tie off the discussion on why moving _FORTIFY_SOURCE
related flags into the toolchain wrapper doesn't currently work.
- Currently -D_FORTIFY_SOURCE and optimizations are passed through
CFLAGS
- Packages like linux-tools ignore CFLAGS entirely and some
autotools toolchain testing cases dependent on not using
CFLAGS.
- If FORTIFY_SOURCE is passed through the wrapper, then linux-tools
will no longer be able to ignore it, because it's enforced at a
lower-level and since the optimization -Os/g/1/2/3 are via CFLAGS,
there is no optimization flag set. Therefore linux-tools will do
all its configuration tests with FORTIFY_SOURCE forcefully enabled
at the wrapper level, but no optimization enabled, and consequently
tests will fail.
Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Diffstat (limited to 'package/php/php.mk')
0 files changed, 0 insertions, 0 deletions
