From 4fee9155f396cb2bcfe707f78aa4332837520f93 Mon Sep 17 00:00:00 2001
From: Waldemar Brodkorb <wbx@uclibc-ng.org>
Date: Tue, 7 Jun 2016 04:14:23 +0200
Subject: ssp: remove SSP legacy code

Nobody should use gcc 3.3 nowadays.
---
 extra/Configs/Config.in | 16 ----------------
 1 file changed, 16 deletions(-)

(limited to 'extra/Configs')

diff --git a/extra/Configs/Config.in b/extra/Configs/Config.in
index f3494db99..a21bdac2f 100644
--- a/extra/Configs/Config.in
+++ b/extra/Configs/Config.in
@@ -2151,22 +2151,6 @@ config UCLIBC_HAS_SSP
 
 	  Most people will answer N.
 
-config UCLIBC_HAS_SSP_COMPAT
-	bool "Support for gcc-3.x propolice smashing stack protector"
-	depends on UCLIBC_HAS_SSP
-	help
-	  Add gcc-3.x propolice smashing stack protector to the library.
-
-	  This requires a patched version of GCC, supporting the
-	  -fstack-protector[-all] options, with the __guard and
-	  __stack_smash_handler functions removed from libgcc.
-	  These functions are added to ldso/libc instead.
-
-	  More information at:
-	  <http://www.research.ibm.com/trl/projects/security/ssp/>
-
-	  Most people will answer N.
-
 config SSP_QUICK_CANARY
 	bool "Use simple guard values without accessing /dev/urandom"
 	depends on UCLIBC_HAS_SSP
-- 
cgit v1.2.3