| Summary: | Warnings when ICECC is enabled | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Bogdan Alexandru Voiculescu <bogdanx.a.voiculescu> |
| Component: | meta-yocto | Assignee: | Joshua Watt <JPEWhacker> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Low | CC: | benjamin.esquivel, jose.perez.carranza, nick.owens, poky.bs.watcher, poky.watcher, randy.macleod |
| Version: | 2.1 | ||
| Target Milestone: | Future | ||
| Hardware: | x86 | ||
| OS: | x86_64 | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Bogdan Alexandru Voiculescu
2016-05-11 08:15:57 UTC
Hi Bogdan, just wondering if this bug came up as part of a test, if so, which is it? Benjamin: I discovered this when verifying bug 8934. More information: In mega-manual we have:"If ICECC_ENV_EXEC is set in your local.conf file, the variable should point to the icecc-create-env script provided by the user. If you do not point to a user-provided script, the build system uses the default script provided by the recipe icecc-create-env-native.bb." I have not defined variable ICECC_ENV_EXEC; so default mechanism seems not to work. Joshua, since you use this could you confirm if this was fixed please? The warning is a little misleading; icecc is probably working its just not being used for those specific recipes because they don't specify a compiler. The warning probably needs to be adjusted to not show up in those sorts of cases where it is expected. I think doing that should be pretty straight forward i believe this was resolved in oe-core 0315aabeff8e6483b737d0e23d6841f1394ad3c8. Resolved in 0315aabeff8e6483b737d0e23d6841f1394ad3c8 |