:: [dyne:bolic] A little help?
Top Page
Delete this message
Reply to this message
Author: El Evans
Date:  
To: dynebolic mailinglist
Subject: [dyne:bolic] A little help?
I am trying to compile valgrind 3.6.1. from source. It was complaining about
the kernel version (shown below).

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 gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking whether gcc and cc understand -c and -o together... yes
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for ranlib... ranlib
checking for a sed that does not truncate output... /bin/sed
checking for ar... /usr/bin/ar
checking for perl... /usr/bin/perl
checking for gdb... /no/gdb/was/found/at/configure/time
checking dependency style of gcc... gcc3
checking for diff -u... yes
checking for a supported version of gcc... ok (4.4.1)
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a supported CPU... ok (i686)
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 (3.0.1-libredyne) <<<<< The
problem
configure: error: Valgrind works on kernels 2.4, 2.6
zsh: exit 1     ./configure --prefix=/home/luther/Bin/Apps/VALGRIND.3.6.1


I did some searching and found that I am supposed to edit the trunk/
configure.in file like this below.


valgrind: r11796 - trunk

by svn-2 :: Rate this Message:
<http://old.nabble.com/valgrind%3A-r11796---trunk-td31776201.html#>
<http://old.nabble.com/valgrind%3A-r11796---trunk-td31776201.html#><http://old.nabble.com/valgrind%3A-r11796---trunk-td31776201.html#><http://old.nabble.com/valgrind%3A-r11796---trunk-td31776201.html#><http://old.nabble.com/valgrind%3A-r11796---trunk-td31776201.html#><http://old.nabble.com/valgrind%3A-r11796---trunk-td31776201.html#>
<http://old.nabble.com/valgrind%3A-r11796---trunk-td31776201.html#>

| View Threaded | Show Only this

Message<http://old.nabble.com/valgrind%3A-r11796---trunk-p31776201.html>
Author: bart
Date: 2011-06-05 09:51:47 +0100 (Sun, 05 Jun 2011)
New Revision: 11796

Log:
Make Valgrind build on Linux kernel 3.0 and beyond. Closes #274926. An
official
statement that the Linux kernel 3.0 API and ABI is compatible with Linux
kernel
2.6 can be found here: http://lkml.org/lkml/2011/5/29/204.


Modified:
trunk/configure.in


Modified: trunk/configure.in
===================================================================
--- trunk/configure.in 2011-06-03 23:27:39 UTC (rev 11795)
+++ trunk/configure.in 2011-06-05 08:51:47 UTC (rev 11796)
@@ -225,7 +225,7 @@
         kernel=`uname -r`


         case "${kernel}" in
            2.6.*) <<<< change this
             2.6.*|3.*) <<<<< to this
             AC_MSG_RESULT([2.6 family (${kernel})])
             AC_DEFINE([KERNEL_2_6], 1, [Define to 1 if you're using Linux
2.6.x])
             ;;


I am still getting the same error. I assume it is because of the way the
kernel is named in dyne (i.e. the version number is first) and was wondering
if any gurus out there would know what I needed to do to make this configure
file work with the dyne kernel. As far as I have read there are no
compatibility issues except for the kernel name. Any help would be
appreciated. :)