Bug 750199 - The -m32 option is missing when rpmbuild builds yaboot on ppc64 for ppc arch
Summary: The -m32 option is missing when rpmbuild builds yaboot on ppc64 for ppc arch
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yaboot
Version: 6.3
Hardware: powerpc
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jiri Skala
QA Contact: Release Test Team
URL:
Whiteboard:
: 751433 (view as bug list)
Depends On:
Blocks: 756082
TreeView+ depends on / blocked
 
Reported: 2011-10-31 10:37 UTC by Jiri Skala
Modified: 2014-11-09 22:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 12:43:21 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0791 0 normal SHIPPED_LIVE yaboot bug fix update 2012-06-19 20:34:34 UTC

Description Jiri Skala 2011-10-31 10:37:15 UTC 
Description of problem:
The yaboot package is built only for ppc (mentioned ppc32) arch. When the package is built on ppc64 system using `rpmbuild -bb --target ppc <spec-file>` the build will fail due to missing -m32 option in optflags. The -m32 options should be contained in optflags when '--target ppc' is specified.

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


How reproducible:


Steps to Reproduce:
1. install yaboot srpm on ppc64 system
2. rpmbuild --b --target ppc <srpm>
3. 
  
Actual results:
build fails

Expected results:
package build succeed

Additional info:
Adding -m32 to %build section of spec file fixes described issue.
Comment 2 Panu Matilainen 2011-10-31 13:29:03 UTC 
redhat-rpm-config does specify -m32 for ppc. The real issue here is that yaboot does not use $RPM_OPT_FLAGS at all when building, and there's no way for rpm to enforce that.
Comment 9 Jiri Skala 2011-11-07 10:35:16 UTC 
*** Bug 751433 has been marked as a duplicate of this bug. ***
Comment 18 errata-xmlrpc 2012-06-20 12:43:21 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-2012-0791.html
Note You need to log in before you can comment on or make changes to this bug.