Hi, It looks like configure did not detect the kernel features correctly. What kernel is this running? Can you send us your pvfs2-config.h file? configure should be run against the kernel that is running on the ppc64 machines. (configure --with-kernel=...) Hopefully that should point us towards the problem (and fixes!). Thanks, Murali
> Great! > > I forged ahead and did > > make CROSS_COMPILE=powerpc64-unknown-linux-gnu- kmod > > and got the following error. I wonder if I need extended ACLs defined > somewhere in the kernel config - would this be under ext3? > > thanks, > --bob > > CC [M] /root/pvfs2-1.5.1/src/kernel/linux-2.6/inode.o > /root/pvfs2-1.5.1/src/kernel/linux-2.6/inode.c: In function > `pvfs2_setattr': > /root/pvfs2-1.5.1/src/kernel/linux-2.6/inode.c:330: warning: implicit > declaration of function `pvfs2_acl_chmod' > /root/pvfs2-1.5.1/src/kernel/linux-2.6/inode.c: At top level: > /root/pvfs2-1.5.1/src/kernel/linux-2.6/inode.c:411: error: > `generic_setxattr' undeclared here (not in a function) > /root/pvfs2-1.5.1/src/kernel/linux-2.6/inode.c:411: error: > initializer element is not constant > /root/pvfs2-1.5.1/src/kernel/linux-2.6/inode.c:411: error: (near > initialization for `pvfs2_file_inode_operations.setxattr') > /root/pvfs2-1.5.1/src/kernel/linux-2.6/inode.c:412: error: > `generic_getxattr' undeclared here (not in a function) > /root/pvfs2-1.5.1/src/kernel/linux-2.6/inode.c:412: error: > initializer element is not constant > /root/pvfs2-1.5.1/src/kernel/linux-2.6/inode.c:412: error: (near > initialization for `pvfs2_file_inode_operations.getxattr') > /root/pvfs2-1.5.1/src/kernel/linux-2.6/inode.c:413: error: > `generic_removexattr' undeclared here (not in a function) > /root/pvfs2-1.5.1/src/kernel/linux-2.6/inode.c:413: error: > initializer element is not constant > /root/pvfs2-1.5.1/src/kernel/linux-2.6/inode.c:413: error: (near > initialization for `pvfs2_file_inode_operations.removexattr') > /root/pvfs2-1.5.1/src/kernel/linux-2.6/inode.c: In function > `pvfs2_get_custom_inode': > /root/pvfs2-1.5.1/src/kernel/linux-2.6/inode.c:508: warning: implicit > declaration of function `pvfs2_init_acl' > > > On Aug 8, 2006, at 3:06 PM, Murali Vilayannur wrote: > > > Hi, > > The kernel module is standalone from a compilation standpoint > > and does not depend on any libraries. > >> From an execution standpoint, it is not standalone. > > There is a user-space client application that is needed as a > > transport for the VFS requests which in turn depends on the PVFS2 > > libraries. > > > > We have spent some time getting 64 bit kmods to work with 32 bit > > userspace. So hopefully that should not be a problem. > > If you do encounter any issues, please do let us know. > > Thanks, > > Murali > > > > > >> I'm looking at installing PVFS2 on my debian-ppc64 mac cluster here > >> at ANL. > >> > >> It appears that the system compiles fine, but I am concerned about > >> the kernel module. On the G5 Xserves I need to build the kernels with > >> a ppc64 cross compiler (the standard runtime environment is 32-bit). > >> Do I need to have the rest of the libraries compiled in order to > >> compile the kernel module, or is the module standalone? > >> > >> Thanks, > >> --bob > >> _______________________________________________ > >> Pvfs2-users mailing list > >> [email protected] > >> http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users > >> > >> > > > > _______________________________________________ Pvfs2-users mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
