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_1
41 config KERNEL_V_2_6_33
45 config KERNEL_V_2_6_32_10
49 config KERNEL_V_2_6_31_12
53 config KERNEL_V_2_6_30_10
57 config KERNEL_V_2_6_29_6
59 prompt "2.6.29.6 (OBSOLETE)"
62 config KERNEL_V_2_6_28_10
64 prompt "2.6.28.10 (OBSOLETE)"
67 config KERNEL_V_2_6_27_45
69 prompt "2.6.27.45 (long-term stable)"
71 The Linux 2.6.27 tree is the current "long-term stable" maintenance branch.
72 It is intended to fill the niche for users who are not using distribution
73 kernels but want to use a regression-free kernel for a longer time.
75 Critical bug fixes to later 2.6 releases are often ported to this branch
76 which makes 2.6.27 a very useful base for many embedded developers seeking
77 stable APIs or those who do not need the latest bleeding edge features.
79 ... and no, this kernel has not undergone any specific QA testing.
81 See the original announcement by Adrian Bunk in the following mailing list
82 entry: http://marc.info/?l=linux-kernel&m=122375909403298&w=2
88 # Don't remove next line
89 # CT_INSERT_VERSION_STRING_BELOW
90 default "2.6.33.1" if KERNEL_V_2_6_33_1
91 default "2.6.33" if KERNEL_V_2_6_33
92 default "2.6.32.10" if KERNEL_V_2_6_32_10
93 default "2.6.31.12" if KERNEL_V_2_6_31_12
94 default "2.6.30.10" if KERNEL_V_2_6_30_10
95 default "2.6.29.6" if KERNEL_V_2_6_29_6
96 default "2.6.28.10" if KERNEL_V_2_6_28_10
97 default "2.6.27.45" if KERNEL_V_2_6_27_45
101 prompt "Kernel verbosity:"
102 default KERNEL_LINUX_VERBOSITY_0
104 config KERNEL_LINUX_VERBOSITY_0
108 Print simplified command lines.
110 config KERNEL_LINUX_VERBOSITY_1
112 prompt "Full commands"
114 Print full command lines.
116 config KERNEL_LINUX_VERBOSITY_2
118 prompt "Exec reasons"
120 Print the reasons why a make target is rebuild.
124 config KERNEL_LINUX_VERBOSE_LEVEL
126 default 0 if KERNEL_LINUX_VERBOSITY_0
127 default 1 if KERNEL_LINUX_VERBOSITY_1
128 default 2 if KERNEL_LINUX_VERBOSITY_2
132 config KERNEL_LINUX_USE_CUSTOM_HEADERS
134 prompt "Use custom headers"
136 If you have some kernel headers lying around, you can enter the path
139 if KERNEL_LINUX_USE_CUSTOM_HEADERS
141 config KERNEL_LINUX_CUSTOM_IS_TARBALL
143 prompt "This is a tarball"
146 If you say 'n' here, the path below is expected to point to a directory
147 containing readily prepared headers
149 If you say 'y' here, then the path below is expected to point to a
150 tarball of such a directory.
152 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
153 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
155 Now, passing a tarball around is easier than passing a directory, so
156 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
157 say 'y' here, and enter the path to this tarball below.
159 config KERNEL_LINUX_CUSTOM_PATH
161 prompt "Path to custom headers directory/tarball"
163 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
165 endif # KERNEL_LINUX_USE_CUSTOM_DIR