diff options
| author | Julien Dusser <julien.dusser@free.fr> | 2018-01-07 18:47:21 +0100 |
|---|---|---|
| committer | Hauke Mehrtens <hauke@hauke-m.de> | 2018-01-27 19:02:48 +0100 |
| commit | 241e6dd3e92c4f215b8ac75379a4b5aeaeb92171 (patch) | |
| tree | df5884c1112280f9d9c04f292e854e55e7b29bb1 /config/Config-build.in | |
| parent | 55779569eb817361222d653accd929a752b8327d (diff) | |
| download | mtk-20170518-241e6dd3e92c4f215b8ac75379a4b5aeaeb92171.zip mtk-20170518-241e6dd3e92c4f215b8ac75379a4b5aeaeb92171.tar.gz mtk-20170518-241e6dd3e92c4f215b8ac75379a4b5aeaeb92171.tar.bz2 | |
build: cleanup SSP_SUPPORT configure option
Configure variable SSP_SUPPORT is ambiguous for packages (tor, openssh,
avahi, freeswitch). It means 'toolchain supporting SSP', but for toolchain
and depends it means 'build gcc with libssp'.
Musl no longer uses libssp (1877bc9d8f), it has internal support, so
SSP_SUPPORT was disabled leading some package to not use SSP.
No information why Glibc and uClibc use libssp, but they may also provide
their own SSP support. uClibc used it own with commit 933b588e25 but it was
reverted in f3cacb9e84 without details.
Create an new configure GCC_LIBSSP and automatically enable SSP_SUPPORT
if either USE_MUSL or GCC_LIBSSP.
Signed-off-by: Julien Dusser <julien.dusser@free.fr>
Diffstat (limited to 'config/Config-build.in')
| -rw-r--r-- | config/Config-build.in | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/config/Config-build.in b/config/Config-build.in index 660da1c..a082a5e 100644 --- a/config/Config-build.in +++ b/config/Config-build.in @@ -210,11 +210,11 @@ menu "Global build settings" bool "None" config PKG_CC_STACKPROTECTOR_REGULAR bool "Regular" - select SSP_SUPPORT if !USE_MUSL + select GCC_LIBSSP if !USE_MUSL depends on KERNEL_CC_STACKPROTECTOR_REGULAR config PKG_CC_STACKPROTECTOR_STRONG bool "Strong" - select SSP_SUPPORT if !USE_MUSL + select GCC_LIBSSP if !USE_MUSL depends on !GCC_VERSION_4_8 depends on KERNEL_CC_STACKPROTECTOR_STRONG endchoice |