Bug 1028710 - gcc arguments used on the build system result in errors that cannot be disabled.
Summary: gcc arguments used on the build system result in errors that cannot be disabled.
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: redhat-rpm-config
Version: 6.4
Hardware: All
OS: Linux
Target Milestone: pre-dev-freeze
: 6.6
Assignee: Panu Matilainen
QA Contact: BaseOS QE Security Team
Depends On:
Blocks: 1028609
TreeView+ depends on / blocked
Reported: 2013-11-09 20:33 UTC by Brian Lane
Modified: 2014-01-16 12:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-01-16 12:02:23 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Brian Lane 2013-11-09 20:33:59 UTC
Description of problem:
On the el6 branch gcc is being called with options that result in warnings that cannot be disabled being treated as errors.

eg. http://kojipkgs.fedoraproject.org//work/tasks/8032/6158032/build.log

-Wno-unused-result was apparently added in gcc 4.5 so it cannot be used to disable the warning/error.

This must have changed since the last build of bip since the line in question has been in the source tree since 2005.

Comment 1 Rex Dieter 2013-11-10 00:34:45 UTC
Better to just not build with -Werror (which is arguably silly for release builds)

Comment 2 Dennis Gilmore 2013-11-10 04:13:36 UTC
moving to redhat-rpm-config and rhel, which is where it is all defined.

Comment 4 Panu Matilainen 2014-01-16 12:02:23 UTC
-Werror can be useful for development work but its a terrible idea to use it for "release builds" because of issues like this: compilers can and do grow new warnings over time so code which at some point compiled free of any warnings might trip tonnes of warnings with a later compiler version.

NOTABUG, just eliminate the -Werror usage.

Note You need to log in before you can comment on or make changes to this bug.