Make sure that the PTRACE_... symbols are available for ppc/plt.c.
On a Fedora 12 x86_64 build/host box, this file was complaining about
PTRACE_PEEKTEXT being undefined. Adding in the "ptrace.h" include
fixed it.
Signed-off-by: Anthony Foiani <anthony.foiani@gmail.com>
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"
15 select COMPLIBS_NEEDED
21 select COMPLIBS_NEEDED
27 select COMPLIBS_NEEDED
33 select COMPLIBS_NEEDED
39 select COMPLIBS_NEEDED
45 select COMPLIBS_NEEDED
89 source "config/companion_libs/gmp.in"
92 source "config/companion_libs/mpfr.in"
95 source "config/companion_libs/ppl.in"
98 source "config/companion_libs/cloog.in"
101 source "config/companion_libs/mpc.in"
103 if LIBELF || LIBELF_TARGET
104 comment "libelf version needed to build for target"
106 source "config/companion_libs/libelf.in"
114 comment "Companion libraries common options"
116 config COMPLIBS_BACKUP
119 depends on ! COMPLIBS_SHARED
121 config COMPLIBS_CHECK
123 prompt "Check the companion libraries builds (!!! READ HELP!!!)"
126 It is highly recommended to check the newly built companion libraries.
127 Unfortunately, this is a very intensive task, and takes a loooong time.
129 Checking the newly built companion libraries is thus disabled by default,
130 but it is suggested that you check them at least once on your machine,
131 and if they work, disable the check on subsequent builds.
133 If you suspect that one (or more) of your companion libraries is the
134 cause for incorrectly generated code, you should answer 'Y' here.
135 Note however that this will take a really long time. For example,
136 building PPL on my machine takes roughly 1'40", while checking it takes
139 config COMPLIBS_SHARED
141 prompt "Build shared companion libraries"
144 select WRAPPER_NEEDED
146 By default, the companion libraries will be build static. If you want to
147 build shared libraries, then you can say 'Y' here, but a wrapper will be
148 needed (see docs/overview.txt,section "Tools wrapper").
150 It is highly recommended that you keep static libraries.
154 prompt "| Install tools wrapper as:"
155 depends on WRAPPER_NEEDED
156 default TOOLS_WRAPPER_SHELL
158 config TOOLS_WRAPPER_SCRIPT
160 prompt "shell script"
162 If your host has a shell, then you should say 'Y' here, to use
163 a (very very simple) shell script as wrapper.
165 See docs/overview.txt, section "Tools wrapper".
167 config TOOLS_WRAPPER_EXEC
171 If your host lacks a shell, then you should say 'Y' here, to use
174 See docs/overview.txt, section "Tools wrapper".
180 default "script" if TOOLS_WRAPPER_SCRIPT
181 default "exec" if TOOLS_WRAPPER_EXEC