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
23 config KERNEL_LINUX_INSTALL_CHECK
25 prompt "Check installed headers"
28 If you are in doubt that installed headers are buggy, say 'Y'
29 here to have an extra check passed onto the headers.
33 prompt "Linux kernel version"
34 # Don't remove next line
35 # CT_INSERT_VERSION_BELOW
37 config KERNEL_V_2_6_32_7
41 config KERNEL_V_2_6_32_6
45 config KERNEL_V_2_6_32_5
49 config KERNEL_V_2_6_32_4
53 config KERNEL_V_2_6_32_3
57 config KERNEL_V_2_6_32_2
61 config KERNEL_V_2_6_32_1
65 config KERNEL_V_2_6_32
69 config KERNEL_V_2_6_31_12
73 config KERNEL_V_2_6_30_10
77 config KERNEL_V_2_6_29_6
79 prompt "2.6.29.6 (OBSOLETE)"
82 config KERNEL_V_2_6_28_10
84 prompt "2.6.28.10 (OBSOLETE)"
87 config KERNEL_V_2_6_27_45
89 prompt "2.6.27.45 (long-term stable)"
91 The Linux 2.6.27 tree is the current "long-term stable" maintenance branch.
92 It is intended to fill the niche for users who are not using distribution
93 kernels but want to use a regression-free kernel for a longer time.
95 Critical bug fixes to later 2.6 releases are often ported to this branch
96 which makes 2.6.27 a very useful base for many embedded developers seeking
97 stable APIs or those who do not need the latest bleeding edge features.
99 ... and no, this kernel has not undergone any specific QA testing.
101 See the original announcement by Adrian Bunk in the following mailing list
102 entry: http://marc.info/?l=linux-kernel&m=122375909403298&w=2
106 config KERNEL_VERSION
108 # Don't remove next line
109 # CT_INSERT_VERSION_STRING_BELOW
110 default "2.6.32.7" if KERNEL_V_2_6_32_7
111 default "2.6.32.6" if KERNEL_V_2_6_32_6
112 default "2.6.32.5" if KERNEL_V_2_6_32_5
113 default "2.6.32.4" if KERNEL_V_2_6_32_4
114 default "2.6.32.3" if KERNEL_V_2_6_32_3
115 default "2.6.32.2" if KERNEL_V_2_6_32_2
116 default "2.6.32.1" if KERNEL_V_2_6_32_1
117 default "2.6.32" if KERNEL_V_2_6_32
118 default "2.6.31.12" if KERNEL_V_2_6_31_12
119 default "2.6.30.10" if KERNEL_V_2_6_30_10
120 default "2.6.29.6" if KERNEL_V_2_6_29_6
121 default "2.6.28.10" if KERNEL_V_2_6_28_10
122 default "2.6.27.45" if KERNEL_V_2_6_27_45
126 prompt "Kernel verbosity:"
127 default KERNEL_LINUX_VERBOSITY_0
129 config KERNEL_LINUX_VERBOSITY_0
133 Print simplified command lines.
135 config KERNEL_LINUX_VERBOSITY_1
137 prompt "Full commands"
139 Print full command lines.
141 config KERNEL_LINUX_VERBOSITY_2
143 prompt "Exec reasons"
145 Print the reasons why a make target is rebuild.
149 config KERNEL_LINUX_VERBOSE_LEVEL
151 default 0 if KERNEL_LINUX_VERBOSITY_0
152 default 1 if KERNEL_LINUX_VERBOSITY_1
153 default 2 if KERNEL_LINUX_VERBOSITY_2
157 config KERNEL_LINUX_USE_CUSTOM_HEADERS
159 prompt "Use custom headers"
161 If you have some kernel headers lying around, you can enter the path
164 if KERNEL_LINUX_USE_CUSTOM_HEADERS
166 config KERNEL_LINUX_CUSTOM_IS_TARBALL
168 prompt "This is a tarball"
171 If you say 'n' here, the path below is expected to point to a directory
172 containing readily prepared headers
174 If you say 'y' here, then the path below is expected to point to a
175 tarball of such a directory.
177 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
178 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
180 Now, passing a tarball around is easier than passing a directory, so
181 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
182 say 'y' here, and enter the path to this tarball below.
184 config KERNEL_LINUX_CUSTOM_PATH
186 prompt "Path to custom headers directory/tarball"
188 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
190 endif # KERNEL_LINUX_USE_CUSTOM_DIR