Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 158215 - rpmrc and ppc64pseries and ppc64iseries macros files are broken
Summary: rpmrc and ppc64pseries and ppc64iseries macros files are broken
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: rpm
Version: 3.0
Hardware: powerpc
OS: Linux
Target Milestone: ---
Assignee: Panu Matilainen
QA Contact:
Depends On:
Blocks: 190430
TreeView+ depends on / blocked
Reported: 2005-05-19 17:14 UTC by David Lehman
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-10-19 19:01:58 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description David Lehman 2005-05-19 17:14:34 UTC
Description of problem:
anaconda writes the canonical arch into /etc/rpm/platform. rpm uses this arch by
default when doing package builds. The problem is that the macros files for the
canonical arches are wrong. They don't define %_multilibno and %optflags is wrong.

More importantly, rpmrc doesn't have the correct buildarchtranslate entries for
ppc64pseries and ppc64iseries. 

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

How reproducible:

Steps to Reproduce:
1. try to rebuild any package on a pSeries without using --target
Actual results:
The resulting package will be .ppc64pseries.rpm

Expected results:
The resulting package should be .ppc.rpm

Additional info:

Comment 5 RHEL Program Management 2007-10-19 19:01:58 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

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