6 select KERNEL_SUPPORTS_SHARED_LIBS
8 Build a toolchain targeting systems running Linux as a kernel.
12 prompt "Get kernel headers from:"
14 config KERNEL_LINUX_INSTALL
16 prompt "kernel's 'headers_install'"
18 This will make use of the new headers_install rule in recent kernels.
19 This is most probably what you want to use.
21 if KERNEL_LINUX_INSTALL
25 prompt "Linux kernel version"
26 # Don't remove next line
27 # CT_INSERT_VERSION_BELOW
29 config KERNEL_V_2_6_34_1
33 config KERNEL_V_2_6_34
37 config KERNEL_V_2_6_33_6
41 config KERNEL_V_2_6_33_5
45 config KERNEL_V_2_6_33_4
49 config KERNEL_V_2_6_33_3
53 config KERNEL_V_2_6_33_2
57 config KERNEL_V_2_6_33_1
61 config KERNEL_V_2_6_33
65 config KERNEL_V_2_6_32_16
69 config KERNEL_V_2_6_31_14
73 config KERNEL_V_2_6_30_10
77 config KERNEL_V_2_6_27_48
79 prompt "2.6.27.48 (long-term stable)"
81 The Linux 2.6.27 tree is the current "long-term stable" maintenance branch.
82 It is intended to fill the niche for users who are not using distribution
83 kernels but want to use a regression-free kernel for a longer time.
85 Critical bug fixes to later 2.6 releases are often ported to this branch
86 which makes 2.6.27 a very useful base for many embedded developers seeking
87 stable APIs or those who do not need the latest bleeding edge features.
89 ... and no, this kernel has not undergone any specific QA testing.
91 See the original announcement by Adrian Bunk in the following mailing list
92 entry: http://marc.info/?l=linux-kernel&m=122375909403298&w=2
94 config KERNEL_LINUX_CUSTOM
96 prompt "custom tarball"
98 Use a local tarball of a complete kernel source tree.
100 config KERNEL_LINUX_CUSTOM_TARBALL
102 prompt "Path to custom tarball"
103 depends on KERNEL_LINUX_CUSTOM
105 Enter here the path to the tarball of your full kernel tree.
109 config KERNEL_VERSION
111 # Don't remove next line
112 # CT_INSERT_VERSION_STRING_BELOW
113 default "2.6.34.1" if KERNEL_V_2_6_34_1
114 default "2.6.34" if KERNEL_V_2_6_34
115 default "2.6.33.6" if KERNEL_V_2_6_33_6
116 default "2.6.33.5" if KERNEL_V_2_6_33_5
117 default "2.6.33.4" if KERNEL_V_2_6_33_4
118 default "2.6.33.3" if KERNEL_V_2_6_33_3
119 default "2.6.33.2" if KERNEL_V_2_6_33_2
120 default "2.6.33.1" if KERNEL_V_2_6_33_1
121 default "2.6.33" if KERNEL_V_2_6_33
122 default "2.6.32.16" if KERNEL_V_2_6_32_16
123 default "2.6.31.14" if KERNEL_V_2_6_31_14
124 default "2.6.30.10" if KERNEL_V_2_6_30_10
125 default "2.6.27.48" if KERNEL_V_2_6_27_48
129 prompt "Kernel verbosity:"
130 default KERNEL_LINUX_VERBOSITY_0
132 config KERNEL_LINUX_VERBOSITY_0
136 Print simplified command lines.
138 config KERNEL_LINUX_VERBOSITY_1
140 prompt "Full commands"
142 Print full command lines.
144 config KERNEL_LINUX_VERBOSITY_2
146 prompt "Exec reasons"
148 Print the reasons why a make target is rebuild.
152 config KERNEL_LINUX_VERBOSE_LEVEL
154 default 0 if KERNEL_LINUX_VERBOSITY_0
155 default 1 if KERNEL_LINUX_VERBOSITY_1
156 default 2 if KERNEL_LINUX_VERBOSITY_2
158 config KERNEL_LINUX_INSTALL_CHECK
160 prompt "Check installed headers"
163 If you are in doubt that installed headers are buggy, say 'Y'
164 here to have an extra check passed onto the headers.
166 endif # KERNEL_LINUX_INSTALL
168 config KERNEL_LINUX_USE_CUSTOM_HEADERS
170 prompt "pre-installed headers tree"
172 If you have some pre-installed kernel headers lying around, you can
173 enter the path to these headers, below, they will be copied from
174 there, and into the toolchain's sysroot.
177 This will *not* let you use a complete kernel tree!
178 If you want to use your own full kernel tree, then you want to
179 say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
181 if KERNEL_LINUX_USE_CUSTOM_HEADERS
183 config KERNEL_LINUX_CUSTOM_IS_TARBALL
185 prompt "This is a tarball"
188 If you say 'n' here, the path below is expected to point to a directory
189 containing readily prepared headers
191 If you say 'y' here, then the path below is expected to point to a
192 tarball of such a directory.
194 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
195 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
197 Now, passing a tarball around is easier than passing a directory, so
198 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
199 say 'y' here, and enter the path to this tarball below.
201 config KERNEL_LINUX_CUSTOM_PATH
203 prompt "Path to custom headers directory/tarball"
205 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
207 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS