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
31 config KERNEL_V_2_6_36_3
35 config KERNEL_V_2_6_36_2
39 config KERNEL_V_2_6_36_1
43 config KERNEL_V_2_6_36
47 config KERNEL_V_2_6_35_10
49 prompt "2.6.35.10 (longterm)"
51 The Linux 2.6.35 tree is a "longterm" maintenance branch.
53 It is intended to fill the niche for users who are not using distribution
54 kernels but want to use a regression-free kernel for a longer time.
56 Critical bug fixes to later 2.6 releases are often ported to this branch
57 which makes 2.6.35 a very useful base for many embedded developers seeking
58 stable APIs or those who do not need the latest bleeding edge features.
60 ... and no, this kernel has not undergone any specific QA testing.
62 See the original announcement by Andi Kleen in the following mailing
64 http://marc.info/?l=linux-kernel&m=129136895415202&w=4
66 config KERNEL_V_2_6_34_8
70 config KERNEL_V_2_6_33_7
74 config KERNEL_V_2_6_32_28
76 prompt "2.6.32.28 (longterm)"
78 The Linux 2.6.32 tree is a "longterm" maintenance branch.
80 It is intended to fill the niche for users who are not using distribution
81 kernels but want to use a regression-free kernel for a longer time.
83 Critical bug fixes to later 2.6 releases are often ported to this branch
84 which makes 2.6.32 a very useful base for many embedded developers seeking
85 stable APIs or those who do not need the latest bleeding edge features.
87 ... and no, this kernel has not undergone any specific QA testing.
89 See the original announcement by Greg Kroah-Hartman in the following
91 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
93 config KERNEL_V_2_6_31_14
97 config KERNEL_V_2_6_27_57
99 prompt "2.6.27.57 (longterm)"
101 The Linux 2.6.27 tree is a "longterm" maintenance branch.
103 It is intended to fill the niche for users who are not using distribution
104 kernels but want to use a regression-free kernel for a longer time.
106 Critical bug fixes to later 2.6 releases are often ported to this branch
107 which makes 2.6.27 a very useful base for many embedded developers seeking
108 stable APIs or those who do not need the latest bleeding edge features.
110 ... and no, this kernel has not undergone any specific QA testing.
112 See the original announcement by Adrian Bunk in the following mailing list
114 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
116 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
117 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
119 config KERNEL_LINUX_CUSTOM
121 prompt "custom tarball"
123 Use a local tarball of a complete kernel source tree.
125 config KERNEL_LINUX_CUSTOM_TARBALL
127 prompt "Path to custom tarball"
128 depends on KERNEL_LINUX_CUSTOM
130 Enter here the path to the tarball of your full kernel tree.
134 config KERNEL_VERSION
136 # Don't remove next line
137 # CT_INSERT_VERSION_STRING_BELOW
138 default "2.6.37" if KERNEL_V_2_6_37
139 default "2.6.36.3" if KERNEL_V_2_6_36_3
140 default "2.6.36.2" if KERNEL_V_2_6_36_2
141 default "2.6.36.1" if KERNEL_V_2_6_36_1
142 default "2.6.36" if KERNEL_V_2_6_36
143 default "2.6.35.10" if KERNEL_V_2_6_35_10
144 default "2.6.34.8" if KERNEL_V_2_6_34_8
145 default "2.6.33.7" if KERNEL_V_2_6_33_7
146 default "2.6.32.28" if KERNEL_V_2_6_32_28
147 default "2.6.31.14" if KERNEL_V_2_6_31_14
148 default "2.6.27.57" if KERNEL_V_2_6_27_57
152 prompt "Kernel verbosity:"
153 default KERNEL_LINUX_VERBOSITY_0
155 config KERNEL_LINUX_VERBOSITY_0
159 Print simplified command lines.
161 config KERNEL_LINUX_VERBOSITY_1
163 prompt "Full commands"
165 Print full command lines.
167 config KERNEL_LINUX_VERBOSITY_2
169 prompt "Exec reasons"
171 Print the reasons why a make target is rebuild.
175 config KERNEL_LINUX_VERBOSE_LEVEL
177 default 0 if KERNEL_LINUX_VERBOSITY_0
178 default 1 if KERNEL_LINUX_VERBOSITY_1
179 default 2 if KERNEL_LINUX_VERBOSITY_2
181 config KERNEL_LINUX_INSTALL_CHECK
183 prompt "Check installed headers"
186 If you are in doubt that installed headers are buggy, say 'Y'
187 here to have an extra check passed onto the headers.
189 endif # KERNEL_LINUX_INSTALL
191 config KERNEL_LINUX_USE_CUSTOM_HEADERS
193 prompt "pre-installed headers tree"
195 If you have some pre-installed kernel headers lying around, you can
196 enter the path to these headers, below, they will be copied from
197 there, and into the toolchain's sysroot.
200 This will *not* let you use a complete kernel tree!
201 If you want to use your own full kernel tree, then you want to
202 say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
204 if KERNEL_LINUX_USE_CUSTOM_HEADERS
206 config KERNEL_LINUX_CUSTOM_IS_TARBALL
208 prompt "This is a tarball"
211 If you say 'n' here, the path below is expected to point to a directory
212 containing readily prepared headers
214 If you say 'y' here, then the path below is expected to point to a
215 tarball of such a directory.
217 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
218 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
220 Now, passing a tarball around is easier than passing a directory, so
221 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
222 say 'y' here, and enter the path to this tarball below.
224 config KERNEL_LINUX_CUSTOM_PATH
226 prompt "Path to custom headers directory/tarball"
228 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
230 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS