From: "Brian J. Murrell" <Brian.Murrell-veTT2BtV2gBXrIkS9f7CXA@public.gmane.org>
To: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: compiling against lustre 1.8.2 kernel
Date: Mon, 17 May 2010 12:27:09 -0400 [thread overview]
Message-ID: <1274113630.396.41.camel@pc.interlinx.bc.ca> (raw)
In-Reply-To: <AANLkTil_7L_cbglOcaHKPRmrrntXew9jwxvSrTkxNcnF-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
On Mon, 2010-05-17 at 12:15 -0400, Michael Di Domenico wrote:
> I ran across an error when trying to compile OFED-1.4.2 agianst the
> Lustre 1.8.2 kernel on Redhat v5.4 (2.6.18-164.11.1)
>
> /var/tmp/ofed.topdir/BUILD/ofa_kernel_1.4.2/kernel_addons/backport/2.6.18-EL5.3/include/linux/sched.h:13
> error: static declaration of '__fatal_signal_pending' follows
> non-static declaration include/linux/sched.h: 1570 error: previous
> declaration of '__fatal_signal_pending' was here
>
> Any suggestions?
Have you checked that OFED 1.4.2 supports the RHEL5 2.6.18-164.11.1
kernel? I don't have release notes handy so I don't know.
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-05-17 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 16:15 compiling against lustre 1.8.2 kernel Michael Di Domenico
[not found] ` <AANLkTil_7L_cbglOcaHKPRmrrntXew9jwxvSrTkxNcnF-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-17 16:27 ` Brian J. Murrell [this message]
[not found] ` <1274113630.396.41.camel-lA68w17JHpfIgqYUaR6mlLDks+cytr/Z@public.gmane.org>
2010-05-17 17:32 ` Michael Di Domenico
[not found] ` <AANLkTikwu0pcBUNaxJQvTJdBDi18KpcQiUeyM3d_YhSi-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-17 18:10 ` Brian J. Murrell
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=1274113630.396.41.camel@pc.interlinx.bc.ca \
--to=brian.murrell-vett2btv2gbxriks9f7cxa@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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