Bugzilla Bug 88138

emerge callgrind-0.9.11 fails when the ./configure script checks for valgrind
version, even when I have the required valgrind version installed.

 * econf: updating callgrind-0.9.11/config.guess with
/usr/share/gnuconfig/config.guess
 * econf: updating callgrind-0.9.11/config.sub with
/usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man
--infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
--localstatedir=/var/lib
configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-linux-gnu-strip... i686-pc-linux-gnu-strip
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether i686-pc-linux-gnu-gcc accepts -g... yes
checking for i686-pc-linux-gnu-gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of i686-pc-linux-gnu-gcc... gcc3
checking for i686-pc-linux-gnu-g++... i686-pc-linux-gnu-g++
checking whether we are using the GNU C++ compiler... yes
checking whether i686-pc-linux-gnu-g++ accepts -g... yes
checking dependency style of i686-pc-linux-gnu-g++... gcc3
checking for a BSD-compatible install... /bin/install -c
checking for i686-pc-linux-gnu-ranlib... i686-pc-linux-gnu-ranlib
checking for valgrind installation... in /usr
checking for valgrind version... Executable range 0xb0000000-0xb0216540 is
outside the
acceptable range 0x80e3000-0xaf8b0000
valgrind: failed to load /usr/lib/valgrind/stage2: Cannot allocate memory

configure: error: Unsupported version. Please use 2.0.x/2.2.x

The configure.log is attached.

Reproducible: Always
Steps to Reproduce:




# emerge --info 
Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.4.3-20050110, 
glibc-2.3.4.20050125-r1, 2.6.12-rc1-love1 i686) 
================================================================= 
System uname: 2.6.12-rc1-love1 i686 Intel(R) Pentium(R) 4 CPU 1.70GHz 
Gentoo Base System version 1.6.10 
Python:              dev-lang/python-2.3.5 [2.3.5 (#1, Apr  4 2005, 15:57:33)] 
ccache version 2.4 [enabled] 
dev-lang/python:     2.3.5 
sys-devel/autoconf:  2.59-r6, 2.13 
sys-devel/automake:  1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5 
sys-devel/binutils:  2.15.92.0.2-r8 
sys-devel/libtool:   1.5.14 
virtual/os-headers:  2.6.8.1-r4 
ACCEPT_KEYWORDS="x86 ~x86" 
AUTOCLEAN="yes" 
CFLAGS="-march=pentium4 -mtune=pentium4 -O3 -pipe 
-fomit-frame-pointer -momit-leaf-frame-pointer -fforce-addr -ftracer" 
CHOST="i686-pc-linux-gnu" 
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /var/qmail/control" 
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" 
CXXFLAGS="-march=pentium4 -mtune=pentium4 -O3 -pipe 
-fomit-frame-pointer -momit-leaf-frame-pointer -fforce-addr -ftracer 
-fvisibility-inlines-hidden" 
DISTDIR="/usr/portage/distfiles" 
FEATURES="autoaddcvs autoconfig ccache distcc distlocks sandbox 
sfperms userpriv usersandbox" 
GENTOO_MIRRORS="http://mirror.averse.net/pub/gentoo 
http://ftp.isu.edu.tw/pub/Linux/Gentoo http://gentoo.osuosl.org" 
MAKEOPTS="-j3" 
PKGDIR="/usr/portage/packages" 
PORTAGE_TMPDIR="/var/tmp" 
PORTDIR="/usr/portage" 
PORTDIR_OVERLAY="/usr/local/portage" 
SYNC="rsync://mirror.averse.net/gentoo-portage" 
USE="x86 3dfx X acpi alsa apm arts bitmap-fonts cjk curl fam flac 
font-server gif gpm imagemagick ithreads jpeg kde kdeenablefinal 
kdexdeltas mmx mp3 ncurses nls nptl oggvorbis opengl oss pic png 
pthreads qt readline samba sdl spell sse ssl threads tiff truetype 
truetype-fonts type1-fonts unicode xv zlib" 
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS 

# etcat -v valgrind 
[ Results for search key           : valgrind ] 
[ Candidate applications found : 9 ] 

 Only printing found installed programs. 

*  dev-util/valgrind : 
        [   ] 2.0.0 (0) 
        [ ~ ] 2.1.0 (0) 
        [ ~ ] 2.1.1 (0) 
        [ ~ ] 2.1.1-r1 (0) 
        [ ~ ] 2.1.2 (0) 
        [   ] 2.2.0 (0) 
        [ ~ ] 2.2.0-r1 (0) 
        [  I] 2.2.0-r2 (0) 
        [M~ ] 2.4.0 (0)

Created an attachment (id=55445) [details]
configure.log from callgrind emerge

Caleb, it seems like you are the maintainer -- please rectify the information
in metadata.xml to reflect this.

Interesting, since the homepage says that this version is designed to work with
valgrind 2.4.0.  I'll take another look.

For me the callgrind-0.9.11 works just fine:

checking for valgrind installation... in /usr
checking for valgrind version... valgrind-2.4.0

I think the problem might be the valgrind-2.4.0.ebuild being broken as reported in [Bug 87598] - resulting in the configure script having problem in detecting the valgrind version... 
(I have tweaked my ebuild to get a functional valgrind-2.4.0 install as reported in the allready mentioned bug...)

Bug 87598 has been solved. If it was the source of the problem, please try
again.

Version checking is fixed, as of the latest emerge --sync. :)

Closing.

*** This bug has been marked as a duplicate of 87598 ***