From: Brian J. Murrell <Brian.Murrell@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] building lustre from source on Linux kernel 2.6.24
Date: Thu, 18 Dec 2008 09:27:32 -0500 [thread overview]
Message-ID: <1229610452.709.42.camel@pc.interlinx.bc.ca> (raw)
In-Reply-To: <01ac01c95c9e$8e941f70$4262d38d@um7d7332d2a74e>
On Fri, 2008-12-12 at 16:14 -0500, wenjing wu wrote:
> Hi,
>
> I was trying to build lustre from the source (lustre-source-1.6.6-2.6.9_67.0.22.EL_lustre.1.6.6smp.x86_64) on linux kernel 2.6.24, but it failed with these errors:
This topic has been discussed in the last couple of weeks on
lustre-discuss. Please see the archives for that list.
This type of message does not belong on lustre-devel. This list is for
discussion of development issues, not help requests.
b.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20081218/d2737bbe/attachment.pgp>
prev parent reply other threads:[~2008-12-18 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 21:14 [Lustre-devel] building lustre from source on Linux kernel 2.6.24 wenjing wu
2008-12-18 14:27 ` Brian J. Murrell [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=1229610452.709.42.camel@pc.interlinx.bc.ca \
--to=brian.murrell@sun.com \
--cc=lustre-devel@lists.lustre.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 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.