script: allow to pass any float value for CT_LOAD
authorSamuel Martin <s.martin49@gmail.com>
Sun Jan 27 17:54:19 2013 +0100 (2013-01-27)
changeset 3172edb17e96ca60
parent 3171 15f1160573a4
child 3173 16fdf4cf35b5
script: allow to pass any float value for CT_LOAD

Signed-off-by: Samuel Martin <s.martin49@gmail.com>
Message-Id: <b51acf21c72b4a8e882e.1359320015@laptop>
Patchwork-Id: 216062
config/global/build-behave.in
scripts/crosstool-NG.sh.in
     1.1 --- a/config/global/build-behave.in	Thu Jan 24 22:24:38 2013 +0100
     1.2 +++ b/config/global/build-behave.in	Sun Jan 27 17:54:19 2013 +0100
     1.3 @@ -19,19 +19,17 @@
     1.4        Enter 0 to set automatically based on how many processors the host has.
     1.5  
     1.6  config LOAD
     1.7 -    int
     1.8 +    string
     1.9      prompt "Maximum allowed load" if ! BACKEND
    1.10 -    default 0
    1.11 +    default ""
    1.12      help
    1.13        Specifies that no new jobs should be started if there are others jobs
    1.14        running and the load average is at least this value.
    1.15 -      
    1.16 -      Makes sense on SMP machines only.
    1.17 -      
    1.18 -      Enter 0 to have no limit on the load average.
    1.19 -      
    1.20 -      Note: only the integer part of the load is allowed here (you can't enter
    1.21 -            0.75 for example).
    1.22 +
    1.23 +      Leave to empty for no load limit.
    1.24 +
    1.25 +      Note: any float value is allowed and will be passed to the '-l' option
    1.26 +            of make (for further details, refer to the make manpage).
    1.27  
    1.28  config USE_PIPES
    1.29      bool
     2.1 --- a/scripts/crosstool-NG.sh.in	Thu Jan 24 22:24:38 2013 +0100
     2.2 +++ b/scripts/crosstool-NG.sh.in	Sun Jan 27 17:54:19 2013 +0100
     2.3 @@ -516,7 +516,7 @@
     2.4      AUTO_JOBS=$((`getconf _NPROCESSORS_ONLN 2> /dev/null || echo 0` + 1))
     2.5      [ ${CT_PARALLEL_JOBS} -eq 0 ] && JOBSFLAGS="${JOBSFLAGS} -j${AUTO_JOBS}"
     2.6      [ ${CT_PARALLEL_JOBS} -gt 0 ] && JOBSFLAGS="${JOBSFLAGS} -j${CT_PARALLEL_JOBS}"
     2.7 -    [ ${CT_LOAD} -ne 0 ] && JOBSFLAGS="${JOBSFLAGS} -l${CT_LOAD}"
     2.8 +    JOBSFLAGS="${JOBSFLAGS} -l${CT_LOAD}"
     2.9  
    2.10      # Now that we've set up $PATH and $CT_CFLAGS_FOR_HOST, sanity test that gcc
    2.11      # is runnable so that the user can troubleshoot problems if not.