I want to make people aware we're seeing some issues with gcc 4.8 on the autobuilder.
gcc is a whitelisted dependency in sstate so it is *not* accounted for in the sstate checksums. This means if you run a build with gcc 4.8, switch to 4.7 and then run a similar build, you can reuse sstate between the two. This has lead to failures on the autobuilder recently which have been rather confusing and is why the weekly test report is as red. I want to highlight the problem and make it clear this isn't an sstate bug, the sstate class is explicitly allowing this as things stand. In normal usage, you don't want a small change to gcc changing your world around so the class is probably ok as it is but we are going to have to be careful with builds going forwards. 1.5M1 may need clean sstate, just to be sure. Cheers, Richard _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
