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!!!"
23 gcc 4.3.0 and above requires GMP to build some frontends, and some
24 other components can use them as well.
26 This will be automatically selected if you choose gcc>=4.3.0, but you
27 can say 'Y' here if you want to build this library for the other
28 components (that don't select them by default).
30 The packages that can use GMP and MPFR are:
42 gcc 4.3.0 and above requires MPFR to build some frontends, and some
43 other components can use them as well.
45 This will be automatically selected if you choose gcc>=4.3.0, but you
46 can say 'Y' here if you want to build this library for the other
47 components (that don't select them by default).
49 The packages that can use GMP and MPFR are:
62 gcc-4.4.0 and above requires PPL to build some parts of the optimiser
63 (the GRAPHITE loop optimisation, to be precise).
65 This will be automatically selected if you choose gcc>=4.4.0, but you
66 can say 'Y' here, although it is unknown yet if any other component
78 gcc-4.4.0 and above requires CLooG/PPL to build some parts of the
79 optimiser (the GRAPHITE loop optimisation, to be precise).
81 This will be automatically selected if you choose gcc>=4.4.0, but you
82 can say 'Y' here, although it is unknown yet if any other component
95 gcc-4.4.0 and above can also optionally use MPC to enable additional
96 optimisations on complex numbers. Although MPC is optional,
97 crosstool-NG requires it and uses it to build gcc >= 4.4.0.
99 This will be automatically selected if you choose gcc>=4.4.0, but you
100 can say 'Y' here, although it is unknown yet if any other component
129 comment "GMP version needed to build for target"
131 source config/companion_libs/gmp.in
133 if MPFR || MPFR_TARGET
134 comment "MPFR version needed to build for target"
136 source config/companion_libs/mpfr.in
139 comment "PPL version needed to build for target"
141 source config/companion_libs/ppl.in
143 if CLOOG || CLOOG_TARGET
144 comment "CLOOG version needed to build for target"
146 source config/companion_libs/cloog.in
149 comment "MPC version needed to build for target"
151 source config/companion_libs/mpc.in
157 comment "Companion libraries common options"
158 depends on COMPLIBS || WRAPPER_NEEDED
160 config COMP_LIBS_CHECK
162 prompt "| Check the companion libraries builds (!!! READ HELP!!!)"
166 It is highly recommended to check the newly built companion libraries.
167 Unfortunately, this is a very intensive task, and takes a loooong time.
169 Checking the newly built companion libraries is thus disabled by default,
170 but it is suggested that you check them at least once on your machine,
171 and if they work, disable the check on subsequent builds.
173 If you suspect that one (or more) of your companion libraries is the
174 cause for incorrectly generated code, you should answer 'Y' here.
175 Note however that this will take a really long time. For example,
176 building PPL on my machine takes roughly 1'40", while checking it takes
181 prompt "| Install tools wrapper as:"
182 depends on WRAPPER_NEEDED
183 default TOOLS_WRAPPER_SHELL
185 config TOOLS_WRAPPER_SCRIPT
187 prompt "shell script"
189 If your host has a shell, then you should say 'Y' here, to use
190 a (very very simple) shell script as wrapper.
192 See docs/overview.txt, section "Tools wrapper".
194 config TOOLS_WRAPPER_EXEC
198 If your host lacks a shell, then you should say 'Y' here, to use
201 See docs/overview.txt, section "Tools wrapper".
207 default "script" if TOOLS_WRAPPER_SCRIPT
208 default "exec" if TOOLS_WRAPPER_EXEC