1 # Options related to how the build behaves
3 comment "Build behavior"
7 prompt "Number of parallel jobs"
10 Number of jobs make will be allowed to run concurently.
11 Set this higher than the number of processors you have, but not too high.
12 A good rule of thumb is twice the number of processors you have.
14 Enter 1 (or 0) to have only one job at a time.
18 prompt "Maximum allowed load"
21 Specifies that no new jobs should be started if there are others jobs
22 running and the load average is at least this value.
24 Makes sense on SMP machines only.
26 Enter 0 to have no limit on the load average.
28 Note: only the integer part of the load is allowed here (you can't enter
37 Renices the build process up.
44 Use gcc's option -pipe to use pipes rather than temp files when building
49 prompt "Shell to use as CONFIG_SHELL"
50 default CONFIG_SHELL_SYSTEM
52 config CONFIG_SHELL_SH
54 prompt "sh (the system shell)"
56 Use 'sh' as CONFIG_SHELL.
58 ./configure scripts and Makefiles make intensive use of calling
59 sub-shells. This is usually done by calling /bin/sh. /bin/sh ought
60 to be an at-least-POSIX-conformant shell (that is, able to interpret
63 On many (most?) systems, /bin/sh is a symlink to bash. On some other
64 systems (eg. Ubuntu, latest Debian), /bin/sh points to dash (or ash).
65 bash is a full-featured shell, with many extension to POSIX, but is
66 quite slow (see ection BUGS in the bash man page), while dash is
67 faster, with very few extensions to POSIX. On the other hand, some
68 ./configure scripts, although written to use /bin/sh, may really
69 require to be run by bash.
71 The default is to use your system's /bin/sh shell. If you want to
72 run faster, you can select to use dash. If you have problems with
73 either the system shell or when using dash, then you can force to
76 config CONFIG_SHELL_ASH
80 Use 'ash' as CONFIG_SHELL.
82 See help for CONFIG_SHELL_SH, above, for more explanations.
88 default "sh" if CONFIG_SHELL_SH
89 default "ash" if CONFIG_SHELL_ASH