From: "Mike Black" <mblack@csi-inc.com>
To: "linux-kernel" <linux-kernel@vger.kernel.org>
Cc: "Neil Brown" <neilb@cse.unsw.edu.au>
Subject: 2.5.23 LVM
Date: Thu, 20 Jun 2002 08:46:18 -0400 [thread overview]
Message-ID: <02f101c21858$7970f5f0$f6de11cc@black> (raw)
FYI...after applying Neil's latest patches for raid got this (not Neil's fault)...I'm not currently using LVM so I disabled it.
Good news is that it all compiled (yeah!!! -- first time in months that I've been able to compile with RAID5)
Other question -- it looks like the 2.5 build now builds modules automagically instead of saying "make modules" ???
Hopefully I'll get chance to test 2.5 soon.
gcc -Wp,-MD,./.lvm.o.d -D__KERNEL__ -I/usr/src/linux-2.5.23/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-poin
ter -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -nostdinc -iwithprefix include -DMODULE -DKBUI
LD_BASENAME=lvm -c -o lvm.o lvm.c
lvm.c:1: #error Broken until maintainers will sanitize kdev_t handling
lvm.c: In function `lvm_blk_ioctl':
lvm.c:882: warning: implicit declaration of function `fsync_bdev'
lvm.c:883: warning: implicit declaration of function `invalidate_buffers'
lvm.c: In function `lvm_user_bmap':
lvm.c:1023: structure has no member named `bi_dev'
lvm.c:1024: structure has no member named `bi_dev'
lvm.c:1032: structure has no member named `bi_dev'
lvm.c:1032: structure has no member named `bi_dev'
lvm.c:1032: structure has no member named `bi_dev'
lvm.c:1032: structure has no member named `bi_dev'
Michael D. Black mblack@csihq.com
http://www.csihq.com/
http://www.csihq.com/~mike
321-676-2923, x203
Melbourne FL
next reply other threads:[~2002-06-20 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 12:46 Mike Black [this message]
2002-06-20 14:02 ` 2.5.23 LVM Dave Jones
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='02f101c21858$7970f5f0$f6de11cc@black' \
--to=mblack@csi-inc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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