From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: why would ASSUME_PROVIDED recipes be built anyway?
Date: Wed, 8 Apr 2026 09:34:29 -0400 (EDT) [thread overview]
Message-ID: <daa91ca5-ef8c-bb83-7079-3d03ace27a8a@crashcourse.ca> (raw)
puzzled by something i just noticed ... the documentation for
"ASSUME_PROVIDED":"
https://docs.yoctoproject.org/ref-manual/variables.html#term-ASSUME_PROVIDED
clearly suggests that these represent recipes that would not be built
as they are already on the host, the example given there is
"git-native".
however, in a walnascar-based build i just built, native recipes
that were listed in ASSUME_PROVIDED were built anyway, even though
they are clearly on my Debian 13 host, "git-native" among them. in
fact, a number of recipes i checked appear to all have been built from
scratch, despite being listed in ASSUME_PROVIDED.
as a test, if i then tried to "cleanall" such a recipe, i got the
perfectly reasonable:
$ bitbake -c cleanall git-native
... snip ...
WARNING: Explicit target "git-native" is in ASSUME_PROVIDED, ignoring
is there some reason that something listed in ASSUME_PROVIDED will be
fetched and built anyway? is it a version thing?
rday
next reply other threads:[~2026-04-08 13:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 13:34 Robert P. J. Day [this message]
2026-04-08 21:47 ` [OE-core] why would ASSUME_PROVIDED recipes be built anyway? Richard Purdie
2026-04-08 21:53 ` Robert P. J. Day
2026-04-08 21:59 ` Richard Purdie
2026-04-08 22:07 ` Robert P. J. Day
2026-04-09 17:05 ` Robert P. J. Day
2026-04-09 20:13 ` Richard Purdie
2026-04-10 10:51 ` Robert P. J. Day
2026-04-10 13:05 ` Antonin Godard
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=daa91ca5-ef8c-bb83-7079-3d03ace27a8a@crashcourse.ca \
--to=rpjday@crashcourse.ca \
--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