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_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_14
69 config KERNEL_V_2_6_31_13
73 config KERNEL_V_2_6_30_10
77 config KERNEL_V_2_6_27_47
79 prompt "2.6.27.47 (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
98 # Don't remove next line
99 # CT_INSERT_VERSION_STRING_BELOW
100 default "2.6.34" if KERNEL_V_2_6_34
101 default "2.6.33.5" if KERNEL_V_2_6_33_5
102 default "2.6.33.4" if KERNEL_V_2_6_33_4
103 default "2.6.33.3" if KERNEL_V_2_6_33_3
104 default "2.6.33.2" if KERNEL_V_2_6_33_2
105 default "2.6.33.1" if KERNEL_V_2_6_33_1
106 default "2.6.33" if KERNEL_V_2_6_33
107 default "2.6.32.14" if KERNEL_V_2_6_32_14
108 default "2.6.31.13" if KERNEL_V_2_6_31_13
109 default "2.6.30.10" if KERNEL_V_2_6_30_10
110 default "2.6.27.47" if KERNEL_V_2_6_27_47
114 prompt "Kernel verbosity:"
115 default KERNEL_LINUX_VERBOSITY_0
117 config KERNEL_LINUX_VERBOSITY_0
121 Print simplified command lines.
123 config KERNEL_LINUX_VERBOSITY_1
125 prompt "Full commands"
127 Print full command lines.
129 config KERNEL_LINUX_VERBOSITY_2
131 prompt "Exec reasons"
133 Print the reasons why a make target is rebuild.
137 config KERNEL_LINUX_VERBOSE_LEVEL
139 default 0 if KERNEL_LINUX_VERBOSITY_0
140 default 1 if KERNEL_LINUX_VERBOSITY_1
141 default 2 if KERNEL_LINUX_VERBOSITY_2
145 config KERNEL_LINUX_USE_CUSTOM_HEADERS
147 prompt "Use custom headers"
149 If you have some kernel headers lying around, you can enter the path
152 if KERNEL_LINUX_USE_CUSTOM_HEADERS
154 config KERNEL_LINUX_CUSTOM_IS_TARBALL
156 prompt "This is a tarball"
159 If you say 'n' here, the path below is expected to point to a directory
160 containing readily prepared headers
162 If you say 'y' here, then the path below is expected to point to a
163 tarball of such a directory.
165 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
166 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
168 Now, passing a tarball around is easier than passing a directory, so
169 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
170 say 'y' here, and enter the path to this tarball below.
172 config KERNEL_LINUX_CUSTOM_PATH
174 prompt "Path to custom headers directory/tarball"
176 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
178 endif # KERNEL_LINUX_USE_CUSTOM_DIR