From b7184e66c07be704ce4e86d46c73e61ed85eb915 Mon Sep 17 00:00:00 2001 From: Thomas Petazzoni Date: Mon, 9 Nov 2015 21:25:11 +0100 Subject: ruby: explicitly disable SSP support The SSP support checks of the Ruby configure script do not do a full link, and therefore don't properly detect if SSP support is fully functional or not, which causes some build failures if the compiler supports -fstack-protector but the C library does not provide the SSP implementation. To avoid this, we explicitly tell ruby if SSP support is available or not. Fixes: http://autobuild.buildroot.net/results/001/00154b0142f51c197d5d53ae36f7adc4f8250d9d/ Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard --- package/ruby/ruby.mk | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/package/ruby/ruby.mk b/package/ruby/ruby.mk index 298493c0f1..17104b6d85 100644 --- a/package/ruby/ruby.mk +++ b/package/ruby/ruby.mk @@ -36,6 +36,10 @@ RUBY_CONF_ENV += ac_cv_func_dl_iterate_phdr=no RUBY_CONF_OPTS += --with-out-ext=fiddle endif +ifeq ($(BR2_TOOLCHAIN_HAS_SSP),) +RUBY_CONF_ENV += stack_protector=no +endif + # Force optionals to build before we do ifeq ($(BR2_PACKAGE_BERKELEYDB),y) RUBY_DEPENDENCIES += berkeleydb -- cgit v1.2.1