Re: [PATCH 0/8] Cleanup rootfs creation

["Maxim Yu. Osipov" <mosipov@ilbers.de>]

[-- Attachment #1: Type: text/plain, Size: 5886 bytes --]

Hi,

Tried the series against the current 'next'.

Creation of SDK has been failed (my host is Debian 9) (see log below).

I've double checked - in the current 'next' 'bitbake -c do_populate_sdk 
multiconfig:qemuarm-stretch:isar-image-base' works fine.

My local.conf is attached for convenience.

Maxim.

===============
bitbake -c do_populate_sdk multiconfig:qemuarm-stretch:isar-image-base
Parsing recipes: 100% 
|#######################################################################################################################################################################################################| 
Time: 0:00:02
Parsing of 26 .bb files complete (0 cached, 26 parsed). 390 targets, 0 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
Initialising tasks: 100% 
|####################################################################################################################################################################################################| 
Time: 0:00:03
NOTE: Executing RunQueue Tasks
ERROR: mc:qemuarm-stretch:sdkchroot-${ROOTFS_DISTRO}-amd64-armhf 
do_build: Function failed: do_build (log file is located at 
/home/myo/work/isar/src/trunk/isar/build/tmp/work/debian-stretch-armhf/sdkchroot-${ROOTFS_DISTRO}-amd64-armhf/temp/log.do_build.24544)
ERROR: Logfile of failure stored in: 
/home/myo/work/isar/src/trunk/isar/build/tmp/work/debian-stretch-armhf/sdkchroot-${ROOTFS_DISTRO}-amd64-armhf/temp/log.do_build.24544
Log data follows:
| DEBUG: Executing shell function do_build
| cp: cannot stat 
'/home/myo/work/isar/src/trunk/isar/build/tmp/deploy/bootstrap/debian-stretch-amd64/': 
No such file or directory
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_build (log file is located at 
/home/myo/work/isar/src/trunk/isar/build/tmp/work/debian-stretch-armhf/sdkchroot-${ROOTFS_DISTRO}-amd64-armhf/temp/log.do_build.24544)
ERROR: Task 
(multiconfig:qemuarm-stretch:/home/myo/work/isar/src/trunk/isar/meta/recipes-devtools/sdkchroot/sdkchroot.bb:do_build) 
failed with exit code '1'
ERROR: mc:qemuarm-stretch:buildchroot-host-debian-stretch-amd64-armhf 
do_build: Function failed: do_build (log file is located at 
/home/myo/work/isar/src/trunk/isar/build/tmp/work/debian-stretch-armhf/buildchroot-host-debian-stretch-amd64-armhf/temp/log.do_build.24543)
ERROR: Logfile of failure stored in: 
/home/myo/work/isar/src/trunk/isar/build/tmp/work/debian-stretch-armhf/buildchroot-host-debian-stretch-amd64-armhf/temp/log.do_build.24543
Log data follows:
| DEBUG: Executing shell function do_build
| cp: cannot stat 
'/home/myo/work/isar/src/trunk/isar/build/tmp/deploy/bootstrap/debian-stretch-amd64/': 
No such file or directory
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_build (log file is located at 
/home/myo/work/isar/src/trunk/isar/build/tmp/work/debian-stretch-armhf/buildchroot-host-debian-stretch-amd64-armhf/temp/log.do_build.24543)
ERROR: Task 
(multiconfig:qemuarm-stretch:/home/myo/work/isar/src/trunk/isar/meta/recipes-devtools/buildchroot/buildchroot-host.bb:do_build) 
failed with exit code '1'

=====


On 4/16/19 3:26 PM, claudius.heine.ext@siemens.com wrote:
> From: Claudius Heine <ch@denx.de>
> 
> Hi,
> 
> this patchset contains some patches that where developed while implementing
> the preprocessing image pipeline. They are universally useful, but do prepare
> for the next steps.
> 
> Cheers,
> Claudius
> 
> Claudius Heine (8):
>    isar-boostrap-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/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         | 14 --------------
>   meta/conf/bitbake.conf                             | 13 ++++++++-----
>   .../isar-bootstrap/isar-bootstrap-host.bb          | 11 +++--------
>   .../isar-bootstrap/isar-bootstrap-target.bb        |  6 +-----
>   .../recipes-core/isar-bootstrap/isar-bootstrap.inc |  1 +
>   .../buildchroot/buildchroot-host.bb                |  1 +
>   meta/recipes-devtools/buildchroot/buildchroot.inc  |  3 +--
>   .../buildchroot/files/configscript.sh              |  4 ++--
>   meta/recipes-devtools/sdkchroot/sdkchroot.bb       |  3 +--
>   13 files changed, 30 insertions(+), 41 deletions(-)
> 


-- 
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov

[-- Attachment #2: local.conf --]
[-- Type: text/plain, Size: 7090 bytes --]

#
# This file is your local configuration file and is where all local user settings
# are placed. The comments in this file give some guide to the options a new user
# to the system might want to change but pretty much any configuration option can
# be set in this file. More adventurous users can look at local.conf.extended
# which contains other examples of configuration which can be placed in this file
# but new users likely won't need any of them initially.
#
# Lines starting with the '#' character are commented out and in some cases the
# default values are provided as comments to show people example syntax. Enabling
# the option is a question of removing the # character and making any change to the
# variable as required.

#
# Machine Selection
#
# You need to select a specific machine to target the build with. There are a selection
# of emulated machines available which can boot and run in the QEMU emulator:
#
# This sets the default machine to be qemuarm if no other machine is selected:
MACHINE ??= "qemuarm"

#
# Isar Configuration Selection
#
# You need to select a specific distribution configuration which will used for both:
# generation of buildchroot environment and target root filesystem.
#
# This sets the default distribution configuration:
DISTRO ??= "debian-stretch"
DISTRO_ARCH ??= "armhf"

#
# Multiple Configuration Selection
#
# If you want to use multiple configuration files for the build, list them in the
# following option.
#
# This sets the default multiple configurations used:
BBMULTICONFIG = " \
    qemuarm-stretch \
    qemuarm-buster \
    qemuarm64-stretch \
    qemuarm64-buster \
    qemui386-stretch \
    qemui386-buster \
    qemuamd64-stretch \
    bananapi-stretch \
    de0-nano-soc-stretch \
    hikey-stretch \
    qemuamd64-buster \
    qemuamd64-buster-tgz \
    nand-ubi-demo-buster \
    rpi-stretch \
"

#
# Where to place downloads
#
# During a first build the system will download many different source code tarballs
# from various upstream projects. This can take a while, particularly if your network
# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
# can preserve this directory to speed up this part of subsequent builds. This directory
# is safe to share between multiple builds on the same machine too.
#
# The default is a downloads directory under TOPDIR which is the build directory.
#
#DL_DIR ?= "${TOPDIR}/downloads"

#
# Where to place shared-state files
#
# BitBake has the capability to accelerate builds based on previously built output.
# This is done using "shared state" files which can be thought of as cache objects
# and this option determines where those files are placed.
#
# You can wipe out TMPDIR leaving this directory intact and the build would regenerate
# from these files if no changes were made to the configuration. If changes were made
# to the configuration, only shared state files where the state was still valid would
# be used (done using checksums).
#
# The default is a sstate-cache directory under TOPDIR.
#
#SSTATE_DIR ?= "${TOPDIR}/sstate-cache"

#
# Where to place the build output
#
# This option specifies where the bulk of the building work should be done and
# where BitBake should place its temporary files and output. Keep in mind that
# this includes the extraction and compilation of many applications and the toolchain
# which can use Gigabytes of hard disk space.
#
# The default is a tmp directory under TOPDIR.
#
#TMPDIR = "${TOPDIR}/tmp"

#
# Interactive shell configuration
#
# Under certain circumstances the system may need input from you and to do this it
# can launch an interactive shell. It needs to do this since the build is
# multithreaded and needs to be able to handle the case where more than one parallel
# process may require the user's attention. The default is iterate over the available
# terminal types to find one that works.
#
# Examples of the occasions this may happen are when resolving patches which cannot
# be applied, to use the devshell or the kernel menuconfig
#
# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
# Note: currently, Konsole support only works for KDE 3.x due to the way
# newer Konsole versions behave
#OE_TERMINAL = "auto"
# By default disable interactive patch resolution (tasks will just fail instead):
PATCHRESOLVE = "noop"

#
# Disk Space Monitoring during the build
#
# Monitor the disk space during the build. If there is less that 1GB of space or less
# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
# of the build. The reason for this is that running completely out of space can corrupt
# files and damages the build in ways which may not be easily recoverable.
# It's necesary to monitor /tmp, if there is no space left the build will fail
# with very exotic errors.
BB_DISKMON_DIRS = "\
    STOPTASKS,${TMPDIR},1G,100K \
    STOPTASKS,${DL_DIR},1G,100K \
    STOPTASKS,${SSTATE_DIR},1G,100K \
    STOPTASKS,/tmp,100M,100K \
    ABORT,${TMPDIR},100M,1K \
    ABORT,${DL_DIR},100M,1K \
    ABORT,${SSTATE_DIR},100M,1K \
    ABORT,/tmp,10M,1K"

#
# Shared-state files from other locations
#
# As mentioned above, shared state files are prebuilt cache data objects which can
# used to accelerate build time. This variable can be used to configure the system
# to search other mirror locations for these objects before it builds the data itself.
#
# This can be a filesystem directory, or a remote url such as http or ftp. These
# would contain the sstate-cache results from previous builds (possibly from other
# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
# cache locations to check for the shared objects.
# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
# at the end as shown in the examples below. This will be substituted with the
# correct path within the directory structure.
#SSTATE_MIRRORS ?= "\
#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
#file://.* file:///some/local/dir/sstate/PATH"

# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
# track the version of this file when it was generated. This can safely be ignored if
# this doesn't mean anything to you.
CONF_VERSION = "1"

#
# The default list of extra packages to be installed.
IMAGE_INSTALL = "hello-isar example-raw example-module-${KERNEL_NAME} enable-fsck"

#
# Enable cross-compilation support
# NOTE: this works on build host >= stretch for armhf, arm64 and amd64 targets for now.
ISAR_CROSS_COMPILE ?= "1"

#
# Uncomment this to enable use of cached base repository
#ISAR_USE_CACHED_BASE_REPO ?= "1"

# Set root password to 'root'
# Password was encrypted using following command:
#   mkpasswd -m sha512crypt -R 10000
# mkpasswd is part of the 'whois' package of Debian
CFG_ROOT_PW ?= "$6$rounds=10000$RXeWrnFmkY$DtuS/OmsAS2cCEDo0BF5qQsizIrq6jPgXnwv3PHqREJeKd1sXdHX/ayQtuQWVDHe0KIO0/sVH8dvQm1KthF0d/"