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_CFLAGS_FOR_BUILD
46 prompt "Extra build compiler flags"
49 Extra flags to pass to the build C and C++ compiler.
51 May be used to change the default features of the build
52 compiler such as turning off the stack protector or fortify.
54 config EXTRA_LDFLAGS_FOR_BUILD
56 prompt "Extra build linker flags"
59 Extra flags to pass to the build linker.
61 May be used to change the default features of the build
64 config EXTRA_CFLAGS_FOR_HOST
66 prompt "Extra host compiler flags"
69 Extra flags to pass to the host C and C++ compiler.
71 May be used to change the default features of the host
72 compiler such as turning off the stack protector or fortify.
74 config EXTRA_LDFLAGS_FOR_HOST
76 prompt "Extra host linker flags"
79 Extra flags to pass to the host linker.
81 May be used to change the default features of the host
86 prompt "Shell to use as CONFIG_SHELL"
87 default CONFIG_SHELL_BASH
90 config CONFIG_SHELL_SH
92 prompt "sh (the system shell)"
94 Use 'sh' as CONFIG_SHELL.
96 ./configure scripts and Makefiles make intensive use of calling
97 sub-shells. This is usually done by calling /bin/sh. /bin/sh ought
98 to be an at-least-POSIX-conformant shell (that is, able to interpret
101 On many (most?) systems, /bin/sh is a symlink to bash. On some other
102 systems (eg. Ubuntu, latest Debian), /bin/sh points to dash (or ash).
103 bash is a full-featured shell, with many extension to POSIX, but is
104 quite slow (see ection BUGS in the bash man page), while dash is
105 faster, with very few extensions to POSIX. On the other hand, some
106 ./configure scripts, although written to use /bin/sh, may really
107 require to be run by bash.
109 The default is to use bash, as some components (eg. GMP) will fail
110 to build with anything else than bash.
112 Unless you have a very strong reason not to (eg. you are debugging
113 the bashisms in a ./configure script), you should use the default,
116 config CONFIG_SHELL_ASH
118 prompt "ash (READ HELP!)"
120 Use 'ash' as CONFIG_SHELL.
122 See help for CONFIG_SHELL_SH, above, for more explanations.
124 NOTE: It is advised that you do NOT use ash as CONFIG_SHELL, as some
125 components are broken. If you decide to use ash, and the build breaks,
126 don't come moaning and set the CONFIG_SHELL to bash, below.
128 config CONFIG_SHELL_BASH
132 Use 'bash' as CONFIG_SHELL.
134 See help for CONFIG_SHELL_SH, above, for more explanations.
136 config CONFIG_SHELL_CUSTOM
138 prompt "custom shell"
140 Enter full path to the custom shell below.
142 See help for CONFIG_SHELL_SH, above, for more explanations.
146 # Do not put this into the choice above, because the choice
147 # is not available in BACKEND-mode, while we do want this to
148 # be set even in BACKEND-mode.
149 config CONFIG_SHELL_CUSTOM_PATH
151 prompt "Path to custom shell" if ! BACKEND
152 depends on CONFIG_SHELL_CUSTOM || BACKEND
156 # And we must use the ./configured bash...
159 default "/bin/sh" if CONFIG_SHELL_SH
160 default "/bin/ash" if CONFIG_SHELL_ASH
161 default "${bash}" if CONFIG_SHELL_BASH
162 default CONFIG_SHELL_CUSTOM_PATH if CONFIG_SHELL_CUSTOM || BACKEND