From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Niko Mauno <niko.mauno@vaisala.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] bitbake.conf: Add comm to HOSTTOOLS
Date: Tue, 30 Jan 2018 08:38:16 +0200 [thread overview]
Message-ID: <2afb5638-31ca-39fa-bf28-d305fea507c0@linux.intel.com> (raw)
In-Reply-To: <20180129174724.26768-1-niko.mauno@vaisala.com>
On 01/29/2018 07:47 PM, Niko Mauno wrote:
> This mitigates following issues during u-boot do_compile() step --
> otherwise, if comm is not available, they are quietly ignored:
>
> .../scripts/check-config.sh: line 33: comm: command not found
> .../scripts/check-config.sh: line 39: comm: command not found
>
> Since 'comm' is provided by coreutils package, adding it to HOSTTOOLS
> was considered a lower impact fix compared to adding coreutils-native
> buildtime dependency to u-boot recipe.
I disagree. Expanding HOSTTOOLS just to cater to the needs of a single
recipe is not optimal, IMO.
Alex
next prev parent reply other threads:[~2018-01-30 6:38 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 [this message]
2018-01-30 7:07 ` Khem Raj
2018-01-30 14:20 ` Alexander Kanavin
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=2afb5638-31ca-39fa-bf28-d305fea507c0@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=niko.mauno@vaisala.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