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 <stilor@att.net>

3 files changed, 11 insertions, 23 deletions

diff --git a/config/global/build-behave.in b/config/global/build-behave.in
index 9ad54384..d3298eaa 100644
--- a/config/global/build-behave.in
+++ b/config/global/build-behave.in
@@ -2,12 +2,9 @@
 
 comment "Build behavior"
 
-comment "Build options hiden"
-    depends on BACKEND
-
 config PARALLEL_JOBS
     int
-    prompt "Number of parallel jobs" if ! BACKEND
+    prompt "Number of parallel jobs"
     default 0
     help
       Number of jobs make will be allowed to run concurently.
@@ -20,7 +17,7 @@ config PARALLEL_JOBS
 
 config LOAD
     string
-    prompt "Maximum allowed load" if ! BACKEND
+    prompt "Maximum allowed load"
     default ""
     help
       Specifies that no new jobs should be started if there are others jobs
@@ -33,7 +30,7 @@ config LOAD
 
 config USE_PIPES
     bool
-    prompt "Use -pipe" if ! BACKEND
+    prompt "Use -pipe"
     default y
     help
       Use gcc's option -pipe to use pipes rather than temp files when building
@@ -83,7 +80,6 @@ choice
     bool
     prompt "Shell to use as CONFIG_SHELL"
     default CONFIG_SHELL_BASH
-    depends on ! BACKEND
 
 config CONFIG_SHELL_SH
     bool
@@ -141,13 +137,10 @@ config CONFIG_SHELL_CUSTOM
 
 endchoice
 
-# Do not put this into the choice above, because the choice
-# is not available in BACKEND-mode, while we do want this to
-# be set even in BACKEND-mode.
 config CONFIG_SHELL_CUSTOM_PATH
     string
-    prompt "Path to custom shell" if ! BACKEND
-    depends on CONFIG_SHELL_CUSTOM || BACKEND
+    prompt "Path to custom shell"
+    depends on CONFIG_SHELL_CUSTOM
     default "/bin/sh"
 
 # Ditto.
@@ -157,4 +150,4 @@ config CONFIG_SHELL
     default "/bin/sh"                   if CONFIG_SHELL_SH
     default "/bin/ash"                  if CONFIG_SHELL_ASH
     default "${bash}"                   if CONFIG_SHELL_BASH
-    default CONFIG_SHELL_CUSTOM_PATH    if CONFIG_SHELL_CUSTOM || BACKEND
+    default CONFIG_SHELL_CUSTOM_PATH    if CONFIG_SHELL_CUSTOM
diff --git a/config/global/ct-behave.in b/config/global/ct-behave.in
index a57c7984..42171e4d 100644
--- a/config/global/ct-behave.in
+++ b/config/global/ct-behave.in
@@ -63,7 +63,6 @@ config ALLOW_BUILD_AS_ROOT_SURE
 config DEBUG_CT
     bool
     prompt "Debug crosstool-NG"
-    depends on ! BACKEND
     help
       Say 'y' here to get some options regarding debugging crosstool-NG.
 
diff --git a/config/global/paths.in b/config/global/paths.in
index 5313d0d0..39e15f35 100644
--- a/config/global/paths.in
+++ b/config/global/paths.in
@@ -4,7 +4,7 @@ comment "Paths"
 
 config LOCAL_TARBALLS_DIR
     string
-    prompt "Local tarballs directory" if ! BACKEND
+    prompt "Local tarballs directory"
     default "${HOME}/src"
     help
       If you have previously downloaded the tarballs, enter the PATH where
@@ -12,8 +12,8 @@ config LOCAL_TARBALLS_DIR
 
 config SAVE_TARBALLS
     bool
-    prompt "Save new tarballs" if ! BACKEND
-    depends on LOCAL_TARBALLS_DIR != "" || BACKEND
+    prompt "Save new tarballs"
+    depends on LOCAL_TARBALLS_DIR != ""
     default y
     help
       If you say 'y' here, new downloaded tarballs will be saved in the
@@ -21,7 +21,7 @@ config SAVE_TARBALLS
 
 config WORK_DIR
     string
-    prompt "Working directory" if ! BACKEND
+    prompt "Working directory"
     default "${CT_TOP_DIR}/.build"
     help
       Set this to the directory where all build actions will be done.
@@ -46,7 +46,7 @@ config BUILD_TOP_DIR
 
 config PREFIX_DIR
     string
-    prompt "Prefix directory" if ! BACKEND
+    prompt "Prefix directory"
     default "${CT_PREFIX:-${HOME}/x-tools}/${CT_HOST:+HOST-${CT_HOST}/}${CT_TARGET}"
     help
       This is the path the toolchain will run from.
@@ -55,7 +55,6 @@ config RM_RF_PREFIX_DIR
     bool
     prompt "|  Remove the prefix dir prior to building"
     default y
-    depends on !BACKEND
     help
       If you say 'y' here, then PREFIX_DIR (above) will be eradicated
       prior to the toolchain is built.
@@ -69,9 +68,6 @@ config RM_RF_PREFIX_DIR
       it into a directory with pre-install, unrelated programs, it would be
       damageable to remove that directory. In this case, you may want to
       say 'n' here.
-      
-      Note that when acting as a backend, this option is not available, and
-      is forced to 'n'.
 
 config REMOVE_DOCS
     bool