[rajagopal.n_at_gmail_dot_com: BLCR 0.4.2 - checking for Linux kernel 2.6 build directory... not found]

From: Jason Duell (jcduell_at_lbl_dot_gov)
Date: Tue Feb 20 2007 - 14:04:31 PST

  • Next message: Paul H. Hargrove: "Re: [rajagopal.n_at_gmail_dot_com: BLCR 0.4.2 - checking for Linux kernel 2.6 build directory... not found]"
    Rajagopal,
    
    I'm forwarding your email to the entire checkpoint group at LBL.  It looks like
    your problem is that you do not have the Linux kernel source code on your
    machine (or it's not in the standard location).  I'm not personally famililar
    with Debian, so I'm not sure what the best fix is.  Hopefully someone who's more
    familiar with Debian will know the answer.
    
    Regards,
    
    -- 
    Jason Duell             Future Technologies Group
    <jcduell_at_lbl_dot_gov>       Computational Research Division
    Tel: +1-510-495-2354    Lawrence Berkeley National Laboratory
    
    
    ----- Forwarded message from Rajagopal Natarajan <rajagopal.n_at_gmail_dot_com> -----
    
    From: Rajagopal Natarajan <rajagopal.n_at_gmail_dot_com>
    Subject: BLCR 0.4.2 - checking for Linux kernel 2.6 build directory... not found
    Date: Tue, 20 Feb 2007 23:23:56 +0530
    To: JCDuell_at_lbl_dot_gov
    
    Hi,
    
    I've a 10Node PIII cluster using MPI-LAM 7.1.2 . The operating system used
    is Debian Etch. When trying to configure the BLCR 0.4.2 package, we get the
    error "checking for Linux kernel 2.6 build directory... not found". I have
    installed the linux header and linux source packages from the apt
    repository. I'm unable to figure out what I need to do inorder to get past
    this error. Please do help me get BLCR running on the cluster. The following
    is the output of the configure script.
    
    
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking for pwd... /bin/pwd
    checking build system type... i686-pc-linux-gnu
    checking host system type... i686-pc-linux-gnu
    checking for perl5... no
    checking for perl... /usr/bin/perl
    checking for gmake... no
    checking for make... /usr/bin/make
    checking if /usr/bin/make is GNU make... yes (3.81)
    checking for style of include used by /usr/bin/make... GNU
    checking for gcc... gcc
    checking for C compiler default output... 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 gcc accepts -g... yes
    checking for gcc option to accept ANSI C... none needed
    checking dependency style of gcc... gcc3
    checking for ld used by GCC... /usr/bin/ld
    checking if the linker (/usr/bin/ld) is GNU ld... yes
    checking for /usr/bin/ld option to reload object files... -r
    checking for BSD-compatible nm... /usr/bin/nm -B
    checking whether ln -s works... yes
    checking how to recognise dependant libraries... pass_all
    checking command to parse /usr/bin/nm -B output... ok
    checking how to run the C preprocessor... gcc -E
    checking for egrep... grep -E
    checking for ANSI C header files... yes
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking dlfcn.h usability... yes
    checking dlfcn.h presence... yes
    checking for dlfcn.h... yes
    checking for ranlib... ranlib
    checking for strip... strip
    checking for objdir... .libs
    checking for gcc option to produce PIC... -fPIC
    checking if gcc PIC flag -fPIC works... yes
    checking if gcc static flag -static works... yes
    checking if gcc supports -c -o file.o... yes
    checking if gcc supports -c -o file.lo... yes
    checking if gcc supports -fno-rtti -fno-exceptions... yes
    checking whether the linker (/usr/bin/ld) supports shared libraries... yes
    checking how to hardcode library paths into programs... immediate
    checking whether stripping libraries is possible... yes
    checking dynamic linker characteristics... GNU/Linux ld.so
    checking if libtool supports shared libraries... yes
    checking whether to build shared libraries... yes
    checking whether to build static libraries... no
    checking whether -lc should be explicitly linked in... no
    creating libtool
    checking for rpmbuild... no
    checking for rpmb... no
    checking for rpm... no
    checking for gcc... (cached) gcc
    checking whether we are using the GNU C compiler... (cached) yes
    checking whether gcc accepts -g... (cached) yes
    checking for gcc option to accept ANSI C... (cached) none needed
    checking dependency style of gcc... (cached) gcc3
    checking for GNU libc version >= 2.1... yes
    checking for dlsym in -ldl... yes
    checking for pthread_create in -lpthread... yes
    checking for value of CR_SIGNUM... 64
    checking for void *... yes
    checking size of void *... 4
    checking for Linux kernel 2.6 source directory...
    /lib/modules/2.6.18-3-686/build (base version 2.6.18)
    checking for Linux kernel 2.6 build directory... not found
    checking for Linux kernel 2.4 source directory... not found in
    /lib/modules/2.6.18-3-686/build
    configure: error: required Linux kernel headers and/or build not found.
    
    Thanks and regards,
    N. Rajagopal
    
    ----- End forwarded message -----
    

  • Next message: Paul H. Hargrove: "Re: [rajagopal.n_at_gmail_dot_com: BLCR 0.4.2 - checking for Linux kernel 2.6 build directory... not found]"