Bug 257961 - RPM needs secondary arch macro files
RPM needs secondary arch macro files
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: rpm (Show other bugs)
All All
medium Severity low
: ---
: ---
Assigned To: Panu Matilainen
Depends On:
  Show dependency treegraph
Reported: 2007-08-27 16:19 EDT by Doug Ledford
Modified: 2012-06-20 12:03 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 12:03:50 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 Doug Ledford 2007-08-27 16:19:54 EDT
+++ This bug was initially created as a clone of Bug #257921 +++

Description of problem:
When trying to run rpmbuild --ba --target=%{secondary_arch} $package.spec on a
multiarch capable machine (aka, i386 on x86_64, ppc64 on ppc, etc), the
necessary /usr/lib/rpm/arch-linux/macros files do not exist to set the proper
paths and compile options.  For example, to compile i386 on x86_64, %{_libdir}
needs to change to /usr/lib instead of /usr/lib64 and RPM_OPT_FLAGS/CFLAGS needs
to have -m32 added to the compiler options to compile properly, as well as
proper linking options.  Since the secondary arch macro files are contained in
the base rpm package, and the base rpm package is not multilib installable (you
get conflicts if you try), it becomes impossible to compile an rpm for a
secondary arch on the primary arch without hand munging the spec file.

Version-Release number of selected component (if applicable):
Comment 1 Jiri Pallich 2012-06-20 12:03:50 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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