This service will be undergoing maintenance at 20:00 UTC, 2017-04-03. It is expected to last about 30 minutes
Bug 158221 - rpmbuild --target ppc64 builds ppc32 binaries
rpmbuild --target ppc64 builds ppc32 binaries
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: rpm (Show other bugs)
powerpc Linux
medium Severity medium
: ---
: ---
Assigned To: Panu Matilainen
: 167834 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2005-05-19 14:05 EDT by David Lehman
Modified: 2010-06-07 01:12 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-07 01:12:13 EDT
Type: ---
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 David Lehman 2005-05-19 14:05:48 EDT
+++ This bug was initially created as a clone of Bug #146155 +++

Description of problem:
Running rpmbuild --target ppc64 builds ppc32 objects but puts them in /lib64 and
calls the rpm a .ppc64.rpm. I seems CFLAGS and/or RPM_OPT_FLAGS are not being
set correctly.

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

How reproducible:

Steps to Reproduce:
1. Grab any SRPM for which we ship a ppc64 package (eg: pcre)
2. run rpmbuild -bb --target ppc64 pcre.spec 
Actual results:
rpmbuild creates a .ppc64.rpm containing 32-bit libraries in /usr/lib64

Expected results:
If it builds a ppc64 package the package should contain 64-bit objects

Additional info:
Comment 1 Jens Petersen 2006-01-05 05:00:54 EST
-m64 is used with RHEL4U2 at least AFAICT.
Also I believe (for better or worse) rpmbuild defaults to ppc64
on our powerpc os currently too FWIW.
Comment 2 Jeff Johnson 2006-02-12 10:47:38 EST
*** Bug 167834 has been marked as a duplicate of this bug. ***
Comment 3 Jeff Johnson 2006-08-06 18:09:30 EDT
This problem is like fixed (by setting arch from --target) in rpm-4.4.7-0.15.


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