Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: ASSUME_PROVIDED versus SANITY_REQUIRED_UTILITIES versus "The Build Host Packages"
Date: Mon, 28 Nov 2016 06:20:09 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.20.1611280544090.16875@localhost.localdomain> (raw)


  a bit confused by what i'm seeing in a recent
qemuppc/core-image-minimal build on my fedora system regarding which
native packages are built, despite what's in bitbake.conf (using
current poky layer checkout).

  first, here's a snippet from bitbake.conf:

  ASSUME_PROVIDED = "\
    bzip2-native \          <---
    chrpath-native \
    file-native \           <---
    findutils-native \
    git-native \
    grep-native \
    diffstat-native \
    ... snip ...

suggesting that (among other things) bzip2-native and file-native
shouldn't be built -- it's the developer's responsibility to install
them, yes? but if i peek under tmp/work/x86_64-linux, i can see:

  ...
  byacc-native/
  bzip2-native/             <---
  createrepo-native/
  cross-localedef-native/
  cryptodev-linux-native/
  db-native/
  dtc-native/
  e2fsprogs-native/
  elfutils-native/
  expat-native/
  file-native/              <---
  flex-native/
  ...

so that's ... confusing.

  add to that this bit in the YP Quick Start Guide at
http://www.yoctoproject.org/docs/2.1/yocto-project-qs/yocto-project-qs.html:

  "Build Host Packages
  ...
  Fedora

     $ sudo dnf install gawk make wget tar bzip2 gzip python unzip perl patch \
     diffutils diffstat git cpp gcc gcc-c++ glibc-devel texinfo chrpath \
     ccache perl-Data-Dumper perl-Text-ParseWords perl-Thread-Queue perl-bignum socat \
     findutils which SDL-devel xterm

my understanding was that that list represented what the developer was
required to install on his build host *manually* before going any
further, so you can see "bzip2" in that list, but you don't see
"file". given that the "file" command comes in its own package, should
that list of allegedly mandatory Build Host Packages not include
*everything* listed in ASSUME_PROVIDED?

  finally, in sanity.bbclass, one reads:

  SANITY_REQUIRED_UTILITIES ?= "patch diffstat makeinfo git bzip2 tar \
      gzip gawk chrpath wget cpio perl file"

which oddly *does* list the "file" command, but says nothing about
"sed", which *is* mentioned in ASSUME_PROVIDED, but is also not
mentioned in the "Build Host Packages" in the YP Quick Start Guide.

  is it just me, or does some of this seem out of sync?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================




             reply	other threads:[~2016-11-28 11:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-28 11:20 Robert P. J. Day [this message]
2016-11-28 12:04 ` ASSUME_PROVIDED versus SANITY_REQUIRED_UTILITIES versus "The Build Host Packages" Richard Purdie
2016-11-28 13:17   ` Patrick Ohly
2016-11-28 13:45     ` Richard Purdie
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=alpine.LFD.2.20.1611280544090.16875@localhost.localdomain \
    --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