|
From: Александар М. <dar...@gm...> - 2011-11-11 17:14:00
|
Sure,
once I extracted the valgrind-3.7 tarball into android/external, i
just went into the folder and used this
$ ./configure --build i686-pc-linux-gnu --host arm-marvell-linux-gnueabi
Then configuration proceeded fine... once everything was setup, it was easy
$make clean; make
Both passing good and with no errors.
Then I go into /valgrind-3.7/coregrind and pick up the file from
there, and put it in a folder which is used as the root file system of
the board. A faster alternative to adb pushing really.
So whichever kind of app Valgrind is, I was guessing that I'll
probably be missing some binaries which is why i compiled it
statically.
I even went as far as to put it in /tmp/ folder, enter the folder and
try to call it. So... here's what I did to get up to here.
$ ./configure --build i686-pc-linux-gnu --host arm-marvell-eabi
checking host system type... arm-marvell-eabi
checking for a supported CPU... no (arm)
configure: error: Unsupported host architecture. Sorry
** I go into the configure script and fix that. ***
$ ./configure --build i686-pc-linux-gnu --host arm-marvell-eabi
checking for a supported CPU... ok (arm)
checking for a 64-bit only build... no
checking for a 32-bit only build... no
checking for a supported OS... no (eabi)
this one I wasn't going to fix so instead I just did
$ ./configure --build i686-pc-linux-gnu --host arm-marvell-linux-gnueabi
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for arm-marvell-linux-gnueabi-strip... arm-marvell-linux-gnueabi-strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether ln -s works... yes
checking for arm-marvell-linux-gnueabi-gcc...
/scratch/workareas/MV88DE3100_SDK/SDK_Tools/cross_toolchain/tarballs/4.4.5/arm-marvell-linux-gnueabi-4.4.5/bin/arm-marvell-linux-gnueabi-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... yes
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
. . . . . . .
Maximum build arch: arm
Primary build arch: arm
Secondary build arch:
Build OS: linux
Primary build target: ARM_LINUX
Secondary build target:
Platform variant: vanilla
Primary -DVGPV string: -DVGPV_arm_linux_vanilla=1
Default supp files: exp-sgcheck.supp xfree-3.supp
xfree-4.supp glibc-2.X-drd.supp glibc-2.34567-NPTL-helgrind.supp
glibc-2.X.supp
Now, the only difference between the readme.android and this I see is
that in the readme, they say i should see this:
# Platform variant: android
# Primary -DVGPV string: -DVGPV_arm_linux_android=1
... so, how do I hack this platform variant to return a proper result? :)
|