| Summary: | linux-libc-headers: icecc | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Lukas Bulwahn <lukas.bulwahn> |
| Component: | devtools / tool chain | Assignee: | Laurentiu Palcu <laurentiu.palcu> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | minor | ||
| Priority: | Low | CC: | bruce.ashfield, lukas.bulwahn, Martin.Jansa, meta.mr.watcher, meta.watcher, richard.purdie, tom.zanussi |
| Version: | unspecified | ||
| Target Milestone: | Future | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Lukas Bulwahn
2013-08-22 09:42:10 UTC
Martin, would you have any ideas on this one? Isn't it caused by ICECC_BASEDIR pointing to /tmp/.icecream-root where the user running bitbake cannot write? So the best fix would be to point ICECC_BASEDIR to be under TMPDIR somewhere? icecc is usually configured outside OE (sort of ASSUME_PROVIDED when user inherits icecc). Pointing it to TMPDIR looks sane, but if the user is using icecc for other project than OE then any user-write-able directory will work - it could be a bit confused from pseudo (I guess root's icecc.conf was used instead of user running bitbake). I doubt this issue is pseudo related since compile tasks are not performed under pseudo. I'm going to resolve this as 'invalid' for want of a better category since I believe this is a configuration issue, the user shouldn't point icecc at a shared directory for locks. |