From 2f286ce5ab5f9938e504549726bf25acc5bdfe4b Mon Sep 17 00:00:00 2001 From: Alexey Neyman Date: Sat, 22 Apr 2017 23:51:05 -0700 Subject: Retire BACKEND stuff ... it is possible to just not set it in the configuration, why force it? It just increases the complexity in Kconfig. Signed-off-by: Alexey Neyman --- kconfig/kconfig.mk | 5 ----- 1 file changed, 5 deletions(-) (limited to 'kconfig') diff --git a/kconfig/kconfig.mk b/kconfig/kconfig.mk index 955ae0bb..c82e5022 100644 --- a/kconfig/kconfig.mk +++ b/kconfig/kconfig.mk @@ -8,11 +8,6 @@ # Top file of crosstool-NG configuration export KCONFIG_TOP = $(CT_LIB_DIR)/config/config.in -export CT_IS_A_BACKEND:=$(CT_IS_A_BACKEND) -export CT_BACKEND_ARCH:=$(CT_BACKEND_ARCH) -export CT_BACKEND_KERNEL:=$(CT_BACKEND_KERNEL) -export CT_BACKEND_LIBC:=$(CT_BACKEND_LIBC) - # We need CONF for savedefconfig in scripts/saveSample.sh export CONF := $(CT_LIB_DIR)/kconfig/conf MCONF := $(CT_LIB_DIR)/kconfig/mconf -- cgit v1.2.3