[LU-251] gcc configure warnings cause build failures on RHEL6.1 Created: 29/Apr/11  Updated: 28/Sep/12  Resolved: 28/Sep/12

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.0.0, Lustre 2.1.0
Fix Version/s: Lustre 2.3.0

Type: Bug Priority: Minor
Reporter: Ned Bass Assignee: Yang Sheng
Resolution: Fixed Votes: 0
Labels: None
Environment:

RHEL 6.1


Severity: 3
Rank (Obsolete): 4625

 Description   

Our latest CHAOS kernel builds are based on RHEL 6.1 pre-release kernels. The kernel build system has enabled -Werror so warnings are treated as errors. Also, gcc is detecting and warning about things like unused variables and use of unitialized values. This causes several autoconf tests to fail and give false results. To fix these we can annotate unused variables with _attribute_ ((unused)) and initialize variables as needed.

I will upload a patch to gerrit to clean up the warnings. This patch may be needed to build Lustre on hyperion.



 Comments   
Comment by Ned Bass [ 29/Apr/11 ]

http://review.whamcloud.com/478

Comment by Peter Jones [ 02/May/11 ]

YangSheng

Could you please look into this one?

Thanks

Peter

Comment by Yang Sheng [ 11/Jul/11 ]

I'll investigate this issue now.

Comment by Yang Sheng [ 19/Jul/11 ]

This issue seem isn't effect rhel6.1 for now. But set-but-unused problem is really exist while newer gcc used. I'll open other ticket to fix it for fc15 patchless support.

Comment by Peter Jones [ 25/Jul/11 ]

ok Yang Sheng. What ticket will this work be tracked under?

Comment by Yang Sheng [ 25/Jul/11 ]

Hi, Peter, It is LU-506.

Comment by Peter Jones [ 09/Aug/11 ]

This work is being tracked under LU506

Comment by Christopher Morrone [ 15/Mar/12 ]

This was never done as part of LU-506. Can we remove the duplicate tag and get http://review.whamcloud.com/478 landed please?

Comment by Yang Sheng [ 16/Mar/12 ]

I'll rework after lu-709 finsihed.

Comment by Jodi Levi (Inactive) [ 28/Sep/12 ]

Reopening because patch landed in 2.3

Comment by Jodi Levi (Inactive) [ 28/Sep/12 ]

patch landed in 2.3

Generated at Sat Feb 10 01:05:14 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.