Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>, Mike Crowe <mac@mcrowe.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] Remove unhelpful default value of EXTRA_OEMAKE
Date: Fri, 05 Feb 2016 18:31:34 +0000	[thread overview]
Message-ID: <1454697094.27087.280.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMKF1srahWOS2zu2G6JEXZiwcX9sgqXQ9LOb4z6n0te73H=RDg@mail.gmail.com>

On Fri, 2016-02-05 at 10:22 -0800, Khem Raj wrote:
> On Fri, Feb 5, 2016 at 9:32 AM, Mike Crowe <mac@mcrowe.com> wrote:
> > On Tue, 2016-02-02 at 14:49 +0000, Mike Crowe wrote:
> > On Tue, 2016-02-02 at 21:04 +0000, Mike Crowe wrote:
> > > > I've compile-tested qemux86 and qemuarm for core-image-sato.
> > > > qemumips
> > > > is building now.
> > 
> > Since then I've collected enough patches to make "bitbake world"
> > build
> > successfully for qemux86, qemuarm, qemuppc and qemumips. qemux86-64
> > is
> > building now. The recipes that needed fixing to explicitly set
> > EXTRA_OEMAKE = "-e MAKEFLAGS=" were:
> > 
> >   meta/recipes-bsp/apmd/apmd_3.2.2-15.bb
> >   meta/recipes-bsp/libacpi/libacpi_0.2.bb
> >   meta/recipes-bsp/pciutils/pciutils_3.4.1.bb
> >   meta/recipes-connectivity/openssl/openssl.inc
> >   meta/recipes-devtools/dmidecode/dmidecode_3.0.bb
> >   meta/recipes-devtools/fdisk/gptfdisk_1.0.1.bb
> >   meta/recipes-devtools/perl/perl-native_5.22.1.bb
> >   meta/recipes-devtools/perl/perl_5.22.1.bb
> >   meta/recipes-extended/ed/ed_1.9.bb
> >   meta/recipes-extended/iputils/iputils_s20151218.bb
> >   meta/recipes-extended/pigz/pigz.inc
> >   meta/recipes-extended/stat/stat_3.3.bb
> >   meta/recipes-extended/sysklogd/sysklogd.inc
> >   meta/recipes-extended/unzip/unzip_6.0.bb
> >   meta/recipes-gnome/gtk-theme-torturer/gtk-theme-torturer_git.bb
> >   meta/recipes-support/ptest-runner/ptest-runner_2.0.bb
> > 
> > I will submit patches for these shortly.
> 
> then there are other layers besides OE-Core where this will be
> needed.
> so phase it right so it doesnt cause land slide work for other layers

How do we do that?

Obviously I can merge the above into OE-Core and then there is just the
final bitbake.conf patch. How long do we need to wait for other layers
to sort this out though?

I'm facing this dilemma with a few patches atm...

Cheers,

Richard



  reply	other threads:[~2016-02-05 18:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 14:49 [PATCH 0/3] Remove unhelpful default value of EXTRA_OEMAKE Mike Crowe
2016-02-02 14:49 ` [PATCH 1/3] openssl: Explicitly set EXTRA_OEMAKE as required Mike Crowe
2016-02-02 14:49 ` [PATCH 2/3] pciutils: " Mike Crowe
2016-02-02 14:49 ` [PATCH 3/3] bitbake.conf: Remove unhelpful default value for EXTRA_OEMAKE Mike Crowe
2016-02-16 12:28   ` Richard Purdie
2016-02-02 16:01 ` [PATCH 0/3] Remove unhelpful default value of EXTRA_OEMAKE Richard Purdie
2016-02-02 16:17   ` Martin Jansa
2016-02-06 17:32     ` Martin Jansa
2016-02-06 20:41       ` Mike Crowe
2016-02-07 22:07         ` Mike Crowe
2016-02-08  0:07           ` Martin Jansa
2016-02-09 10:39             ` Martin Jansa
2016-02-09 12:30               ` Mike Crowe
2016-02-09 12:51                 ` Andrea Adami
2016-02-09 15:16                   ` Mike Crowe
2016-02-02 21:04   ` Mike Crowe
2016-02-02 22:41     ` Richard Purdie
2016-02-05 17:32       ` Mike Crowe
2016-02-05 18:22         ` Khem Raj
2016-02-05 18:31           ` Richard Purdie [this message]
2016-02-05 18:35             ` Khem Raj
2016-02-06 17:43             ` Khem Raj
2016-02-05 18:35         ` Martin Jansa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1454697094.27087.280.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=mac@mcrowe.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox