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_34
41 config KERNEL_V_2_6_33_4
45 config KERNEL_V_2_6_33_3
49 config KERNEL_V_2_6_33_2
53 config KERNEL_V_2_6_33_1
57 config KERNEL_V_2_6_33
61 config KERNEL_V_2_6_32_13
65 config KERNEL_V_2_6_31_13
69 config KERNEL_V_2_6_30_10
73 config KERNEL_V_2_6_27_46
75 prompt "2.6.27.46 (long-term stable)"
77 The Linux 2.6.27 tree is the current "long-term stable" maintenance branch.
78 It is intended to fill the niche for users who are not using distribution
79 kernels but want to use a regression-free kernel for a longer time.
81 Critical bug fixes to later 2.6 releases are often ported to this branch
82 which makes 2.6.27 a very useful base for many embedded developers seeking
83 stable APIs or those who do not need the latest bleeding edge features.
85 ... and no, this kernel has not undergone any specific QA testing.
87 See the original announcement by Adrian Bunk in the following mailing list
88 entry: http://marc.info/?l=linux-kernel&m=122375909403298&w=2
94 # Don't remove next line
95 # CT_INSERT_VERSION_STRING_BELOW
96 default "2.6.34" if KERNEL_V_2_6_34
97 default "2.6.33.4" if KERNEL_V_2_6_33_4
98 default "2.6.33.3" if KERNEL_V_2_6_33_3
99 default "2.6.33.2" if KERNEL_V_2_6_33_2
100 default "2.6.33.1" if KERNEL_V_2_6_33_1
101 default "2.6.33" if KERNEL_V_2_6_33
102 default "2.6.32.13" if KERNEL_V_2_6_32_13
103 default "2.6.31.13" if KERNEL_V_2_6_31_13
104 default "2.6.30.10" if KERNEL_V_2_6_30_10
105 default "2.6.27.46" if KERNEL_V_2_6_27_46
109 prompt "Kernel verbosity:"
110 default KERNEL_LINUX_VERBOSITY_0
112 config KERNEL_LINUX_VERBOSITY_0
116 Print simplified command lines.
118 config KERNEL_LINUX_VERBOSITY_1
120 prompt "Full commands"
122 Print full command lines.
124 config KERNEL_LINUX_VERBOSITY_2
126 prompt "Exec reasons"
128 Print the reasons why a make target is rebuild.
132 config KERNEL_LINUX_VERBOSE_LEVEL
134 default 0 if KERNEL_LINUX_VERBOSITY_0
135 default 1 if KERNEL_LINUX_VERBOSITY_1
136 default 2 if KERNEL_LINUX_VERBOSITY_2
140 config KERNEL_LINUX_USE_CUSTOM_HEADERS
142 prompt "Use custom headers"
144 If you have some kernel headers lying around, you can enter the path
147 if KERNEL_LINUX_USE_CUSTOM_HEADERS
149 config KERNEL_LINUX_CUSTOM_IS_TARBALL
151 prompt "This is a tarball"
154 If you say 'n' here, the path below is expected to point to a directory
155 containing readily prepared headers
157 If you say 'y' here, then the path below is expected to point to a
158 tarball of such a directory.
160 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
161 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
163 Now, passing a tarball around is easier than passing a directory, so
164 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
165 say 'y' here, and enter the path to this tarball below.
167 config KERNEL_LINUX_CUSTOM_PATH
169 prompt "Path to custom headers directory/tarball"
171 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
173 endif # KERNEL_LINUX_USE_CUSTOM_DIR