Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>,
	Khem Raj <raj.khem@gmail.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	Bruce Ashfield <bruce.ashfield@windriver.com>
Subject: Re: [PATCH 1/2] conf/bitbake.conf: include ed in hosttools
Date: Fri, 19 May 2017 14:01:17 +0100	[thread overview]
Message-ID: <1495198877.27342.150.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJTo0LZmtYMT2Z2N19J85dXi5JnOfPxXBMX=rwEuwcaq1GeiAg@mail.gmail.com>

On Fri, 2017-05-19 at 12:56 +0100, Burton, Ross wrote:
> 
> On 19 May 2017 at 10:02, Anders Darander <anders@chargestorm.se>
> wrote:
> > As fas as I can (in a recent kernel), whoami is only used in
> > scripts/mkcompile_h. And there, it's only used if
> > $KBUILD_BUILD_USER is
> > empty. I'd rather see that we set $KBUILD_BUILD_USER to something
> > deterministic in our kernel.bbclass.
> > 
> Definitely this.

Agreed, I've mentioned this would be preferred already. I'm just living
in hope someone sends a patch!

-- 
RP


  reply	other threads:[~2017-05-19 13:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18 22:28 [PATCH 0/2] bc: upgrade 1.06 to 1.07.1 Jose Lamego
2017-05-18 22:28 ` [PATCH 1/2] conf/bitbake.conf: include ed in hosttools Jose Lamego
2017-05-18 23:12   ` Richard Purdie
2017-05-18 23:16     ` Khem Raj
2017-05-19  9:02       ` Anders Darander
2017-05-19 11:56         ` Burton, Ross
2017-05-19 13:01           ` Richard Purdie [this message]
2017-05-19 12:54         ` Jose Lamego
2017-05-19 15:47           ` Burton, Ross
2017-05-18 22:28 ` [PATCH 2/2] bc: upgrade 1.06 to 1.07.1 Jose Lamego
2017-05-19 15:25   ` Burton, Ross
2017-05-19 19:17     ` Jose Lamego
2017-07-20 21:24       ` Jose Lamego

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=1495198877.27342.150.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --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