diff options
| author | Michael Heimpold <mhei@heimpold.de> | 2015-08-30 14:33:46 +0200 |
|---|---|---|
| committer | Michael Heimpold <mhei@heimpold.de> | 2015-08-30 14:33:46 +0200 |
| commit | 0db8bac00cc787a494b84a92322aeb07cc852051 (patch) | |
| tree | 564af8588660c213d8ee8635a0b408c61151e6e2 /lang/python/files/python-package-dev.mk | |
| parent | 0ec3a557677af9eb617e1451f5963148904e9e83 (diff) | |
mmc-utils: don't set -D_FORTIFY_SOURCE in Makefile, take 2
Also already mentioned in ba4338d6f7753c77b03357aa74cc63771e94074a,
the security feature FORTIFY_SOURCE could be set globally.
The current approach tries to undefine and redefine it, however,
the order on the command line prevents this from being successfully, e.g.:
arm-openwrt-linux-muslgnueabi-gcc ... -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 ... -D_FORTIFY_SOURCE=1 ...
`---------------v-------------------' `--------v--------'
AM_CFLAGS OpenWrt params
So to have the original source (static) _FORTIFY_SOURCE=2 define,
the only option is to remove it from AM_CFLAGS completely, and
to pass it after the OpenWrt settings explicitely in the Makefile.
This should fix the buildbots finally.
Signed-off-by: Michael Heimpold <mhei@heimpold.de>
Diffstat (limited to 'lang/python/files/python-package-dev.mk')
0 files changed, 0 insertions, 0 deletions
