From: Justin Clift <justin-oNuxUQfTmABg9hUCZPvPmw@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Initial patch for OFED 1.5.x to work on RHEL 6
Date: Wed, 28 Apr 2010 14:13:57 +1000 [thread overview]
Message-ID: <4BD7B605.2070203@salasaga.org> (raw)
Hi all,
Taking a look at the RHEL6 beta at the moment. It was failing
compilation of OFED 1.5.1 release on the main ofa kernel rpm, giving the
same error reported by Jeremy Enos back in Aug 2009 on Fedora 10.
Thankfully the problem turned out to be a bug in the scripting in the
rpm's spec file, easily fixed, which let's this now compile fine:
**********************************************************
--- ofa_kernel.spec_orig 2010-04-28 13:01:43.505217495 +1000
+++ ofa_kernel.spec 2010-04-28 13:52:44.386217393 +1000
@@ -188,6 +188,7 @@
if [ -n "$modsyms" ]; then
for modsym in $modsyms
do
+ mkdir -p $RPM_BUILD_ROOT/%{_prefix}/src/%{_name}
cat $modsym >>
$RPM_BUILD_ROOT/%{_prefix}/src/%{_name}/Module.symvers
done
else
@@ -800,9 +801,7 @@
%files -n kernel-ib-devel
%defattr(-,root,root,-)
%dir %{_prefix}/src
-%{_prefix}/src/%{_name}-%{_version}
%{_prefix}/src/%{_name}
-%{_prefix}/src/openib
%endif
# END Files
**********************************************************
The "mkdir -p" is the important part that needed adding, and should be
safe to add on all the platforms.
Near the end however, it needed the removal of two directories not built
on RHEL 6. Not sure if they do get built on other platforms though.
Vladimir Sokolovsky would probably know. :)
Hope that helps.
Regards and best wishes,
Justin Clift
--
Salasaga - Open Source eLearning IDE
http://www.salasaga.org
--
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
reply other threads:[~2010-04-28 4:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4BD7B605.2070203@salasaga.org \
--to=justin-onuxuqftmabg9huczpvpmw@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