From: Patrick Swartz <pswartz@digitalrom.com>
To: linux-lvm@sistina.com
Subject: RE: [linux-lvm] lvm 0.9 kernel build problems
Date: Wed, 29 Nov 2000 11:19:46 -0600 [thread overview]
Message-ID: <OLEAJMNOEMOMMNEIMMINIENLCBAA.pswartz@digitalrom.com> (raw)
In-Reply-To: <Pine.OSF.4.21.0011290939380.31070-100000@lazy.accessus.net>
I have found a way around the problem I was having. The first time I tried
to build the kernel I built lvm into the kernel, but I said "no" to the lvm
proc fs question. This time I went ahead and said "yes" and everything
worked.
Now my question is having lvm report things to /proc will I notice any slow
downs?
Just courious.
Thanks for all of the hard work everyone is putting into lvm!!!!!!!
Patrick
-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On
Behalf Of Jay Weber
Sent: Wednesday, November 29, 2000 9:42 AM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm 0.9 kernel build problems
I had the same errors in past when compiling it on 2.2.18pre kernels.
I believe my problem was that my /usr/src/linux didn't point back to the
proper kernel source tree. It was a while ago though, but I'm thinking
that solved it for me. I believe one of the files included in lvm.c is a
<linux/*whatever*> and that didn't exist or have the proper struct or
such.
On Wed, 29 Nov 2000, Patrick Swartz wrote:
> Hello,
>
> Could someone give me some hints to why I get the following error when
> trying to build my kernel with the lvm 0.9patches. This box started out
as
> a RH7.0 with all current RH updates, then installed the stock 2.4.0-test10
> kernel with lvm built into the kernel. This build worked. I then applied
> the two patches for 2.4.0-test10 and they applied cleanly. I normally
build
> kernels using the following approach -- make dep clean bzImage modules
> modules_install, then take care of lilo. This error happens during the
> bzImage stage.
>
>
> lvm.c: In function `lvm_do_vg_extend':
> lvm.c:2020: warning: implicit declaration of function
> `lvm_do_create_proc_entry_
> of_pv'
> lvm.c: In function `lvm_do_create_proc_entry_of_lv':
> lvm.c:3012: `pde' undeclared (first use in this function)
> lvm.c:3012: (Each undeclared identifier is reported only once
> lvm.c:3012: for each function it appears in.)
> lvm.c: At top level:
> lvm.c:3040: warning: type mismatch with previous implicit declaration
> lvm.c:2020: warning: previous implicit declaration of
> `lvm_do_create_proc_entry_
> of_pv'
> lvm.c:3040: warning: `lvm_do_create_proc_entry_of_pv' was previously
> implicitly
> declared to return `int'
> lvm.c: In function `lvm_do_create_proc_entry_of_pv':
> lvm.c:3046: `pde' undeclared (first use in this function)
> lvm.c: At top level:
> lvm.c:146: warning: `lvm_short_version' defined but not used
> make[3]: *** [lvm.o] Error 1
> make[3]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers/md'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers/md'
> make[1]: *** [_subdir_md] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers'
> make: *** [_dir_drivers] Error 2
>
> Thanks for your help,
>
> Patrick Swartz
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
>
_______________________________________________
linux-lvm mailing list
linux-lvm@sistina.com
http://lists.sistina.com/mailman/listinfo/linux-lvm
next prev parent reply other threads:[~2000-11-29 17:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-29 15:05 [linux-lvm] lvm 0.9 kernel build problems Patrick Swartz
2000-11-29 15:41 ` Jay Weber
2000-11-29 17:19 ` Patrick Swartz [this message]
2000-11-29 17:22 ` Jay Weber
2000-11-29 22:07 ` Heinz J. Mauelshagen
2000-11-29 21:19 ` Heinz J. Mauelshagen
2000-11-29 21:47 ` Falcon
2000-11-30 8:44 ` Chewie
2000-11-30 10:41 ` Stephen C. Tweedie
2000-11-30 11:42 ` Eric M. Hopper
2000-11-30 18:46 ` Rik van Riel
2000-11-30 21:01 ` OT: " Chewie
2000-11-30 3:48 ` Steven Lembark
2000-11-29 22:08 ` Heinz J. Mauelshagen
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=OLEAJMNOEMOMMNEIMMINIENLCBAA.pswartz@digitalrom.com \
--to=pswartz@digitalrom.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.