From: Juro Bystricky <juro.bystricky@intel.com>
To: openembedded-core@lists.openembedded.org
Cc: jurobystricky@hotmail.com
Subject: [PATCH 0/3] Build Appliance tweaks
Date: Wed, 15 Mar 2017 15:13:35 -0700 [thread overview]
Message-ID: <1489616018-8969-1-git-send-email-juro.bystricky@intel.com> (raw)
The Build Appliance recipe needs several tweaks in order for the BA to build and
to function.
1. Use native pip3: Do not rely on pip3 being installed on host.
This, of course, assumes there is already python-pip3-native support available.
(a previous patch)
2. Remove symlinks before creating them to avid build errors, otherwise we may run
into "File already exists" build errors.
3. Ensure pod2man is present in the BA image, toaster will not run without it.
Even with all these changes, it may not be possible to use BA to build any image, unless
the sanity.bbclass accepts /bin/bash.bash as a viable shell. This has already been addressed
in another patch. The BA then needs to be rebuilt with SRCREV containing the sanity.bbclass patch.
Juro Bystricky (3):
build-appliance-image: use pip3-native
build-appliance-image: fix build errors
build-appliance-image: ensure pod2man present in BA
meta/recipes-core/images/build-appliance-image_15.0.0.bb | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
--
2.7.4
next reply other threads:[~2017-03-15 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 22:13 Juro Bystricky [this message]
2017-03-15 22:13 ` [PATCH 1/3] build-appliance-image: use pip3-native Juro Bystricky
2017-03-15 22:16 ` Richard Purdie
2017-03-15 22:57 ` Bystricky, Juro
2017-03-15 22:13 ` [PATCH 2/3] build-appliance-image: fix build errors Juro Bystricky
2017-03-15 22:13 ` [PATCH 3/3] build-appliance-image: ensure pod2man present in BA Juro Bystricky
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=1489616018-8969-1-git-send-email-juro.bystricky@intel.com \
--to=juro.bystricky@intel.com \
--cc=jurobystricky@hotmail.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