Bug 772693 - systemtap can't be installed on PPC architecture
Summary: systemtap can't be installed on PPC architecture
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: systemtap
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Frank Ch. Eigler
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-09 17:08 UTC by Daniel Berrangé
Modified: 2012-01-09 19:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-09 19:22:13 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Daniel Berrangé 2012-01-09 17:08:37 UTC
Description of problem:
Attempting to build the latest perl-Sys-Virt RPM, I encountered an unresolvable dependency in Systemtap on PPC architectures:

http://download.devel.redhat.com/brewroot/work/tasks/7361/3927361/root.log

DEBUG util.py:256:  Error: Missing Dependency: kernel-devel is needed by package systemtap-1.6-4.el6.ppc (build)


The problem is that 'kernel-devel' is not built on PPC architecture in RHEL-6. So AFAICT, there is no way that the 'systemtap' RPM can ever be installed on the PPC archictecture, despite it being built.

Version-Release number of selected component (if applicable):
systemtap-1.6-4.el6.ppc

How reproducible:
Always

Steps to Reproduce:
1. yum install systemtap  on a 'ppc' RHEL-6 root. (ie *not* ppc64)
2.
3.
  
Actual results:
DEBUG util.py:256:  Error: Missing Dependency: kernel-devel is needed by package systemtap-1.6-4.el6.ppc (build)

Expected results:
It is unclear what we should do here, but I can see two options

 - Don't build systemtap on PPC architectures
 - Built systemtap on PPC, but don't put a dep on kernel-devel which doesn't exist


Additional info:

Comment 1 Frank Ch. Eigler 2012-01-09 17:13:33 UTC
Dan, what kernel RPMs are used on your installation?

Comment 3 Daniel Berrangé 2012-01-09 17:22:59 UTC
This is not a host install, this is a mock build root - see the URL in the comment above. I guess that brew does 'ppc' build roots on a ppc64 host, but that's not relevant to the dependency resolution of mock inside the root.

Comment 4 Frank Ch. Eigler 2012-01-09 17:31:48 UTC
Sorry, I don't understand.  What kernel would be installed in a mock buildroot?
Or do mock buildroots simply lack kernels entirely?  I see no ppc (32-bit) kernel
build, and a 32-bit systemtap.ppc should be quite happy with a 64-bit
kernel-devel.ppc64 installed.

Comment 5 Daniel Berrangé 2012-01-09 17:42:23 UTC
There's no kernel package installed in the mock buildroot at all - only a noarch  kernel-headers package. IIUC, The ppc build roots won't ever pull in RPMs from ppc64 RPMs.

So even though systemtap.ppc can work fine with a kernel-devel.ppc64, AFAICT, you can't install that combo inside mock :-(

Comment 6 Frank Ch. Eigler 2012-01-09 17:43:16 UTC
That seems like a mock problem, rather than a systemtap one.

Comment 7 Frank Ch. Eigler 2012-01-09 19:22:13 UTC
It appears as though mock isn't in RHEL, so we can't file a bug against it
for its treatment of kernel-* prereqs.  It is not wrong for systemtap to
prereq kernel-devel.


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