From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patrick Ohly <patrick.ohly@intel.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: ASSUME_PROVIDED versus SANITY_REQUIRED_UTILITIES versus "The Build Host Packages"
Date: Mon, 28 Nov 2016 13:45:42 +0000 [thread overview]
Message-ID: <1480340742.28508.172.camel@linuxfoundation.org> (raw)
In-Reply-To: <1480339031.6873.181.camel@intel.com>
On Mon, 2016-11-28 at 14:17 +0100, Patrick Ohly wrote:
> I recently ran into a third usage of "file-native": swupd-server
> links against libmagic from file and therefore has a DEPENDS =
> "file". But building swupd-server-native didn't actually build file
> because of ASSUME_PROVIDED and because I hadn't installed libmagic-
> dev on my build host, the build was failing.
>
> Is there a way to declare that ASSUME_PROVIDED does not apply to this
> case? It sounds like there is a way (based on your comments about
> building file-native when building file and the libbz2-devel
> example), but it did not become clear to me how that works in
> practice.
If you look at the file recipe, you'll see:
DEPENDS = "zlib file-replacement-native"
> Or is it just a case of educating the developer that libmagic-dev
> needs to be installed on the build host in addition to the file
> command?
No, DEPENDS on file-replacement-native.
Cheers,
Richard
next prev parent reply other threads:[~2016-11-28 13:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 11:20 ASSUME_PROVIDED versus SANITY_REQUIRED_UTILITIES versus "The Build Host Packages" Robert P. J. Day
2016-11-28 12:04 ` Richard Purdie
2016-11-28 13:17 ` Patrick Ohly
2016-11-28 13:45 ` Richard Purdie [this message]
2016-11-28 14:09 ` Burton, Ross
2016-11-29 10:47 ` Robert P. J. Day
2016-11-29 11:31 ` Burton, Ross
2016-11-29 17:24 ` Paul Eggleton
2016-11-29 17:27 ` Burton, Ross
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=1480340742.28508.172.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=patrick.ohly@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