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_33_2
41 config KERNEL_V_2_6_33_1
45 config KERNEL_V_2_6_33
49 config KERNEL_V_2_6_32_11
53 config KERNEL_V_2_6_31_13
57 config KERNEL_V_2_6_30_10
61 config KERNEL_V_2_6_29_6
63 prompt "2.6.29.6 (OBSOLETE)"
66 config KERNEL_V_2_6_28_10
68 prompt "2.6.28.10 (OBSOLETE)"
71 config KERNEL_V_2_6_27_46
73 prompt "2.6.27.46 (long-term stable)"
75 The Linux 2.6.27 tree is the current "long-term stable" maintenance branch.
76 It is intended to fill the niche for users who are not using distribution
77 kernels but want to use a regression-free kernel for a longer time.
79 Critical bug fixes to later 2.6 releases are often ported to this branch
80 which makes 2.6.27 a very useful base for many embedded developers seeking
81 stable APIs or those who do not need the latest bleeding edge features.
83 ... and no, this kernel has not undergone any specific QA testing.
85 See the original announcement by Adrian Bunk in the following mailing list
86 entry: http://marc.info/?l=linux-kernel&m=122375909403298&w=2
92 # Don't remove next line
93 # CT_INSERT_VERSION_STRING_BELOW
94 default "2.6.33.2" if KERNEL_V_2_6_33_2
95 default "2.6.33.1" if KERNEL_V_2_6_33_1
96 default "2.6.33" if KERNEL_V_2_6_33
97 default "2.6.32.11" if KERNEL_V_2_6_32_11
98 default "2.6.31.13" if KERNEL_V_2_6_31_13
99 default "2.6.30.10" if KERNEL_V_2_6_30_10
100 default "2.6.29.6" if KERNEL_V_2_6_29_6
101 default "2.6.28.10" if KERNEL_V_2_6_28_10
102 default "2.6.27.46" if KERNEL_V_2_6_27_46
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
137 config KERNEL_LINUX_USE_CUSTOM_HEADERS
139 prompt "Use custom headers"
141 If you have some kernel headers lying around, you can enter the path
144 if KERNEL_LINUX_USE_CUSTOM_HEADERS
146 config KERNEL_LINUX_CUSTOM_IS_TARBALL
148 prompt "This is a tarball"
151 If you say 'n' here, the path below is expected to point to a directory
152 containing readily prepared headers
154 If you say 'y' here, then the path below is expected to point to a
155 tarball of such a directory.
157 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
158 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
160 Now, passing a tarball around is easier than passing a directory, so
161 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
162 say 'y' here, and enter the path to this tarball below.
164 config KERNEL_LINUX_CUSTOM_PATH
166 prompt "Path to custom headers directory/tarball"
168 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
170 endif # KERNEL_LINUX_USE_CUSTOM_DIR