mmc-utils: don't set -D_FORTIFY_SOURCE in Makefile, take 2
authorMichael Heimpold <mhei@heimpold.de>
Sun, 30 Aug 2015 12:33:46 +0000 (14:33 +0200)
committerMichael Heimpold <mhei@heimpold.de>
Sun, 30 Aug 2015 12:33:46 +0000 (14:33 +0200)
commit0db8bac00cc787a494b84a92322aeb07cc852051
tree564af8588660c213d8ee8635a0b408c61151e6e2
parent0ec3a557677af9eb617e1451f5963148904e9e83
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>
utils/mmc-utils/Makefile
utils/mmc-utils/patches/001-properly-set-fortify-source-in-makefile.patch