Please disregard this post. I found, in going through the process, that the cause was the VFS-patch. I fat-fingered the patch command, and instead of applying linux-2.4.19-VFS-lock.patch, I applied linux-2.4.9-VFS-lock.patch. Sorry to post a question then answer it. On Wed, Nov 06, 2002 at 05:14:45PM -0500, Bradley M Alexander wrote: > Hi, > > I have successfully rebuilt my system after the issues a couple of weeks > ago, and am trying to recompile the kernel with LVM support. > > I am using Debian's kernel source 2.4.19 with lvm-1.0.6. The compile stops > with > > gcc -D__KERNEL__ -I/usr/src/kernel-source-2.4.19/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common > -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 > -malign-functions=4 -nostdinc -I > /usr/lib/gcc-lib/i386-linux/2.95.4/include -DKBUILD_BASENAME=super -c -o > super.o super.c > super.c: In function `unlockfs': > super.c:520: `mount_sem' undeclared (first use in this function) > super.c:520: (Each undeclared identifier is reported only once > super.c:520: for each function it appears in.) > make[3]: *** [super.o] Error 1 > > Am I missing a package I needed? How do I fix this so I can get the kernel > compiled and get on with restoring from backups? > > Thanks, > --Brad > > _______________________________________________ > linux-lvm mailing list > linux-lvm@sistina.com > http://lists.sistina.com/mailman/listinfo/linux-lvm > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ _______________________________________________ linux-lvm mailing list linux-lvm@sistina.com http://lists.sistina.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
