1 # Companion libraries config options
2 # Those libraries are required for different versions of gcc,
3 # and can be used by binutils and gdb (maybe others as well).
5 menu "Companion libraries"
7 comment "FIXME: check real dependencies!!!"
22 gcc 4.3.0 and above requires GMP to build some frontends, and some
23 other components can use them as well.
25 This will be automatically selected if you choose gcc>=4.3.0, but you
26 can say 'Y' here if you want to build this library for the other
27 components (that don't select them by default).
29 The packages that can use GMP and MPFR are:
40 gcc 4.3.0 and above requires MPFR to build some frontends, and some
41 other components can use them as well.
43 This will be automatically selected if you choose gcc>=4.3.0, but you
44 can say 'Y' here if you want to build this library for the other
45 components (that don't select them by default).
47 The packages that can use GMP and MPFR are:
59 gcc-4.4.0 and above requires PPL to build some parts of the optimiser
60 (the GRAPHITE loop optimisation, to be precise).
62 This will be automatically selected if you choose gcc>=4.4.0, but you
63 can say 'Y' here, although it is unknown yet if any other component
74 gcc-4.4.0 and above requires CLooG/PPL to build some parts of the
75 optimiser (the GRAPHITE loop optimisation, to be precise).
77 This will be automatically selected if you choose gcc>=4.4.0, but you
78 can say 'Y' here, although it is unknown yet if any other component
90 gcc-4.4.0 and above can also optionally use MPC to enable additional
91 optimisations on complex numbers. Although MPC is optional,
92 crosstool-NG requires it and uses it to build gcc >= 4.4.0.
94 This will be automatically selected if you choose gcc>=4.4.0, but you
95 can say 'Y' here, although it is unknown yet if any other component
101 select WRAPPER_NEEDED
103 gcc-4.5.0 and above can also use libelf to enable some optimisation
104 (LTO, Link-Time Optimisation, to be precise). Although libelf is
105 optional, crosstool-NG requires it and uses it to build gcc >= 4.5.0.
107 This will be automatically selected if you choose gcc>=4.5.0, but you
108 can say 'Y' here, although it is unknown yet if any other component
140 comment "GMP version needed to build for target"
142 source config/companion_libs/gmp.in
144 if MPFR || MPFR_TARGET
145 comment "MPFR version needed to build for target"
147 source config/companion_libs/mpfr.in
150 comment "PPL version needed to build for target"
152 source config/companion_libs/ppl.in
154 if CLOOG || CLOOG_TARGET
155 comment "CLOOG version needed to build for target"
157 source config/companion_libs/cloog.in
160 comment "MPC version needed to build for target"
162 source config/companion_libs/mpc.in
164 if LIBELF || LIBELF_TARGET
165 comment "libelf version needed to build for target"
167 source config/companion_libs/libelf.in
173 comment "Companion libraries common options"
174 depends on COMPLIBS || WRAPPER_NEEDED
176 config COMP_LIBS_CHECK
178 prompt "| Check the companion libraries builds (!!! READ HELP!!!)"
182 It is highly recommended to check the newly built companion libraries.
183 Unfortunately, this is a very intensive task, and takes a loooong time.
185 Checking the newly built companion libraries is thus disabled by default,
186 but it is suggested that you check them at least once on your machine,
187 and if they work, disable the check on subsequent builds.
189 If you suspect that one (or more) of your companion libraries is the
190 cause for incorrectly generated code, you should answer 'Y' here.
191 Note however that this will take a really long time. For example,
192 building PPL on my machine takes roughly 1'40", while checking it takes
197 prompt "| Install tools wrapper as:"
198 depends on WRAPPER_NEEDED
199 default TOOLS_WRAPPER_SHELL
201 config TOOLS_WRAPPER_SCRIPT
203 prompt "shell script"
205 If your host has a shell, then you should say 'Y' here, to use
206 a (very very simple) shell script as wrapper.
208 See docs/overview.txt, section "Tools wrapper".
210 config TOOLS_WRAPPER_EXEC
214 If your host lacks a shell, then you should say 'Y' here, to use
217 See docs/overview.txt, section "Tools wrapper".
223 default "script" if TOOLS_WRAPPER_SCRIPT
224 default "exec" if TOOLS_WRAPPER_EXEC