| Summary: | core-image-tiny-initramfs fails to build due to misconfiguration in busysbox | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Iuliu Vasilescu <iuliuv> |
| Component: | core | Assignee: | Unassigned <unassigned> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | Undecided | CC: | meta.mr.watcher, meta.watcher, richard.purdie, tim.orling |
| Version: | unspecified | ||
| Target Milestone: | 0.0.0 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Iuliu Vasilescu
2024-08-28 18:32:51 UTC
The mdev feature is controlled by a config fragment, i.e. meta/recipes-core/busybox/busybox/mdev.cfg
In meta/recipes-core/busybox/busybox_1.36.1.bb this is controlled by:
${@["", "file://mdev.cfg"][(d.getVar('VIRTUAL-RUNTIME_dev_manager') == 'busybox-mdev')]} \
so it is only enabled when the init manager is selected.
I don't think we should enable this unless something is using it. That is a distro policy decision (which can add the cfg to busybox.
And since you are using a raspberrypi4-64 machine, you may want to ask in a meta-rapsberrypi issue on GitHub https://github.com/agherzan/meta-raspberrypi But first make sure you have your "distro" configured properly, as RP said. |