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)"
42 The Linux 2.6.35 tree is a "longterm" maintenance branch.
44 It is intended to fill the niche for users who are not using distribution
45 kernels but want to use a regression-free kernel for a longer time.
47 Critical bug fixes to later 2.6 releases are often ported to this branch
48 which makes 2.6.35 a very useful base for many embedded developers seeking
49 stable APIs or those who do not need the latest bleeding edge features.
51 ... and no, this kernel has not undergone any specific QA testing.
53 See the original announcement by Andi Kleen in the following mailing
55 http://marc.info/?l=linux-kernel&m=129136895415202&w=4
57 config KERNEL_V_2_6_34_7
61 config KERNEL_V_2_6_33_7
65 config KERNEL_V_2_6_32_27
67 prompt "2.6.32.27 (longterm)"
69 The Linux 2.6.32 tree is a "longterm" maintenance branch.
71 It is intended to fill the niche for users who are not using distribution
72 kernels but want to use a regression-free kernel for a longer time.
74 Critical bug fixes to later 2.6 releases are often ported to this branch
75 which makes 2.6.32 a very useful base for many embedded developers seeking
76 stable APIs or those who do not need the latest bleeding edge features.
78 ... and no, this kernel has not undergone any specific QA testing.
80 See the original announcement by Greg Kroah-Hartman in the following
82 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
84 config KERNEL_V_2_6_31_14
88 config KERNEL_V_2_6_27_57
90 prompt "2.6.27.57 (longterm)"
92 The Linux 2.6.27 tree is a "longterm" maintenance branch.
94 It is intended to fill the niche for users who are not using distribution
95 kernels but want to use a regression-free kernel for a longer time.
97 Critical bug fixes to later 2.6 releases are often ported to this branch
98 which makes 2.6.27 a very useful base for many embedded developers seeking
99 stable APIs or those who do not need the latest bleeding edge features.
101 ... and no, this kernel has not undergone any specific QA testing.
103 See the original announcement by Adrian Bunk in the following mailing list
105 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
107 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
108 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
110 config KERNEL_LINUX_CUSTOM
112 prompt "custom tarball"
114 Use a local tarball of a complete kernel source tree.
116 config KERNEL_LINUX_CUSTOM_TARBALL
118 prompt "Path to custom tarball"
119 depends on KERNEL_LINUX_CUSTOM
121 Enter here the path to the tarball of your full kernel tree.
125 config KERNEL_VERSION
127 # Don't remove next line
128 # CT_INSERT_VERSION_STRING_BELOW
129 default "2.6.36.2" if KERNEL_V_2_6_36_2
130 default "2.6.36.1" if KERNEL_V_2_6_36_1
131 default "2.6.36" if KERNEL_V_2_6_36
132 default "2.6.35.10" if KERNEL_V_2_6_35_10
133 default "2.6.34.7" if KERNEL_V_2_6_34_7
134 default "2.6.33.7" if KERNEL_V_2_6_33_7
135 default "2.6.32.27" if KERNEL_V_2_6_32_26
136 default "2.6.31.14" if KERNEL_V_2_6_31_14
137 default "2.6.27.57" if KERNEL_V_2_6_27_57
141 prompt "Kernel verbosity:"
142 default KERNEL_LINUX_VERBOSITY_0
144 config KERNEL_LINUX_VERBOSITY_0
148 Print simplified command lines.
150 config KERNEL_LINUX_VERBOSITY_1
152 prompt "Full commands"
154 Print full command lines.
156 config KERNEL_LINUX_VERBOSITY_2
158 prompt "Exec reasons"
160 Print the reasons why a make target is rebuild.
164 config KERNEL_LINUX_VERBOSE_LEVEL
166 default 0 if KERNEL_LINUX_VERBOSITY_0
167 default 1 if KERNEL_LINUX_VERBOSITY_1
168 default 2 if KERNEL_LINUX_VERBOSITY_2
170 config KERNEL_LINUX_INSTALL_CHECK
172 prompt "Check installed headers"
175 If you are in doubt that installed headers are buggy, say 'Y'
176 here to have an extra check passed onto the headers.
178 endif # KERNEL_LINUX_INSTALL
180 config KERNEL_LINUX_USE_CUSTOM_HEADERS
182 prompt "pre-installed headers tree"
184 If you have some pre-installed kernel headers lying around, you can
185 enter the path to these headers, below, they will be copied from
186 there, and into the toolchain's sysroot.
189 This will *not* let you use a complete kernel tree!
190 If you want to use your own full kernel tree, then you want to
191 say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
193 if KERNEL_LINUX_USE_CUSTOM_HEADERS
195 config KERNEL_LINUX_CUSTOM_IS_TARBALL
197 prompt "This is a tarball"
200 If you say 'n' here, the path below is expected to point to a directory
201 containing readily prepared headers
203 If you say 'y' here, then the path below is expected to point to a
204 tarball of such a directory.
206 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
207 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
209 Now, passing a tarball around is easier than passing a directory, so
210 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
211 say 'y' here, and enter the path to this tarball below.
213 config KERNEL_LINUX_CUSTOM_PATH
215 prompt "Path to custom headers directory/tarball"
217 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
219 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS