I attempt to install dev-util/callgrind-0.10.1-r1, however it fails to configre with the following error despite dev-util/valgrind-3.1.1 clearly being installed: checking for valgrind version... configure: error: Unsupported version. This tool is for Valgrind 3.0.x/3.1.x Here is the output of 'emerge --info' on my system: Portage 2.1-r1 (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.4-r1, 2.6.10-rc3-lo ve1 i686) ================================================================= System uname: 2.6.10-rc3-love1 i686 AMD Athlon(tm) XP 2000+ Gentoo Base System version 1.6.14 app-admin/eselect-compiler: [Not Present] dev-lang/python: 2.2.3-r5, 2.3.3-r1, 2.4.2 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/gcc-config: 1.3.13-r1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer -fforce-addr" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/li b/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvip dfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/terminfo" CXXFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer -fforce-addr" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/ distributions/gentoo" LDFLAGS="-Wl,-O1 -Wl,--enable-new-dtags -Wl,--sort-common -s" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/d istfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/overlays/custom" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow 3dnowext X aac acpi alsa apache2 apm audiofile avi berkdb bitmap- fonts blender-game bonobo cdparanoia cli cpudetection crypt cups custom-cflags d lloader dri eds emboss encode esd exif fbcon flash foomaticdb fortran gd gdbm gi f gnome gpm gstreamer gtk gtk2 gtkhtml imagemagick imlib innodb ipv6 isdnlog jac k jit jpeg libg++ libwww lzo mad mikmod mmx mmxext mng motif mozsvg mp3 mpeg mul tislot mysql ncurses nls nptl nptlonly ogg oggvorbis opengl oss pam pcre pdflib perl pic png ppds pppd python qt3 qt4 quicktime readline reflection rtc samba sd k sdl session spell spl sse ssl svg tcpd tiff truetype truetype-fonts type1-font s udev unicode usb vorbis win32codecs xml xml2 xmms xorg xv xvid xvmc zlib elibc _glibc input_devices_keyboard input_devices_mouse input_devices_evdev kernel_lin ux userland_GNU" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LINGUAS, MAKEO PTS, PORTAGE_RSYNC_EXTRA_OPTS
Created attachment 92723 [details] config.log
What's the output of /usr/bin/valgrind --version ?
Hmm, odd... for some reason running valgrind results in: $ valgrind --version Killed and any commandline I give it results in that, except for when I pass it an invalid --tool=foobar flag. (which results in "valgrind: failed to start tool 'foobad' for platform 'x86-linux': No such file or directory") Also, just to double check: $ equery belongs /usr/bin/valgrind [ Searching for file(s) /usr/bin/valgrind in *... ] dev-util/valgrind-3.1.1 (/usr/bin/valgrind)
well, callgrind uses that to determine if the right valigrind is installing. fixing whatever is killing valgrind will fix the issue.
(In reply to comment #4) > well, callgrind uses that to determine if the right valigrind is installing. > > fixing whatever is killing valgrind will fix the issue. > Just for the record: callgrind is integrated in valgrind since 3.2.0 (http://valgrind.org/info/tools.html#callgrind). usage: valgrind --tool=callgrind myprogram Maybe add an einfo to valgrind ebuild and close this bug
(In reply to comment #5) > Just for the record: callgrind is integrated in valgrind since 3.2.0 > (http://valgrind.org/info/tools.html#callgrind). > usage: valgrind --tool=callgrind myprogram Oh, I forgot to respond again. A while back, I got tired of these weird issues I was having and decided to just just valgrind 3.2.x from ~x86, and that's working perfectly fine for me, so I'm not sure what was going wrong before.
I've removed callgrind from the tree, so shouldn't be an issue anymore.
