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"
49 source "config/companion_libs/gmp.in"
52 source "config/companion_libs/mpfr.in"
55 source "config/companion_libs/ppl.in"
58 source "config/companion_libs/cloog.in"
61 source "config/companion_libs/mpc.in"
63 if LIBELF || LIBELF_TARGET
64 comment "libelf version needed to build for target"
66 source "config/companion_libs/libelf.in"
74 comment "Companion libraries common options"
78 prompt "Check the companion libraries builds (!!! READ HELP!!!)"
81 It is highly recommended to check the newly built companion libraries.
82 Unfortunately, this is a very intensive task, and takes a loooong time.
84 Checking the newly built companion libraries is thus disabled by default,
85 but it is suggested that you check them at least once on your machine,
86 and if they work, disable the check on subsequent builds.
88 If you suspect that one (or more) of your companion libraries is the
89 cause for incorrectly generated code, you should answer 'Y' here.
90 Note however that this will take a really long time. For example,
91 building PPL on my machine takes roughly 1'40", while checking it takes
94 config COMPLIBS_SHARED
96 prompt "Build shared companion libraries"
101 By default, the companion libraries will be build static. If you want to
102 build shared libraries, then you can say 'Y' here, but a wrapper will be
103 needed (see docs/overview.txt,section "Tools wrapper").
105 It is highly recommended that you keep static libraries.
109 prompt "| Install tools wrapper as:"
110 depends on WRAPPER_NEEDED
111 default TOOLS_WRAPPER_SHELL
113 config TOOLS_WRAPPER_SCRIPT
115 prompt "shell script"
117 If your host has a shell, then you should say 'Y' here, to use
118 a (very very simple) shell script as wrapper.
120 See docs/overview.txt, section "Tools wrapper".
122 config TOOLS_WRAPPER_EXEC
126 If your host lacks a shell, then you should say 'Y' here, to use
129 See docs/overview.txt, section "Tools wrapper".
135 default "script" if TOOLS_WRAPPER_SCRIPT
136 default "exec" if TOOLS_WRAPPER_EXEC