From 70f87b89699f1ed99d14a174d0a32f3aa1ecb653 Mon Sep 17 00:00:00 2001
From: "Yann E. MORIN\"" <yann.morin.1998@anciens.enib.fr>
Date: Sun, 2 Aug 2009 23:50:22 +0200
Subject: [config] Warn againt using ash as CONFIG_SHELL

It apears that more and more ./configure scripts and Makefiles
make use of non-POSIXly correct shell constructs, that don't
work with ash.

For now, just warn the user against using ash, but keep it as
an option in case newer versions of the /broken/ components
come fixed, and we can again use ash, as it is in some cases
really faster than bash.

diff --git a/config/global/build-behave.in b/config/global/build-behave.in
index ca43a09..9ee8316 100644
--- a/config/global/build-behave.in
+++ b/config/global/build-behave.in
@@ -75,11 +75,15 @@ config CONFIG_SHELL_SH
       
 config CONFIG_SHELL_ASH
     bool
-    prompt "ash"
+    prompt "ash (READ HELP!)"
     help
       Use 'ash' as CONFIG_SHELL.
       
       See help for CONFIG_SHELL_SH, above, for more explanations.
+      
+      NOTE: It is advised that you do NOT use ash as CONFIG_SHELL, as some
+      components are broken. If you decide to use ash, and the build breaks,
+      don't come moaning and set the CONFIG_SHELL to bash, below.
 
 config CONFIG_SHELL_BASH
     bool
-- 
cgit v0.10.2-6-g49f6