On 31 October 2014 12:58, Richard Purdie <richard.pur...@linuxfoundation.org > wrote:
> On Fri, 2014-10-31 at 09:44 +0000, Burton, Ross wrote: > > On 29 October 2014 08:38, Fathi Boudra <fathi.bou...@linaro.org> > > wrote: > > bump SRCREV to 20140828 tag > > drop automake-foreign patch - fixed upstream (commit 18594de > > and edbae29) > > update realtime tests fixes upstream status from submitted to > > backported - merged upstream > > > > This doesn't build on the autobuilders, see for > > example > https://autobuilder.yoctoproject.org/main/builders/minnow/builds/84/steps/BuildImages/logs/stdio > > > > There are hundreds of compiler warnings, and a missing header. > > Now, since I've heard complaints that we don't merge patches quickly, I > want to highlight what this means. > I'm one them and I guess it's the stick I asked for, for complaining ;) > > We tried this patch, we found it had issues, therefore whenever we see > similar patches from similar authors, we now have a nagging doubt about > how much testing they've had. fwiw, it has been built and tested on armv7 and armv8 architectures, both successfully. Now I'm lokking why this issue is triggered on x86: /home/pokybuild/yocto-autobuilder/yocto-worker/minnow/build/build/tmp/sysroots/minnow/usr/include/tirpc/rpc/rpc.h:74:61: fatal error: rpc/rpcb_clnt.h: No such file or directory > This means we when we aggregate those > patches there is more risk to the build, we need a clean build before we > merge patches so it can delay other people's patches. This is a bit of a > vicious circle and its why you see some of the behaviour we get > complaints about. > > So I'd remind people that if they send things which don't work, it does > have an impact. There is also something you can do to influence this. > > Cheers, > > Richard > > > br, Fathi
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core