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
33 config KERNEL_V_2_6_33_5
37 config KERNEL_V_2_6_33_4
41 config KERNEL_V_2_6_33_3
45 config KERNEL_V_2_6_33_2
49 config KERNEL_V_2_6_33_1
53 config KERNEL_V_2_6_33
57 config KERNEL_V_2_6_32_14
61 config KERNEL_V_2_6_31_13
65 config KERNEL_V_2_6_30_10
69 config KERNEL_V_2_6_27_47
71 prompt "2.6.27.47 (long-term stable)"
73 The Linux 2.6.27 tree is the current "long-term stable" maintenance branch.
74 It is intended to fill the niche for users who are not using distribution
75 kernels but want to use a regression-free kernel for a longer time.
77 Critical bug fixes to later 2.6 releases are often ported to this branch
78 which makes 2.6.27 a very useful base for many embedded developers seeking
79 stable APIs or those who do not need the latest bleeding edge features.
81 ... and no, this kernel has not undergone any specific QA testing.
83 See the original announcement by Adrian Bunk in the following mailing list
84 entry: http://marc.info/?l=linux-kernel&m=122375909403298&w=2
90 # Don't remove next line
91 # CT_INSERT_VERSION_STRING_BELOW
92 default "2.6.34" if KERNEL_V_2_6_34
93 default "2.6.33.5" if KERNEL_V_2_6_33_5
94 default "2.6.33.4" if KERNEL_V_2_6_33_4
95 default "2.6.33.3" if KERNEL_V_2_6_33_3
96 default "2.6.33.2" if KERNEL_V_2_6_33_2
97 default "2.6.33.1" if KERNEL_V_2_6_33_1
98 default "2.6.33" if KERNEL_V_2_6_33
99 default "2.6.32.14" if KERNEL_V_2_6_32_14
100 default "2.6.31.13" if KERNEL_V_2_6_31_13
101 default "2.6.30.10" if KERNEL_V_2_6_30_10
102 default "2.6.27.47" if KERNEL_V_2_6_27_47
106 prompt "Kernel verbosity:"
107 default KERNEL_LINUX_VERBOSITY_0
109 config KERNEL_LINUX_VERBOSITY_0
113 Print simplified command lines.
115 config KERNEL_LINUX_VERBOSITY_1
117 prompt "Full commands"
119 Print full command lines.
121 config KERNEL_LINUX_VERBOSITY_2
123 prompt "Exec reasons"
125 Print the reasons why a make target is rebuild.
129 config KERNEL_LINUX_VERBOSE_LEVEL
131 default 0 if KERNEL_LINUX_VERBOSITY_0
132 default 1 if KERNEL_LINUX_VERBOSITY_1
133 default 2 if KERNEL_LINUX_VERBOSITY_2
135 config KERNEL_LINUX_INSTALL_CHECK
137 prompt "Check installed headers"
140 If you are in doubt that installed headers are buggy, say 'Y'
141 here to have an extra check passed onto the headers.
143 endif # KERNEL_LINUX_INSTALL
145 config KERNEL_LINUX_USE_CUSTOM_HEADERS
147 prompt "custom, and/or pre-installed, headers tree"
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_HEADERS