| Summary: | Error when installing Kernelshark on intel-core2-32 machine with RPM package class | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | California Sullivan <california.l.sullivan> |
| Component: | core | Assignee: | Darren Hart <dvhart> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | dvhart, meta.mr.watcher, meta.watcher |
| Version: | 1.6.1 | ||
| Target Milestone: | 1.6.2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | New (Never tested) |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
California Sullivan
2014-07-17 21:59:28 UTC
Patch submitted to oe-core. The problem was that if you try to install both kernelshark and trace-cmd, they both have packaged trace-cmd. I can't explain why this only appeared on one machine for Cal, but this did reproduce for me on intel-corei7-64 too.
A simple fix is just to remove trace-cmd from the install prior to packaging. It is maybe a little crude, but it's simple and consistent with the current do_install() task which already removes the datadir.
diff --git a/meta/recipes-kernel/trace-cmd/kernelshark_1.2.bb b/meta/recipes-kernel/trace-cmd/kernelshark_1.2.bb
index d61097d..f287bed 100644
--- a/meta/recipes-kernel/trace-cmd/kernelshark_1.2.bb
+++ b/meta/recipes-kernel/trace-cmd/kernelshark_1.2.bb
@@ -25,6 +25,7 @@ FILESPATH = "${FILE_DIRNAME}/trace-cmd"
do_install() {
oe_runmake CC="${CC}" AR="${AR}" prefix="${prefix}" DESTDIR="${D}" install_gui
+ rm ${D}${bindir}/trace-cmd
rm -rf ${D}${datadir}/trace-cmd
rmdir ${D}${datadir}
}
I think this would be appropriate for daisy as well. Fixed in master: commit 5be57ba62b47f12f937b2e1e0f5ea07092c243d8 Author: Darren Hart <dvhart@linux.intel.com> Date: 2014-07-18 kernelshark: Remove trace-cmd from the kernelshark package |