On Tue, Feb 02, 2016 at 04:01:14PM +0000, Richard Purdie wrote: > On Tue, 2016-02-02 at 14:49 +0000, Mike Crowe wrote: > > bitbake.conf currently contains: > > > > EXTRA_OEMAKE = "-e MAKEFLAGS=" > > > > Back in November[1] I submitted a patch that allowed this default > > value to be overridden without affecting anything else that was > > appended to it. I received feedback that the default value was no > > longer useful and that it would be good to get rid of it. > > > > So, this patch series fixes the two recipes that still appear to be > > relying on the previous default and then makes the default > > EXTRA_OEMAKE = "". After these changes core-image-sato builds > > successfully for me (although I have not run it.) > > > > Mike. > > > > [1] http://lists.openembedded.org/pipermail/openembedded-core/2015-No > > vember/112393.html > > This is a pretty major change and we likely need a bit more of an idea > of impact. > > Which architectures did you test? Often, x86 is a bad choice here and > we'd need something cross (arm/mips/ppc) to ensure it really is doing > the right things. We also need to assess a bit more than just sato. We > can run this up on the autobuilder and see what happens. > > A post to the architecture list is probably needed so everyone knows > this is happening (or at least being considered). > > I do worry how much of meta-oe may be affected by this. > > Martin: Any opinion on this?
I can give it a shot in next rounds of jenkins builds, but the state is already quite bad, so it will be hard to spot new issues. -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
signature.asc
Description: Digital signature
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
