From: Mike Crowe <mac@mcrowe.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] Remove unhelpful default value of EXTRA_OEMAKE
Date: Fri, 5 Feb 2016 17:32:56 +0000 [thread overview]
Message-ID: <20160205173256.GA7728@mcrowe.com> (raw)
In-Reply-To: <1454452885.27087.127.camel@linuxfoundation.org>
On Tue, 2016-02-02 at 14:49 +0000, Mike Crowe wrote:
> > > > [snip] Set EXTRA_OEMAKE = "" in bitbake.conf
On Tuesday 02 February 2016 at 16:01:14 +0000, Richard Purdie wrote:
> > > 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.
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.
> > We've been running with the previous version of the patch with our code
> > for a while but now I look more closely that solution didn't have
> > anywhere near as wide an impact so I'll switch us over to using these
> > patches. That will runtime-test a few real mips and arm targets (and
> > even x86 and x86-64 to a limited extent) but only with our customised
> > set of packages.
On Tuesday 02 February 2016 at 22:41:25 +0000, Richard Purdie wrote:
> Thanks. Please do mention what tests have passed/failed just so I can
> build some idea of the risk of the patch and decide if/as/when the
> right time to merge it is.
I've not yet done any more runtime tests. I hope to get the change into our
tree tonight so everything gets rebuilt with it over the weekend and I can
test next week.
> > > A post to the architecture list is probably needed so everyone knows
> > > this is happening (or at least being considered).
I hope to send such a post later today.
Mike.
next prev parent reply other threads:[~2016-02-05 17:32 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 [this message]
2016-02-05 18:22 ` Khem Raj
2016-02-05 18:31 ` Richard Purdie
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=20160205173256.GA7728@mcrowe.com \
--to=mac@mcrowe.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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