<div dir="ltr"><div class="gmail_default" style="font-size:small">I&#39;m attempting to install lustre-client-dkms 2.12.9 on a Rocky Linux 8.6 system with kernel 4.18.0-372.19.1.el8_6.x86_64 and Mellanox OFED 5.7.1.0.2.1.rhel8u5.x86_64. I have the mlnx-ofa_kernel-devel RPM installed, but the lustre configure script is giving me the following error during the `yum install`:</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><span style="font-family:monospace">You seem to have an OFED installed but have not installed it&#39;s devel package.<br>If you still want to build Lustre for your OFED I/B stack, you need to install its devel headers RPM.<br>Instead, if you want to build Lustre for your kernel&#39;s built-in I/B stack rather than your installed OFED stack, either remove the OFED package(s) or use --with-o2ib=no.<br>                                       <br>Error! Bad return status for module build on kernel: 4.18.0-372.19.1.el8_6.x86_64 (x86_64)<br>Consult /var/lib/dkms/lustre-client/2.12.9/build/make.log for more information.<br>warning: %post(lustre-client-dkms-2.12.9-1.el8.noarch) scriptlet failed, exit status 10</span></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">I think I&#39;ve tracked it down to a &quot;$&quot; at the end of a grep in the /<span style="font-family:monospace">var/lib/dkms/lustre-client/2.12.9/build/configure</span> script, line 19530. Running the commands manually, if I drop the &quot;$&quot; then the O2IBPATHS variable gets populated.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><span style="font-family:monospace">[root@n1]# O2IBPATHS=$(eval /usr/bin/ofed_info | egrep -w &#39;mlnx-ofed-kernel-dkms|mlnx-ofa_kernel-devel|compat-rdma-devel|kernel-ib-devel|ofa_kernel-devel&#39; | xargs rpm -ql | grep &#39;\(/openib\|/ofa_kernel/default\|/ofa_kernel\)$&#39; | head -n1)<br>[root@n1]# echo $O2IBPATHS<br><br>[root@n1]# O2IBPATHS=$(eval /usr/bin/ofed_info | egrep -w &#39;mlnx-ofed-kernel-dkms|mlnx-ofa_kernel-devel|compat-rdma-devel|kernel-ib-devel|ofa_kernel-devel&#39; | xargs rpm -ql | grep &#39;\(/openib\|/ofa_kernel/default\|/ofa_kernel\)&#39; | head -n1)<br>[root@n1]# echo $O2IBPATHS<br>/usr/src/ofa_kernel/x86_64/4.18.0-372.19.1.el8_6.x86_64</span></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">It&#39;s hard to believe that I&#39;m the first person to run into this, but googling I haven&#39;t found any other reports of it being an issue. Just thought I&#39;d check. I&#39;m also not sure how to insert this tweak to test if it really fixes the configure failure.</div><div class="gmail_default" style="font-size:small"><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Regards,<br>-liam<br><br>-There are uncountably more irrational fears than rational ones. -P. Dolan<br>Liam Forbes           <a href="mailto:loforbes@alaska.edu" target="_blank">loforbes@alaska.edu</a>                       ph: 907.450.8618<br>UAF GI Research Computing Systems Manager</div><div><a href="https://calendly.com/ualoforbes/30min" target="_blank">https://calendly.com/ualoforbes/30min</a><br></div></div></div></div>