Bug 798543

Summary: device-mapper-multipath: standard rpm cflags not used during build [rhel-5]
Product: Red Hat Enterprise Linux 5 Reporter: Tomas Hoger <thoger>
Component: device-mapper-multipathAssignee: Ben Marzinski <bmarzins>
Status: CLOSED ERRATA QA Contact: Storage QE <storage-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.8CC: agk, bdonahue, bmarzins, bmr, dwysocha, heinzm, prajnoha, prockai, zkabelac
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: device-mapper-multipath-0.4.7-61.el5 Doc Type: Bug Fix
Doc Text:
no documentation needed.
Story Points: ---
Clone Of: 798541 Environment:
Last Closed: 2014-09-16 00:21:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tomas Hoger 2012-02-29 08:27:18 UTC
+++ This bug was initially created as a clone of Bug #798541 +++

Description of problem:
spec file for device-mapper-multipath does not use rpm macro %configure and invokes make without explicitly adding default rpm cflags.  As a consequence, build is not made with optimization level and protections expected to be the default for all packages.

Version-Release number of selected component (if applicable):
device-mapper-multipath-0.4.7-48.el5

Comment 1 RHEL Program Management 2014-01-29 10:37:04 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Comment 2 Ben Marzinski 2014-03-29 03:48:11 UTC
Multipath has been updated to use RPM_OPT_FLAGS, and the build warnings that resulted were fixed.

Comment 5 errata-xmlrpc 2014-09-16 00:21:12 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.

http://rhn.redhat.com/errata/RHBA-2014-1228.html