From 241e6dd3e92c4f215b8ac75379a4b5aeaeb92171 Mon Sep 17 00:00:00 2001 From: Julien Dusser Date: Sun, 7 Jan 2018 18:47:21 +0100 Subject: 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 --- toolchain/gcc/Config.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'toolchain/gcc/Config.in') diff --git a/toolchain/gcc/Config.in b/toolchain/gcc/Config.in index 0fe0ea2957..30ac137873 100644 --- a/toolchain/gcc/Config.in +++ b/toolchain/gcc/Config.in @@ -52,9 +52,9 @@ config GCC_DEFAULT_SSP help Use gcc configure option --enable-default-ssp to turn on -fstack-protector-strong by default. -config SSP_SUPPORT +config GCC_LIBSSP bool - prompt "Enable Stack-Smashing Protection support" if TOOLCHAINOPTS + prompt "Build gcc libssp" if TOOLCHAINOPTS depends on !USE_MUSL default y if !USE_MUSL help -- cgit v1.2.3