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'
This commit is contained in:
Yann E. MORIN" 2010-01-29 23:14:53 +01:00
parent 3bd33664df
commit 88d3a95eca
2 changed files with 0 additions and 11 deletions

View File

@ -28,14 +28,6 @@ config LOAD
Note: only the integer part of the load is allowed here (you can't enter Note: only the integer part of the load is allowed here (you can't enter
0.75 for example). 0.75 for example).
config NICE
int
prompt "Nice level"
default 0
range 0 19
help
Renices the build process up.
config USE_PIPES config USE_PIPES
bool bool
prompt "Use -pipe" prompt "Use -pipe"

View File

@ -97,9 +97,6 @@ CT_STAR_DATE_HUMAN=$(CT_DoDate +%Y%m%d.%H%M%S)
# Log real begining of build, now # Log real begining of build, now
CT_DoLog INFO "Build started ${CT_STAR_DATE_HUMAN}" CT_DoLog INFO "Build started ${CT_STAR_DATE_HUMAN}"
# renice oursleves
CT_DoExecLog DEBUG renice ${CT_NICE} $$
CT_DoStep DEBUG "Dumping user-supplied crosstool-NG configuration" CT_DoStep DEBUG "Dumping user-supplied crosstool-NG configuration"
CT_DoExecLog DEBUG grep -E '^(# |)CT_' .config CT_DoExecLog DEBUG grep -E '^(# |)CT_' .config
CT_EndStep CT_EndStep