Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 543648 - dev-util/valgrind-3.10.1 with kernel 4.0 - configure: error: Valgrind works on kernels 2.4, 2.6
Summary: dev-util/valgrind-3.10.1 with kernel 4.0 - configure: error: Valgrind works o...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Anthony Basile
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-17 21:44 UTC by Thomas Deutschmann (RETIRED)
Modified: 2015-03-19 23:58 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
patch to configure.ac for linux 4.* support (valgrind-3.10-linux-4.patch,972 bytes, patch)
2015-03-19 21:55 UTC, Janne Grunau
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Deutschmann (RETIRED) gentoo-dev 2015-03-17 21:44:59 UTC
Hi,

you cannot install dev-util/valgrind when using linux-4.x kernel (and according to the error message using valgrind with kernel 3.x shouldn't be possible too):


 * Package:    dev-util/valgrind-3.10.1
 * Repository: gentoo
 * Maintainer: blueness@gentoo.org
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU
 * FEATURES:   preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Unpacking valgrind-3.10.1.tar.bz2 to /var/tmp/portage/dev-util/valgrind-3.10.1/work
>>> Source unpacked in /var/tmp/portage/dev-util/valgrind-3.10.1/work
>>> Preparing source in /var/tmp/portage/dev-util/valgrind-3.10.1/work/valgrind-3.10.1 ...
 * Applying valgrind-3.7.0-respect-flags.patch ...
 [ ok ]
 * Applying valgrind-3.7.0-fno-stack-protector.patch ...
 [ ok ]
 * Applying valgrind-3.6.0-local-labels.patch ...
 [ ok ]
 * Applying valgrind-3.10.1-non-exec-stack.patch ...
 [ ok ]
 * Applying valgrind-3.9.0-glibc-2.19.patch ...
 [ ok ]
 * Running eautoreconf in '/var/tmp/portage/dev-util/valgrind-3.10.1/work/valgrind-3.10.1' ...
 * Running aclocal ...
 [ ok ]
 * Running autoconf --force ...
 [ ok ]
 * Running autoheader ...
 [ ok ]
 * Running automake --add-missing --copy --foreign --force-missing ...
 [ ok ]
 * Running elibtoolize in: valgrind-3.10.1/
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-util/valgrind-3.10.1/work/valgrind-3.10.1 ...
 * econf: updating valgrind-3.10.1/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating valgrind-3.10.1/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --libdir=/usr/lib64 --without-mpicc
configure: loading site script /usr/share/config.site
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether ln -s works... yes
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-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... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking whether x86_64-pc-linux-gnu-gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of x86_64-pc-linux-gnu-gcc... none
checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E
checking for x86_64-pc-linux-gnu-g++... x86_64-pc-linux-gnu-g++
checking whether we are using the GNU C++ compiler... yes
checking whether x86_64-pc-linux-gnu-g++ accepts -g... yes
checking dependency style of x86_64-pc-linux-gnu-g++... none
checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib
checking for a sed that does not truncate output... /bin/sed
checking for perl... /usr/bin/perl
checking for gdb... /usr/bin/gdb
checking dependency style of x86_64-pc-linux-gnu-gcc... none
checking for diff -u... yes
checking for a supported version of gcc... ok (4.9.2)
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for a supported CPU... ok (x86_64)
checking for a 64-bit only build... no
checking for a 32-bit only build... no
checking for a supported OS... ok (linux-gnu)
checking for the kernel version... unsupported (4.0.0-rc4)
configure: error: Valgrind works on kernels 2.4, 2.6

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/dev-util/valgrind-3.10.1/work/valgrind-3.10.1/config.log
 * ERROR: dev-util/valgrind-3.10.1::gentoo failed (configure phase):
 *   econf failed
 * 
 * Call stack:
 *               ebuild.sh, line   93:  Called src_configure
 *             environment, line 3057:  Called econf '--without-mpicc'
 *        phase-helpers.sh, line  662:  Called __helpers_die 'econf failed'
 *   isolated-functions.sh, line  117:  Called die
 * The specific snippet of code:
 *   		die "$@"
 * 
 * If you need support, post the output of `emerge --info '=dev-util/valgrind-3.10.1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-util/valgrind-3.10.1::gentoo'`.
 * The complete build log is located at '/var/log/portage/dev-util:valgrind-3.10.1:20150317-214209.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-util/valgrind-3.10.1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-util/valgrind-3.10.1/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-util/valgrind-3.10.1/work/valgrind-3.10.1'
 * S: '/var/tmp/portage/dev-util/valgrind-3.10.1/work/valgrind-3.10.1'



# emerge --info
Portage 2.2.18 (python 3.4.3-final-0, default/linux/amd64/13.0, gcc-4.9.2, glibc-2.20-r2, 4.0.0-rc4 x86_64)
=================================================================
System uname: Linux-4.0.0-rc4-x86_64-Intel-R-_Core-TM-_i7-3770K_CPU_@_3.50GHz-with-gentoo-2.2
KiB Mem:     4025588 total,   2747672 free
KiB Swap:    1048572 total,   1048572 free
Timestamp of repository gentoo: Tue, 17 Mar 2015 17:45:01 +0000
Timestamp of repository poly-c: Mon, 16 Mar 2015 23:00:50 +0000
sh bash 4.3_p33-r2
ld GNU ld (Gentoo 2.25 p1.0) 2.25
app-shells/bash:          4.3_p33-r2::gentoo
dev-java/java-config:     2.2.0::gentoo
dev-lang/perl:            5.20.2::gentoo
dev-lang/python:          2.7.9-r2::gentoo, 3.4.3::gentoo
dev-util/cmake:           3.1.0::gentoo
dev-util/pkgconfig:       0.28-r2::gentoo
sys-apps/baselayout:      2.2::gentoo
sys-apps/openrc:          0.13.11::gentoo
sys-apps/sandbox:         2.6-r1::gentoo
sys-devel/autoconf:       2.69::gentoo
sys-devel/automake:       1.14.1::gentoo, 1.15::gentoo
sys-devel/binutils:       2.25::gentoo
sys-devel/gcc:            4.9.2::gentoo
sys-devel/gcc-config:     1.8::gentoo
sys-devel/libtool:        2.4.6-r1::gentoo
sys-devel/make:           4.1-r1::gentoo
sys-kernel/linux-headers: 3.19::gentoo (virtual/os-headers)
sys-libs/glibc:           2.20-r2::gentoo


Reproducible: Always
Comment 1 Anthony Basile gentoo-dev 2015-03-18 22:40:53 UTC
(In reply to Thomas D. from comment #0)
> Hi,
> 
> you cannot install dev-util/valgrind when using linux-4.x kernel (and
> according to the error message using valgrind with kernel 3.x shouldn't be
> possible too):
> 

Hack the build system and see if valgrind actually does work under linux-4.  If it does, I'll patch it.  I don't want to relax the contraint if its going to fail.
Comment 2 Janne Grunau 2015-03-19 21:55:43 UTC
Created attachment 399282 [details, diff]
patch to configure.ac for linux 4.* support

There is nothing special in linux 4.0. Valgrind can handle it as another 2.6.*/3.* release.

Valgrind compiles and works with attached patch on an arm system running linux 4.0-rc4.
Comment 3 Anthony Basile gentoo-dev 2015-03-19 23:58:10 UTC
(In reply to Janne Grunau from comment #2)
> Created attachment 399282 [details, diff] [details, diff]
> patch to configure.ac for linux 4.* support
> 
> There is nothing special in linux 4.0. Valgrind can handle it as another
> 2.6.*/3.* release.
> 
> Valgrind compiles and works with attached patch on an arm system running
> linux 4.0-rc4.

+  19 Mar 2015; Anthony G. Basile <blueness@gentoo.org>
+  +files/valgrind-3.10.1-linux-4.patch, valgrind-3.10.1.ebuild:
+  Patch 3.10.1 to work on linux-4, bug #543648.  Thanks Janne Grunau <janne-
+  gentoo@jannau.net>.
+


No rev bump needed.  Let me know if this works for you guys.