From: "rpjday@crashcourse.ca" <rpjday@crashcourse.ca>
To: Adrian Bunk <bunk@stusta.de>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] wanting to clarify variables related to using host tools
Date: Mon, 23 Mar 2020 13:06:37 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.2003231306070.43469@localhost.localdomain> (raw)
In-Reply-To: <20200323170422.GA10964@localhost>
On Mon, 23 Mar 2020, Adrian Bunk wrote:
> On Mon, Mar 23, 2020 at 12:26:04PM -0400, rpjday@crashcourse.ca wrote:
> >...
> > in that case, i notice this line from bitbake.conf regarding
> > ASSUME_PROVIDED:
> >
> > # gzip-native should be listed above?
> >
> > which seems like a reasonable question since both gzip and gunzip are
> > listed in HOSTTOOLS, so why would gzip-native *not* be in
> > ASSUME_PROVIDED?
> >...
>
> meta/conf/distro/include/default-providers.inc:
> PREFERRED_PROVIDER_gzip-native ?= "pigz-native"
ah, thanks, must remember to take that file into account.
rday
prev parent reply other threads:[~2020-03-23 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 16:26 wanting to clarify variables related to using host tools rpjday
2020-03-23 17:04 ` [OE-core] " Adrian Bunk
2020-03-23 17:06 ` rpjday [this message]
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=alpine.LFD.2.21.2003231306070.43469@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=bunk@stusta.de \
--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