| Summary: | Usability: autotools: Provide config.log in the bitbake log for do_configure() failures | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Darren Hart <dvhart> |
| Component: | meta-yocto | Assignee: | Richard Purdie <richard.purdie> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | infras.ab.watcher, Infras.watcher, laurentiu.serban, poky.bs.watcher, poky.watcher, richard.purdie, song.liu |
| Version: | unspecified | ||
| Target Milestone: | 1.3 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | (P1)(patch review) Patch out for review | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Darren Hart
2012-05-16 16:12:59 UTC
I'm not sure this is autobuilder specific, we should probably dump the config.log into the bitbake logs whenever we see the expression "please see config.log". I've lost count of how often I've said "please send me the config.log file as the real failure is there". We should be able to improve autotools.bbclass to do this if configure fails. Richard, ah that makes even more sense. Recategorizing. Fixed in master: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=b8bd56e34d05ed7463d3125e630f6e70ff2fdbd9 Setting this to verified. Tested in commit 6382732a7516c67cb1a3e3e438b06f4fc43efa4e |