From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] for a header-file-cannot-found building error
Date: Mon, 20 Aug 2007 09:01:03 -0500 [thread overview]
Message-ID: <20070820140103.GB31911@redhat.com> (raw)
In-Reply-To: <46C7D609.90607@ubuntu.com>
On Sun, Aug 19, 2007 at 07:32:57AM +0200, Fabio Massimo Di Nitto wrote:
> David Teigland wrote:
>
> >
> > I believe that the correct solution is to install the necessary kernel
> > headers into /usr/include/linux/ prior to building cluster. This
> > usually means doing something like this:
> > cd /usr/src/linux
> > make headers_install
> > cp usr/include/linux/dlm* /usr/include/linux/
> > cp usr/include/linux/gfs* /usr/include/linux/
> > cp usr/include/linux/lock_dlm_plock.h /usr/include/linux/
> > cp usr/include/linux/lm_interface.h /usr/include/linux/
> > (that's all I can think of at the moment)
> >
> > Dave
> >
>
> I did look into this a bit more and we need to make some kind of a
> decision here.
>
> If we expect people building the cluster to install the headers with
> headers_install then we can basically remove all the references to
> KERNEL_SRC in all userland and everything will keep building just fine.
>
> If we want to allow people to build the cluster with an outside kernel
> then we need to fix or change the dirafter and change the Makefile's
> that use KERNEL_SRC to be all consistent in the same way.
>
> Given that we need KERNEL_SRC defined for the kernel modules that we
> carry around in the CVS tree, I would suggest to go for the latter
> solution and allow our users to build whatever they need.
Yep, I agree
next prev parent reply other threads:[~2007-08-20 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 3:27 [Cluster-devel] [PATCH] for a header-file-cannot-found building error Denis Cheng
2007-08-15 18:10 ` David Teigland
2007-08-16 1:45 ` 程任全
2007-08-19 5:32 ` Fabio Massimo Di Nitto
2007-08-20 14:01 ` David Teigland [this message]
2007-08-21 4:48 ` Fabio Massimo Di Nitto
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=20070820140103.GB31911@redhat.com \
--to=teigland@redhat.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;
as well as URLs for NNTP newsgroup(s).