[oe] [PATCH] bitbake.conf: don't append MACHINE_OVERRIDES to OVERRIDES when it's empty

Maupin, Chase chase.maupin at ti.com
Tue Oct 19 19:24:43 UTC 2010


> -----Original Message-----
> From: openembedded-devel-bounces at lists.openembedded.org
> [mailto:openembedded-devel-bounces at lists.openembedded.org] On Behalf Of
> Chris Larson
> Sent: Tuesday, October 19, 2010 2:09 PM
> To: openembedded-devel at lists.openembedded.org
> Subject: Re: [oe] [PATCH] bitbake.conf: don't append MACHINE_OVERRIDES to
> OVERRIDES when it's empty
> 
> On Tue, Oct 19, 2010 at 12:05 PM, Maupin, Chase <chase.maupin at ti.com>
> wrote:
> 
> > > -----Original Message-----
> > > From: openembedded-devel-bounces at lists.openembedded.org
> > > [mailto:openembedded-devel-bounces at lists.openembedded.org] On Behalf
> Of
> > > Martin Jansa
> > > Sent: Saturday, October 16, 2010 2:25 PM
> > > To: openembedded-devel at lists.openembedded.org
> > > Subject: [oe] [PATCH] bitbake.conf: don't append MACHINE_OVERRIDES to
> > > OVERRIDES when it's empty
> > >
> > > * empty MACHINE_OVERRIDES adds :: to OVERRIDES (then in FILESPATH
> skips
> > >   every directory after this)
> > > * strip() is needed to remove space in case some distribution has ie
> > >   MACHINE_OVERRIDES ?= ""
> > >   and then
> > >   MACHINE_OVERRIDES += ""
> > >   or
> > >   MACHINE_OVERRIDES ?= "${MACHINE_CLASS}", where MACHINE_CLASS is
> empty
> > > again
> >
> > I saw this issue in my overlay of having a "::" in my OVERRIDES which
> > caused my parsing to fail in angstrom.inc.  Applying this fix from
> Martin
> > resolves the parsing issue.  My OVERRIDES appear to be in the correct
> order
> > with this change:
> 
> 
> Can you explain this?  "caused my parsing to fail" is not very useful
> information.  What exactly failed?

One other detail I forgot to mention is that I was actually using bitbake from the Arago project which is based on 1.8.18.  I did not see this issue if I used bitbake 1.10 I did not see this issue.  I kept this same fix in my tree and tried with bitbake 1.10 and it too worked so it didn't seem like the fix was negatively impacting the 1.10 version.

> --
> Christopher Larson
> clarson at kergoth dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Maintainer - Tslib
> Senior Software Engineer, Mentor Graphics
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel




More information about the Openembedded-devel mailing list