Bug 1505492

Summary: glibc: Build with -Werror and -Wundef
Product: Red Hat Enterprise Linux 7 Reporter: Patsy Griffin <pfrankli>
Component: glibcAssignee: Florian Weimer <fweimer>
Status: CLOSED ERRATA QA Contact: Alexandra Petlanová Hájková <ahajkova>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5CC: ahajkova, ashankar, codonell, fweimer, hannsj_uhl, mcermak, mnewsome, pfrankli, skolosov
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glibc-2.17-234.el7 Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 09:36:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1349967, 1564638, 1566623    
Bug Blocks: 1565233    

Description Patsy Griffin 2017-10-23 16:57:15 UTC
Description of problem:

Backport "Do not build with -Winline" to avoid unnecessary warnings.

We need to backport this patch.  

commit ed159672eb3cd650a32b7e5cb4d5ec1fe0e63802
Author: Florian Weimer <fweimer>
Date:   Fri Apr 24 11:10:24 2015 +0200

    Do not build with -Winline
    
    -Winline causes architecture- and optimization-dependent build failures
    due to -Werror.  -Winline warns about inlining decisions based on
    branch hints, in effect preventing the use of inline functions in
    header files (because they might be called on unlikely branches, leading
    to a decision not to inline).
    
    The option was apparently added to the glibc build at a time when GCC
    did not support the always_inline attribute.  With current GCC versions,
    inlining failure for functions declared always_inline will receive a
    warning under -Wattributes, which is enabled by default, so -Winline
    appears unnecessary.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Florian Weimer 2018-04-02 20:59:13 UTC
Should we backport -Werror?  I already added -Werror=implicit-function-declaration a while back.

Comment 2 Carlos O'Donell 2018-04-02 21:17:00 UTC
(In reply to Florian Weimer from comment #1)
> Should we backport -Werror?  I already added
> -Werror=implicit-function-declaration a while back.

This is an internal request, and it has some value to us, but given we have some upstream goals we want to accomplish, I'd say the value would have to be high and it would have to be straight forward for us to do it in the upcoming release.

How much work do you estimate this is?

Comment 13 Florian Weimer 2018-08-24 08:42:32 UTC
Note that -Werror is *not* used for bootstrap builds.  You will only see -Werror in regular builds.

Comment 16 errata-xmlrpc 2018-10-30 09:36:35 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:3092