all: fix wildcard to work with make-4.x
In make-3.8x, the $(wildacrd) function would sort the entries,
while in make-4.x, it would just return the entries in any
unpredictable order [*]
Use the $(sort) function to get reproducible behaviour.
[*] Well, most probably the roder the entries appear when read
from readdir()
Reported-by: Andrew Ruder <andrew.ruder@elecsyscorp.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Tested-by: Andrew Ruder <andrew.ruder@elecsyscorp.com>
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 Leave to empty for no load limit.
31 Note: any float value is allowed and will be passed to the '-l' option
32 of make (for further details, refer to the make manpage).
36 prompt "Use -pipe" if ! BACKEND
39 Use gcc's option -pipe to use pipes rather than temp files when building
42 config EXTRA_CFLAGS_FOR_BUILD
44 prompt "Extra build compiler flags"
47 Extra flags to pass to the build C and C++ compiler.
49 May be used to change the default features of the build
50 compiler such as turning off the stack protector or fortify.
52 config EXTRA_LDFLAGS_FOR_BUILD
54 prompt "Extra build linker flags"
57 Extra flags to pass to the build linker.
59 May be used to change the default features of the build
62 config EXTRA_CFLAGS_FOR_HOST
64 prompt "Extra host compiler flags"
67 Extra flags to pass to the host C and C++ compiler.
69 May be used to change the default features of the host
70 compiler such as turning off the stack protector or fortify.
72 config EXTRA_LDFLAGS_FOR_HOST
74 prompt "Extra host linker flags"
77 Extra flags to pass to the host linker.
79 May be used to change the default features of the host
84 prompt "Shell to use as CONFIG_SHELL"
85 default CONFIG_SHELL_BASH
88 config CONFIG_SHELL_SH
90 prompt "sh (the system shell)"
92 Use 'sh' as CONFIG_SHELL.
94 ./configure scripts and Makefiles make intensive use of calling
95 sub-shells. This is usually done by calling /bin/sh. /bin/sh ought
96 to be an at-least-POSIX-conformant shell (that is, able to interpret
99 On many (most?) systems, /bin/sh is a symlink to bash. On some other
100 systems (eg. Ubuntu, latest Debian), /bin/sh points to dash (or ash).
101 bash is a full-featured shell, with many extension to POSIX, but is
102 quite slow (see ection BUGS in the bash man page), while dash is
103 faster, with very few extensions to POSIX. On the other hand, some
104 ./configure scripts, although written to use /bin/sh, may really
105 require to be run by bash.
107 The default is to use bash, as some components (eg. GMP) will fail
108 to build with anything else than bash.
110 Unless you have a very strong reason not to (eg. you are debugging
111 the bashisms in a ./configure script), you should use the default,
114 config CONFIG_SHELL_ASH
116 prompt "ash (READ HELP!)"
118 Use 'ash' as CONFIG_SHELL.
120 See help for CONFIG_SHELL_SH, above, for more explanations.
122 NOTE: It is advised that you do NOT use ash as CONFIG_SHELL, as some
123 components are broken. If you decide to use ash, and the build breaks,
124 don't come moaning and set the CONFIG_SHELL to bash, below.
126 config CONFIG_SHELL_BASH
130 Use 'bash' as CONFIG_SHELL.
132 See help for CONFIG_SHELL_SH, above, for more explanations.
134 config CONFIG_SHELL_CUSTOM
136 prompt "custom shell"
138 Enter full path to the custom shell below.
140 See help for CONFIG_SHELL_SH, above, for more explanations.
144 # Do not put this into the choice above, because the choice
145 # is not available in BACKEND-mode, while we do want this to
146 # be set even in BACKEND-mode.
147 config CONFIG_SHELL_CUSTOM_PATH
149 prompt "Path to custom shell" if ! BACKEND
150 depends on CONFIG_SHELL_CUSTOM || BACKEND
154 # And we must use the ./configured bash...
157 default "/bin/sh" if CONFIG_SHELL_SH
158 default "/bin/ash" if CONFIG_SHELL_ASH
159 default "${bash}" if CONFIG_SHELL_BASH
160 default CONFIG_SHELL_CUSTOM_PATH if CONFIG_SHELL_CUSTOM || BACKEND