On Fri, 2009-01-30 at 16:53 +0530, Nitin Bhardwaj wrote: > Now, I have tried building the RPMs with different permutations of > kernel specs and unionfs-2.x patches, and have deduced the following > (The version of patch doesn't matter: problem is exhibited by both > 2.3.3 as well as 2.4 RHEL5 patches, > and the kabi check has to be turned OFF everytime): > > If I do NOT include CONFIG_UNION_FS_XATTR=y in the kernel spec, the > prep stage of the rpmbuild fails with the following: > -------------------------------------------------------- > + make ARCH=i386 nonint_oldconfig > CONFIG_UNION_FS_XATTR > make[1]: *** [nonint_oldconfig] Error 2 > --------------------------------------------------------
So what is in .config for this failed build. There probably no CONFIG_UNION_FS_XATTR entry at all. Did you actually follow the instructions I gave regarding the changes needed in SOURCES/kernel-*.config files used by the build? > > On the other hand, If I insert CONFIG_UNION_FS_XATTR=y into the kernel > spec, the prep goes fine, but later the compilation > fails with the following: > -------------------------------------------------------- > CC [M] fs/unionfs/rdstate.o > CC [M] fs/unionfs/copyup.o > fs/unionfs/copyup.c: In function 'copyup_xattrs': > fs/unionfs/copyup.c:38: error: implicit declaration of function > 'vfs_listxattr' > make[2]: *** [fs/unionfs/copyup.o] Error 1 > make[1]: *** [fs/unionfs] Error 2 > make: *** [fs] Error 2 > -------------------------------------------------------- Not really relevant since we've been told it isn't supported. > > > Any suggestions ? > > > Thanks, > Nitin. > _______________________________________________ > unionfs mailing list: http://unionfs.filesystems.org/ > [email protected] > http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs _______________________________________________ unionfs mailing list: http://unionfs.filesystems.org/ [email protected] http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
