From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fabio Massimo Di Nitto Date: Sun, 19 Aug 2007 07:32:57 +0200 Subject: [Cluster-devel] [PATCH] for a header-file-cannot-found building error In-Reply-To: <20070815181040.GA4031@redhat.com> References: <1187148421286-git-send-email-crquan@gmail.com> <20070815181040.GA4031@redhat.com> Message-ID: <46C7D609.90607@ubuntu.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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. I have patches ready for both cases so David, please let me know what you guys would prefer. Fabio -- I'm going to make him an offer he can't refuse.