| Summary: | Incorrect path set for ppc adt in x86 machines | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] ADT | Reporter: | Alexandru Georgescu <alexandru.c.georgescu> |
| Component: | adt | Assignee: | Richard Purdie <richard.purdie> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | alexandru.c.georgescu, jessica.zhang, laurentiu.palcu, poky.adt.watcher, poky.watcher, yi.zhao |
| Version: | 1.5 | ||
| Target Milestone: | 1.6 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Alexandru Georgescu
2013-10-15 15:20:15 UTC
Just did a brief testing on other arches, and the issue seem to be only for PPC. I think there are two powerpc toolchains getting built on the autobuilder, probably due to meta-fsl-ppc. One uses "linux" and the other "linux-gnuspe" as the TARGET_OS. The question is therefore whether they're compatible and how we handle this. We don't see this for arm since we always use linux-gnueabi everywhere. So just to be clear, the reason there is a problem in the release artifacts is because meta-fsl-ppc was built after the other powerpc toolchains. The workaround for this issue is to only build either normal or spe SDK/ADT toolchains but not both in the same build. If both are required, use a separate ADT repo for one of them. A patch which addresses the problem is in review on the mailing list. Fixed in master with http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=bd1cf71974699e4dd5fac88ffdf54cf7f53f67e3 This should be verified on the next weekly build. Verified. |