Cluster-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] avoid configure failure with F10's 2.6.27.21 kernel headers
Date: Thu, 25 Jun 2009 19:30:30 +0200	[thread overview]
Message-ID: <87y6rg9q6h.fsf@meyering.net> (raw)
In-Reply-To: <1245501817.3665.338.camel@cerberus.int.fabbione.net> (Fabio M. Di Nitto's message of "Sat, 20 Jun 2009 14:43:37 +0200")

Fabio M. Di Nitto wrote:

> Hi Jim,
>
> On Fri, 2009-06-19 at 20:26 +0200, Jim Meyering wrote:
>> Without the patch below, ./configure would fail like this on Fedora 10:
>>
>>   checking linux/dlm_plock.h usability... no
>>   checking linux/dlm_plock.h presence... yes
>>   configure: WARNING: linux/dlm_plock.h: present but cannot be compiled
>>   configure: WARNING: linux/dlm_plock.h:     check for missing prerequisite headers?
>>   configure: WARNING: linux/dlm_plock.h: see the Autoconf documentation
>>   configure: WARNING: linux/dlm_plock.h:     section "Present But Cannot Be Compiled"
>>   configure: WARNING: linux/dlm_plock.h: proceeding with the compiler's result
>>   configure: WARNING:     ## --------------------------------------- ##
>>   configure: WARNING:     ## Report this to linux-cluster at redhat.com ##
>>   configure: WARNING:     ## --------------------------------------- ##
>>   checking for linux/dlm_plock.h... no
>>   configure: error: Unable to find dlm kernel headers.
>>   Make sure to install kernel headers 2.6.26 (or higher) or use --with-kernel=path
>>   configure option to point to the kernel source.
>>   [Exit 1]
>>
>> and config.log showed the problem:
>>
>>   In file included from conftest.c:79:0:
>>   /usr/include/linux/dlm_plock.h:25:2: error: expected specifier-qualifier-list before '__u32'
>>
>> Here's the patch:
>
> I haven't tested this patch directly but it looks good to go in.

Pushed to dlm.git.

> gfs2-utils.git might benefit for a similar change, let me know if you
> have time to do go for it, or I'll do it at the next round of merges.

Doing it there, too.



      reply	other threads:[~2009-06-25 17:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19 18:26 [Cluster-devel] [PATCH] avoid configure failure with F10's 2.6.27.21 kernel headers Jim Meyering
2009-06-20 10:22 ` Andrew Price
2009-06-21  7:49   ` Jim Meyering
2009-06-20 12:43 ` Fabio M. Di Nitto
2009-06-25 17:30   ` Jim Meyering [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=87y6rg9q6h.fsf@meyering.net \
    --to=jim@meyering.net \
    /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