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"
11 gcc 4.3.0 and above requires both GMP and MPFR to build some frontends,
12 and some other components can use them as well.
14 These will be automatically selected if you choose gcc>=4.3.0, but you
15 can say 'Y' here if you want to build those two libraries for the other
16 components (that don't select them by default).
18 The packages that can use GMP and MPFR are:
23 config GMP_MPFR_TARGET
25 prompt "Build libraries for the target"
27 depends on ! BARE_METAL
30 Also build libraries for the target. This can be usefull if you want
31 to later build a compiler that will run on the target, or if you want
32 to run gdb natively on the target.
35 source config/companion_libs/gmp.in
36 source config/companion_libs/mpfr.in
41 prompt "PPL, GLooG/PPL and MPC"
43 gcc-4.4.0 and above requires PPL and CLooG/PPL to build some parts
44 of the optimiser (GRAPHITE loop optimisation, to be precise).
46 In addition to those, gcc-4.4 also optionally uses MPC to enable
47 additional optimisations on complex numbers. Although MPC is optional,
48 crosstool-NG requires it and uses it to build gcc >= 4.4.0.
50 These will be automatically selected if you choose gcc>=4.4.0, but you
51 can say 'Y' here, although it is unknown yet if any other component
55 source config/companion_libs/ppl.in
56 source config/companion_libs/cloog.in
57 source config/companion_libs/mpc.in