Bug 1028710 - gcc arguments used on the build system result in errors that cannot be disabled.
gcc arguments used on the build system result in errors that cannot be disabled.
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: redhat-rpm-config (Show other bugs)
All Linux
unspecified Severity urgent
: pre-dev-freeze
: 6.6
Assigned To: Panu Matilainen
BaseOS QE Security Team
Depends On:
Blocks: 1028609
  Show dependency treegraph
Reported: 2013-11-09 15:33 EST by Brian Lane
Modified: 2014-01-16 07:02 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-01-16 07:02:23 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Brian Lane 2013-11-09 15:33:59 EST
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-09 19:34:45 EST
Better to just not build with -Werror (which is arguably silly for release builds)
Comment 2 Dennis Gilmore 2013-11-09 23:13:36 EST
moving to redhat-rpm-config and rhel, which is where it is all defined.
Comment 4 Panu Matilainen 2014-01-16 07:02:23 EST
-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.