From: Vladimir Sokolovsky <vlad-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Tanin <fanqielee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: OpenFabrics EWG
<ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [ewg] Installation problems of OFED-1.5.2
Date: Wed, 23 Feb 2011 11:14:18 +0200 [thread overview]
Message-ID: <4D64CFEA.1030805@dev.mellanox.co.il> (raw)
In-Reply-To: <AANLkTi=s7YtdX2+bb4pLY035OXQSqyf21JuxatDCL=N_-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 02/23/2011 05:12 AM, Tanin wrote:
> Dear all,
>
> I have recompiled the kernel to 2.6.18, and try to install OFED-1.5.2
> instead.
>
> Now the kernel version is
>
> [litan@tera04 OFED-1.5.2]$ uname -a
> Linux tera04.ultralight.org 2.6.18-prep #1 SMP Tue Feb 22 18:51:00 EST 2011
> x86_64 x86_64 x86_64 GNU/Linux
>
>
> I have the full log file in the attachment. Dose it related to that I try
> many times to install different version of OFED? Thanks a million!
>
OFED's backport system is rely on kernel version.
So, changing kernel version changes the set of patches and headers to be used for the compilation.
You should keep the kernel version as close as possible to the original version.
E.g.:
If you compile 2.6.18 from kernel.org then you can name it 2.6.18-prep
But, if you recompile 2.6.18-164.el5, then you should name it 2.6.18-164.<any extension>.el5
Regards,
Vladimir
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-23 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 3:12 Installation problems of OFED-1.5.2 Tanin
[not found] ` <AANLkTi=s7YtdX2+bb4pLY035OXQSqyf21JuxatDCL=N_-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-02-23 9:14 ` Vladimir Sokolovsky [this message]
[not found] ` <4D64CFEA.1030805-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2011-02-23 19:02 ` Tanin
[not found] ` <AANLkTinLQ0zo1jbENOAoaDTVi6dmpPn3zTSfY12q-gxf-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-02-23 19:24 ` Tanin
[not found] ` <AANLkTimXs07EaMp0Q4WgJ0gX3sPp9tsqURGdKc=sxEyo-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-02-23 22:38 ` Tanin
2011-02-24 8:46 ` [ewg] " Vladimir Sokolovsky
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=4D64CFEA.1030805@dev.mellanox.co.il \
--to=vlad-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
--cc=fanqielee-Re5JQEeQqe8AvxtiuMwx3w@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