Hello,
 
Does anyone have any ideas as to build the 2.6.x kernel module on 64 bits Scientific Linux 4.0 updated kernel (linux-2.6.9-22.0.1.EL) ?
I have
1) generated the config files as described on pvfs2-quickstart page:
    ./configure -with-kernel=/lib/modules/2.6.9-22.0.1.EL/build -with-mpi=/opt/mpich2
2) "make" and "make install" to install pvfs2 were fine without warring or error message.
then
3) "make kmod" to build a pvfs2.ko module, but got error message like:
    /tmp/pvfs2-1.3.0/src/kernel/linux-2.6/acl.c: In function `pvfs2_acl_decode':
    /tmp/pvfs2-1.3.0/src/kernel/linux-2.6/acl.c:62: warning: int format, different type arg (arg 2)
    /tmp/pvfs2-1.3.0/src/kernel/linux-2.6/acl.c:62: warning: int format, different type arg (arg 3)
    /tmp/pvfs2-1.3.0/src/kernel/linux-2.6/acl.c: In function `pvfs2_acl_encode':
    /tmp/pvfs2-1.3.0/src/kernel/linux-2.6/acl.c:132: warning: int format, different type arg (arg 2)
    /tmp/pvfs2-1.3.0/src/kernel/linux-2.6/acl.c: In function `pvfs2_permission':
    /tmp/pvfs2-1.3.0/src/kernel/linux-2.6/acl.c:546: warning: implicit declaration of function `IS_IMMMUTABLE'
    /tmp/pvfs2-1.3.0/src/kernel/linux-2.6/acl.c:558: error: `error' undeclared (first use in this function)
    /tmp/pvfs2-1.3.0/src/kernel/linux-2.6/acl.c:558: error: (Each undeclared identifier is reported only once
    /tmp/pvfs2-1.3.0/src/kernel/linux-2.6/acl.c:558: error: for each function it appears in.)
    make[3]: *** [/tmp/pvfs2-1.3.0/src/kernel/linux-2.6/acl.o] Error 1
    make[2]: *** [_module_/tmp/pvfs2-1.3.0/src/kernel/linux-2.6] Error 2
    make[1]: *** [default] Error 2
    make: *** [just_kmod] Error 2
 
It was tested fine on 32 bits FC2 and FC3 OS. So what's wrong with 64 bits Scientific Linux 4.0? Any ideas or suggestions to help me resolve this problem? Any suggestions will be appreciated and thanks in advance for any help!
 
Tim Lin
_______________________________________________
PVFS2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users

Reply via email to