1 # Options related to how the build behaves
3 comment "Build behavior"
5 comment "Build options hiden"
10 prompt "Number of parallel jobs" if ! BACKEND
13 Number of jobs make will be allowed to run concurently.
14 Set this higher than the number of processors you have, but not too high.
15 A good rule of thumb is twice the number of processors you have.
17 Enter 1 (or 0) to have only one job at a time.
19 Enter -1 to set automatically based on how many processors the host has.
23 prompt "Maximum allowed load" if ! BACKEND
26 Specifies that no new jobs should be started if there are others jobs
27 running and the load average is at least this value.
29 Makes sense on SMP machines only.
31 Enter 0 to have no limit on the load average.
33 Note: only the integer part of the load is allowed here (you can't enter
38 prompt "Use -pipe" if ! BACKEND
41 Use gcc's option -pipe to use pipes rather than temp files when building
46 prompt "Shell to use as CONFIG_SHELL"
47 default CONFIG_SHELL_BASH
50 config CONFIG_SHELL_SH
52 prompt "sh (the system shell)"
54 Use 'sh' as CONFIG_SHELL.
56 ./configure scripts and Makefiles make intensive use of calling
57 sub-shells. This is usually done by calling /bin/sh. /bin/sh ought
58 to be an at-least-POSIX-conformant shell (that is, able to interpret
61 On many (most?) systems, /bin/sh is a symlink to bash. On some other
62 systems (eg. Ubuntu, latest Debian), /bin/sh points to dash (or ash).
63 bash is a full-featured shell, with many extension to POSIX, but is
64 quite slow (see ection BUGS in the bash man page), while dash is
65 faster, with very few extensions to POSIX. On the other hand, some
66 ./configure scripts, although written to use /bin/sh, may really
67 require to be run by bash.
69 The default is to use bash, as some components (eg. GMP) will fail
70 to build with anything else than bash.
72 config CONFIG_SHELL_ASH
74 prompt "ash (READ HELP!)"
76 Use 'ash' as CONFIG_SHELL.
78 See help for CONFIG_SHELL_SH, above, for more explanations.
80 NOTE: It is advised that you do NOT use ash as CONFIG_SHELL, as some
81 components are broken. If you decide to use ash, and the build breaks,
82 don't come moaning and set the CONFIG_SHELL to bash, below.
84 config CONFIG_SHELL_BASH
88 Use 'bash' as CONFIG_SHELL.
90 See help for CONFIG_SHELL_SH, above, for more explanations.
92 config CONFIG_SHELL_CUSTOM
96 Enter full path to the custom shell below.
98 See help for CONFIG_SHELL_SH, above, for more explanations.
104 default "sh" if CONFIG_SHELL_SH
105 default "ash" if CONFIG_SHELL_ASH
106 default "bash" if CONFIG_SHELL_BASH
107 default "custom" if CONFIG_SHELL_CUSTOM || BACKEND
109 config CONFIG_SHELL_CUSTOM_PATH
111 prompt "Path to custom shell" if ! BACKEND
112 depends on CONFIG_SHELL_CUSTOM || BACKEND