Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Olof Johansson <olof.johansson@axis.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-architecture
	<openembedded-architecture@lists.openembedded.org>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 00/15] Prepare for EXTRA_OEMAKE = "" in bitbake.conf
Date: Mon, 8 Feb 2016 13:08:40 +0100	[thread overview]
Message-ID: <20160208120839.GL31212@axis.com> (raw)
In-Reply-To: <CAJTo0LbrD3JrzKM--emSMxDyERK4qstMVsMQ4VXisMpc6AvqqA@mail.gmail.com>

On 16-02-08 11:49 +0000, Burton, Ross wrote:
> On 5 February 2016 at 18:04, Mike Crowe <mac@mcrowe.com> wrote:
> 
> > This series (sent only to openembedded-core) fixes various recipes
> > that rely on the current default value of
> > EXTRA_OEMAKE = "-e MAKEFLAGS=" to explicitly set that value in the
> > hope that bitbake.conf can set EXTRA_OEMAKE = "" in the future.
> >
> 
> We need to also vet all instances of EXTRA_OEMAKE in recipes.  I did a
> build with the EXTRA_OEMAKE change in bitbake.conf and hdparm failed to
> pass QA because the binary was already stripped, as the recipe does
> EXTRA_OEMAKE += "STRIP=echo".  That assignment isn't getting through to the
> makefiles without -e.

It should though, since all -e does is to make the environment
variables take precedence over make assignments. But in case of
assignments in EXTRA_OEMAKE, they are make assignments, so they
shouldn't be affected:

$ cat Makefile
FOO = bar

all:
        echo $(FOO)

.PHONY: all


$ make FOO=qux
echo qux
qux
$ make -e FOO=qux
echo qux
qux
$ FOO=qux make
echo bar
bar
$ FOO=qux make -e
echo qux
qux


-- 
olofjn


  reply	other threads:[~2016-02-08 12:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 18:04 [PATCH 00/15] Prepare for EXTRA_OEMAKE = "" in bitbake.conf Mike Crowe
2016-02-05 18:04 ` [PATCH 01/15] openssl: Explicitly set EXTRA_OEMAKE as required Mike Crowe
2016-02-05 18:04 ` [PATCH 02/15] pciutils: " Mike Crowe
2016-02-05 18:04 ` [PATCH 03/15] perl: " Mike Crowe
2016-02-05 18:04 ` [PATCH 04/15] apmd: " Mike Crowe
2016-02-05 18:04 ` [PATCH 05/15] libacpi: " Mike Crowe
2016-02-05 18:04 ` [PATCH 06/15] dmidecode: " Mike Crowe
2016-02-05 18:04 ` [PATCH 07/15] gptfdisk: " Mike Crowe
2016-02-05 18:04 ` [PATCH 08/15] ed: " Mike Crowe
2016-02-05 18:04 ` [PATCH 09/15] iputils: " Mike Crowe
2016-02-05 18:04 ` [PATCH 10/15] pigz: " Mike Crowe
2016-02-05 18:04 ` [PATCH 11/15] stat: " Mike Crowe
2016-02-05 18:04 ` [PATCH 12/15] sysklogd: " Mike Crowe
2016-02-05 18:04 ` [PATCH 13/15] unzip: " Mike Crowe
2016-02-05 18:04 ` [PATCH 14/15] gtk-theme-torturer: " Mike Crowe
2016-02-05 18:04 ` [PATCH 15/15] ptest-runner: " Mike Crowe
2016-02-08 11:49 ` [PATCH 00/15] Prepare for EXTRA_OEMAKE = "" in bitbake.conf Burton, Ross
2016-02-08 12:08   ` Olof Johansson [this message]
2016-02-08 14:04   ` Mike Crowe

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=20160208120839.GL31212@axis.com \
    --to=olof.johansson@axis.com \
    --cc=openembedded-architecture@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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