Bug 464754 - rpm prints error: Macro %__isa_name (and %__isa_bits) has empty body on ppc
Summary: rpm prints error: Macro %__isa_name (and %__isa_bits) has empty body on ppc
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: rawhide
Hardware: ppc64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Panu Matilainen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-30 08:52 UTC by Adam Tkac
Modified: 2013-04-30 23:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-01 09:04:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Adam Tkac 2008-09-30 08:52:22 UTC
Description of problem:
when I run rpm command (simple "rpm -q rpm" for example) it prints error about undefined macros

Version-Release number of selected component (if applicable):
# rpm -qa |grep rpm
rpm-4.5.90-0.git8461.7.ppc
rpm-libs-4.5.90-0.git8461.7.ppc
rpm-libs-4.5.90-0.git8461.7.ppc64

How reproducible:
always

Steps to Reproduce:
1. run "rpm -q rpm"
2. look on output
  
Actual results:
# rpm -q rpm
error: Macro %__isa_name has empty body
error: Macro %__isa_bits has empty body
rpm-4.5.90-0.git8461.7.ppc

Expected results:
# rpm -q rpm
rpm-4.5.90-0.git8461.7.ppc

Additional info:
macros __isa_name and __isa_bits are undefined in /usr/lib/rpm/platform/ppc{64,}{i,p}series-linux/macros but they are defined in /usr/lib/rpm/platform/ppc{64,}-linux/macros.

It seems those macros shall be defined everywhere or rpm shall use ppc{64,}-linux platform directories.

Let me know if you need more info or access to machine where this problem is reproducable.

Comment 1 Panu Matilainen 2008-10-01 09:04:12 UTC
This should be fixed in rawhide now (rpm-4.5.90-0.git8514.1). If not, please reopen, then I need to take a closer look at what's going on...

Comment 2 Adam Tkac 2008-10-01 10:09:32 UTC
4.5.90-0.git8514.1 looks fine for me.


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