[Pvfs2-users] configure: error: The kernel source tree must have been configured.

[Amit H Kumar]

Hello list,

I have a working version of basic Pvfs2 file system. Now need to configure
it with the linux kernel configuration.

In preparation to linux Kernel configuration: ./configure
--with-db=/root/BUILD/db-4.6.21 --with-kernel=/usr/src/linux-2.6

I get the following error
configure: error: The kernel source tree must have been configured.

Above I use --with-db option, because I eneded up with the same problem -gb
had:(
http://www.beowulf-underground.org/pipermail/pvfs2-users/2006-July/001472.html
 )

I am new to the concept of kernel source trees: how it is built and its
location and requirements.
Can anyone please provide some insight into what could be the cause of this
problem. Below here I believe, I have the necessary information to show the
setup I have.

Thank you,
«Amit»


# ls /lib/modules/`uname -r`
kernel  modules.alias  modules.ccwmap  modules.dep  modules.ieee1394map
modules.inputmap  modules.isapnpmap  modules.pcimap  modules.symbols
modules.usbmap


#ls -l /usr/src/linux-2.6/
total 0
lrwxrwxrwx  1 root root 41 Feb 27 09:38 2.6.9-42.0.2.EL-smp-i686 ->
/usr/src/kernels/2.6.9-42.0.2.EL-smp-i686

#ls -l /usr/src/kernels/2.6.9-42.0.2.EL-smp-i686
total 0
lrwxrwxrwx  1 root root 41 Feb 27 09:38 2.6.9-42.0.2.EL-smp-i686 ->
/usr/src/kernels/2.6.9-42.0.2.EL-smp-i686


# uname -a
Linux matrix.domain.edu 2.6.9-42.0.2.ELsmp #1 SMP Wed Aug 23 00:17:26 CDT
2006 i686 athlon i386 GNU/Linux


#pvfs2-statfs -m /mnt/pvfs2/

aggregate statistics:
---------------------------------------

        fs_id: 1476215359
        total number of servers (meta and I/O): 1
        handles available (meta and I/O):       9223372036854775798
        handles total (meta and I/O):           9223372036854775804
        bytes available:                        14235357184
        bytes total:                            17628909568

NOTE: The aggregate total and available statistics are calculated based
on an algorithm that assumes data will be distributed evenly; thus
the free space is equal to the smallest I/O server capacity
multiplied by the number of I/O servers.  If this number seems
unusually small, then check the individual server statistics below
to look for problematic servers.

meta server statistics:
---------------------------------------

server: tcp://matrix:3334
        RAM bytes total  : 1058979840
        RAM bytes free   : 24133632
        uptime (seconds) : 1119467
        load averages    : 384 352 0
        handles available: 9223372036854775798
        handles total    : 9223372036854775804
        bytes available  : 14235357184
        bytes total      : 17628909568
        mode: serving both metadata and I/O data


I/O server statistics:
---------------------------------------

server: tcp://matrix:3334
        RAM bytes total  : 1058979840
        RAM bytes free   : 24133632
        uptime (seconds) : 1119467
        load averages    : 384 352 0
        handles available: 9223372036854775798
        handles total    : 9223372036854775804
        bytes available  : 14235357184
        bytes total      : 17628909568
        mode: serving both metadata and I/O data