[linux-lvm] no such member 'de'

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



LVM 1.0.1rc4, Linux 2.2.19 stock kernel:

I applied the rawio patch for 2.2.18 (no errors, a few fuzzy offsets).
Configured LVM, ran make in the PATCHES dir.
Applied the newly made LVM patch.  Again, no errors, some fuzzy offsets.
Configured LVM support in the kernel.

Make fails, with:

cc -D__KERNEL__ -I/usr/src/linux-2.2.19/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -D__SMP__ -pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586   -c -o lvm.o lvm.c
lvm.c: In function `lvm_do_lv_create':
lvm.c:2192: structure has no member named `de'
lvm.c: In function `lvm_do_lv_remove':
lvm.c:2277: structure has no member named `de'
make[3]: *** [lvm.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.2.19/drivers/block'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.2.19/drivers/block'
make[1]: *** [_subdir_block] Error 2
make[1]: Leaving directory `/usr/src/linux-2.2.19/drivers'

It appears it's hardcoded to refer to the devfs entries, which don't exit in 
2.2.19 -- is this simply the final stage of dropping support for 2.2.19, or 
an oversight?

-m



-- 
Michael Kershaw
Michael.Kershaw@reason.marist.edu
Linux Systems Programmer, Information Technology

"Don't worry, I'm sure they'll listen to Reason." -- Fisheye, Snowcrash



[Index of Archives]     [Gluster Users]     [Kernel Development]     [Linux Clusters]     [Device Mapper]     [Security]     [Bugtraq]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]

  Powered by Linux