Move the whole threading ;odel choice out of glibc and into the generic C library options: even uClibc may have NPTL at one point in the (hopefully near) future.
Mark the progress bar as being CPU-intensive.
Little style fix to the core C compiler build step.
1 menu "Toolchain options"
3 comment "General toolchain options"
7 prompt "Use sysroot'ed toolchain"
10 Use the 'shinny new' sysroot feature of gcc: libraries split between
11 prefix/target/sys-root/lib and prefix/target/sys-root/usr/lib
13 You definitely want to say 'Y' here. Yes you do. I know you do. Say 'Y'.
17 prompt "Build shared libraries"
20 Say 'y' here, unless you don't want shared libraries.
22 You might not want shared librries if you're building for a target that
23 don't support it (maybe some nommu targets, for example, or bare metal).
25 config TARGET_MULTILIB
27 # prompt "Enable 'multilib' support (EXPERIMENTAL)"
30 Enable the so-called 'multilib' support.
32 With the same toolchain, and on some architectures, you will be able to
33 build big and little endian binaries, soft- and hard-float, etc...
35 See the gcc configure manual at http://gcc.gnu.org/install/configure.html
36 to see what multilib your target supports.
38 It's preferable for now to build two (or more) toolchains, one for each
39 configuration you need to support (eg. one for thumb and one for ARM,
40 etc...). You can use the vendor string to diferentiate those toolchains.
44 prompt "Vendor string"
47 Vendor part of the machine triplet.
49 A triplet is of the form arch-vendor-kernel-system.
50 You can set the second part, vendor, to whatever you see fit.
51 Use a single word, or use underscores "_" to separate words.
53 Keep the default (unkown) if you don't know better.
60 Normaly, you'd call your toolchain component (especially gcc) by
61 prefixing the target triplet followed by a dash and the component name
62 (eg. armeb-unknown-linux-uclibc-gcc).
64 You can enter a shortcut here. This string will be used to create
65 symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
66 then gcc for your toolchain will also be available as "foo-bar-gcc" along
67 with the original name).
69 You shouldn't need to enter anything here, unless you plan to manually
70 call the tools (autotools-based ./configure will use the standard name).
72 comment "Toolchain type"
81 prompt "Native (EXPERIMENTAL)"
82 depends on EXPERIMENTAL
84 Build a native toolchain.
91 Build a cross-toolchain.
96 prompt "Croos-native (EXPERIMENTAL)"
97 depends on EXPERIMENTAL
99 Build a cross-native toolchain.
100 See docs/overview.txt
104 prompt "Canadian (EXPERIMENTAL)"
105 depends on EXPERIMENTAL
107 Build a canadian-toolchain.
108 See docs/overview.txt
114 prompt "Build system triplet"
117 Canonical name of the machine building the toolchain.
118 You should leave empty, unless you really now what you're doing.
125 The native C compiler.
127 You can set this to an alternative compiler if you have more than one
128 installed (eg. gcc is gcc-4.1.1 and you want to use gcc-3.4.6).
130 You can leave this empty as well, in which case gcc will be used.
134 prompt "Host system triplet"
136 depends on NATIVE || CANADIAN
138 Canonical name of the machine running the toolchain.
142 prompt "Cross-compiler prefix for host system"
143 default "${CT_HOST}-"
144 depends on NATIVE || CANADIAN
146 C compiler targeting the host system.
150 prompt "Cross-compiler prefix for target system"
151 default "${CT_TARGET}-"
154 C compiler targeting the target system.