What's state of valgrind port on pure amd64 system?
Here, it core dumps upon linking both with clang and gcc47,
with complaint that looks suspicious (expected i386 not X86_64
or something to that effect).
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/valgrind-on
on. There must be some OS support which FreeBSD
> i386 has and FreeBSD amd64 has not. It was just curiosity, though.
AFAIK it's not about OS-support for valgrind being required (but there is a
module for freebsd which speeds up valgrind considerably), but about
syscall-support. valgrind ha
Roland Smith wrote:
Read http://valgrind.org/info/platforms.html, especially 'Porting Plans'.
I had read this, but it dates back to Feb 2007; I just hoped it was
obsolete :-(
Or remove the line 'ONLY_FOR_ARCHS= i386' from the port Makefile, try it
and see where it breaks. :-) I'm guessi
On Wed, Jul 30, 2008 at 05:12:39PM +0200, Andrea Venturoli wrote:
>
> ** Port marked as IGNORE: devel/valgrind:
> is only for i386, while you are running amd64
> ** Listing the failed packages (-:ignored / *:skipped / !:failed)
> - devel/valgrind
>
> Sa
** Port marked as IGNORE: devel/valgrind:
is only for i386, while you are running amd64
** Listing the failed packages (-:ignored / *:skipped / !:failed)
- devel/valgrind
Same holds for valgrind-snapshot.
On it's website I see it supports AMD64 on Linux, so I guess this
Hi,
I would really like to use valgrind on my FreeBSD machine, but.. :-)
-Yony
>make
===> Building for valgrind-352_7
gmake all-recursive
gmake[1]: Entering directory
`/usr/ports/devel/valgrind/work/valgrind-stable-352'
Making all in include
gmake[2]: Entering directory
`/usr/
