|
From: Julian S. <js...@ac...> - 2010-06-06 20:19:09
|
Oh, darn. It looks like I broke cross compilation recently by introducing link_tool_exe.c as part of the build process. Honestly .. the your best bet is to rewrite link_tool_exe.c as a perl script, so it can run on the host. I actually started out to write it as a perl script, but couldn't find a way to make it portably do 64-bit arithmetic, which it needs to do on some platforms. Hence I wimped out and wrote a C program instead. However, that evidently isn't going to work in this case. J On Sunday 06 June 2010, Robert Berger wrote: > Hi, > > I'm trying to get valgrind running with an AMCC PPC kilauea board, > ELDK4.2, and a recent kernel. > > That's what I did so far: > svn co svn://svn.valgrind.org/valgrind/trunk valgrind > cp dispatch-ppc32-linux.S valgrind/coregrind/m_dispatch > (that's a patched version, which gets rid of the altivec instructions) > cd valgrind > source ../../../env.sh > (this sets up my cross environment) > ./autogen.sh > ./configure --host=powerpc-linux > --prefix=$ELDK_PREFIX/eldk-4.2-ppc_4xx/ppc_4xx > make > > it fails like this: > mv -f .deps/memcheck_ppc32_linux-mc_translate.Tpo > .deps/memcheck_ppc32_linux-mc_translate.Po > powerpc-linux-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include > -I../VEX/pub -DVGA_ppc32=1 -DVGO_linux=1 -DVGP_ppc32_linux=1 -m32 -O2 > -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith > -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length > -fno-strict-aliasing -O2 -Wno-long-long -Wno-pointer-sign > -fno-stack-protector -MT memcheck_ppc32_linux-mc_machine.o -MD -MP -MF > .deps/memcheck_ppc32_linux-mc_machine.Tpo -c -o > memcheck_ppc32_linux-mc_machine.o `test -f 'mc_machine.c' || echo > './'`mc_machine.c > mv -f .deps/memcheck_ppc32_linux-mc_machine.Tpo > .deps/memcheck_ppc32_linux-mc_machine.Po > powerpc-linux-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include > -I../VEX/pub -DVGA_ppc32=1 -DVGO_linux=1 -DVGP_ppc32_linux=1 -m32 -O2 > -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith > -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length > -fno-strict-aliasing -O2 -Wno-long-long -Wno-pointer-sign > -fno-stack-protector -MT memcheck_ppc32_linux-mc_errors.o -MD -MP -MF > .deps/memcheck_ppc32_linux-mc_errors.Tpo -c -o > memcheck_ppc32_linux-mc_errors.o `test -f 'mc_errors.c' || echo > './'`mc_errors.c > mv -f .deps/memcheck_ppc32_linux-mc_errors.Tpo > .deps/memcheck_ppc32_linux-mc_errors.Po > ../coregrind/link_tool_exe 0x38000000 powerpc-linux-gcc -Wno-long-long > -Wno-pointer-sign -fno-stack-protector -o memcheck-ppc32-linux -m32 > -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith > -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length > -fno-strict-aliasing -O2 -static -nodefaultlibs -nostartfiles -u _start > -m32 memcheck_ppc32_linux-mc_leakcheck.o > memcheck_ppc32_linux-mc_malloc_wrappers.o memcheck_ppc32_linux-mc_main.o > memcheck_ppc32_linux-mc_translate.o memcheck_ppc32_linux-mc_machine.o > memcheck_ppc32_linux-mc_errors.o ../coregrind/libcoregrind-ppc32-linux.a > ../VEX/libvex-ppc32-linux.a -lgcc > ../coregrind/link_tool_exe: ../coregrind/link_tool_exe: cannot execute > binary file > make[3]: *** [memcheck-ppc32-linux] Error 126 > make[3]: Leaving directory > `/home/rber/projects/ldd/ldd_for_trainer/src/30_valgrind/valgrind/memcheck' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory > `/home/rber/projects/ldd/ldd_for_trainer/src/30_valgrind/valgrind/memcheck' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory > `/home/rber/projects/ldd/ldd_for_trainer/src/30_valgrind/valgrind' > make: *** [all] Error 2 > > The link_tool_exe is a ppc executable, so it can not be executed by my > x86 host. > When I try not to build on my host but directly on my target it fails > because it does not find the aclocal. > > Please advise. > > Regards, > > Robert |