summaryrefslogtreecommitdiffstats
path: root/package/gcc/gcc-final/gcc-final.mk
diff options
context:
space:
mode:
authorArnout Vandecappelle <arnout@mind.be>2015-10-04 13:28:43 +0100
committerPeter Korsgaard <peter@korsgaard.com>2015-10-04 18:22:20 +0200
commit2f8dc29c1d9f2adda850dead5325e422715d251e (patch)
tree6ab9ce613902d0219296c298fed38c73825e9781 /package/gcc/gcc-final/gcc-final.mk
parent919c06c28295f19ca49459b98d8954148b381360 (diff)
downloadbuildroot-2f8dc29c1d9f2adda850dead5325e422715d251e.tar.gz
buildroot-2f8dc29c1d9f2adda850dead5325e422715d251e.zip
gcc: remove unsafe patch check (poison system dirs) patch
Now that the calls to gcc always pass through the toolchain wrapper, it is no longer necessary to patch gcc to support poisoning. This does have the disadvantage that there is no unsafe path check for libc, libgcc and libstdc++ (all of these are built before the wrapper exists). But we can assume that the toolchain components themselves should be pretty safe. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Reviewed-by: Romain Naour <romain.naour@openwide.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Diffstat (limited to 'package/gcc/gcc-final/gcc-final.mk')
-rw-r--r--package/gcc/gcc-final/gcc-final.mk1
1 files changed, 0 insertions, 1 deletions
diff --git a/package/gcc/gcc-final/gcc-final.mk b/package/gcc/gcc-final/gcc-final.mk
index 2c16fdf6b3..a5be3c73ea 100644
--- a/package/gcc/gcc-final/gcc-final.mk
+++ b/package/gcc/gcc-final/gcc-final.mk
@@ -50,7 +50,6 @@ GCC_FINAL_CROSS_LANGUAGES = $(subst $(space),$(comma),$(GCC_FINAL_CROSS_LANGUAGE
HOST_GCC_FINAL_CONF_OPTS = \
$(HOST_GCC_COMMON_CONF_OPTS) \
--enable-languages=$(GCC_FINAL_CROSS_LANGUAGES) \
- --enable-poison-system-directories \
--with-build-time-tools=$(HOST_DIR)/usr/$(GNU_TARGET_NAME)/bin
HOST_GCC_FINAL_GCC_LIB_DIR = $(HOST_DIR)/usr/$(GNU_TARGET_NAME)/lib*
OpenPOWER on IntegriCloud