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_36_2
31 config KERNEL_V_2_6_36_1
35 config KERNEL_V_2_6_36
39 config KERNEL_V_2_6_35_10
41 prompt "2.6.35.10 (longterm)"
43 The Linux 2.6.35 tree is a "longterm" maintenance branch.
45 It is intended to fill the niche for users who are not using distribution
46 kernels but want to use a regression-free kernel for a longer time.
48 Critical bug fixes to later 2.6 releases are often ported to this branch
49 which makes 2.6.35 a very useful base for many embedded developers seeking
50 stable APIs or those who do not need the latest bleeding edge features.
52 ... and no, this kernel has not undergone any specific QA testing.
54 See the original announcement by Andi Kleen in the following mailing
56 http://marc.info/?l=linux-kernel&m=129136895415202&w=4
58 config KERNEL_V_2_6_34_7
62 config KERNEL_V_2_6_33_7
66 config KERNEL_V_2_6_32_27
68 prompt "2.6.32.27 (longterm)"
70 The Linux 2.6.32 tree is a "longterm" maintenance branch.
72 It is intended to fill the niche for users who are not using distribution
73 kernels but want to use a regression-free kernel for a longer time.
75 Critical bug fixes to later 2.6 releases are often ported to this branch
76 which makes 2.6.32 a very useful base for many embedded developers seeking
77 stable APIs or those who do not need the latest bleeding edge features.
79 ... and no, this kernel has not undergone any specific QA testing.
81 See the original announcement by Greg Kroah-Hartman in the following
83 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
85 config KERNEL_V_2_6_31_14
89 config KERNEL_V_2_6_27_57
91 prompt "2.6.27.57 (longterm)"
93 The Linux 2.6.27 tree is a "longterm" maintenance branch.
95 It is intended to fill the niche for users who are not using distribution
96 kernels but want to use a regression-free kernel for a longer time.
98 Critical bug fixes to later 2.6 releases are often ported to this branch
99 which makes 2.6.27 a very useful base for many embedded developers seeking
100 stable APIs or those who do not need the latest bleeding edge features.
102 ... and no, this kernel has not undergone any specific QA testing.
104 See the original announcement by Adrian Bunk in the following mailing list
106 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
108 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
109 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
111 config KERNEL_LINUX_CUSTOM
113 prompt "custom tarball"
115 Use a local tarball of a complete kernel source tree.
117 config KERNEL_LINUX_CUSTOM_TARBALL
119 prompt "Path to custom tarball"
120 depends on KERNEL_LINUX_CUSTOM
122 Enter here the path to the tarball of your full kernel tree.
126 config KERNEL_VERSION
128 # Don't remove next line
129 # CT_INSERT_VERSION_STRING_BELOW
130 default "2.6.36.2" if KERNEL_V_2_6_36_2
131 default "2.6.36.1" if KERNEL_V_2_6_36_1
132 default "2.6.36" if KERNEL_V_2_6_36
133 default "2.6.35.10" if KERNEL_V_2_6_35_10
134 default "2.6.34.7" if KERNEL_V_2_6_34_7
135 default "2.6.33.7" if KERNEL_V_2_6_33_7
136 default "2.6.32.27" if KERNEL_V_2_6_32_26
137 default "2.6.31.14" if KERNEL_V_2_6_31_14
138 default "2.6.27.57" if KERNEL_V_2_6_27_57
142 prompt "Kernel verbosity:"
143 default KERNEL_LINUX_VERBOSITY_0
145 config KERNEL_LINUX_VERBOSITY_0
149 Print simplified command lines.
151 config KERNEL_LINUX_VERBOSITY_1
153 prompt "Full commands"
155 Print full command lines.
157 config KERNEL_LINUX_VERBOSITY_2
159 prompt "Exec reasons"
161 Print the reasons why a make target is rebuild.
165 config KERNEL_LINUX_VERBOSE_LEVEL
167 default 0 if KERNEL_LINUX_VERBOSITY_0
168 default 1 if KERNEL_LINUX_VERBOSITY_1
169 default 2 if KERNEL_LINUX_VERBOSITY_2
171 config KERNEL_LINUX_INSTALL_CHECK
173 prompt "Check installed headers"
176 If you are in doubt that installed headers are buggy, say 'Y'
177 here to have an extra check passed onto the headers.
179 endif # KERNEL_LINUX_INSTALL
181 config KERNEL_LINUX_USE_CUSTOM_HEADERS
183 prompt "pre-installed headers tree"
185 If you have some pre-installed kernel headers lying around, you can
186 enter the path to these headers, below, they will be copied from
187 there, and into the toolchain's sysroot.
190 This will *not* let you use a complete kernel tree!
191 If you want to use your own full kernel tree, then you want to
192 say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
194 if KERNEL_LINUX_USE_CUSTOM_HEADERS
196 config KERNEL_LINUX_CUSTOM_IS_TARBALL
198 prompt "This is a tarball"
201 If you say 'n' here, the path below is expected to point to a directory
202 containing readily prepared headers
204 If you say 'y' here, then the path below is expected to point to a
205 tarball of such a directory.
207 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
208 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
210 Now, passing a tarball around is easier than passing a directory, so
211 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
212 say 'y' here, and enter the path to this tarball below.
214 config KERNEL_LINUX_CUSTOM_PATH
216 prompt "Path to custom headers directory/tarball"
218 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
220 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS