From: Patrick Michael Kane <modus@pr.es.to>
To: Andreas Dilger <adilger@turbolinux.com>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] problems compiling andreas' 3.4 userland tools under test11-pre1
Date: Wed, 8 Nov 2000 19:32:32 -0800 [thread overview]
Message-ID: <20001108193232.A4682@pr.es.to> (raw)
In-Reply-To: <200011090323.eA93N7s02605@webber.adilger.net>; from adilger@turbolinux.com on Wed, Nov 08, 2000 at 08:23:07PM -0700
* Andreas Dilger (adilger@turbolinux.com) [001108 19:23]:
> Patrick Kane writes:
> > I'm trying to get the 0.8final-3.4 to compile under test11-pre1, with no
> > luck. I get all sorts of gcc parse errors in linux/lvm.h and liblvm.h.
> >
> > I've tried compiling the tools with and without Andreas' 2.4 patch. It
> > fails both ways.
>
> The 2.4 patch you refer to is lvm-0.8final-2.4-kernel.diff? Is it
> possible you applied it to /usr/src/linux-2.4*/include/linux/lvm.h but
> there isn't a symlink /usr/include/linux -> /usr/src/linux/include/linux
> (i.e. you are running Debian or something)?
No, test11-1 is definately living in /usr/src/linux and the symlinks from
/usr/include/linux point to the right spot. All of the other third party
modules I need compile up fine, for what it's worth.
> Alternately, you can simply change linux/lvm.h to lib/lvm.h and it should
> compile.
This fixed it. It may well be that I'm not fixing the rejection in the
final-2.4-kernel.diff file correctly.
Best,
--
Patrick Michael Kane
<modus@pr.es.to>
prev parent reply other threads:[~2000-11-09 3:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 0:07 [linux-lvm] problems compiling andreas' 3.4 userland tools under test11-pre1 Patrick Michael Kane
2000-11-09 3:23 ` Andreas Dilger
2000-11-09 3:32 ` Patrick Michael Kane [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=20001108193232.A4682@pr.es.to \
--to=modus@pr.es.to \
--cc=adilger@turbolinux.com \
--cc=linux-lvm@msede.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.