| Summary: | Usability: Improve RRECOMMENDS warning messages for -dbg packages | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Mark Hatle <mark.hatle> |
| Component: | configuration | Assignee: | Unassigned <unassigned> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | bluelightning, jessica.zhang, poky.bs.watcher, poky.watcher, randy.macleod, richard.purdie, scott.branden, tim.orling |
| Version: | unspecified | ||
| Target Milestone: | 5.99 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
Paul, I know you've been working in this area recently. Is this still an issue? I suspect if it is, current experience might make it easy to fix? For -dbg packages this will no longer be an issue since the dependency has been removed: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=eff37ecde9dee196eaa07867cd5876dc42b26dd5 However I still think we should try to improve the error message since the same situation can apply to -dev and -staticdev packages. Bulk move from 4.99 or 0.00 to 5.99 Still valid. |
When a recipe is created that does not have a ${PN} in the PACKAGES, but does have the ${PN}-dbg, a dependency error occurs of the type: NOTE: Runtime target 'gcc-runtime' is unbuildable, removing... Missing or unbuildable dependency chain was: ['gcc-runtime'] ERROR: Required build target 'gcc-runtime' has no buildable providers. Missing or unbuildable dependency chain was: ['gcc-runtime', 'gcc-runtime'] ERROR: Nothing RPROVIDES 'gcc-runtime' (but /home/mhatle/git/poky/meta/recipes-devtools/gcc/gcc-runtime_4.5.1.bb RDEPENDS on or otherwise requires it) A simple change to the recipe: # The base package doesn't exist, so we clear the recommends. RRECOMMENDS_${PN}-dbg = "" resolves the problem. It would be good to improve the error message about the dependencies to indicate that it came from RRECOMMENDS_${PN}-dbg, instead of just calling it a dependency. It was difficult to understand where the dependency came from in order to fix it.