Bug 477729 - Missing PPC64 Build Dependency
Missing PPC64 Build Dependency
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kexec-tools (Show other bugs)
ppc64 Linux
low Severity low
: rc
: ---
Assigned To: Neil Horman
Martin Jenner
Depends On:
  Show dependency treegraph
Reported: 2008-12-22 23:35 EST by CAI Qian
Modified: 2008-12-23 07:43 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-12-23 07:43:34 EST
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 CAI Qian 2008-12-22 23:35:08 EST
Description of problem:
Kexec-tools failed to build on system without elfutils-devel-static.ppc64 installed.

521-makedumpfile.c:5143: warning: unused variable 'offset_page'
522-makedumpfile.c:5142: warning: unused variable 'paddr'
523-/usr/bin/ld: skipping incompatible /usr/lib/libdw.a when searching for -ldw
524-/usr/bin/ld: cannot find -ldw
525-collect2: ld returned 1 exit status
526:make: *** [makedumpfile] Error 1
527:make: Leaving directory
528:error: Bad exit status from /var/tmp/rpm-tmp.3896 (%build)

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

How reproducible:

Steps to Reproduce:
1. install elfutils-devel-static.ppc
2. uninstall elfutils-devel-static.ppc64
3. rpmbuild -ba kexec-tools.spec
Actual results:
Failed to build

Expected results:
Exit gracefully like,

# rpmbuild -bp /usr/src/redhat/SPECS/kexec-tools.spec
error: Failed build dependencies:
       elfutils-devel-static.ppc64 is needed by kexec-tools-1.102pre-56.el5.ppc64
Comment 1 Neil Horman 2008-12-23 07:43:34 EST
As per our email conversation, I'm closing this as NOTABUG.  I really don't think this is anything that needs to be fixed in kexec-tools at the moment.  Its alsmot like rpm is getting very confused about what is allowedto satisfy dependencies during a build.

We can re-open this is we find that this actaully does need to be fixed in the spec file, but given what you have above this really sounds like an rpm bug to me.

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