All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jay Lan <jay.zen.lan@gmail.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] ldiskfs build problem with rhel5.5
Date: Sun, 26 Dec 2010 22:48:17 -0800	[thread overview]
Message-ID: <4D1836B1.4060702@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1012201345350.18487@casper.infradead.org>

James Simmons wrote:
>> Hi,
>>
>> I ran into a problem in building ldiskfs-3.1.4 with 2.6.18-194.3.1.el5 
>> kernel.
>> The kernel was patched with kernel patches provided by lustre-1.8.5 and
>> ldiskfs-3.1.4.
>>
>> The problem I encountered was that the kernel and kernel-devel rpms
>> did not provide fs/ext4/*.[ch], which the build process would need.
>>
>> Is there a kernel patch for this problem?
>>     
>
> Does it deal with export_decode_fh ? Do you build againt OFED 1.5.2 ? If 
> that is the case then I ran into that issue last week. OFED alters your 
> kernel to build the modules but it doesn't alter the source tree. When  
> lustre builds it looks at your source tree which is different then what 
> the biniaries export. The solution is to copy what is in include-nfs/linux 
> from OFED to your kernel source tree include/linux directory.
>   

Hi James,

I was building against ofed 1.5.2, but I did not run into the
problem you described though. But thanks for sharing your
solution.

Thanks,
Jay

> _______________________________________________
> Lustre-devel mailing list
> Lustre-devel at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-devel
>   

      parent reply	other threads:[~2010-12-27  6:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-18  0:43 [Lustre-devel] ldiskfs build problem with rhel5.5 Jay Lan
2010-12-18  5:02 ` Andreas Dilger
2010-12-27  6:41   ` Jay Lan
2010-12-20 13:51 ` James Simmons
2010-12-21 17:34   ` [Lustre-devel] Compiling source code Ravi
2010-12-27  6:48   ` Jay Lan [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=4D1836B1.4060702@gmail.com \
    --to=jay.zen.lan@gmail.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.