Mercurialcrosstool-ng / changeset
summary | shortlog | changelog | graph | tags | branches | files | changeset | raw | bz2 | help
[config] Warn againt using ash as CONFIG_SHELL
author"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Aug 02 23:50:22 2009 +0200 (2009-08-02)
changeset 14478ef937cc57ba
parent 1446 0a44fc4d6bd0
child 1448 8a21b4be90cd
[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.
config/global/build-behave.in file | annotate | diff | revisions 
     1.1 --- a/config/global/build-behave.in	Sun Aug 02 20:06:44 2009 +0200
     1.2 +++ b/config/global/build-behave.in	Sun Aug 02 23:50:22 2009 +0200
     1.3 @@ -75,11 +75,15 @@
     1.4        
     1.5  config CONFIG_SHELL_ASH
     1.6      bool
     1.7 -    prompt "ash"
     1.8 +    prompt "ash (READ HELP!)"
     1.9      help
    1.10        Use 'ash' as CONFIG_SHELL.
    1.11        
    1.12        See help for CONFIG_SHELL_SH, above, for more explanations.
    1.13 +      
    1.14 +      NOTE: It is advised that you do NOT use ash as CONFIG_SHELL, as some
    1.15 +      components are broken. If you decide to use ash, and the build breaks,
    1.16 +      don't come moaning and set the CONFIG_SHELL to bash, below.
    1.17  
    1.18  config CONFIG_SHELL_BASH
    1.19      bool
crosstool-ng