Interesting..., so what about cross-compiling?
I build valgrind on Suse x86 for PPC32 using a build script like this:
export
CC=/opt/wrsysroot/x86-linux2/powerpc-wrs-linux-gnu-ppc_603e-glibc_small-gcc
export
CXX=/opt/wrsysroot/x86-linux2/powerpc-wrs-linux-gnu-ppc_603e-glibc_small-g++
export
LD=/opt/wrsysroot/x86-linux2/powerpc-wrs-linux-gnu-ppc_603e-glibc_small-ld
export LDFLAGS=-L/home/mln/evb/rootfs/usr/lib
tar -xjf valgrind-3.3.1_with_mfspr_patch.tar.bz2
cd valgrind-3.3.1
./configure --prefix=/home/mln/valgrind/install_debug
--enable-shared --host=ppc-linux --target=ppc-linux --enable-debug
--disable-tls || exit 1
make || exit 1
make install || exit 1
Will this give me the correct suppression files?
Another thing:
As you may see in the script above I use mfspr patch. I had problems
running valgrind on PPC, since it reported illegal instruction. I have
added support for this instruction (which reads the CPU Core id/type). I
have mailed this patch to this list in 18 June 2009 (Re: [Valgrind-users]
PPC: unhandled instruction: dis_proc_ctl(ppc)(mfspr, SPR)(0x11F)), but
didn't really get any feedback. See :
http://sourceforge.net/mailarchive/message.php?msg_name=B54FB955F5DC4DF1826FD76E9CB943A7%40mail2world.com
Could this be added to the repository?
Kind regards,
Mogens
Julian Seward <jsew...@acm.org>
20-08-2009 23:41
To
valgrind-users@lists.sourceforge.net
cc
Subject
Re: [Valgrind-users] suppression files with valgrind 3.5.0
On Thursday 20 August 2009, Paul Floyd wrote:
> Nikos Chantziaras wrote:
> > If you look at the release notes of 3.5.0 (they were posted here too)
> > you'll see that this change is intended. So if you want the extra
> > suppression files, you will need to copy them manually. The specific
> > note said:
> >
> > "- Previously, all the distributed suppression (*.supp) files were
> > installed. Now, only default.supp is installed. This should not
> > affect users as the other installed suppression files were not
> > read; the fact that they were installed was a mistake."
>
> I did skim through the release notes, but that paragraph didn't catch my
> attention.
>
> Does this mean that building Valgrind on one OS, installing it on an NFS
> mount and using it from later OSes isn't really supported?
It's not supported. The build system assumes that the build is done for
one platform (distro) only. If you need to run it on multiple distros,
you really should build it individually for each distro.
In some circumstances you might get away with using a build from one
distro on a different one, but if that works it's more by accident than
design.
J
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day
trial. Simplify your report design, integration and deployment - and focus
on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
