[LU-16819] Using "uname -r" in lnet/autoconf/lustre-lnet.m4 limits building to the currently running kernel Created: 11/May/23  Updated: 11/May/23

Status: Open
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.16.0
Fix Version/s: Lustre 2.16.0

Type: Bug Priority: Minor
Reporter: Åke Sandgren Assignee: Åke Sandgren
Resolution: Unresolved Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

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.

 

This shows up in LU-16659



 Comments   
Comment by Gerrit Updater [ 11/May/23 ]

"ake sandgren <ake.sandgren@hpc2n.umu.se>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/50937
Subject: LU-16819 build: use mofed path based on target kernel
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 9cfaf1e9420b4436363f0762d6de05ca1e59314d

Generated at Sat Feb 10 03:30:16 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.