yann@445: # Options related to how the build behaves
yann@121: 
yann@121: comment "Build behavior"
yann@121: 
yann@1866: comment "Build options hiden"
yann@1866:     depends on BACKEND
yann@1866: 
yann@1: config PARALLEL_JOBS
yann@1:     int
yann@1866:     prompt "Number of parallel jobs" if ! BACKEND
yann@2716:     default 0
yann@1:     help
yann@1:       Number of jobs make will be allowed to run concurently.
yann@1:       Set this higher than the number of processors you have, but not too high.
yann@1:       A good rule of thumb is twice the number of processors you have.
yann@1:       
yann@2716:       Enter 1 to have only one job at a time.
yann@1: 
yann@2716:       Enter 0 to set automatically based on how many processors the host has.
michael@2695: 
yann@1: config LOAD
yann@1:     int
yann@1866:     prompt "Maximum allowed load" if ! BACKEND
yann@1:     default 0
yann@1:     help
yann@1:       Specifies that no new jobs should be started if there are others jobs
yann@1:       running and the load average is at least this value.
yann@1:       
yann@1:       Makes sense on SMP machines only.
yann@1:       
yann@1:       Enter 0 to have no limit on the load average.
yann@1:       
yann@1:       Note: only the integer part of the load is allowed here (you can't enter
yann@1:             0.75 for example).
yann@1: 
yann@1: config USE_PIPES
yann@1:     bool
yann@1866:     prompt "Use -pipe" if ! BACKEND
yann@1:     default y
yann@1:     help
yann@1:       Use gcc's option -pipe to use pipes rather than temp files when building
yann@1:       the toolchain.
yann@805: 
michael@2701: config EXTRA_FLAGS_FOR_HOST
michael@2701:     string
michael@2701:     prompt "Extra host compiler flags"
michael@2701:     default ""
michael@2701:     help
michael@2701:       Extra flags to pass to the host C and C++ compiler.
michael@2701: 
michael@2701:       May be used to change the default features of the host
michael@2701:       compiler such as turning off the stack protector or fortify.
michael@2701: 
yann@1444: choice
yann@1444:     bool
yann@1444:     prompt "Shell to use as CONFIG_SHELL"
yann@1459:     default CONFIG_SHELL_BASH
yann@1866:     depends on ! BACKEND
yann@1444: 
yann@1444: config CONFIG_SHELL_SH
yann@1444:     bool
yann@1444:     prompt "sh (the system shell)"
yann@1444:     help
yann@1444:       Use 'sh' as CONFIG_SHELL.
yann@1444:       
yann@1444:       ./configure scripts and Makefiles make intensive use of calling
yann@1444:       sub-shells. This is usually done by calling /bin/sh. /bin/sh ought
yann@1444:       to be an at-least-POSIX-conformant shell (that is, able to interpret
yann@1444:       POSIX shell scripts).
yann@1444:       
yann@1444:       On many (most?) systems, /bin/sh is a symlink to bash. On some other
yann@1444:       systems (eg. Ubuntu, latest Debian), /bin/sh points to dash (or ash).
yann@1444:       bash is a full-featured shell, with many extension to POSIX, but is
yann@1444:       quite slow (see ection BUGS in the bash man page), while dash is
yann@1444:       faster, with very few extensions to POSIX.  On the other hand, some
yann@1444:       ./configure scripts, although written to use /bin/sh, may really
yann@1444:       require to be run by bash.
yann@1444:       
yann@1459:       The default is to use bash, as some components (eg. GMP) will fail
yann@1459:       to build with anything else than bash.
yann@2705:       
yann@2705:       Unless you have a very strong reason not to (eg. you are debugging
yann@2705:       the bashisms in a ./configure script), you should use the default,
yann@2705:       and use bash.
yann@1459: 
yann@805: config CONFIG_SHELL_ASH
yann@805:     bool
yann@1447:     prompt "ash (READ HELP!)"
yann@805:     help
yann@1444:       Use 'ash' as CONFIG_SHELL.
yann@805:       
yann@1444:       See help for CONFIG_SHELL_SH, above, for more explanations.
yann@1447:       
yann@1447:       NOTE: It is advised that you do NOT use ash as CONFIG_SHELL, as some
yann@1447:       components are broken. If you decide to use ash, and the build breaks,
yann@1447:       don't come moaning and set the CONFIG_SHELL to bash, below.
yann@1444: 
yann@1445: config CONFIG_SHELL_BASH
yann@1445:     bool
yann@1445:     prompt "bash"
yann@1445:     help
yann@1445:       Use 'bash' as CONFIG_SHELL.
yann@1445:       
yann@1445:       See help for CONFIG_SHELL_SH, above, for more explanations.
yann@1445: 
yann@1446: config CONFIG_SHELL_CUSTOM
yann@1446:     bool
yann@1446:     prompt "custom shell"
yann@1446:     help
yann@1446:       Enter full path to the custom shell below.
yann@1446:       
yann@1446:       See help for CONFIG_SHELL_SH, above, for more explanations.
yann@1446: 
yann@1444: endchoice
yann@1444: 
yann@2705: # Do not put this into the choice above, because the choice
yann@2705: # is not available in BACKEND-mode, while we do want this to
yann@2705: # be set even in BACKEND-mode.
yann@1866: config CONFIG_SHELL_CUSTOM_PATH
yann@1866:     string
yann@1866:     prompt "Path to custom shell" if ! BACKEND
yann@1866:     depends on CONFIG_SHELL_CUSTOM || BACKEND
yann@1866:     default "/bin/sh"
yann@2705: 
yann@2705: # Ditto.
yann@2705: # And we must use the ./configured bash...
yann@2705: config CONFIG_SHELL
yann@2705:     string
yann@2705:     default "/bin/sh"                   if CONFIG_SHELL_SH
yann@2705:     default "/bin/ash"                  if CONFIG_SHELL_ASH
yann@2705:     default "${bash}"                   if CONFIG_SHELL_BASH
yann@2705:     default CONFIG_SHELL_CUSTOM_PATH    if CONFIG_SHELL_CUSTOM || BACKEND