Allow using ash as the shell for ./configure and make.
After an idea by "Martin Guy" <martinwguy@yahoo.it>:
http://sourceware.org/ml/crossgcc/2008-08/msg00037.html
/trunk/scripts/crosstool.sh | 4 4 0 0 ++++
/trunk/config/global/build-behave.in | 14 14 0 0 ++++++++++++++
2 files changed, 18 insertions(+)
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
47 config CONFIG_SHELL_ASH
49 prompt "Use 'ash' as CONFIG_SHELL"
52 Use /bin/ash as the shell used by ./configure scripts.
54 ./configure scripts make intensive use of calling a sub-shell, and the
55 traditional bash is slow, whereas ash is faster.
57 Saying 'y' here should be safe enough, but some components may not
58 accept using a shell other than bash (this is most probably true for
59 old versions). If you have trouble, say 'n' here and see if it fixes it.