Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mike Crowe <mac@mcrowe.com>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] bitbake.conf, module.bbclass: Support opting out of legacy EXTRA_OEMAKE
Date: Thu, 12 Nov 2015 12:10:48 +0000	[thread overview]
Message-ID: <20151112121048.GA13777@mcrowe.com> (raw)
In-Reply-To: <20151106103004.GA7454@mcrowe.com>

On Friday 06 November 2015 at 10:30:04 +0000, Mike Crowe wrote:
> It would be great to get to the point that EXTRA_OEMAKE is empty by default
> but I imagine that the experts are already aware of the difficulties with
> doing this which is why the current value has lasted so long.

I had a go at this. Fewer recipes than I expected seem to be affected.

With bitbake.conf containing EXTRA_OEMAKE = "", the following recipes
needed to be changed to explicitly set EXTRA_OEMAKE = "-e MAKEFLAGS=":

 meta/recipes-bsp/pciutils/pciutils_3.3.1.bb
 meta/recipes-connectivity/openssl/openssl.inc
 meta/recipes-core/busybox/busybox.inc
 meta/recipes-devtools/perl/perl_5.22.0.bb

for core-image-minimal to build successfully[1].

I tried core-image-sato but got stuck when apr-util-native wouldn't compile
for me[2], even with stock master.

So, perhaps the situation isn't quite as bad as I feared and it might be
possible to change the default value of EXTRA_OEMAKE.

Mike.

[1] I suspect that perl isn't required by core-image-minimal. That list is
    my complete set of changes from trying to get core-image-sato to build.

[2] x86_64-linux-libtool: compile: unable to infer tagged configuration


  parent reply	other threads:[~2015-11-12 12:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05 14:47 [PATCH] bitbake.conf, module.bbclass: Support opting out of legacy EXTRA_OEMAKE Mike Crowe
2015-11-05 16:23 ` Khem Raj
2015-11-05 16:27   ` Christopher Larson
2015-11-05 17:56     ` Khem Raj
2015-11-06  9:16 ` Andre McCurdy
2015-11-06 10:30   ` Mike Crowe
2015-11-06 13:18     ` Martin Jansa
2015-11-06 14:59       ` Christopher Larson
2015-11-06 16:28         ` Martin Jansa
2015-11-12 12:10     ` Mike Crowe [this message]
2015-11-12 20:21       ` Andre McCurdy

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=20151112121048.GA13777@mcrowe.com \
    --to=mac@mcrowe.com \
    --cc=openembedded-core@lists.openembedded.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