From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Dumb (well known I hope) symbol problem
Date: Tue, 22 May 2001 16:01:31 +0000 [thread overview]
Message-ID: <20010522160131.A16787@sistina.com> (raw)
In-Reply-To: <3B0A6E1B.2CA74065@in.tum.de>; from vidalrod@informatik.tu-muenchen.de on Tue, May 22, 2001 at 03:48:11PM +0200
David,
this looks like a missing LVM kernel patch.
Did you follow the instructions contained in the INSTALL
and PATCHES/README files in order to update the LVM kernel code?
We are working on updating vanilla to the recent LVM code, but up to 2.4.4
you still need to apply a patch which comes with the LVM distribution.
Regards,
Heinz -- The LVM Guy --
On Tue, May 22, 2001 at 03:48:11PM +0200, David Vidal Rodriguez wrote:
> Hi folks,
>
> I have just downloaded the CVS source tree of LVM and I'm still
> wondering why I can't compile the module/compiled-in version.
> I have the Linus-2.4.0 source tree in /var/tmp and I'm not root ('cause
> I'm not the owner of this --quick-- machine and compiling the source in
> my P90 would be too much). The following symbols appear to be missing
> after running ./configure with --with-kernel_dir=/var/tmp/linux, applied
> the patch to the source and tried to compile as usual:
>
> drivers/md/mddev.o: In function lvm_init_fs'
> drivers/md/mddev.o: In function lvm_fin_fs'
> drivers/md/mddev.o: In function lvm_fs_create_vg'
> drivers/md/mddev.o: In function lvm_fs_remove_vg'
> drivers/md/mddev.o(.text+0x2221): undefined reference to
> lvm_do_vg_remove':
> drivers/md/mddev.o(.text+0x228b): undefined reference to
> lvm_do_pv_create':
> drivers/md/mddev.o(.text+0x245f): undefined reference to
> lvm_do_pv_remove':
> drivers/md/mddev.o(.text+0x2488): undefined reference to
> lvm_do_lv_create':
> drivers/md/mddev.o(.text+0x2d79): undefined reference to
> lvm_do_lv_remove':
> drivers/md/mddev.o(.text+0x2ea7): undefined reference to
> lvm_do_lv_rename':
> drivers/md/mddev.o(.text+0x3de6): undefined reference to
> lvm_fs_create_lv'
> make: *** [vmlinux] Error 1
>
>
> I promise that's the last time I ask such a thing; it really screws me
> up not being able to have a decent beta7 kernel!
>
> Thanks & cheers,
> --
> ------------------------------------------------------------------------
> David Vidal R. (vidalrod <at> in DOT tum DOT de)
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-05-22 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 13:48 [linux-lvm] Dumb (well known I hope) symbol problem David Vidal Rodriguez
2001-05-22 13:54 ` Joe Thornber
2001-05-22 14:14 ` David Vidal Rodriguez
2001-05-22 16:01 ` Heinz J. Mauelshagen [this message]
2001-05-22 14:51 ` David Vidal Rodriguez
2001-05-22 15:01 ` David Vidal Rodriguez
2001-05-22 15:08 ` Joe Thornber
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=20010522160131.A16787@sistina.com \
--to=mauelshagen@sistina.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.