global: do not offer the renice option, let's the user handle that
author"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Fri Jan 29 23:14:53 2010 +0100 (2010-01-29)
changeset 1753fcc55af9aee5
parent 1752 2a0656d9c905
child 1757 c7495bd76985
global: do not offer the renice option, let's the user handle that

It's broken anyway. Eg.:
- user is already niced at 10
- user configures to renice at 5
- breaks because user is not allowed to 'boost' his/her nice value

Bette let the user handle the renice with:
nice -XX ct-ng 'action'
config/global/build-behave.in
scripts/crosstool-NG.sh.in
     1.1 --- a/config/global/build-behave.in	Sun Jan 24 22:53:51 2010 +0100
     1.2 +++ b/config/global/build-behave.in	Fri Jan 29 23:14:53 2010 +0100
     1.3 @@ -28,14 +28,6 @@
     1.4        Note: only the integer part of the load is allowed here (you can't enter
     1.5              0.75 for example).
     1.6  
     1.7 -config NICE
     1.8 -    int
     1.9 -    prompt "Nice level"
    1.10 -    default 0
    1.11 -    range 0 19
    1.12 -    help
    1.13 -      Renices the build process up.
    1.14 -
    1.15  config USE_PIPES
    1.16      bool
    1.17      prompt "Use -pipe"
     2.1 --- a/scripts/crosstool-NG.sh.in	Sun Jan 24 22:53:51 2010 +0100
     2.2 +++ b/scripts/crosstool-NG.sh.in	Fri Jan 29 23:14:53 2010 +0100
     2.3 @@ -97,9 +97,6 @@
     2.4  # Log real begining of build, now
     2.5  CT_DoLog INFO "Build started ${CT_STAR_DATE_HUMAN}"
     2.6  
     2.7 -# renice oursleves
     2.8 -CT_DoExecLog DEBUG renice ${CT_NICE} $$
     2.9 -
    2.10  CT_DoStep DEBUG "Dumping user-supplied crosstool-NG configuration"
    2.11  CT_DoExecLog DEBUG grep -E '^(# |)CT_' .config
    2.12  CT_EndStep