Dear All,
I'm wondering if anyone has managed to build kmod with the latest kernel? I'm getting curious errors, e.g.,

test:pvfs-2.7.1 # make kmod
/bin/sh: -c: line 0: syntax error near unexpected token `cat'
/bin/sh: -c: line 0: `echo(cat /dev/null; echo kernel//dist/ pvfs2/2.6.25/pvfs-2.7.1/src/kernel/linux-2.6/pvfs2.ko;) > /dist/ pvfs2/2.6.25/pvfs-2.7.1/src/kernel/linux-2.6/modules.order' make[3]: *** [/dist/pvfs2/2.6.25/pvfs-2.7.1/src/kernel/linux-2.6/ modules.order] Error 2 make[2]: *** [_module_/dist/pvfs2/2.6.25/pvfs-2.7.1/src/kernel/ linux-2.6] Error 2
make[1]: *** [default] Error 2
make: *** [just_kmod] Error 2

It seems there are conflicting definitions of Q in pvfs and linux and they have collided horribly in this case. I tried to define Q to be empty, but it unfortunately did not help, though the erorr now is in a different place:

test:pvfs-2.7.1 # make kmod Q=
test -e include/linux/autoconf.h -a -e include/config/auto.conf || ( \ echo; \ echo " ERROR: Kernel configuration is invalid."; \ echo " include/linux/autoconf.h or include/config/ auto.conf are missing."; \ echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo; \ /bin/false) mkdir -p /dist/pvfs2/2.6.25/pvfs-2.7.1/src/kernel/ linux-2.6/.tmp_versions ; rm -f /dist/pvfs2/2.6.25/pvfs-2.7.1/src/ kernel/linux-2.6/.tmp_versions/* make -f scripts/Makefile.build obj=/dist/pvfs2/2.6.25/pvfs-2.7.1/src/ kernel/linux-2.6 (cat /dev/null; echo kernel//dist/pvfs2/2.6.25/pvfs-2.7.1/src/ kernel/linux-2.6/pvfs2.ko;) > /dist/pvfs2/2.6.25/pvfs-2.7.1/src/ kernel/linux-2.6/modules.order
  Building modules, stage 2.
make -f /usr/src/linux-2.6.25/scripts/Makefile.modpost
 MODPOST 1 modules
"  CC           src/apps/kernel/linux/pvfs2-client.o"
/bin/sh: CC src/apps/kernel/linux/pvfs2-client.o: No such file or directory
make: *** [src/apps/kernel/linux/pvfs2-client.o] Error 127


Thanks,
--andrew

_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users

Reply via email to