1 # Options specific to extracting packages
7 prompt "Force extractions"
9 Force extraction of already exctracted tarballs.
11 Usefull if you suspect a previous extract did not complete (eg. broken
12 tarball), or you added a new set of patches for this component.
14 config OVERIDE_CONFIG_GUESS_SUB
16 prompt "Override config.{guess,sub}"
19 Override tools' versions of config.guess and config.sub with the ones
20 from crosstool-NG. This means that all instances of config.guess and
21 config.sub in gcc, binutils, glibc, etc... will be replaced.
23 Most of the time, the versions of those scripts found in packages are old
24 versions, thus lacking some target definitions. This is the case for
25 uClibc-based tuples in old versions of gcc and gdb, for example.
27 Also, doing so will guarantee that all components have the same tuples
28 definitions for your target, and not diverging ones.
30 You can update the ones provided with crosstool-NG by first running:
32 in the directory where you want to run crosstool-NG prior to the build.
36 prompt "Stop after extracting tarballs"
38 Exit after unpacking and patching tarballs.
40 Usefull to look at the code before doing the build itself.
43 prompt "Patches origin"
51 Only apply patches bundled with crosstool-NG.
56 select PATCH_USE_LOCAL
58 Only apply your local patches.
60 config PATCH_BUNDLED_LOCAL
62 prompt "Bundled, then local"
63 select PATCH_USE_LOCAL
65 Apply the patches bundled with crosstool-NG,
66 then apply your local patches.
68 config PATCH_LOCAL_BUNDLED
70 prompt "Local, then bundled"
71 select PATCH_USE_LOCAL
73 Apply your local patches, then apply the patches
74 bundled with crosstool-NG.
76 config PATCH_BUNDLED_FALLBACK_LOCAL
78 prompt "Bundled only, local if no bundled"
79 select PATCH_USE_LOCAL
82 Apply the patches bundled with crosstool-NG;
83 if there's no bundled patches, apply your local patches.
85 config PATCH_LOCAL_FALLBACK_BUNDLED
87 prompt "Local only, bundled if no local"
88 select PATCH_USE_LOCAL
91 Only apply your local patches;
92 if there's no local patches, apply patches bundled with crosstool-NG.
98 Don't use any patch at all.
100 Please be carefull if you select this. Most components do require
101 patches to properly build. It can happen, however, that support for
102 your architecture is clean enough that you can build a toolchain
103 with no patch. But most probably, this is *not* the case.
105 Be safe, use (the bundeld) patches.
111 default "bundled" if PATCH_BUNDLED
112 default "local" if PATCH_LOCAL
113 default "bundled,local" if PATCH_BUNDLED_LOCAL || PATCH_BUNDLED_FALLBACK_LOCAL
114 default "local,bundled" if PATCH_LOCAL_BUNDLED || PATCH_LOCAL_FALLBACK_BUNDLED
115 default "none" if PATCH_NONE
120 config PATCH_USE_LOCAL
123 config LOCAL_PATCH_DIR
125 prompt "| Local patch directory"
127 depends on PATCH_USE_LOCAL
129 Enter the custom patch directory here.
131 Note that you must ensure that the directory contianing your custom
132 patches is arranged the same way the official directory is.