1 # Options specific to extracting packages
7 prompt "Force extractions"
10 Force extraction of already exctracted tarballs.
12 Usefull if you suspect a previous extract did not complete (eg. broken
13 tarball), or you added a new set of patches for this component.
15 config OVERIDE_CONFIG_GUESS_SUB
17 prompt "Override config.{guess,sub}"
20 Override tools' versions of config.guess and config.sub with the ones
21 from crosstool-NG. This means that all instances of config.guess and
22 config.sub in gcc, binutils, glibc, etc... will be replaced.
24 Most of the time, the versions of those scripts found in packages are old
25 versions, thus lacking some target definitions. This is the case for
26 uClibc-based tuples in old versions of gcc and gdb, for example.
28 Also, doing so will guarantee that all components have the same tuples
29 definitions for your target, and not diverging ones.
31 You can update the ones provided with crosstool-NG by first running:
33 in the directory where you want to run crosstool-NG prior to the build.
37 prompt "Stop after extracting tarballs"
40 Exit after unpacking and patching tarballs.
42 Usefull to look at the code before doing the build itself.
45 prompt "Patches origin"
53 Only apply patches bundled with crosstool-NG.
58 select PATCH_USE_LOCAL
60 Only apply your local patches.
62 config PATCH_BUNDLED_LOCAL
64 prompt "Bundled, then local"
65 select PATCH_USE_LOCAL
67 Apply the patches bundled with crosstool-NG,
68 then apply your local patches.
70 config PATCH_LOCAL_BUNDLED
72 prompt "Local, then bundled"
73 select PATCH_USE_LOCAL
75 Apply your local patches, then apply the patches
76 bundled with crosstool-NG.
78 config PATCH_BUNDLED_FALLBACK_LOCAL
80 prompt "Bundled only, local if no bundled"
81 select PATCH_USE_LOCAL
84 Apply the patches bundled with crosstool-NG;
85 if there's no bundled patches, apply your local patches.
87 config PATCH_LOCAL_FALLBACK_BUNDLED
89 prompt "Local only, bundled if no local"
90 select PATCH_USE_LOCAL
93 Only apply your local patches;
94 if there's no local patches, apply patches bundled with crosstool-NG.
100 Don't use any patch at all.
102 Please be carefull if you select this. Most components do require
103 patches to properly build. It can happen, however, that support for
104 your architecture is clean enough that you can build a toolchain
105 with no patch. But most probably, this is *not* the case.
107 Be safe, use (the bundeld) patches.
113 default "bundled" if PATCH_BUNDLED
114 default "local" if PATCH_LOCAL
115 default "bundled,local" if PATCH_BUNDLED_LOCAL
116 default "local,bundled" if PATCH_LOCAL_BUNDLED
117 default "none" if PATCH_NONE
123 config PATCH_USE_LOCAL
127 config LOCAL_PATCH_DIR
129 prompt "| Local patch directory"
131 depends on PATCH_USE_LOCAL
133 Enter the custom patch directory here.
135 Note that you must ensure that the directory contianing your custom
136 patches is arranged the same way the official directory is.