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 to have only one job at a time.
19 Enter 0 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
44 config EXTRA_FLAGS_FOR_HOST
46 prompt "Extra host compiler flags"
49 Extra flags to pass to the host C and C++ compiler.
51 May be used to change the default features of the host
52 compiler such as turning off the stack protector or fortify.
56 prompt "Shell to use as CONFIG_SHELL"
57 default CONFIG_SHELL_BASH
60 config CONFIG_SHELL_SH
62 prompt "sh (the system shell)"
64 Use 'sh' as CONFIG_SHELL.
66 ./configure scripts and Makefiles make intensive use of calling
67 sub-shells. This is usually done by calling /bin/sh. /bin/sh ought
68 to be an at-least-POSIX-conformant shell (that is, able to interpret
71 On many (most?) systems, /bin/sh is a symlink to bash. On some other
72 systems (eg. Ubuntu, latest Debian), /bin/sh points to dash (or ash).
73 bash is a full-featured shell, with many extension to POSIX, but is
74 quite slow (see ection BUGS in the bash man page), while dash is
75 faster, with very few extensions to POSIX. On the other hand, some
76 ./configure scripts, although written to use /bin/sh, may really
77 require to be run by bash.
79 The default is to use bash, as some components (eg. GMP) will fail
80 to build with anything else than bash.
82 Unless you have a very strong reason not to (eg. you are debugging
83 the bashisms in a ./configure script), you should use the default,
86 config CONFIG_SHELL_ASH
88 prompt "ash (READ HELP!)"
90 Use 'ash' as CONFIG_SHELL.
92 See help for CONFIG_SHELL_SH, above, for more explanations.
94 NOTE: It is advised that you do NOT use ash as CONFIG_SHELL, as some
95 components are broken. If you decide to use ash, and the build breaks,
96 don't come moaning and set the CONFIG_SHELL to bash, below.
98 config CONFIG_SHELL_BASH
102 Use 'bash' as CONFIG_SHELL.
104 See help for CONFIG_SHELL_SH, above, for more explanations.
106 config CONFIG_SHELL_CUSTOM
108 prompt "custom shell"
110 Enter full path to the custom shell below.
112 See help for CONFIG_SHELL_SH, above, for more explanations.
116 # Do not put this into the choice above, because the choice
117 # is not available in BACKEND-mode, while we do want this to
118 # be set even in BACKEND-mode.
119 config CONFIG_SHELL_CUSTOM_PATH
121 prompt "Path to custom shell" if ! BACKEND
122 depends on CONFIG_SHELL_CUSTOM || BACKEND
126 # And we must use the ./configured bash...
129 default "/bin/sh" if CONFIG_SHELL_SH
130 default "/bin/ash" if CONFIG_SHELL_ASH
131 default "${bash}" if CONFIG_SHELL_BASH
132 default CONFIG_SHELL_CUSTOM_PATH if CONFIG_SHELL_CUSTOM || BACKEND