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

-- 
Robert Berger
Embedded Software Specialist

Reliable Embedded Systems
Consulting Training Engineering
Tel.: (+30) 697 593 3428
Fax.:(+30) 210 684 7881
URL: http://www.reliableembeddedsystems.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
..."It is always easier to ask forgiveness than it is to get
permission." - (Amazing) Grace Hopper

My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1



------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to