| Summary: | kernel build failed when it's bundled with initramfs and inherit rm_work | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Xufeng Zhang <xufeng.zhang> |
| Component: | deployment | Assignee: | Xufeng Zhang <xufeng.zhang> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | bruce.ashfield, jason.wessel, jessica.zhang |
| Version: | unspecified | ||
| Target Milestone: | 1.5.1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
The kernel objects are required to be around if you are doing the bundling because they are required to re-link things. We do not really want to bundle all these .o files into the sysroot because the do_package and do_install is already too slow for the kernel. Is there a way to pass on the rm_work for a certain package if the option to bundle is turned on? >>Is there a way to pass on the rm_work for a certain package if the option to bundle is turned on?
Actually kernel could be excluded from rm_work by RM_WORK_EXCLUDE variable,
but kernel build stuff occupy lots of disk space, so we still need to
clean up the kernel after do_bundle_initramfs task is finished.
Patch has already been merged. |
This is a regression introduced by commit 609d5a9ab (kernel.bbclass, image.bbclass: Implement kernel INITRAMFS dependency and bundling). Since kernel will build twice when we are trying to bundle the kernel and initramfs together after 609d5a9ab("kernel.bbclass, image.bbclass: Implement kernel INITRAMFS dependency and bundling"), thus, the second building for kernel would fail if rm_work is done previously.