From: claudius.heine.ext@siemens.com
To: isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: [PATCH v4 0/9] Cleanup rootfs creation
Date: Thu, 25 Apr 2019 15:44:41 +0200 [thread overview]
Message-ID: <20190425134450.13443-1-claudius.heine.ext@siemens.com> (raw)
From: Claudius Heine <ch@denx.de>
Hi,
so after some debugging 'fast' build now succeeds:
http://isar-build.org:8080/job/isar_claudius_ilbers_fast_ci/15/
I needed a patch that removes the DISTRO_APT_KEYS from the isar-bootstrap-host
as well as some fixes to the paths when cross-compiling. Also raspbian only
supports debian-stretch as HOST_DISTRO.
Well the lessons learned from this is that the 'standard' CI build does not
test cross-compiling as I would have assumed and that there is a 'fast' CI
build configuration that tests this.
Also some investigation into why rpi-stretch:isar-bootstrap-host accepted a
keyring with the raspberry pi keys for building a ordinary debian stretch
rootfs at some point needs to happen. There might be a task ordering issue
hidden there.
regards,
Claudius
P.S. The 'standard' CI build for this is still running. I got
'E: Couldn't download packages: libpam0g' while bootstraping, which
sound like a issue that might be fixed by restarting the build. Maybe using
an apt-cacher as proxy might help?
changes from v3:
- added patch for isar-bootstrap-host
- fixed HOST_DISTRO for raspbian-stretch
- fixed cross-compiling paths
changes from v2:
- replaced 'ROOTFS_ARCH' with 'HOST_ARCH' in sdkchroot.bb to avoid
populate_sdk issue
changes from v1:
- fixed typo in commit message
Claudius Heine (9):
isar-bootstrap-host: disable DISTRO_APT_KEYS usage
isar-bootstrap-helper: move 'HOST_ARCH' and 'HOST_DISTRO' to
base.bbclass
move 'HOST_DISTRO_APT_SOURCES' from bootstrap-helper to isar-bootstrap
buildchroot.bbclass: only cross build if HOST_ARCH != DISTRO_ARCH
isar-bootstrap/buildchroot/sdkchroot: refactor PF and WORKDIR
bitbake.conf: remove unneeded and differently used variables
image.bbclass: make IMAGE_ROOTFS overwritable
bitbake.conf: set default QEMU_ARCH variables
buildchroot/configscript: make creation of builder uid/gid idempotent
meta-isar/conf/multiconfig/rpi-stretch.conf | 1 +
meta/classes/base.bbclass | 9 +++++++++
meta/classes/buildchroot.bbclass | 2 +-
meta/classes/image-sdk-extension.bbclass | 2 +-
meta/classes/image.bbclass | 2 +-
meta/classes/isar-bootstrap-helper.bbclass | 18 ++----------------
meta/conf/bitbake.conf | 13 ++++++++-----
.../isar-bootstrap/isar-bootstrap-host.bb | 13 +++++--------
.../isar-bootstrap/isar-bootstrap-target.bb | 6 +-----
.../isar-bootstrap/isar-bootstrap.inc | 1 +
.../buildchroot/buildchroot-host.bb | 4 ++--
.../buildchroot/buildchroot.inc | 3 +--
.../buildchroot/files/configscript.sh | 4 ++--
meta/recipes-devtools/sdkchroot/sdkchroot.bb | 5 ++---
14 files changed, 37 insertions(+), 46 deletions(-)
--
2.20.1
next reply other threads:[~2019-04-25 13:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 13:44 claudius.heine.ext [this message]
2019-04-25 13:44 ` [PATCH v4 1/9] isar-bootstrap-host: disable DISTRO_APT_KEYS usage claudius.heine.ext
2019-04-25 18:20 ` Maxim Yu. Osipov
2019-04-26 7:36 ` Claudius Heine
2019-04-26 8:41 ` Maxim Yu. Osipov
2019-04-26 10:39 ` Claudius Heine
2019-04-26 10:45 ` Claudius Heine
2019-04-26 11:22 ` Maxim Yu. Osipov
2019-04-26 11:47 ` Jan Kiszka
2019-04-30 9:34 ` Andreas Reichel
2019-04-30 13:30 ` Maxim Yu. Osipov
2019-04-30 15:22 ` Andreas Reichel
2019-04-30 15:30 ` Jan Kiszka
2019-04-30 15:46 ` Maxim Yu. Osipov
2019-05-02 12:14 ` Andreas Reichel
2019-04-26 11:31 ` Jan Kiszka
2019-04-26 11:50 ` Jan Kiszka
2019-05-14 9:22 ` Fwd: " Maxim Yu. Osipov
2019-05-14 11:32 ` Claudius Heine
2019-05-14 11:35 ` Claudius Heine
2019-04-25 13:44 ` [PATCH v4 2/9] isar-bootstrap-helper: move 'HOST_ARCH' and 'HOST_DISTRO' to base.bbclass claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 3/9] move 'HOST_DISTRO_APT_SOURCES' from bootstrap-helper to isar-bootstrap claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 4/9] buildchroot.bbclass: only cross build if HOST_ARCH != DISTRO_ARCH claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 5/9] isar-bootstrap/buildchroot/sdkchroot: refactor PF and WORKDIR claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 6/9] bitbake.conf: remove unneeded and differently used variables claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 7/9] image.bbclass: make IMAGE_ROOTFS overwritable claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 8/9] bitbake.conf: set default QEMU_ARCH variables claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 9/9] buildchroot/configscript: make creation of builder uid/gid idempotent claudius.heine.ext
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=20190425134450.13443-1-claudius.heine.ext@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=ch@denx.de \
--cc=isar-users@googlegroups.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