Typo.
/trunk/config/toolchain.in | 2 1 1 0 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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 libraries if you're building for a target that
23 don't support it (maybe some nommu targets, for example, or bare metal).
27 prompt "Vendor string"
30 Vendor part of the target tuple.
32 A tuple is of the form arch-vendor-kernel-system.
33 You can set the second part, vendor, to whatever you see fit.
34 Use a single word, or use underscores "_" to separate words.
36 Keep the default (unkown) if you don't know better.
38 config TARGET_ALIAS_SED_EXPR
40 prompt "Target sed transform"
43 Normaly, you'd call your toolchain components (especially gcc) by
44 prefixing the target tuple followed by a dash and the component name
45 (eg. armeb-unknown-linux-uclibc-gcc).
47 You can enter here a sed expression to be applied to ${CT_TARGET} to
48 create an alias for your toolchain.
50 For example, "s/${CT_TARGET_VENDOR}/foobar/" (without the double quotes)
51 will create the armeb-foobar-linux-uclibc alias to the above-mentioned
54 You shouldn't need to enter anything here, unless you plan to manually
55 call the tools (autotools-based ./configure will use the standard name).
62 Normaly, you'd call your toolchain components (especially gcc) by
63 prefixing the target tuple followed by a dash and the component name
64 (eg. armeb-unknown-linux-uclibc-gcc).
66 You can enter a shortcut here. This string will be used to create
67 symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
68 then gcc for your toolchain will also be available as "foo-bar-gcc" along
69 with the original name).
71 You shouldn't need to enter anything here, unless you plan to manually
72 call the tools (autotools-based ./configure will use the standard name).
74 comment "Toolchain type"
83 prompt "Native (EXPERIMENTAL)"
84 depends on EXPERIMENTAL
86 Build a native toolchain.
93 Build a cross-toolchain.
98 prompt "Cross-native (EXPERIMENTAL)"
99 depends on EXPERIMENTAL
101 Build a cross-native toolchain.
102 See docs/overview.txt
106 prompt "Canadian (EXPERIMENTAL)"
107 depends on EXPERIMENTAL
109 Build a canadian-toolchain.
110 See docs/overview.txt
114 config TOOLCHAIN_TYPE
116 default "native" if NATIVE
117 default "cross" if CROSS
118 default "cross-native" if CROSS_NATIVE
119 default "canadian" if CANADIAN
123 prompt "Build system tuple"
126 Canonical name of the machine building the toolchain.
127 You should leave empty, unless you really now what you're doing.
134 The native C compiler.
136 You can set this to an alternative compiler if you have more than one
137 installed (eg. gcc is gcc-4.1.1 and you want to use gcc-3.4.6).
139 You can leave this empty as well, in which case gcc will be used.
143 prompt "Host system tuple"
145 depends on NATIVE || CANADIAN
147 Canonical name of the machine running the toolchain.
151 prompt "Cross-compiler prefix for host system"
152 default "${CT_HOST}-"
153 depends on NATIVE || CANADIAN
155 C compiler targeting the host system.
159 prompt "Cross-compiler prefix for target system"
160 default "${CT_TARGET}-"
163 C compiler targeting the target system.