https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-16819 Lustre <p>Using "uname -r" anywhere in the build process limits building to the currently running kernel. This is bad since it's quite common to build for multiple kernels when doing DKMS builds.</p> <p> </p> <p>This shows up in <a href="https://jira.whamcloud.com/browse/LU-16659" title="mofed detection would detect multiple OFED installed by mistake for multiple kernels installed" class="issue-link" data-issue-key="LU-16659"><del>LU-16659</del></a></p> LU-16819

Using "uname -r" in lnet/autoconf/lustre-lnet.m4 limits building to the currently running kernel

Bug Minor Open Unresolved Åke Sandgren Åke Sandgren Thu, 11 May 2023 06:21:21 +0000 Thu, 11 May 2023 12:46:23 +0000 Lustre 2.16.0 Lustre 2.16.0 0 3 <p>"ake sandgren &lt;ake.sandgren@hpc2n.umu.se&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/c/fs/lustre-release/+/50937" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/50937</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-16819" title="Using &quot;uname -r&quot; in lnet/autoconf/lustre-lnet.m4 limits building to the currently running kernel" class="issue-link" data-issue-key="LU-16819">LU-16819</a> build: use mofed path based on target kernel<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 9cfaf1e9420b4436363f0762d6de05ca1e59314d</p> Development Rank 1|i03l3r: Rank (Obsolete) 9223372036854775807 Severity