Linux LVM users
 help / color / mirror / Atom feed
From: Jesus Manuel NAVARRO LOPEZ <jesus_navarro@promofinarsa.es>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] no such member 'de'
Date: Fri, 05 Oct 2001 10:07:16 +0200	[thread overview]
Message-ID: <3BBD6A34.439845AA@promofinarsa.es> (raw)
In-Reply-To: 20011004170447.A17897@reason.marist.edu

Hi, Michael:

urmk@reason.marist.edu wrote:
> 
> 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's have been described.  Look for the thread "kernel 2.2.19 support".
I *hope* this will be repaired on next rc.
-- 
SALUD,
Jes�s
***
jesus_navarro@promofinarsa.es
***

      reply	other threads:[~2001-10-05  8:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-04 21:04 [linux-lvm] no such member 'de' urmk
2001-10-05  8:07 ` Jesus Manuel NAVARRO LOPEZ [this message]

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=3BBD6A34.439845AA@promofinarsa.es \
    --to=jesus_navarro@promofinarsa.es \
    --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