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>
3 ## select KERNEL_SUPPORTS_SHARED_LIBS
5 ## help Build a toolchain targeting systems running Linux as a kernel.
7 config KERNEL_LINUX_USE_CUSTOM_HEADERS
9 prompt "Use pre-installed headers tree (OBSOLETE)"
12 If you have some pre-installed kernel headers lying around, you can
13 enter the path to these headers, below, they will be copied from
14 there, and into the toolchain's sysroot.
17 This will *not* let you use a complete kernel tree!
18 If you want to use your own full kernel tree, then you want to say 'N'
19 here, and select KERNEL_LINUX_CUSTOM, in the versions list, below.
21 if ! KERNEL_LINUX_USE_CUSTOM_HEADERS
25 prompt "Linux kernel version"
26 # Don't remove next line
27 # CT_INSERT_VERSION_BELOW
43 prompt "3.10.38 (longterm)"
67 prompt "3.4.88 (longterm)"
85 config KERNEL_V_2_6_39
89 config KERNEL_V_2_6_38
93 config KERNEL_V_2_6_37
97 config KERNEL_V_2_6_36
101 config KERNEL_V_2_6_33
105 This is primarily for the use of those people who are stuck using the
106 .33-rt kernel. Anyone else who really wants to use the .33 kernel tree
107 is welcome to use this one as well.
109 config KERNEL_V_2_6_32
111 prompt "2.6.32.61 (longterm)"
113 The Linux 2.6.32 tree is a "longterm" maintenance branch.
115 It is intended to fill the niche for users who are not using distribution
116 kernels but want to use a regression-free kernel for a longer time.
118 Critical bug fixes to later 2.6 releases are often ported to this branch
119 which makes 2.6.32 a very useful base for many embedded developers seeking
120 stable APIs or those who do not need the latest bleeding edge features.
122 ... and no, this kernel has not undergone any specific QA testing.
124 See the original announcement by Greg Kroah-Hartman in the following
126 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
128 config KERNEL_V_2_6_31
132 config KERNEL_V_2_6_27
134 prompt "2.6.27.62 (longterm)"
136 The Linux 2.6.27 tree is a "longterm" maintenance branch.
138 It is intended to fill the niche for users who are not using distribution
139 kernels but want to use a regression-free kernel for a longer time.
141 Critical bug fixes to later 2.6 releases are often ported to this branch
142 which makes 2.6.27 a very useful base for many embedded developers seeking
143 stable APIs or those who do not need the latest bleeding edge features.
145 ... and no, this kernel has not undergone any specific QA testing.
147 See the original announcement by Adrian Bunk in the following mailing list
149 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
151 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
152 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
154 config KERNEL_LINUX_CUSTOM
156 prompt "custom tarball or directory"
158 Use a local tarball or local kernel directory of a complete kernel source tree.
160 config KERNEL_LINUX_CUSTOM_LOCATION
162 prompt "Path to custom source, tarball or directory"
163 depends on KERNEL_LINUX_CUSTOM
165 Enter here the path to the tarball of your full kernel tree or
170 config KERNEL_VERSION
172 # Don't remove next line
173 # CT_INSERT_VERSION_STRING_BELOW
174 default "3.13.11" if KERNEL_V_3_13
175 default "3.12.18" if KERNEL_V_3_12
176 default "3.11.10" if KERNEL_V_3_11
177 default "3.10.38" if KERNEL_V_3_10
178 default "3.9.11" if KERNEL_V_3_9
179 default "3.8.13.9" if KERNEL_V_3_8
180 default "3.7.10" if KERNEL_V_3_7
181 default "3.6.11" if KERNEL_V_3_6
182 default "3.5.7.25" if KERNEL_V_3_5
183 default "3.4.88" if KERNEL_V_3_4
184 default "3.3.8" if KERNEL_V_3_3
185 default "3.2.58" if KERNEL_V_3_2
186 default "3.1.10" if KERNEL_V_3_1
187 default "3.0.101" if KERNEL_V_3_0
188 default "2.6.39.4" if KERNEL_V_2_6_39
189 default "2.6.38.8" if KERNEL_V_2_6_38
190 default "2.6.37.6" if KERNEL_V_2_6_37
191 default "2.6.36.4" if KERNEL_V_2_6_36
192 default "2.6.33.20" if KERNEL_V_2_6_33
193 default "2.6.32.61" if KERNEL_V_2_6_32
194 default "2.6.31.14" if KERNEL_V_2_6_31
195 default "2.6.27.62" if KERNEL_V_2_6_27
196 default "custom" if KERNEL_LINUX_CUSTOM
198 endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS
200 if KERNEL_LINUX_USE_CUSTOM_HEADERS
202 config KERNEL_LINUX_CUSTOM_PATH
204 prompt "Path to custom headers directory/tarball"
206 See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
208 config KERNEL_LINUX_CUSTOM_IS_TARBALL
210 prompt "This is a tarball"
212 If you say 'n' here, the path above is expected to point to a directory
213 containing readily prepared headers
215 If you say 'y' here, then the path above is expected to point to a
216 tarball of such a directory.
218 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
219 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
221 Now, passing a tarball around is easier than passing a directory, so
222 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
223 say 'y' here, and enter the path to this tarball below.
225 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS