On Sat, 13 Apr 2019 10:03:03 +0200 Andreas Müller <[email protected]> wrote:
> On Fri, Apr 12, 2019 at 10:18 AM <[email protected]> > wrote: > > > > On Wed, 2019-04-10 at 18:59 -0500, Seebs wrote: > > > On Thu, 11 Apr 2019 00:12:54 +0100 > > > Richard Purdie <[email protected]> wrote: > > > > > > > -SRCREV = "6294b344e5140f5467e6860f45a174440015304e" > > > > +SRCREV = "6ebc7d6bc8ab973d0ba949eeb363821811ce8dc5" > > > > > > I would sort of recommend one of the two commits since then -- one > > > may > > > fix the .NET startup failures, and the other fixes warnings that > > > this one introduced and I forgot to fix. But I'm also okay with > > > this one. > > > > That is good news. I've tested and updated to the later revision, > > thanks! > > > > Cheers, > > > > Richard > > > Hi, > > If you want a happy weekend - stop reading here. > > But somebody has to do widen the audience... > > Seems that this commit causes issues on meta-qt5 / qtbase [1]. To make > it worse it seems that only some host configurations are affected... > > Cheers > > [1] https://github.com/meta-qt5/meta-qt5/issues/187 > > Andreas My guess from looking at it is that qmake is using renameat2 and isn't falling back to something else if renameat2 fails with ENOSYS. -s -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
