From: urmk@reason.marist.edu
To: Linux-LVM@sistina.com
Subject: [linux-lvm] no such member 'de'
Date: Thu, 4 Oct 2001 17:04:47 -0400 [thread overview]
Message-ID: <20011004170447.A17897@reason.marist.edu> (raw)
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
next reply other threads:[~2001-10-04 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-04 21:04 urmk [this message]
2001-10-05 8:07 ` [linux-lvm] no such member 'de' Jesus Manuel NAVARRO LOPEZ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011004170447.A17897@reason.marist.edu \
--to=urmk@reason.marist.edu \
--cc=Linux-LVM@sistina.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox