4 select KERNEL_SUPPORTS_SHARED_LIBS
6 Build a toolchain targeting systems running Linux as a kernel.
10 prompt "Get kernel headers from:"
12 config KERNEL_LINUX_INSTALL
14 prompt "kernel's 'headers_install'"
16 This will make use of the new headers_install rule in recent kernels.
17 This is most probably what you want to use.
19 if KERNEL_LINUX_INSTALL
23 prompt "Linux kernel version"
24 # Don't remove next line
25 # CT_INSERT_VERSION_BELOW
27 config KERNEL_V_2_6_37_2
31 config KERNEL_V_2_6_37_1
35 config KERNEL_V_2_6_37
39 config KERNEL_V_2_6_36_4
43 config KERNEL_V_2_6_35_11
45 prompt "2.6.35.11 (longterm)"
47 The Linux 2.6.35 tree is a "longterm" maintenance branch.
49 It is intended to fill the niche for users who are not using distribution
50 kernels but want to use a regression-free kernel for a longer time.
52 Critical bug fixes to later 2.6 releases are often ported to this branch
53 which makes 2.6.35 a very useful base for many embedded developers seeking
54 stable APIs or those who do not need the latest bleeding edge features.
56 ... and no, this kernel has not undergone any specific QA testing.
58 See the original announcement by Andi Kleen in the following mailing
60 http://marc.info/?l=linux-kernel&m=129136895415202&w=4
62 config KERNEL_V_2_6_34_8
66 config KERNEL_V_2_6_33_7
70 config KERNEL_V_2_6_32_29
72 prompt "2.6.32.29 (longterm)"
74 The Linux 2.6.32 tree is a "longterm" maintenance branch.
76 It is intended to fill the niche for users who are not using distribution
77 kernels but want to use a regression-free kernel for a longer time.
79 Critical bug fixes to later 2.6 releases are often ported to this branch
80 which makes 2.6.32 a very useful base for many embedded developers seeking
81 stable APIs or those who do not need the latest bleeding edge features.
83 ... and no, this kernel has not undergone any specific QA testing.
85 See the original announcement by Greg Kroah-Hartman in the following
87 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
89 config KERNEL_V_2_6_31_14
93 config KERNEL_V_2_6_27_58
95 prompt "2.6.27.58 (longterm)"
97 The Linux 2.6.27 tree is a "longterm" maintenance branch.
99 It is intended to fill the niche for users who are not using distribution
100 kernels but want to use a regression-free kernel for a longer time.
102 Critical bug fixes to later 2.6 releases are often ported to this branch
103 which makes 2.6.27 a very useful base for many embedded developers seeking
104 stable APIs or those who do not need the latest bleeding edge features.
106 ... and no, this kernel has not undergone any specific QA testing.
108 See the original announcement by Adrian Bunk in the following mailing list
110 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
112 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
113 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
115 config KERNEL_LINUX_CUSTOM
117 prompt "custom tarball"
119 Use a local tarball of a complete kernel source tree.
121 config KERNEL_LINUX_CUSTOM_TARBALL
123 prompt "Path to custom tarball"
124 depends on KERNEL_LINUX_CUSTOM
126 Enter here the path to the tarball of your full kernel tree.
130 config KERNEL_VERSION
132 # Don't remove next line
133 # CT_INSERT_VERSION_STRING_BELOW
134 default "2.6.37.2" if KERNEL_V_2_6_37_2
135 default "2.6.37.1" if KERNEL_V_2_6_37_1
136 default "2.6.37" if KERNEL_V_2_6_37
137 default "2.6.36.4" if KERNEL_V_2_6_36_4
138 default "2.6.35.11" if KERNEL_V_2_6_35_11
139 default "2.6.34.8" if KERNEL_V_2_6_34_8
140 default "2.6.33.7" if KERNEL_V_2_6_33_7
141 default "2.6.32.29" if KERNEL_V_2_6_32_29
142 default "2.6.31.14" if KERNEL_V_2_6_31_14
143 default "2.6.27.58" if KERNEL_V_2_6_27_58
147 prompt "Kernel verbosity:"
148 default KERNEL_LINUX_VERBOSITY_0
150 config KERNEL_LINUX_VERBOSITY_0
154 Print simplified command lines.
156 config KERNEL_LINUX_VERBOSITY_1
158 prompt "Full commands"
160 Print full command lines.
162 config KERNEL_LINUX_VERBOSITY_2
164 prompt "Exec reasons"
166 Print the reasons why a make target is rebuild.
170 config KERNEL_LINUX_VERBOSE_LEVEL
172 default 0 if KERNEL_LINUX_VERBOSITY_0
173 default 1 if KERNEL_LINUX_VERBOSITY_1
174 default 2 if KERNEL_LINUX_VERBOSITY_2
176 config KERNEL_LINUX_INSTALL_CHECK
178 prompt "Check installed headers"
181 If you are in doubt that installed headers are buggy, say 'Y'
182 here to have an extra check passed onto the headers.
184 endif # KERNEL_LINUX_INSTALL
186 config KERNEL_LINUX_USE_CUSTOM_HEADERS
188 prompt "pre-installed headers tree"
190 If you have some pre-installed kernel headers lying around, you can
191 enter the path to these headers, below, they will be copied from
192 there, and into the toolchain's sysroot.
195 This will *not* let you use a complete kernel tree!
196 If you want to use your own full kernel tree, then you want to
197 say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
199 if KERNEL_LINUX_USE_CUSTOM_HEADERS
201 config KERNEL_LINUX_CUSTOM_IS_TARBALL
203 prompt "This is a tarball"
206 If you say 'n' here, the path below is expected to point to a directory
207 containing readily prepared headers
209 If you say 'y' here, then the path below is expected to point to a
210 tarball of such a directory.
212 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
213 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
215 Now, passing a tarball around is easier than passing a directory, so
216 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
217 say 'y' here, and enter the path to this tarball below.
219 config KERNEL_LINUX_CUSTOM_PATH
221 prompt "Path to custom headers directory/tarball"
223 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
225 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS