All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc - A. Dahlhaus <mad@wol.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Cluster ./configure fails with 2.6.31-rc* kernel headers
Date: Sun, 12 Jul 2009 13:21:17 +0200	[thread overview]
Message-ID: <4A59C72D.80500@wol.de> (raw)
In-Reply-To: <20090712015544.GA5987@sucs.org>

Hello,

Andrew Price schrieb:
> Hi,
>
> I've been experiencing cluster ./configure failures since this commit
> went into the 2.6.31-rc* kernel:
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c31ae4bb4a9fa4606a74c0a4fb61b74f804e861e
>
> My config.log says:
>
> ----
> configure:13727: checking linux/dlm_plock.h usability
> configure:13744: gcc -c -g -O2 -I/lib/modules/2.6.31-rc2-plato34/build/include conftest.c >&5
> In file included from /usr/include/asm/types.h:4,
>                  from /lib/modules/2.6.31-rc2-plato34/build/include/linux/types.h:4,
>                  from /lib/modules/2.6.31-rc2-plato34/build/include/linux/dlm_plock.h:12,
>                  from conftest.c:81:
> /lib/modules/2.6.31-rc2-plato34/build/include/asm-generic/int-ll64.h:11:29: error: asm/bitsperlong.h: No such file or directory
> configure:13751: $? = 1
> ----
>
> I haven't attempted this on a 32bit system yet but I suspect it only
> affects 64bit builds.
>
> For now I'm working around the problem using this ugly hack in
> configure.ac:
>
> -KERNEL_CPPFLAGS="-I$KERNEL_DIR/include"
> +KERNEL_CPPFLAGS="-I$KERNEL_DIR/include -I$KERNEL_DIR/arch/x86/include"
>
> But what really needs fixing, the kernel headers or the cluster build
> system?
Did you run "make prepare" inside of your kernel tree?
It should take care of linking asm to the right spot in arch tree...

Hope that helps,

Marc



  reply	other threads:[~2009-07-12 11:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-12  1:55 [Cluster-devel] Cluster ./configure fails with 2.6.31-rc* kernel headers Andrew Price
2009-07-12 11:21 ` Marc - A. Dahlhaus [this message]
2009-07-12 14:44   ` Andrew Price

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=4A59C72D.80500@wol.de \
    --to=mad@wol.de \
    /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.