| Summary: | eglibc doesn't depend on gcc version correctly | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Robert Yang <liezhi.yang> |
| Component: | core | Assignee: | Robert Yang <liezhi.yang> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | jessica.zhang, liang.li2, liangliang.wang, meta.mr.watcher, meta.watcher, sgw, yi.zhao |
| Version: | 0.9 | ||
| Target Milestone: | 1.2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | post 1.1 | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Robert Yang
2011-06-15 18:46:02 UTC
please provide some update on the bug since it's been a while from the last activity Here was the information from Richard: The sstate checksum of the sstate-eglibc-xxx_package.tgz package should have changed when the gcc version changed, such that it would repackage (based on updated data). I think the problem is that in the sstate code, we've assumed the toolchain is special and can change: BB_HASHTASK_WHITELIST ?= "(.*-cross$|.*-native$|.*-cross-initial$|.*-cross-intermediate$|^virtual:native:.*|^virtual:nativesdk:.*)" and this may be a sign we should reconsider this. Alternatively we could hiighlight we simply don't support gcc version going backwards I think that we can mark it as WONTFIX |