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"
76 config COMPLIBS_BACKUP
79 depends on ! COMPLIBS_SHARED
83 prompt "Check the companion libraries builds (!!! READ HELP!!!)"
86 It is highly recommended to check the newly built companion libraries.
87 Unfortunately, this is a very intensive task, and takes a loooong time.
89 Checking the newly built companion libraries is thus disabled by default,
90 but it is suggested that you check them at least once on your machine,
91 and if they work, disable the check on subsequent builds.
93 If you suspect that one (or more) of your companion libraries is the
94 cause for incorrectly generated code, you should answer 'Y' here.
95 Note however that this will take a really long time. For example,
96 building PPL on my machine takes roughly 1'40", while checking it takes
99 config COMPLIBS_SHARED
101 prompt "Build shared companion libraries"
104 select WRAPPER_NEEDED
106 By default, the companion libraries will be build static. If you want to
107 build shared libraries, then you can say 'Y' here, but a wrapper will be
108 needed (see docs/overview.txt,section "Tools wrapper").
110 It is highly recommended that you keep static libraries.
114 prompt "| Install tools wrapper as:"
115 depends on WRAPPER_NEEDED
116 default TOOLS_WRAPPER_SHELL
118 config TOOLS_WRAPPER_SCRIPT
120 prompt "shell script"
122 If your host has a shell, then you should say 'Y' here, to use
123 a (very very simple) shell script as wrapper.
125 See docs/overview.txt, section "Tools wrapper".
127 config TOOLS_WRAPPER_EXEC
131 If your host lacks a shell, then you should say 'Y' here, to use
134 See docs/overview.txt, section "Tools wrapper".
140 default "script" if TOOLS_WRAPPER_SCRIPT
141 default "exec" if TOOLS_WRAPPER_EXEC