All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Mike Crowe <mac@mcrowe.com>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] Remove unhelpful default value of EXTRA_OEMAKE
Date: Tue, 2 Feb 2016 17:17:26 +0100	[thread overview]
Message-ID: <20160202161726.GC2607@jama> (raw)
In-Reply-To: <1454428874.27087.87.camel@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]

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.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2016-02-02 16:14 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 [this message]
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
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=20160202161726.GC2607@jama \
    --to=martin.jansa@gmail.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.