Good news is that went green, so the problem is restricted to CC_FOR_BUILD usage I guess.
Ross On 21 April 2018 at 09:09, Burton, Ross <[email protected]> wrote: > Okay, fired at > https://autobuilder.yocto.io/builders/nightly-x86-64-lsb/builds/969. > That won't be catching people using CC_FOR_BUILD in target recipes to > build pieces using the host compiler, but it will be interesting to > see if it catches anything. > > Ross > > On 21 April 2018 at 09:08, Burton, Ross <[email protected]> wrote: >> On 20 April 2018 at 23:09, Andre McCurdy <[email protected]> wrote: >>> On Fri, Apr 20, 2018 at 2:57 PM, Burton, Ross <[email protected]> wrote: >>>> Hi, >>>> >>>> We'll hopefully be firing the 2.5 RC build on Monday, so I did a build >>>> today to see where we stand. As is typical we got two new failures on >>>> the autobuilder... My test build included the pseudo bump which >>>> caused an almost complete rebuild, which is a great way to shake out >>>> intermittent failures. >>>> >>>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=12704 >>>> Go appears to be using the target CFLAGS when using the host compiler, >>>> with predictable failures when the host is old and doesn't support new >>>> flags. >>> >>> Maybe worth resurrecting something like: >>> >>> >>> http://lists.openembedded.org/pipermail/openembedded-core/2016-February/118212.html >>> >>> to flush out similar issues? >> >> Thank you for finding that, I remembered there was a patch but >> couldn't find it. :) >> >> Ross -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
