From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] bitbake.conf: Add comm to HOSTTOOLS
Date: Tue, 30 Jan 2018 16:20:11 +0200 [thread overview]
Message-ID: <32b564ff-9cad-370f-48b1-389bf69e2ffb@linux.intel.com> (raw)
In-Reply-To: <48a79520-c02f-2dfe-b25b-0b89beb182d6@gmail.com>
On 01/30/2018 09:07 AM, Khem Raj wrote:
>> I disagree. Expanding HOSTTOOLS just to cater to the needs of a single
>> recipe is not optimal, IMO.
>
> alternative are
> build time dep on coreutils-native.
> fix uboot script to not use comm
> do not invoke check-config.sh at all.
>
> none of them are any better.
Before we can declare that, we need to look what comm is actually used
for during build, and why its absence is not a problem and doesn't cause
errors.
Consider also that using comm from host may break reproducibility, if
absence or presence of comm on the host results in a different output
from the build.
Alex
next prev parent reply other threads:[~2018-01-30 14:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 17:47 [PATCH] bitbake.conf: Add comm to HOSTTOOLS Niko Mauno
2018-01-29 18:04 ` Manjukumar Harthikote Matha
2018-03-29 22:25 ` Denys Dmytriyenko
2018-03-29 22:55 ` Manjukumar Harthikote Matha
2018-01-30 6:38 ` Alexander Kanavin
2018-01-30 7:07 ` Khem Raj
2018-01-30 14:20 ` Alexander Kanavin [this message]
2018-02-01 11:36 ` Mauno Niko
2018-02-01 14:39 ` Alexander Kanavin
2018-02-01 14:43 ` Burton, Ross
2018-01-30 16:34 ` Manjukumar Harthikote Matha
2018-03-28 14:55 ` Luca Ceresoli
2018-03-28 15:23 ` Burton, Ross
2018-03-28 16:50 ` Luca Ceresoli
2018-03-29 22:29 ` Denys Dmytriyenko
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=32b564ff-9cad-370f-48b1-389bf69e2ffb@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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