From: Bradley M Alexander <storm@tux.org>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] super.c failing in kernel compile
Date: Wed Nov 6 17:38:02 2002 [thread overview]
Message-ID: <20021106233731.GC32597@sonsofthunder.yi.org> (raw)
In-Reply-To: <20021106221445.GB32597@sonsofthunder.yi.org>
Please disregard this post. I found, in going through the process, that the
cause was the VFS-patch. I fat-fingered the patch command, and instead of
applying linux-2.4.19-VFS-lock.patch, I applied linux-2.4.9-VFS-lock.patch.
Sorry to post a question then answer it.
On Wed, Nov 06, 2002 at 05:14:45PM -0500, Bradley M Alexander wrote:
> Hi,
>
> I have successfully rebuilt my system after the issues a couple of weeks
> ago, and am trying to recompile the kernel with LVM support.
>
> I am using Debian's kernel source 2.4.19 with lvm-1.0.6. The compile stops
> with
>
> gcc -D__KERNEL__ -I/usr/src/kernel-source-2.4.19/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
> -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686
> -malign-functions=4 -nostdinc -I
> /usr/lib/gcc-lib/i386-linux/2.95.4/include -DKBUILD_BASENAME=super -c -o
> super.o super.c
> super.c: In function `unlockfs':
> super.c:520: `mount_sem' undeclared (first use in this function)
> super.c:520: (Each undeclared identifier is reported only once
> super.c:520: for each function it appears in.)
> make[3]: *** [super.o] Error 1
>
> Am I missing a package I needed? How do I fix this so I can get the kernel
> compiled and get on with restoring from backups?
>
> Thanks,
> --Brad
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
prev parent reply other threads:[~2002-11-06 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 16:15 [linux-lvm] super.c failing in kernel compile Bradley M Alexander
2002-11-06 17:38 ` Bradley M Alexander [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=20021106233731.GC32597@sonsofthunder.yi.org \
--to=storm@tux.org \
--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.