[LU-9822] build with MOFED 4.1 fails on sles11 Created: 03/Aug/17  Updated: 15/Oct/21  Resolved: 15/Oct/21

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Bob Glossman (Inactive) Assignee: WC Triage
Resolution: Won't Fix Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

Build with MOFED 4.1 fails on sles11sp4. No issue building on other linux distros. Pretty sure I've tracked it down to being a MOFED bug, not a lustre bug. From Skype discussion with Minh:

[7/25/17, 7:41:22 AM] Bob Glossman: about that MOFED build problem that is sles11 only. I think I can see the cause. in MOFED’s compat/config.h file HAVE_IS_VLAN_DEV_CONST is #defined. pretty sure it should be #undef for sles11sp4. this makes it a MOFED bug.
[7/25/17, 7:41:51 AM] Bob Glossman: if I edit that config.h file then lustre builds fine
[7/25/17, 7:43:37 AM] Bob Glossman: something wrong in MOFED logic that generates that file, but only seriously broken on sles11sp4
[7/25/17, 8:06:14 AM] Bob Glossman: looking at logs for autoconf in MOFED that generates their config.h I can see the test compile for HAVE_IS_VLAN_DEV_CONST reporting a ‘warning’. but since they do their autoconf test without a -Werror option the warning isn’t promoted to be an error. This causes the autoconf test give the wrong answer, making HAVE_IS_VLAN_DEV_CONST #defined instead of #undef.

MOFED's #include files are all properly conditioned with #ifdefs to adapt to the environment, but since their autoconf is giving the wrong answer in this case building with their #includes causes conflicts in our build.


Generated at Sat Feb 10 02:29:35 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.