Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] make-mod-scripts: change how some kernel module tools are built
Date: Mon, 19 Feb 2018 23:45:17 +0000	[thread overview]
Message-ID: <1519083917.24236.261.camel@linuxfoundation.org> (raw)
In-Reply-To: <1519054657-4616-2-git-send-email-bruce.ashfield@windriver.com>

On Mon, 2018-02-19 at 10:37 -0500, Bruce Ashfield wrote:
> From: Joe Slater <jslater@windriver.com>
> 
> Remove do_make_scripts() from module-base.bbclass and put
> functionality in a recipe.  This will build the scripts only
> once instead of each time an external module is built.
> 
> [YOCTO #12228]
> 
> Signed-off-by: Joe Slater <jslater@windriver.com>
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> ---
> 
> v2: added the LIC_FILES_CHECKSUM
> 

Sadly this doesn't pass all our tests:

https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/827/steps/Running%20oe-selftest/logs/stdio

oe-selftest -r sstatetests.SStateTests.test_sstate_sametune_samesigs

should reproduce.

I suspect that the recipe may need:

PACKAGE_ARCH = "${MACHINE_ARCH}"

Cheers,

Richard


  reply	other threads:[~2018-02-19 23:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 15:37 [PATCH v2] linux-yocto/4.12: update to v4.12.20 Bruce Ashfield
2018-02-19 15:37 ` [PATCH v2] make-mod-scripts: change how some kernel module tools are built Bruce Ashfield
2018-02-19 23:45   ` Richard Purdie [this message]
2018-02-20  2:13     ` Bruce Ashfield
2018-02-20 15:50     ` Bruce Ashfield
2018-02-20 16:26     ` Bruce Ashfield

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=1519083917.24236.261.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@windriver.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