Date   

[meta-mingw] [PATCH] libgcrypt: drop 1.8.x append and patch

Alexander Kanavin
 

1.9.x no longer requires this, as the code has been
refactored into an external script that has defaults
and a guard for .git directory.

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
---
...-mym4_revision-to-0-if-not-a-git-rep.patch | 46 -------------------
.../libgcrypt/libgcrypt_1.8.%.bbappend | 6 ---
2 files changed, 52 deletions(-)
delete mode 100644 recipes-support/libgcrypt/files/configure.ac-Set-mym4_revision-to-0-if-not-a-git-rep.patch
delete mode 100644 recipes-support/libgcrypt/libgcrypt_1.8.%.bbappend

diff --git a/recipes-support/libgcrypt/files/configure.ac-Set-mym4_revision-to-0-if-not-a-git-rep.patch b/recipes-support/libgcrypt/files/configure.ac-Set-mym4_revision-to-0-if-not-a-git-rep.patch
deleted file mode 100644
index b7b407a..0000000
--- a/recipes-support/libgcrypt/files/configure.ac-Set-mym4_revision-to-0-if-not-a-git-rep.patch
+++ /dev/null
@@ -1,46 +0,0 @@
-From bb6f9e18b5ccef26978f3f3ed2fe7bf3d4d498e7 Mon Sep 17 00:00:00 2001
-From: Nathan Rossi <nathan@nathanrossi.com>
-Date: Fri, 30 Dec 2016 18:02:26 +1000
-Subject: [PATCH] configure.ac: Set 'mym4_revision' to 0 if not a git repo
-
----
-It is possible for the source to not be located in a git repository
-(e.g. source is from a tarball). In which case the git repository
-information is not available. This results in the mym4_revision being an
-empty string however this value is used in BUILD_FILEVERSION where it is
-assumed to be 4 decimal values. Additionally BUILD_REVISION uses this
-value and is also assumed to be non-empty.
-
-In the case of BUILD_FILEVERSION it is used in versioninfo.rc.in, where
-it must be populated as 4 decimal values due to the expected syntax. In
-cases where it is not (e.g. when BUILD_FILEVERSION = '1,7,5,' a syntax
-error is raised.
-
- windres: versioninfo.rc.in:21: syntax error
-
-This patch changes mym4_revision so that if the 'git rev-parse' returns
-non-zero (e.g. not in a git repository) the value falls back to '0'.
-This propagates as '0' to both BUILD_FILEVERSION and BUILD_REVISION.
-
-Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
-Upstream-Status: Submitted
----
- configure.ac | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/configure.ac b/configure.ac
-index 31c0d553fa..a3deffa6e9 100644
---- a/configure.ac
-+++ b/configure.ac
-@@ -39,7 +39,7 @@ m4_define(mym4_version_micro, [0])
- m4_define(mym4_version,
- [mym4_version_major.mym4_version_minor.mym4_version_micro])
- m4_define([mym4_revision],
-- m4_esyscmd([git rev-parse --short HEAD | tr -d '\n\r']))
-+ m4_esyscmd([(git rev-parse --short HEAD || printf '0') | tr -d '\n\r']))
- m4_define([mym4_revision_dec],
- m4_esyscmd_s([echo $((0x$(echo ]mym4_revision[|head -c 4)))]))
- m4_define([mym4_betastring],
---
-2.11.0
-
diff --git a/recipes-support/libgcrypt/libgcrypt_1.8.%.bbappend b/recipes-support/libgcrypt/libgcrypt_1.8.%.bbappend
deleted file mode 100644
index 3da0f53..0000000
--- a/recipes-support/libgcrypt/libgcrypt_1.8.%.bbappend
+++ /dev/null
@@ -1,6 +0,0 @@
-
-FILESEXTRAPATHS_prepend_mingw32 := "${THISDIR}/files:"
-SRC_URI_append_mingw32 = " \
- file://configure.ac-Set-mym4_revision-to-0-if-not-a-git-rep.patch \
- "
-
--
2.29.2


Re: Dunfell, nodejs and typescript - short experience report

Simon Vogl
 

Sure, please find the bbclass file attached to this mail. All it does is to inherit npm and overwrite configure with an extended copy .

Meanwhile, I saw another issue popping up: It seems that multiple indirect dependencies to a package with different versions create inconsitent license checksum entries. In my case, several packages depend on 'xtend' in versions 4.0.0 to 4.0.2, the license file picked is package.json which contains the version, of course, and causes conflicts. Oh my.

Simon



Am 24.02.21 um 12:02 schrieb TRO:

Hi Simon,
I'm dealing actually with the same problem. Would you like to share your  "configure in my own subclass"?

I'm also thinking there is a need for a bbclass which actually is not using gyp, instead it should be able to "npm run build".

There is alsa a patch for speeding up npm npmsw fetcher https://www.mail-archive.com/openembedded-core@.../msg142406.html
cheers Thomas




-- 
VoXel Interaction Design  |  www.voxel.at
DI Dr.techn. Simon Vogl   |  simon@...
Tomaschekweg 46           |  +43 650 2323 555
A-4040 Linz - Austria     |
Office address: Industriezeile 35, 4020 Linz (2nd floor)


How to set static route in yocto for rpi

@prashant2314
 

Dear Team,

I'm using yocto-dunfell poky for my CM3(Raspberrypi) OS.

In this I want to set static route for wan port. So how I can do the same.

I've tried several method from Internet for setting static route in linux, not succeeded. 
Please help me with this to solve this.

Thanks and Regards.


[ANNOUNCEMENT] Yocto Project 3.1.6 (Dunfell 23.0.6) is Released

Vineela
 

Hello,

We are pleased to announce the Yocto Project 3.1.6 (dunfell-23.0.6) Release is now available for download.

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.6/poky-dunfell-23.0.6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.6/poky-dunfell-23.0.6.tar.bz2

A gpg signed version of these release notes is available at:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.6/RELEASENOTES

Full Test Report:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.6/testreport.txt

Thank you for everyone's contributions to this release.

Sincerely,

Vineela Tummalapalli
Yocto Project Build and Release
vineela.tummalapalli@intel.com


--------------------------
yocto-3.1.6 Release Notes
--------------------------


--------------------------
Repositories/Downloads
--------------------------

Repository Name: poky
Repository Location: https://git.yoctoproject.org/git/poky
Branch: dunfell
Tag: yocto-3.1.6
Git Revision: a13bda44fcda4e79e9aed39ca1495eabecb6a7b7
Release Artefact: poky-dunfell-23.0.6
sha: a2480100f6326df25f301e461ace52dad23b77e9ff9e6f0197cb7243703c61c6
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.6/poky-dunfell-23.0.6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.6/poky-dunfell-23.0.6.tar.bz2

Repository Name: openembedded-core
Repository Location: https://git.openembedded.org/openembedded-core
Branch: dunfell
Tag: 2020-04.6-dunfell
Git Revision: a8debddd6cbdd70db74e096d72f97fbee008ee63
Release Artefact: oecore-dunfell-23.0.6
sha: 4fc63ad2e738181c2de0106d5c039021aa3b9b7e0ab539e5c3d2f116bfe9ae16
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.6/oecore-dunfell-23.0.6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.6/oecore-dunfell-23.0.6.tar.bz2

Repository Name: meta-mingw
Repository Location: https://git.yoctoproject.org/git/meta-mingw
Branch: dunfell
Tag: yocto-3.1.6
Git Revision: 524de686205b5d6736661d4532f5f98fee8589b7
Release Artefact: meta-mingw-dunfell-23.0.6
sha: edc0c0310eb6d58d8991af07bbd6725686d07c40d9dabd66d7c4c36f5cb9554d
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.6/meta-mingw-dunfell-23.0.6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.6/meta-mingw-dunfell-23.0.6.tar.bz2

Repository Name: meta-gplv2
Repository Location: https://git.yoctoproject.org/git/meta-gplv2
Branch: dunfell
Tag: yocto-3.1.6
Git Revision: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
Release Artefact: meta-gplv2-dunfell-23.0.6
sha: d322dd47bbf193d4f03348b24b4b0737f36d69aea9be3ba556c0d7f3617df3fb
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.6/meta-gplv2-dunfell-23.0.6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.6/meta-gplv2-dunfell-23.0.6.tar.bz2

Repository Name: bitbake
Repository Location: https://git.openembedded.org/bitbake
Branch: dunfell
Tag: 2020-04.6-dunfell
Git Revision: fa94374baea75a94e3a488126ca7d8e241a77acd
Release Artefact: bitbake-dunfell-23.0.6
sha: 03154eaaf28173de561c274b118452182787a410a1fdcc827eadd9247f57921b
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.6/bitbake-dunfell-23.0.6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.6/bitbake-dunfell-23.0.6.tar.bz2

Repository Name: yocto-docs
Repository Location: https://git.yoctoproject.org/git/yocto-docs
Branch: dunfell
Tag: yocto-3.1.6
Git Revision: 660684b1a1ece4bdedfd63b9fc65d14f05c226d5

--------------
Contributors
-------------
Adrian Herrera
Alexander Kanavin
Anatol Belski
Andrey Mozzhuhin
Armin Kuster
Awais Belal
Bruce Ashfield
Chris Laplante
Dorinda
Jack Mitchell
Joe Slater
Jon Mason
Joshua Watt
Julien Massot
Khem Raj
Lee Chee Yang
Mans Rullgard
Marek Vasut
Mark Hatle
Martin Jansa
Matt Hoosier
Mauro Queirós
Michael Halstead
Michael Ho
Mikko Rapeli
Mingli Yu
Oleksiy Obitotskyy
Oleksiy Obitotskyy yIEf0zt.mo
Ovidiu Panait
Paul Barker
Peter Bergin
Peter Kjellerstedt
Ricardo Ribalda
Ricardo Ribalda Delgado
Richard Purdie
Robert Joslyn
Ross Burton
saloni
Sangeeta Jain
Scott Murray
Sourabh Banerjee
Stephen Jolley
Steve Sakoman
Thomas Perrot
Tomasz Dziendzielski
Vyacheslav Yurkov
Wang Mingyu
Yi Fan Yu
Yi Zhao
zangrc
zhengruoqin

---------------
Known Issues
---------------
N/A


---------------
Security Fixes
---------------
libcroco: Added CVE
libgcrypt: Whitelisted CVEs
glib-2.0: Rename patch file for CVE-2020-35457
openssl: set CVE_VERSION_SUFFIX
cve_check: add CVE_VERSION_SUFFIX to indicate suffix in versioning
ppp: Whitelist CVE-2020-15704
zip: whitelist CVE-2018-13410 and CVE-2018-13684
glibc: CVE-2019-25013
glibc: Security fix for CVE-2020-29573
xorg: Security fix for CVE-2020-14345
curl: fix CVE-2020-8231/8284/8285/8286


---------------
Fixes
---------------
build-appliance-image: Update to dunfell head revision
python3targetconfig.bbclass: Make py3 dep and tasks only for target recipes
gpgme: use python3targetconfig
meta: drop _PYTHON_SYSCONFIGDATA_NAME hacks
distutils3-base.bbclass: use python3targetconfig
python3-pycairo: use python3targetconfig
python3: split python target configuration into own class
gcc-9.3.inc: Fix potential runtime crash
p11-kit: upgrade 0.23.21 -> 0.23.22
p11-kit: upgrade 0.23.20 -> 0.23.21
oe-pkgdata-util: Check if environment script is initialized
opkg: Fix patch glitches
opkg: Fix build reproducibility issue
image_types.bbclass: tar: use posix format instead of gnu
image_types: Ensure tar archives are reproducible
uninative: Upgrade to 2.10
bitbake: lib/bb/fetch2/__init__.py: drop _PYTHON_SYSCONFIGDATA_NAME unsetting
poky.conf: Bump version for 3.1.6 release
documentation: prepare for 3.1.6 release
wic/selftest: test_permissions also test bitbake image
oeqa: wic: Add tests for permissions and change-directory
classes/image_types_wic: Reorder do_flush_pseudodb
rng-tools: fix rngd_jitter initialization
sstatesig: Add descriptive error message to getpwuid/getgrgid "uid/gid not found" KeyError
lib/oe/patch.py: Ignore scissors line on applying patch
layer.conf: fix sanity error for PATH variable in extensible SDK workflow
qemu.inc: Should depend on qemu-system-native, not qemu-native
python3: Use addtask statement instead of task dependencies
npm.bbclass: use python3 for npm config
buildhistory.bbclass: avoid exception for empty BUILDHISTORY_FEATURES variable
linux-yocto/5.4: update to v5.4.94
linux-yocto-rt/5.4: fix 5.4-stable caused build breakage
linux-yocto/5.4: update to v5.4.90
kernel.bbclass: fix deployment for initramfs images
package: Ensure do_packagedata is cleaned correctly
package.bbclass: hash equivalency and pr service
cve-check: replace Looseversion with custom version class
ca-certificates: upgrade 20200601 -> 20210119
ca-certificates: correct upstream version check
ca-certificates: upgrade 20190110 -> 20200601
sanity.bbclass: Check if PSEUDO_IGNORE_PATHS and paths under pseudo control overlap
pseudo: Update to include passwd and file renaming fixes
staging: Clean up files installed into the sysroot
python3: Avoid installing test data into recipe-sysroot
ncurses: Don't put terminfo into the sysroot
externalsrc: Detect code changes in submodules
strace: increase ptest timeout duration 120->240s
timezone: upgrade to 2021a
selftest/devtool: Add modify_localfiles_only test checking symlink path
ovmf-shell-image: image is only buildable on x86-64
core-image-sato-sdk-ptest: these images need ptest
dtc: improve reproducibility
devtool: Fix file:// fetcher symlink directory structure
oeqa/selftest/cases/tinfoil.py: increase timeout 10->60s test_wait_event
externalsrc: Fix parsing error with devtool non-git sources
devtool: Fix source extraction for gcc shared source
toolchain-shar-relocate.sh: Fix handling files with colons
flex: Fix --noline option behavior
flex: Refresh patch
flex: fix build with autoconf 2.70
oeqa/ptest: print a warning if ptests failed
sanity.bbclass: sanity check for if bitbake is present in PATH
sanity: Verify that user isn't building in PSEUDO_IGNORE_PATHS
bitbake: fetch/git: download LFS content too during do_fetch
bitbake: git.py: Use the correct branch to check if the repository has LFS objects.
bitbake: git.py: LFS bitbake note should not be printed if need_lfs is not set.
bitbake: git.py: skip smudging if lfs=0 is set
wic: Optimise fstab modification for ext2/3/4 and msdos partitions
wic: Copy rootfs dir if fstab needs updating
wic: Add --change-directory argument
wic: Update pseudo db when excluding content from rootfs
image_types_wic: Move wic working directory
wic: Ensure internal workdir is not reused
wic: Allow exec_native_cmd to run HOSTTOOLS
wic: Add workdir argument
pseudo: Update for arm host and memleak fixes/cleanup
pseudo: Add lchmod wrapper
bitbake.conf: Add /run/ to PSEUDO_IGNORE_PATHS
license.bbclass: Add COMMON_LICENSE_DIR and LICENSE_PATH dirs to PSEUDO_IGNORE_PATHS
bitbake.conf: Prevent pyc file generation in pseudo context
wic: Pass canonicalized paths in PSEUDO_IGNORE_PATHS
bitbake.conf: Canonicalize paths in PSEUDO_IGNORE_PATHS
lib/oe/path: Add canonicalize()
pseudo: Drop patches merged into upstream branch
distutils3: allow setup.py to be run from a different directory to ${S}
pseudo: Update to print PSEUDO_LOGFILE in abort message on path mismatches
pseudo: Simplify pseudo_client_ignore_path_chroot()
uninative: Don't use single sstate for pseudo-native
bitbake.conf: Exclude ${CCACHE_DIR} from pseudo database
tcl: adapt to potential pseudo changes
oeqa/selftest/runtime_test: Exclude gpg directory from pseudo database
base.bbclass: use os.path.normpath instead of just comparing WORKDIR and S as strings
pseudo: Upgrade to include mkostemp64 wrapper
pseudo: Update to account for patches merged on branch
abi_version,sanity: Tell users TMPDIR must be clean after pseudo changes
bitbake.conf: Extend PSEUDO_IGNORE_PATHS to ${COREBASE}/meta
pseudo: Fix statx function usage
wic: Handle new PSEUDO_IGNORE_PATHS variable
wic: Avoid creating invalid pseudo directory
wic: Fix multi images .wks with bitbake
wic: Fix permissions when using exclude or include path
base/bitbake.conf: Enable pseudo path filtering
pseudo: Add pathfix patch
pseudo: Add may unlink patch
pseudo: Fix xattr segfault
psuedo: Add tracking of linked files for fds
pseudo: Abort on mismatch patch
pseudo: Add support for ignoring paths from the pseudo DB
pseudo: Ignore mismatched inodes from the db
pseudo: fix renaming to self
pseudo: Update to add OFC fcntl lock updates
pseudo: merge in fixes for setfacl issue
pseudo: Switch to oe-core branch in git repo
linuxloader: Avoid confusing string concat errors
bitbake: data_smart: Ensure hash reflects vardepvalue flags correctly
waf: don't assume the waf intepretter is good
classes/waf: Add build and install arguments
boost: drop arm-intrinsics.patch
lib/oe/utils: Return empty string in parallel_make
toolchain-shar-extract.sh: Handle special characters in script path
scripts: oe-run-native, fix *-native directories
linux-yocto/5.4: update to v5.4.87
license_image.bbclass: fix missing recipeinfo on self
systemd.bbclass: improve error message when a service unit specified in SYSTEMD_SERVICE is not found
meta: toolchain-shar-relocate.sh: Filter out post-relocate-setup script
meta: toolchain-shar-relocate.sh: Do not use $target_sdk_dir as regex
go.bbclass: don't stage test data with sources of dependencies


Re: Error during do_image_wic

Darcy Watkins
 

Hi,

 

In follow-up to my previous email, it appears that this error in do_image_wic is triggered by something that the meta-security/meta-integrity layer does.

 

 

 

Regards,

 

Darcy

 

Darcy Watkins ::  Senior Staff Engineer, Firmware

 

SIERRA WIRELESS

Direct  +1 604 233 7989   ::  Fax  +1 604 231 1109  ::  Main  +1 604 231 1100

13811 Wireless Way  :: Richmond, BC Canada V6V 3A4

[M4]

dwatkins@... :: www.sierrawireless.com

 

From: <yocto@...> on behalf of "Darcy Watkins via lists.yoctoproject.org" <dwatkins=sierrawireless.com@...>
Reply-To: Darcy Watkins <dwatkins@...>
Date: Tuesday, February 9, 2021 at 10:51 AM
To: "yocto@..." <yocto@...>
Subject: [yocto] Error during do_image_wic

 

Hi,

 

I have a puzzling error during do_image_wic.  It says a ‘1’ is returned as an error rather than 0, but I don’t see in the output what went wrong.  Anyone recognize it?  (I am not that familiar with the inner workings of the wic image generation tool).

 

This used to work but broke during a fresh build from scratch.

 

 

 

 

dwatkins@carmd-ed-n11377:64bit build $ bitbake core-image-selinux-minimal

Loading cache: 100% |#####################################################################################################################################################################################| Time: 0:00:00

Loaded 3633 entries from dependency cache.

WARNING: No recipes available for:

  /home/dwatkins/workspace/zeta/skylab_mg90-BSP/meta-MG-os-bsp/recipes-kernel/firmware/linux-firmware_git.bbappend

  /home/dwatkins/workspace/zeta/skylab_mg90-BSP/meta-MG-os-bsp/recipes-kernel/linux/linux-qoriq_4.19.bbappend

  /home/dwatkins/workspace/zeta/skylab_mg90-BSP/meta-MG-os-bsp/recipes-kernel/linux/linux-yocto_3.4.bbappend

NOTE: Resolving any missing task queue dependencies

 

Build Configuration:

BB_VERSION           = "1.46.0"

BUILD_SYS            = "x86_64-linux"

NATIVELSBSTRING      = "universal"

TARGET_SYS           = "arm-poky-linux-gnueabi"

MACHINE              = "mg90"

DISTRO               = "poky"

DISTRO_VERSION       = "3.1.5"

TUNE_FEATURES        = "arm vfp cortexa7 neon callconvention-hard"

TARGET_FPU           = "hard"

meta-MG-os-bsp       = "master:db03c4adb9ffe9bd0135538ebe399821036eeeee"

meta                 

meta-poky            

meta-yocto-bsp       = "HEAD:6e89d668246fb37b2217aae7ae57390e793696d8"

meta-oe              

meta-networking      

meta-python          

meta-perl            = "HEAD:de37512b25c1f8c6bb6ab2b3782ac0fe01443483"

meta-selinux         = "HEAD:7af62c91d7d00a260cf28e7908955539304d100d"

meta-security        

meta-integrity       

meta-security-isafw  = "HEAD:c74cc97641fd93e0e7a4383255e9a0ab3deaf9d7"

meta-freescale       = "HEAD:99bd73bec2a9d84509cb012a08f9062cb65fb24e"

 

Initialising tasks: 100% |################################################################################################################################################################################| Time: 0:00:03

Sstate summary: Wanted 2 Found 0 Missed 2 Current 1870 (0% match, 99% complete)

NOTE: Executing Tasks

WARNING: cve-update-db-native-1.0-r0 do_populate_cve_db: Failed to fetch CVE data ([SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1108))

Image CVE report stored in: /home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/deploy/images/mg90/core-image-selinux-minimal-mg90-20210209182741.rootfs.cve

ERROR: core-image-selinux-minimal-1.0-r0 do_image_wic: Execution of '/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/temp/run.do_image_wic.14994' failed with exit code 1:

INFO: Creating image(s)...

 

ERROR: _exec_cmd: export PATH=/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/recipe-sysroot-native/sbin:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/recipe-sysroot-native/usr/sbin:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/recipe-sysroot-native/usr/bin:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/recipe-sysroot-native/bin:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/hosttools:$PATH;export PSEUDO_PREFIX=/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/sysroots-components/x86_64/pseudo-native/usr;export PSEUDO_LOCALSTATEDIR=/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/rootfs/../pseudo;export PSEUDO_PASSWD=/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/rootfs;export PSEUDO_NOSYMLINKEXP=1;export PSEUDO_IGNORE_PATHS=/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/tmp-wic/rootfs_root.3.ext4,/usr/,/etc/,/usr/lib,/dev/,/run/,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/temp,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/recipe-sysroot,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/sstate-cache,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/stamps,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/pkgdata-sysroot,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/sstate-control,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/deploy,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/deploy-,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/buildstats,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/sstate-build-package_,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/sstate-install-package_,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/sstate-build-image_complete,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/sysroots-components,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/pkgdata,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/cache,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/scripts,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/files/common-licenses,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/openembedded/meta-openembedded/meta-oe/licenses,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/openembedded/meta-openembedded/meta-networking/licenses,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/openembedded/meta-openembedded/meta-python/licenses,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/meta-freescale/custom-licenses,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/x86_64-deploy-core-image-selinux-minimal-populate-sdk,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/build-wic,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/core-image-selinux-minimal-1.0,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/core-image-selinux-minimal-1.0;/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/sysroots-components/x86_64/pseudo-native/usr/bin/pseudo fsck.ext4 -pvfD /home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/tmp-wic/rootfs_root.3.ext4 returned '1' instead of 0

output: 5913 inodes used (20.62%, out of 28672)

           9 non-contiguous files (0.2%)

          20 non-contiguous directories (0.3%)

             # of inodes with ind/dind/tind blocks: 0/0/0

             Extent depth histogram: 5376/9

      140547 blocks used (61.28%, out of 229344)

           0 bad blocks

           0 large files

 

        4749 regular files

         635 directories

           0 character device files

           0 block device files

           0 fifos

           8 links

         520 symbolic links (520 fast symbolic links)

           0 sockets

------------

        5912 files

 

WARNING: /home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/temp/run.do_image_wic.14994:1 exit 1 from 'BUILDDIR="/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build" PSEUDO_UNLOAD=1 wic create "$wks" --vars "/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/sysroots/mg90/imgdata/" -e "core-image-selinux-minimal" -o "$build_wic/" -w "$tmp_wic"'

 

ERROR: Logfile of failure stored in: /home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/temp/log.do_image_wic.14994

Log data follows:

| DEBUG: Executing python function set_image_size

| DEBUG: 176420.400000 = 135708 * 1.300000

| DEBUG: 176420.400000 = max(176420.400000, 65536)[176420.400000] + 0

| DEBUG: 176421.000000 = int(176420.400000)

| DEBUG: 176421 = aligned(176421)

| DEBUG: returning 176421

| DEBUG: Python function set_image_size finished

| DEBUG: Executing python function extend_recipe_sysroot

| NOTE: Direct dependencies are ['/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/meta-freescale/recipes-bsp/qe-ucode/qe-ucode_git.bb:do_populate_sysroot', '/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-kernel/kmod/kmod-native_git.bb:do_populate_sysroot', '/home/dwatkins/workspace/zeta/skylab_mg90-BSP/meta-MG-os-bsp/recipes-bsp/omg-hardware/omg-hardware_4.1.bb:do_populate_sysroot', '/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-kernel/kmod/depmodwrapper-cross_1.0.bb:do_populate_sysroot', '/home/dwatkins/workspace/zeta/skylab_mg90-BSP/meta-MG-os-bsp/recipes-support/fec/fec_3.0.1.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/openembedded/meta-openembedded/meta-python/recipes-devtools/python/python3-lxml_4.5.0.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/mtools/mtools_4.0.23.bb:do_populate_sysroot', '/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/gcc/libgcc_9.3.bb:do_populate_sysroot', '/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-core/glibc/glibc_2.31.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/meta-security/meta-integrity/recipes-security/ima-evm-utils/ima-evm-utils_git.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/opkg-utils/opkg-utils_0.4.2.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-bsp/u-boot/u-boot-tools_2020.01.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-connectivity/openssl/openssl_1.1.1i.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/makedevs/makedevs_1.0.1.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-extended/parted/parted_3.3.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/meta-MG-os-bsp/recipes-devtools/change-file-endianess/change-file-endianess.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/patch/patch_2.7.6.bb:do_populate_sysroot', '/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/mklibs/mklibs-native_0.1.44.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-core/update-rc.d/update-rc.d_0.8.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/prelink/prelink_git.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/tcltk/tcl_8.6.10.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/meta-selinux/recipes-security/selinux/policycoreutils_3.0.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/bison/bison_3.5.4.bb:do_populate_sysroot', '/home/dwatkins/workspace/zeta/skylab_mg90-BSP/meta-MG-os-bsp/recipes-bsp/u-boot/u-boot-qoriq_2019.04.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb:do_populate_sysroot', '/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/quilt/quilt-native_0.66.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-extended/pigz/pigz_2.4.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-support/libyaml/libyaml_0.2.2.bb:do_populate_sysroot', '/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/meta-freescale/recipes-kernel/linux/linux-fslc-qoriq_5.4.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/meta-security/meta-security-isafw/recipes-devtools/checksec/checksec_1.5-1.bb:do_populate_sysroot', '/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/qemu/qemuwrapper-cross_1.0.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/fdisk/gptfdisk_1.0.4.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.45.4.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-extended/bc/bc_1.07.1.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/rpm/rpm_4.14.2.1.bb:do_populate_sysroot', '/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/binutils/binutils-cross_2.34.bb:do_populate_sysroot', '/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/gcc/gcc-runtime_9.3.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/dosfstools/dosfstools_4.1.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/createrepo-c/createrepo-c_0.15.7.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/openembedded/meta-openembedded/meta-python/recipes-devtools/python/python3-pyyaml_5.3.1.bb:do_populate_sysroot', '/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-core/glibc/ldconfig-native_2.12.1.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/dnf/dnf_4.2.2.bb:do_populate_sysroot', '/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-core/glibc/cross-localedef-native_2.31.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/opkg/opkg_0.4.2.bb:do_populate_sysroot', '/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/gcc/gcc-cross_9.3.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/swig/swig_3.0.12.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-support/lzop/lzop_1.04.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-kernel/dtc/dtc_1.6.0.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-support/ca-certificates/ca-certificates_20190110.bb:do_populate_sysroot', 'virtual:native:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/recipes-devtools/python/python3_3.8.2.bb:do_populate_sysroot']

| NOTE: Installed into sysroot: []

| NOTE: Skipping as already exists in sysroot: ['qe-ucode', 'kmod-native', 'omg-hardware', 'depmodwrapper-cross', 'fec', 'python3-lxml-native', 'pseudo-native', 'mtools-native', 'libgcc', 'glibc', 'ima-evm-utils-native', 'opkg-utils-native', 'u-boot-tools-native', 'openssl-native', 'makedevs-native', 'parted-native', 'change-file-endianess-native', 'patch-native', 'mklibs-native', 'update-rc.d-native', 'prelink-native', 'tcl-native', 'policycoreutils-native', 'bison-native', 'u-boot-qoriq', 'bmap-tools-native', 'quilt-native', 'pigz-native', 'libyaml-native', 'linux-fslc-qoriq', 'checksec-native', 'qemuwrapper-cross', 'gptfdisk-native', 'e2fsprogs-native', 'bc-native', 'rpm-native', 'binutils-cross-arm', 'gcc-runtime', 'dosfstools-native', 'createrepo-c-native', 'python3-pyyaml-native', 'ldconfig-native', 'dnf-native', 'cross-localedef-native', 'opkg-native', 'gcc-cross-arm', 'swig-native', 'lzop-native', 'dtc-native', 'ca-certificates-native', 'python3-native', 'omg-mcu', 'libxml2-native', 'libxslt-native', 'python3-setuptools-native', 'autoconf-native', 'texinfo-dummy-native', 'automake-native', 'gnu-config-native', 'libtool-native', 'linux-libc-headers', 'keyutils-native', 'pkgconfig-native', 'ncurses-native', 'util-linux-native', 'gettext-minimal-native', 'readline-native', 'xz-native', 'qemu-native', 'binutils-native', 'elfutils-native', 'zlib-native', 'popt-native', 'attr-native', 'db-native', 'perl-native', 'dbus-native', 'bzip2-native', 'file-native', 'libarchive-native', 'shadow-native', 'ninja-native', 'cmake-native', 'curl-native', 'expat-native', 'glib-2.0-native', 'sqlite3-native', 'python3-cython-native', 'libsolv-native', 'libpcre-native', 'libffi-native', 'gdbm-native', 'libtirpc-native', 'libnsl2-native', 'gtk-doc-native', 'flex-native', 'shared-mime-info-native', 'libsepol-native', 'libcap-native', 'gettext-native', 'libsemanage-native', 'libselinux-native', 'python3-six-native', 'debianutils-native', 'libcomps-native', 'libdnf-native', 'librepo-native', 'python3-iniparse-native', 'mpfr-native', 'gmp-native', 'libmpc-native', 'lzo-native', 'unzip-native', 'm4-native', 'libcap-ng-native', 'libpcre2-native', 're2c-native', 'meson-native', 'itstool-native', 'gperf-native', 'libcheck-native', 'libmodulemd-v1-native', 'json-c-native', 'gobject-introspection-native', 'gpgme-native', 'libassuan-native', 'libgpg-error-native']

| DEBUG: Python function extend_recipe_sysroot finished

| DEBUG: Executing shell function do_image_wic

| INFO: Creating image(s)...

| 

| ERROR: _exec_cmd: export PATH=/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/recipe-sysroot-native/sbin:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/recipe-sysroot-native/usr/sbin:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/recipe-sysroot-native/usr/bin:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/recipe-sysroot-native/bin:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/hosttools:$PATH;export PSEUDO_PREFIX=/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/sysroots-components/x86_64/pseudo-native/usr;export PSEUDO_LOCALSTATEDIR=/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/rootfs/../pseudo;export PSEUDO_PASSWD=/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/rootfs;export PSEUDO_NOSYMLINKEXP=1;export PSEUDO_IGNORE_PATHS=/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/tmp-wic/rootfs_root.3.ext4,/usr/,/etc/,/usr/lib,/dev/,/run/,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/temp,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/recipe-sysroot,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/sstate-cache,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/stamps,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/pkgdata-sysroot,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/sstate-control,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/deploy,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/deploy-,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/buildstats,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/sstate-build-package_,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/sstate-install-package_,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/sstate-build-image_complete,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/sysroots-components,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/pkgdata,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/cache,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/scripts,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/files/common-licenses,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/openembedded/meta-openembedded/meta-oe/licenses,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/openembedded/meta-openembedded/meta-networking/licenses,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/openembedded/meta-openembedded/meta-python/licenses,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/meta-freescale/custom-licenses,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/x86_64-deploy-core-image-selinux-minimal-populate-sdk,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/build-wic,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/core-image-selinux-minimal-1.0,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/core-image-selinux-minimal-1.0;/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/sysroots-components/x86_64/pseudo-native/usr/bin/pseudo fsck.ext4 -pvfD /home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/tmp-wic/rootfs_root.3.ext4 returned '1' instead of 0

| output: 5913 inodes used (20.62%, out of 28672)

|            9 non-contiguous files (0.2%)

|           20 non-contiguous directories (0.3%)

|              # of inodes with ind/dind/tind blocks: 0/0/0

|              Extent depth histogram: 5376/9

|       140547 blocks used (61.28%, out of 229344)

|            0 bad blocks

|            0 large files

| 

|         4749 regular files

|          635 directories

|            0 character device files

|            0 block device files

|            0 fifos

|            8 links

|          520 symbolic links (520 fast symbolic links)

|            0 sockets

| ------------

|         5912 files

| 

| WARNING: /home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/temp/run.do_image_wic.14994:1 exit 1 from 'BUILDDIR="/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build" PSEUDO_UNLOAD=1 wic create "$wks" --vars "/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/sysroots/mg90/imgdata/" -e "core-image-selinux-minimal" -o "$build_wic/" -w "$tmp_wic"'

| ERROR: Execution of '/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/temp/run.do_image_wic.14994' failed with exit code 1:

| INFO: Creating image(s)...

| 

| ERROR: _exec_cmd: export PATH=/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/recipe-sysroot-native/sbin:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/recipe-sysroot-native/usr/sbin:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/recipe-sysroot-native/usr/bin:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/recipe-sysroot-native/bin:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/hosttools:$PATH;export PSEUDO_PREFIX=/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/sysroots-components/x86_64/pseudo-native/usr;export PSEUDO_LOCALSTATEDIR=/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/rootfs/../pseudo;export PSEUDO_PASSWD=/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/rootfs;export PSEUDO_NOSYMLINKEXP=1;export PSEUDO_IGNORE_PATHS=/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/tmp-wic/rootfs_root.3.ext4,/usr/,/etc/,/usr/lib,/dev/,/run/,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/temp,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/recipe-sysroot,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/sstate-cache,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/stamps,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/pkgdata-sysroot,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/sstate-control,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/deploy,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/deploy-,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/buildstats,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/sstate-build-package_,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/sstate-install-package_,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/sstate-build-image_complete,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/sysroots-components,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/pkgdata,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/cache,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/scripts,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/poky/meta/files/common-licenses,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/openembedded/meta-openembedded/meta-oe/licenses,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/openembedded/meta-openembedded/meta-networking/licenses,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/openembedded/meta-openembedded/meta-python/licenses,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/meta-freescale/custom-licenses,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/x86_64-deploy-core-image-selinux-minimal-populate-sdk,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/build-wic,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/core-image-selinux-minimal-1.0,/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/core-image-selinux-minimal-1.0;/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/sysroots-components/x86_64/pseudo-native/usr/bin/pseudo fsck.ext4 -pvfD /home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/tmp-wic/rootfs_root.3.ext4 returned '1' instead of 0

| output: 5913 inodes used (20.62%, out of 28672)

|            9 non-contiguous files (0.2%)

|           20 non-contiguous directories (0.3%)

|              # of inodes with ind/dind/tind blocks: 0/0/0

|              Extent depth histogram: 5376/9

|       140547 blocks used (61.28%, out of 229344)

|            0 bad blocks

|            0 large files

| 

|         4749 regular files

|          635 directories

|            0 character device files

|            0 block device files

|            0 fifos

|            8 links

|          520 symbolic links (520 fast symbolic links)

|            0 sockets

| ------------

|         5912 files

| 

| WARNING: /home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/temp/run.do_image_wic.14994:1 exit 1 from 'BUILDDIR="/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build" PSEUDO_UNLOAD=1 wic create "$wks" --vars "/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/sysroots/mg90/imgdata/" -e "core-image-selinux-minimal" -o "$build_wic/" -w "$tmp_wic"'

| 

ERROR: Task (/home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/meta-selinux/recipes-security/images/core-image-selinux-minimal.bb:do_image_wic) failed with exit code '1'

NOTE: Tasks Summary: Attempted 5360 tasks of which 4439 didn't need to be rerun and 1 failed.

 

Summary: 1 task failed:

  /home/dwatkins/workspace/zeta/skylab_mg90-BSP/upstream/yocto/meta-selinux/recipes-security/images/core-image-selinux-minimal.bb:do_image_wic

Summary: There were 2 WARNING messages shown.

Summary: There was 1 ERROR message shown, returning a non-zero exit code.

dwatkins@carmd-ed-n11377:64bit build $

 

Here is my layer stackup…

 

dwatkins@carmd-ed-n11377:64bit build $ cat conf/bblayers.conf 

# Generated by 'setup-environment' from annotations in the repo manifest.

WS_DIR = "/home/dwatkins/workspace/zeta/skylab_mg90-BSP"

BBPATH = "${TOPDIR}"

BBFILES ?= ""

 

LCONF_VERSION = "7"

BSPDIR = "${WS_DIR}"

 

BBLAYERS = " \

    ${WS_DIR}/meta-MG-os-bsp \

    ${WS_DIR}/upstream/yocto/poky/meta \

    ${WS_DIR}/upstream/yocto/poky/meta-poky \

    ${WS_DIR}/upstream/yocto/poky/meta-yocto-bsp \

    ${WS_DIR}/upstream/openembedded/meta-openembedded/meta-oe \

    ${WS_DIR}/upstream/openembedded/meta-openembedded/meta-networking \

    ${WS_DIR}/upstream/openembedded/meta-openembedded/meta-python \

    ${WS_DIR}/upstream/openembedded/meta-openembedded/meta-perl \

    ${WS_DIR}/upstream/yocto/meta-selinux \

    ${WS_DIR}/upstream/yocto/meta-security \

    ${WS_DIR}/upstream/yocto/meta-security/meta-integrity \

    ${WS_DIR}/upstream/yocto/meta-security/meta-security-isafw \

    ${WS_DIR}/upstream/yocto/meta-freescale \

"

dwatkins@carmd-ed-n11377:64bit build

 

 

dwatkins@carmd-ed-n11377:64bit build $ cat ../meta-MG-os-bsp/wic/ls1-uboot-spl-mg90pbl-bootpart.wks 

# short-description: Create SD card image with a boot partition

# long-description:

# Create an image that can be written onto a SD card using dd for use

# with Layerscape ls102xa SoC family.

#

# The disk layout used is:

#  ----- ------------ ------------- ---------------

# | MBR | bootloader | boot (FAT)  | rootfs (ext)  |

#  ----- ------------ ------------- ---------------

# ^     ^            ^             ^               ^

# |     |            |             |               |

# 0     4kB          4MB           16MB            16MiB + rootfs size + IMAGE_EXTRA_SPACE (default 10MiB)

#

# Note: u-boot.bin referenced below is assumed symlinked to u-boot-${MACHINE}.${UBOOT_SUFFIX_SDCARD} or

#       equivalent as used by the legacy image_types_ls1.bbclass prior to migration to using 'wic'.

part bootloader --source rawcopy --sourceparams="file=u-boot.bin" --ondisk mmcblk0 --no-table --align 4

part /boot --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --active --align 4096 --size 16

part / --source rootfs --ondisk mmcblk0 --fstype=ext4 --label root --align 4096

 

bootloader --ptable msdos

dwatkins@carmd-ed-n11377:64bit build

 

 

The wic image for SD card follows similar style pattern as has been used by Freescale Community BSP for the i.MX6 family, etc. and has previously worked and the SD card booted.

 

 

Regards,

 

Darcy

 

Darcy Watkins ::  Senior Staff Engineer, Firmware

 

SIERRA WIRELESS

Direct  +1 604 233 7989   ::  Fax  +1 604 231 1109  ::  Main  +1 604 231 1100

13811 Wireless Way  :: Richmond, BC Canada V6V 3A4

[M4]

dwatkins@... :: www.sierrawireless.com


Package bash-completion was not found - dunfell

Darcy Watkins
 

Hi,

 

I observe something unusual in dunfell.  After the setting up environment for build, if I invoke ‘bash’ I see the following:

 

Package bash-completion was not found in the pkg-config search path.

Perhaps you should add the directory containing `bash-completion.pc'

to the PKG_CONFIG_PATH environment variable

No package 'bash-completion' found

bash: /yum: No such file or directory

 

Is this normal?  (I am using CentOS7 as build machine OS and have the extra packages, buildtools installed, etc).

 

I have determined that this is not prior to setting up the environment, but will occur if using bash any time afterwards.

 

Is Yocto’s setup environment perhaps being overaggressive with sanitizing the paths, etc?

 

 

--

 

Regards,

 

Darcy

 

Equipping worship teams and worshipers

http://xstreamworship.com

[M4]

 


Re: [licensing] [yocto] Package names in IMAGE_MANIFEST and PACKAGES

Jérôme Carretero
 

On Fri, 26 Feb 2021 15:21:10 +0000
"Mikko Rapeli" <mikko.rapeli@bmw.de> wrote:

FWIW, the mapping from binary package names recipes and recipe metadata like
LICENSE is available from buildhistory. Also binary package content of images
is available from buildhistory.
Definitely more powerful than just image manifest + packages.

With some scripting it is possible to list
recipes which produce binaries to images, except for static linking and
header-only recipes but I hope these cought via some other way.
Yeah, that "except" part is something that should be accounted for.

The thing is, I don't see how recipes make any difference between a
build-time dependency such as a build tool, or a statically linked
library, so that some additional information should be input somewhere;
failing to provide that, since I don't feel like finding static library
symbols in binaries to perform a discovery, I just tell my clients to
distribute everything except their proprietary bits...

--
Jérôme


Re: Package names in IMAGE_MANIFEST and PACKAGES

Richard Purdie
 

On Fri, 2021-02-26 at 14:18 +0000, Mikko Murto wrote:
Hello,

I'm developing a meta layer to save details about an image created by Yocto to an 
SPDX document ( https://github.com/doubleopen-project/meta-doubleopen).

I've encountered two issues regarding package names in IMAGE_MANIFEST 
and PACKAGES variables,  

https://github.com/doubleopen-project/meta-doubleopen/issues/2 and
https://github.com/doubleopen-project/meta-doubleopen/issues/3.

The crux of the matter is that I need to find packages created by recipes 
and to link the packages listed in image's manifest files to these packages.

First, the PACKAGES variable of all recipes doesn't seem to include all 
packages created. For example util-linux's PACKAGES doesn't include 
util-linux-sulogin, but util-linux-sulogin may be included in an image's 
manifest and it has a directory in the packages-split directory of util-linux. 
What would be the correct way to get information about all packages?

Second, the package names in the image manifest may differ from those in 
the PACKAGES variable or in packages-split directory. As an example, a
manifest file may include libkmod2, but recipe for kmod creates package 
named libkmod. How to make the link from libkmod2 to libkmod?
I'd suggesting looking at packagedata which is how do_package and friends 
internally looks up things like which recipe provides which package and 
what the final package name is.

An example of this in action is scripts/oe-pkgdata-util.

There is also meta/lib/oe/packagedata.py. Sadly the API is horrible, it
was never really designed for "public" use but I would love to see a better
API around that (maybe one oe-pkgdata-util could use too).

Cheers,

Richard


Re: [licensing] [yocto] Package names in IMAGE_MANIFEST and PACKAGES

Mikko Rapeli
 

Hi,

On Fri, Feb 26, 2021 at 10:08:47AM -0500, Jérôme Carretero wrote:
On Fri, 26 Feb 2021 14:18:59 +0000
"Mikko Murto" <mikko.murto@hhpartners.fi> wrote:

The crux of the matter is that I need to find packages created by recipes and to link the packages listed in image's manifest files to these packages.
The way I've been doing it, which is probably not optimal and specific
to one package format, is to lookup .ipk packages from the image
manifest, then use the .ipk control info "OE" key to find the
originating recipe.
FWIW, the mapping from binary package names recipes and recipe metadata like
LICENSE is available from buildhistory. Also binary package content of images
is available from buildhistory. With some scripting it is possible to list
recipes which produce binaries to images, except for static linking and
header-only recipes but I hope these cought via some other way.

Cheers,

-Mikko


Re: Package names in IMAGE_MANIFEST and PACKAGES

Jérôme Carretero
 

Hi Mikko,


On Fri, 26 Feb 2021 14:18:59 +0000
"Mikko Murto" <mikko.murto@hhpartners.fi> wrote:

The crux of the matter is that I need to find packages created by recipes and to link the packages listed in image's manifest files to these packages.
The way I've been doing it, which is probably not optimal and specific
to one package format, is to lookup .ipk packages from the image
manifest, then use the .ipk control info "OE" key to find the
originating recipe.

Here's a link of this method in use in order to try and identify
license-related obligations from an image:
https://gitlab.com/exmakhina/xm_oe/-/blob/47183b74/licenses.py#L24


Hoping to help,

--
Jérôme


Re: [PATCH] lib/oeqa/selftest/cases/reproducible.py : updated test to faketime in future when buiding the second test build.

Alexander Kanavin
 

Wait, this needs to be explained a bit better. What reproducibility issues does this address that the existing test does not?

Alex


On Fri, 26 Feb 2021 at 15:27, Sangeeta Jain <sangeeta.jain@...> wrote:

This update will ensure that recipes are not including time stamps by creating an image with modified system

 time. It uses libfaketime recipe to fake system time to advance by 34308122 seconds.

Signed-off-by: sangeeta jain <sangeeta.jain@...>
---
 meta/lib/oeqa/selftest/cases/reproducible.py | 19 ++++++++++++++++---
 1 file changed, 16 insertions(+), 3 deletions(-)

diff --git a/meta/lib/oeqa/selftest/cases/reproducible.py b/meta/lib/oeqa/selftest/cases/reproducible.py
index 8849c95..831a304 100644
--- a/meta/lib/oeqa/selftest/cases/reproducible.py
+++ b/meta/lib/oeqa/selftest/cases/reproducible.py
@@ -180,6 +180,7 @@ class ReproducibleTests(OESelftestTestCase):
     # will test that and also make the test run faster. If your sstate is not
     # reproducible, disable this in your derived test class
     build_from_sstate = True
+    use_faketime = False

     def setUpLocal(self):
         super().setUpLocal()
@@ -227,7 +228,7 @@ class ReproducibleTests(OESelftestTestCase):
         bb.utils.mkdirhier(os.path.dirname(dest))
         shutil.copyfile(source, dest)

-    def do_test_build(self, name, use_sstate):
+    def do_test_build(self, name, use_sstate, use_faketime):
         capture_vars = ['DEPLOY_DIR_' + c.upper() for c in self.package_classes]

         tmpdir = os.path.join(self.topdir, name, 'tmp') @@ -256,6 +257,18 @@ class ReproducibleTests(OESelftestTestCase):
                 SSTATE_MIRRORS = ""
                 ''')

+        if use_faketime:  ##sangeeta
+            # This config fragment will enable to fake system time
+            # advance by 34308122 sec
+            bitbake("libfaketime")
+            find_binary = "find . -path '*/image/*/libfaketime.so.1"
+            full_path_to_binary = runCmd(find_binary)
+            binary_path = full_path_to_binary.split("./")
+            ld_preload_path = os.path.join(os.environ.get('BUILDDIR'), binary_path[1])
+            seconds_add_to_system_time = "+34308122"
+            cmd = 'LD_PRELOAD=%s FAKETIME=%s' %(ld_preload_path, seconds_add_to_system_time)
+            runCmd(cmd)
+
         self.logger.info("Building %s (sstate%s allowed)..." % (name, '' if use_sstate else ' NOT'))
         self.write_config(config)
         d = get_bb_vars(capture_vars)
@@ -282,9 +295,9 @@ class ReproducibleTests(OESelftestTestCase):
             os.chmod(save_dir, stat.S_IRWXU | stat.S_IRGRP | stat.S_IXGRP | stat.S_IROTH | stat.S_IXOTH)
             self.logger.info('Non-reproducible packages will be copied to %s', save_dir)

-        vars_A = self.do_test_build('reproducibleA', self.build_from_sstate)
+        vars_A = self.do_test_build('reproducibleA',
+ self.build_from_sstate, self.use_faketime))

-        vars_B = self.do_test_build('reproducibleB', False)
+        vars_B = self.do_test_build('reproducibleB', False, True)

         # NOTE: The temp directories from the reproducible build are purposely
         # kept after the build so it can be diffed for debugging.
--
2.7.4





[PATCH] lib/oeqa/selftest/cases/reproducible.py : updated test to faketime in future when buiding the second test build.

Sangeeta Jain
 

This update will ensure that recipes are not including time stamps by creating an image with modified system

time. It uses libfaketime recipe to fake system time to advance by 34308122 seconds.

Signed-off-by: sangeeta jain <sangeeta.jain@intel.com>
---
meta/lib/oeqa/selftest/cases/reproducible.py | 19 ++++++++++++++++---
1 file changed, 16 insertions(+), 3 deletions(-)

diff --git a/meta/lib/oeqa/selftest/cases/reproducible.py b/meta/lib/oeqa/selftest/cases/reproducible.py
index 8849c95..831a304 100644
--- a/meta/lib/oeqa/selftest/cases/reproducible.py
+++ b/meta/lib/oeqa/selftest/cases/reproducible.py
@@ -180,6 +180,7 @@ class ReproducibleTests(OESelftestTestCase):
# will test that and also make the test run faster. If your sstate is not
# reproducible, disable this in your derived test class
build_from_sstate = True
+ use_faketime = False

def setUpLocal(self):
super().setUpLocal()
@@ -227,7 +228,7 @@ class ReproducibleTests(OESelftestTestCase):
bb.utils.mkdirhier(os.path.dirname(dest))
shutil.copyfile(source, dest)

- def do_test_build(self, name, use_sstate):
+ def do_test_build(self, name, use_sstate, use_faketime):
capture_vars = ['DEPLOY_DIR_' + c.upper() for c in self.package_classes]

tmpdir = os.path.join(self.topdir, name, 'tmp') @@ -256,6 +257,18 @@ class ReproducibleTests(OESelftestTestCase):
SSTATE_MIRRORS = ""
''')

+ if use_faketime: ##sangeeta
+ # This config fragment will enable to fake system time
+ # advance by 34308122 sec
+ bitbake("libfaketime")
+ find_binary = "find . -path '*/image/*/libfaketime.so.1"
+ full_path_to_binary = runCmd(find_binary)
+ binary_path = full_path_to_binary.split("./")
+ ld_preload_path = os.path.join(os.environ.get('BUILDDIR'), binary_path[1])
+ seconds_add_to_system_time = "+34308122"
+ cmd = 'LD_PRELOAD=%s FAKETIME=%s' %(ld_preload_path, seconds_add_to_system_time)
+ runCmd(cmd)
+
self.logger.info("Building %s (sstate%s allowed)..." % (name, '' if use_sstate else ' NOT'))
self.write_config(config)
d = get_bb_vars(capture_vars)
@@ -282,9 +295,9 @@ class ReproducibleTests(OESelftestTestCase):
os.chmod(save_dir, stat.S_IRWXU | stat.S_IRGRP | stat.S_IXGRP | stat.S_IROTH | stat.S_IXOTH)
self.logger.info('Non-reproducible packages will be copied to %s', save_dir)

- vars_A = self.do_test_build('reproducibleA', self.build_from_sstate)
+ vars_A = self.do_test_build('reproducibleA',
+ self.build_from_sstate, self.use_faketime))

- vars_B = self.do_test_build('reproducibleB', False)
+ vars_B = self.do_test_build('reproducibleB', False, True)

# NOTE: The temp directories from the reproducible build are purposely
# kept after the build so it can be diffed for debugging.
--
2.7.4


Package names in IMAGE_MANIFEST and PACKAGES

Mikko Murto
 

Hello,

I'm developing a meta layer to save details about an image created by Yocto to an SPDX document (https://github.com/doubleopen-project/meta-doubleopen).

I've encountered two issues regarding package names in IMAGE_MANIFEST and PACKAGES variables, https://github.com/doubleopen-project/meta-doubleopen/issues/2 and https://github.com/doubleopen-project/meta-doubleopen/issues/3.

The crux of the matter is that I need to find packages created by recipes and to link the packages listed in image's manifest files to these packages.

First, the PACKAGES variable of all recipes doesn't seem to include all packages created. For example util-linux's PACKAGES doesn't include util-linux-sulogin, but util-linux-sulogin may be included in an image's manifest and it has a directory in the packages-split directory of util-linux. What would be the correct way to get information about all packages?

Second, the package names in the image manifest may differ from those in the PACKAGES variable or in packages-split directory. As an example, a manifest file may include libkmod2, but recipe for kmod creates package named libkmod. How to make the link from libkmod2 to libkmod?

Best regards,

Mikko Murto
Associate

HH Partners, Attorneys-at-law Ltd
Eteläesplanadi 22 a, 00130 Helsinki, Finland
P.O. Box 232, 00101 Helsinki, Finland
Tel: +358 9 177 613, Fax: +358 9 653 873
mikko.murto@hhpartners.fi
www.hhpartners.fi

HH Partners shines in international rankings. See details at hhpartners.fi.

Privileged and confidential information may be contained in this message. If you are not the addressee indicated in this message (or responsible for the delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, kindly notify us by reply e-mail and delete this message immediately. Thank you.


[meta-selinux][PATCH] openssh: don't overwrite sshd_config unconditionally

Purushottam choudhary
 

The current implementation was overwriting the sshd_config and sshd
assuming PAM is needed by default.

openssh should use the default sshd_config packaged with the component
if no distro specific needs are present and not overwrite the full
sshd_config file.

1. If PAM is enabled as a distro then enable the UsePAM option in sshd_config.
2. Moved the file sshd to pam directory so that when pam is enabled,
then replace the default from poky by installing the same.

Signed-off-by: Purushottam Choudhary <purushottam.choudhary@kpit.com>
---
recipes-connectivity/openssh/files/{ => pam}/sshd | 0
recipes-connectivity/openssh/files/sshd_config | 118 ----------------------
recipes-connectivity/openssh/openssh_%.bbappend | 14 +++
3 files changed, 14 insertions(+), 118 deletions(-)
rename recipes-connectivity/openssh/files/{ => pam}/sshd (100%)
delete mode 100644 recipes-connectivity/openssh/files/sshd_config

diff --git a/recipes-connectivity/openssh/files/sshd b/recipes-connectivity/openssh/files/pam/sshd
similarity index 100%
rename from recipes-connectivity/openssh/files/sshd
rename to recipes-connectivity/openssh/files/pam/sshd
diff --git a/recipes-connectivity/openssh/files/sshd_config b/recipes-connectivity/openssh/files/sshd_config
deleted file mode 100644
index 1c33ad0..0000000
--- a/recipes-connectivity/openssh/files/sshd_config
+++ /dev/null
@@ -1,118 +0,0 @@
-# $OpenBSD: sshd_config,v 1.102 2018/02/16 02:32:40 djm Exp $
-
-# This is the sshd server system-wide configuration file. See
-# sshd_config(5) for more information.
-
-# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin
-
-# The strategy used for options in the default sshd_config shipped with
-# OpenSSH is to specify options with their default value where
-# possible, but leave them commented. Uncommented options override the
-# default value.
-
-#Port 22
-#AddressFamily any
-#ListenAddress 0.0.0.0
-#ListenAddress ::
-
-#HostKey /etc/ssh/ssh_host_rsa_key
-#HostKey /etc/ssh/ssh_host_ecdsa_key
-#HostKey /etc/ssh/ssh_host_ed25519_key
-
-# Ciphers and keying
-#RekeyLimit default none
-
-# Logging
-#SyslogFacility AUTH
-#LogLevel INFO
-
-# Authentication:
-
-#LoginGraceTime 2m
-#PermitRootLogin prohibit-password
-#StrictModes yes
-#MaxAuthTries 6
-#MaxSessions 10
-
-#PubkeyAuthentication yes
-
-# The default is to check both .ssh/authorized_keys and .ssh/authorized_keys2
-# but this is overridden so installations will only check .ssh/authorized_keys
-#AuthorizedKeysFile .ssh/authorized_keys
-
-#AuthorizedPrincipalsFile none
-
-#AuthorizedKeysCommand none
-#AuthorizedKeysCommandUser nobody
-
-# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
-#HostbasedAuthentication no
-# Change to yes if you don't trust ~/.ssh/known_hosts for
-# HostbasedAuthentication
-#IgnoreUserKnownHosts no
-# Don't read the user's ~/.rhosts and ~/.shosts files
-#IgnoreRhosts yes
-
-# To disable tunneled clear text passwords, change to no here!
-#PasswordAuthentication yes
-#PermitEmptyPasswords no
-
-# Change to yes to enable challenge-response passwords (beware issues with
-# some PAM modules and threads)
-ChallengeResponseAuthentication no
-
-# Kerberos options
-#KerberosAuthentication no
-#KerberosOrLocalPasswd yes
-#KerberosTicketCleanup yes
-#KerberosGetAFSToken no
-
-# GSSAPI options
-#GSSAPIAuthentication no
-#GSSAPICleanupCredentials yes
-
-# Set this to 'yes' to enable PAM authentication, account processing,
-# and session processing. If this is enabled, PAM authentication will
-# be allowed through the ChallengeResponseAuthentication and
-# PasswordAuthentication. Depending on your PAM configuration,
-# PAM authentication via ChallengeResponseAuthentication may bypass
-# the setting of "PermitRootLogin without-password".
-# If you just want the PAM account and session checks to run without
-# PAM authentication, then enable this but set PasswordAuthentication
-# and ChallengeResponseAuthentication to 'no'.
-UsePAM yes
-
-#AllowAgentForwarding yes
-#AllowTcpForwarding yes
-#GatewayPorts no
-#X11Forwarding no
-#X11DisplayOffset 10
-#X11UseLocalhost yes
-#PermitTTY yes
-#PrintMotd yes
-#PrintLastLog yes
-#TCPKeepAlive yes
-#UseLogin no
-#PermitUserEnvironment no
-Compression no
-ClientAliveInterval 15
-ClientAliveCountMax 4
-#UseDNS no
-#PidFile /var/run/sshd.pid
-#MaxStartups 10:30:100
-#PermitTunnel no
-#ChrootDirectory none
-#VersionAddendum none
-
-# no default banner path
-#Banner none
-
-# override default of no subsystems
-Subsystem sftp /usr/libexec/sftp-server
-
-# Example of overriding settings on a per-user basis
-#Match User anoncvs
-# X11Forwarding no
-# AllowTcpForwarding no
-# PermitTTY no
-# ForceCommand cvs server
diff --git a/recipes-connectivity/openssh/openssh_%.bbappend b/recipes-connectivity/openssh/openssh_%.bbappend
index 7719d3b..b541c3e 100644
--- a/recipes-connectivity/openssh/openssh_%.bbappend
+++ b/recipes-connectivity/openssh/openssh_%.bbappend
@@ -1 +1,15 @@
require ${@bb.utils.contains('DISTRO_FEATURES', 'selinux', '${BPN}_selinux.inc', '', d)}
+
+# if pam feature is enabled in the distro then take sshd from the pam directory.
+FILESEXTRAPATHS_prepend := "${@bb.utils.contains('DISTRO_FEATURES', 'pam', '${THISDIR}/files/pam:', ' ', d)}"
+
+do_install_append(){
+
+ if [ "${@bb.utils.filter('DISTRO_FEATURES', 'pam', d)}" ]; then
+ # Make sure UsePAM entry is in the sshd_config file.
+ # If entry not present then append it.
+ grep -q 'UsePAM' "${D}/etc/ssh/sshd_config" && \
+ sed -i 's/.*UsePAM.*/UsePAM yes/' "${D}/etc/ssh/sshd_config" || \
+ echo 'UsePAM yes' >> "${D}/etc/ssh/sshd_config"
+ fi
+}
--
2.7.4

This message contains information that may be privileged or confidential and is the property of the KPIT Technologies Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Technologies Ltd. does not accept any liability for virus infected mails.


Re: [External] Re: [yocto] Yocto- Apache2 build guide

D, Sharmila <sharmila.d@...>
 

Hi MacLeod,

Thanks for your e-mail.
Yes, without apach2 I am able to build the core-image-minimal successfully. The issue is only when I add apache2 in IMAGE_INSTALL.
I am using TI processor SDK and I have setup the arago based yocto environment based on TI user guide.
version is THUD.
Do you need any further details about the setup?
Please provide me the steps to include apache2 package into my final image.

Looking forward to hearing from you at your earliest convenience.

With Best Regards,
Sharmila D

-----Original Message-----
From: Randy MacLeod <randy.macleod@windriver.com>
Sent: Thursday, February 25, 2021 12:08 AM
To: D, Sharmila <Sharmila.D@Honeywell.com>; yocto@lists.yoctoproject.org
Subject: [External] Re: [yocto] Yocto- Apache2 build guide

On 2021-02-24 5:04 a.m., D, Sharmila via lists.yoctoproject.org wrote:
Hi,

I am trying to enable httpd package into my yocto build, steps I
followed is as below

1. Added below layer in bblayer.conf file

sources/meta-openembedded/meta-webserver

2. Added below line in local.conf file

IMAGE_INSTALL_append = "apache2"

The yocto build using bitbake core-image-minimal gives below error

WARNING: core-image-minimal-1.0-r0 do_rootfs: busybox.postinst
returned 1, marking as unpacked only, configuration required on target.
ERROR: core-image-minimal-1.0-r0 do_rootfs: Postinstall scriptlets of
['busybox'] have failed. If the intention is to defer them to first
boot, then please place them into pkg_postinst_ontarget_${PN} ().
Deferring to first boot via 'exit 1' is no longer supported.
Details of the failure are in
/home/h440246/Projects/rfid/BSP/tisdk/build/arago-tmp-glibc/work/omapl138_lcdk-oe-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.
ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in:
/home/h440246/Projects/rfid/BSP/tisdk/build/arago-tmp-glibc/work/omapl
138_lcdk-oe-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs
.2937
ERROR: Task
(/home/h440246/Projects/rfid/BSP/tisdk/sources/oe-core/meta/recipes-co
re/images/core-image-minimal.bb:do_rootfs)
failed with exit code '1'

Please provide the solution for the same
Hi Sharmila,

This doesn't appear to be related to adding apache.
Are you able to build core-image-minimal without adding apache2?

Can you provide detailed steps wrt what layers and HEAD commits for each layer you are using? Ideally, you'd reproduce on a supported release or on master. That's Dunfell/3.1 or later:
https://wiki.yoctoproject.org/wiki/Releases

../Randy


With Best Regards,

Sharmila D





--
# Randy MacLeod
# Wind River Linux


Re: [opkg-devel] [opkg-utils PATCH] CONTRIBUTING: fix yocto ML link

Alex Stewart
 

Thanks for catching that and putting in a fix! ACK from me.

--
Alex Stewart
Software Engineer - NI Real-Time OS
NI (National Instruments)

alex.stewart@ni.com


Re: [opkg-devel] [opkg-utils PATCH] opkg-build: make sure destination dir exists

Alex Stewart
 

Looks good to me. I'll pull tomorrow if there are no objections.

Thanks,

--
Alex Stewart
Software Engineer - NI Real-Time OS
NI (National Instruments)

alex.stewart@ni.com


[meta-rockchip][PATCH] rock-pi-e: add

Trevor Woerner
 

Add support for Radxa's ROCK Pi E device
https://wiki.radxa.com/RockpiE

It's a great surprise to find upstream U-Boot and the Linux kernel already
provide support for this board! On the kernel side this support was
added in 5.11. However, that support is so new that even linux-yocto-dev
(which is based on 5.11) doesn't include the commits that add support
for this board yet. As a result I've added a custom Linux kernel recipe
(linux-stable-bleeding) which should, in time, become unnecessary.

Signed-off-by: Trevor Woerner <twoerner@gmail.com>
---
conf/machine/rock-pi-e.conf | 42 +++++++++++++++++++
.../trusted-firmware-a_%.bbappend | 2 +-
recipes-bsp/u-boot/u-boot%.bbappend | 2 +
.../linux/linux-stable-bleeding_5.11.bb | 18 ++++++++
recipes-kernel/linux/linux-yocto-dev.bbappend | 2 +-
wic/rk3328-boot.wks | 23 ++++++++++
wic/rock-pi-e.wks | 4 ++
7 files changed, 91 insertions(+), 2 deletions(-)
create mode 100644 conf/machine/rock-pi-e.conf
create mode 100644 recipes-kernel/linux/linux-stable-bleeding_5.11.bb
create mode 100644 wic/rk3328-boot.wks
create mode 100644 wic/rock-pi-e.wks

diff --git a/conf/machine/rock-pi-e.conf b/conf/machine/rock-pi-e.conf
new file mode 100644
index 0000000..035a950
--- /dev/null
+++ b/conf/machine/rock-pi-e.conf
@@ -0,0 +1,42 @@
+#@TYPE: Machine
+#@NAME: ROCK Pi E rk3328
+#@DESCRIPTION: ROCK Pi E is a Rockchip RK3328-based SBC by Radxa. E is for Ethernets.
+#https://wiki.radxa.com/RockpiE
+
+MACHINEOVERRIDES =. "rock-pi-e:"
+SOC_FAMILY = "rk3328"
+DEFAULTTUNE = "cortexa53-crypto"
+
+require conf/machine/include/soc-family.inc
+require conf/machine/include/tune-cortexa53.inc
+require conf/machine/include/rockchip-defaults.inc
+
+PREFERRED_PROVIDER_virtual/kernel = "linux-stable-bleeding"
+KERNEL_DEVICETREE = "rockchip/rk3328-rock-pi-e.dtb"
+KBUILD_DEFCONFIG = "defconfig"
+KERNEL_CLASSES = "kernel-fitimage"
+KERNEL_IMAGETYPE = "fitImage"
+MACHINE_EXTRA_RRECOMMENDS += "kernel-modules"
+
+TFA_PLATFORM = "rk3328"
+TFA_BUILD_TARGET = "bl31"
+
+UBOOT_MACHINE = "rock-pi-e-rk3328_defconfig"
+UBOOT_SUFFIX = "itb"
+UBOOT_ENTRYPOINT = "0x06000000"
+PREFERRED_PROVIDER_virtual/bootloader = "u-boot"
+SPL_BINARY = "idbloader.img"
+
+WKS_FILE = "rock-pi-e.wks"
+IMAGE_FSTYPES += "wic.xz wic.bmap"
+WKS_FILE_DEPENDS = " \
+ mtools-native \
+ dosfstools-native \
+ virtual/bootloader \
+ virtual/kernel \
+ "
+IMAGE_BOOT_FILES ?= " \
+ ${KERNEL_IMAGETYPE} \
+ "
+
+SERIAL_CONSOLES = "1500000;ttyS2"
diff --git a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend
index 2374205..442dee8 100644
--- a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend
+++ b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend
@@ -3,4 +3,4 @@
DEPENDS_append_rk3399 = " virtual/arm-none-eabi-gcc-native"

COMPATIBLE_MACHINE_append_rk3399 = "|rk3399"
-
+COMPATIBLE_MACHINE_append_rk3328 = "|rk3328"
diff --git a/recipes-bsp/u-boot/u-boot%.bbappend b/recipes-bsp/u-boot/u-boot%.bbappend
index 042507d..95c019d 100644
--- a/recipes-bsp/u-boot/u-boot%.bbappend
+++ b/recipes-bsp/u-boot/u-boot%.bbappend
@@ -9,6 +9,8 @@ ATF_DEPENDS ??= ""

EXTRA_OEMAKE_append_rk3399 = " BL31=${DEPLOY_DIR_IMAGE}/bl31-rk3399.elf"
ATF_DEPENDS_rk3399 = " virtual/trusted-firmware-a:do_deploy"
+EXTRA_OEMAKE_append_rk3328 = " BL31=${DEPLOY_DIR_IMAGE}/bl31-rk3328.elf"
+ATF_DEPENDS_rk3328 = " virtual/trusted-firmware-a:do_deploy"

do_compile[depends] .= "${ATF_DEPENDS}"

diff --git a/recipes-kernel/linux/linux-stable-bleeding_5.11.bb b/recipes-kernel/linux/linux-stable-bleeding_5.11.bb
new file mode 100644
index 0000000..dce537d
--- /dev/null
+++ b/recipes-kernel/linux/linux-stable-bleeding_5.11.bb
@@ -0,0 +1,18 @@
+# the rock-pi-e is very new
+# it's exciting that support has already been added upstream
+# but it's so new that even linux-yocto-dev doesn't have it yet
+#
+# in time we should see the need for this recipe going away
+
+inherit kernel
+require recipes-kernel/linux/linux-yocto.inc
+
+LIC_FILES_CHKSUM = "file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
+
+SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git"
+SRCREV = "c03c21ba6f4e95e406a1a7b4c34ef334b977c194"
+LINUX_VERSION = "5.11"
+LINUX_VERSION_EXTENSION = ""
+PV = "${LINUX_VERSION}"
+
+COMPATIBLE_MACHINE = "(rock-pi-e)"
diff --git a/recipes-kernel/linux/linux-yocto-dev.bbappend b/recipes-kernel/linux/linux-yocto-dev.bbappend
index 2f498d9..a85b85e 100644
--- a/recipes-kernel/linux/linux-yocto-dev.bbappend
+++ b/recipes-kernel/linux/linux-yocto-dev.bbappend
@@ -1 +1 @@
-COMPATIBLE_MACHINE .= "|firefly-rk3288|marsboard-rk3066|radxarock|rock-pi-4|rock2-square|tinker-board-s|tinker-board|vyasa-rk3288"
+COMPATIBLE_MACHINE .= "|firefly-rk3288|marsboard-rk3066|radxarock|rock-pi-4|rock2-square|tinker-board-s|tinker-board|vyasa-rk3288|rock-pi-e"
diff --git a/wic/rk3328-boot.wks b/wic/rk3328-boot.wks
new file mode 100644
index 0000000..194145b
--- /dev/null
+++ b/wic/rk3328-boot.wks
@@ -0,0 +1,23 @@
+# Copyright (C) 2021 Trevor Woerner
+# Released under the MIT license (see COPYING.MIT for the terms)
+#
+# Disk layout
+# Note that the reference documentation refers to 512 byte disk sectors, but
+# wic uses 1KB blocks
+#
+# Partition Start Sector Number of Sectors
+# loader1 64 8000
+# reserved1 8064 128
+# reserved2 8192 8192
+# loader2 16384 8192
+# atf 24576 8192
+# boot 32768 229376
+# root 262144 - (suggested)
+#
+
+part loader1 --offset 32 --fixed-size 4000K --ondisk ${RK_BOOT_DEVICE} --source rawcopy --sourceparams="file=idbloader.img"
+part reserved1 --offset 4032 --fixed-size 64K --ondisk ${RK_BOOT_DEVICE}
+part reserved2 --offset 4096 --fixed-size 4096K --ondisk ${RK_BOOT_DEVICE}
+part loader2 --offset 8192 --fixed-size 4096K --ondisk ${RK_BOOT_DEVICE} --source rawcopy --sourceparams="file=u-boot.itb"
+part atf --offset 12288 --fixed-size 4096K --ondisk ${RK_BOOT_DEVICE}
+part /boot --offset 16384 --size 114688K --active --ondisk ${RK_BOOT_DEVICE} --source bootimg-partition --fstype=vfat --label boot --sourceparams="loader=u-boot"
diff --git a/wic/rock-pi-e.wks b/wic/rock-pi-e.wks
new file mode 100644
index 0000000..97f84d1
--- /dev/null
+++ b/wic/rock-pi-e.wks
@@ -0,0 +1,4 @@
+include rk3328-boot.wks
+part / --ondisk ${RK_BOOT_DEVICE} --source rootfs --fstype=ext4 --label root
+
+bootloader --ptable gpt --append="console=tty1 console=ttyS2,1500000n8 rw root=/dev/${RK_BOOT_DEVICE}p7 rootfstype=ext4 init=/sbin/init"
--
2.30.0.rc0


Re: [External] Re: [yocto] Yocto- Apache2 build guide

Randy MacLeod
 

On 2021-02-24 10:37 p.m., D, Sharmila wrote:
Hi MacLeod,
Thanks for your e-mail.
Yes, without apach2 I am able to build the core-image-minimal successfully. The issue is only when I add apache2 in IMAGE_INSTALL.
I am using TI processor SDK and I have setup the arago based yocto environment based on TI user guide.
version is THUD.
Do you need any further details about the setup?
Please provide me the steps to include apache2 package into my final image.
Looking forward to hearing from you at your earliest convenience.
Hello Sharmila,

If you can reproduce the problem with only the oe-core/poly + meta-openembedded layers then perhaps someone on this list can help you.
Otherwise, you should contact the people who provided the
TI processor SDK.

By the way, Thud is EOL in the YP community:
https://wiki.yoctoproject.org/wiki/Releases
but commercial vendors do have longer support cycles
so hopefully TI can help you out.

../Randy
With Best Regards,
Sharmila D
-----Original Message-----
From: Randy MacLeod <randy.macleod@windriver.com>
Sent: Thursday, February 25, 2021 12:08 AM
To: D, Sharmila <Sharmila.D@Honeywell.com>; yocto@lists.yoctoproject.org
Subject: [External] Re: [yocto] Yocto- Apache2 build guide
On 2021-02-24 5:04 a.m., D, Sharmila via lists.yoctoproject.org wrote:
Hi,

I am trying to enable httpd package into my yocto build, steps I
followed is as below

1. Added below layer in bblayer.conf file

sources/meta-openembedded/meta-webserver

2. Added below line in local.conf file

IMAGE_INSTALL_append = "apache2"

The yocto build using bitbake core-image-minimal gives below error

WARNING: core-image-minimal-1.0-r0 do_rootfs: busybox.postinst
returned 1, marking as unpacked only, configuration required on target.
ERROR: core-image-minimal-1.0-r0 do_rootfs: Postinstall scriptlets of
['busybox'] have failed. If the intention is to defer them to first
boot, then please place them into pkg_postinst_ontarget_${PN} ().
Deferring to first boot via 'exit 1' is no longer supported.
Details of the failure are in
/home/h440246/Projects/rfid/BSP/tisdk/build/arago-tmp-glibc/work/omapl138_lcdk-oe-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.
ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in:
/home/h440246/Projects/rfid/BSP/tisdk/build/arago-tmp-glibc/work/omapl
138_lcdk-oe-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs
.2937
ERROR: Task
(/home/h440246/Projects/rfid/BSP/tisdk/sources/oe-core/meta/recipes-co
re/images/core-image-minimal.bb:do_rootfs)
failed with exit code '1'

Please provide the solution for the same
Hi Sharmila,
This doesn't appear to be related to adding apache.
Are you able to build core-image-minimal without adding apache2?
Can you provide detailed steps wrt what layers and HEAD commits for each layer you are using? Ideally, you'd reproduce on a supported release or on master. That's Dunfell/3.1 or later:
https://wiki.yoctoproject.org/wiki/Releases
../Randy


With Best Regards,

Sharmila D



--
# Randy MacLeod
# Wind River Linux

--
# Randy MacLeod
# Wind River Linux


Yocto Technical Team Minutes/Engineering Sync for Feb 23, 2021

Trevor Woerner
 

Yocto Technical Team Minutes, Engineering Sync, for Feb 23, 2021
archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit

== disclaimer ==
Best efforts are made to ensure the below is accurate and valid. However,
errors sometimes happen. If any errors or omissions are found, please feel
free to reply to this email with any corrections.

== attendees ==
Trevor Woerner, Stephen Jolley, Scott Murray, Armin Kuster, Michael
Halstead, Steve Sakoman, Richard Purdie, Randy MacLeod, Saul Wold, Jon
Mason, Joshua Watt, Paul Barker, Tim Orling, Mark Morton, John Kaldas,
Alejandro H, Ross Burton

== notes ==
- 3.2.2 passed QA clean, awaiting final approval from TSC
- 3.1.6 built and in QA
- 1 week before -m3 should be built (feature freeze for 3.3)
- adding RPM to reproducibility, still needs some work
- recipe maintainers: please review the patches we’re carrying (push
upstream as many as possible)
- glibc 2.33 issue should be resolved with latest pseudo
- AUH patches are now merged or queued, few of the failures handled
- AB issue list is at record high (not good)

== general ==
RP: can’t get stable test results out of AB on master


RP: would be nice to get RPM reproducibility issues ironed out, but there are
some epoch issues to work through which messes up diffoscope
RP: was surprised to see how bad the interactive response is on the cmdline on
the builders. it seems like an I/O bottleneck
Randy: mostly I/O to SSDs?
RP: i believe so
RP: it was immediately after a build had been started. so it could be related
to downloads or sstate fetching. how much sstate did you expect that build
to be reusing?
SteveS: version bumps to conman, kernel… yea that could lead to a lot of
rebuilds
Michael: we’ve been optimizing for throughput for a while. on some other
build systems we leave some overhead available for cmdline interactivity.
should we start to do that with the YP AB?
RP: i think it would have to be backed off by a significant amount to get that
breathing space. so maybe yes, but we’d have to look at it to see what
to backoff and by how much. looking through the build i see that 77% was
pulled from sstate (therefore pulling data off the NAS, then extracting
it).
Randy: and that’s not coordinated at all, if there are 100 items, then 100
threads?
RP: but limited by BB_THREADS
JPEW: run by buildbot? maybe we could use cgroups?
RP: i don’t think it’s CPU bound, the CPU was 50% idle when the cmdline
was very slow
MichaelH: sometimes we see that when the system isn’t healthy, i wonder if
it’s isolated to specific machines?
RP: on the CentOS machine, a command took over 5 minutes to complete. then
tried debian, same thing. then logged into the fedora machine and was
able to do stuff. but it didn’t seem isolated to any machines, it
seemed localized in time (i.e. right after a build had been started),
then dropped off. so i feel that it might be related to the initial build
startup, probably related to sstate pulling/extraction
Randy: could also limit I/O using cgroups
RP: we do use IOnice for parts of the build (2.1 and 2.7)
Michael: translation: class 2 priority 1; class 2 priority 7
Alejandro: are these sharing any hardware
RP: they’re all connected to the NAS
Michael: and they’re 100% dedicated to this work
RP: i don’t think this is a network bottleneck, i think this is sstate extraction
JPEW: maybe a different compression algorithm? gzip is notoriously slow
RP: wouldn’t that make it worse?
JPEW: does each AB have their own mirror
RP: it’s all done over NFS
JPEW: network bandwidth should be lower than local unzipping/extraction bandwidth?
Alejandro: could we try different I/O scheduling?
RP: don’t know

RP: had a look at patches. 1,300 patches in oe-core, ~600 in pending the rest
are submitted or not appropriate. some of these are 10 years or older,
do we still need them? i sent 2 upstream and was told it wasn’t needed
anymore (problem fixed in other ways). there’s also one in valgrind that
looks similar (different fix upstream) and not needed.
Ross: if some people could try to do 1 a day that would be a huge help
RP: lots of patches related to reproducibility
JPEW: the big issue with perf is that it uses bison (which needs patches)

PaulB: read-only mode for PR server. i’ve been working on it, but it’s 1
big patch. there’s code to handle daemonizing and forking which in hash
server is using the python mutli-processing. we also want to use the
same RPC mechanisms that python is using. are those good lines along which
to break the patches down?
RP: that sounds perfect
PaulB: it was easier to bash on it all together, then go back and break it up
into digestible chunks
RP: it’s 10 year old code, so i’m not surprised
PaulB: i’ve broken out a part that uses JSON RPC, then use that for the
server
RP: sounds good to me
JPEW: me too
RP: scaling that code under python2 was a challenge. glad to see this moving
forward

RP: Randy posted rust patch set. felt it couldn’t be merged in this form
(too many patches)
Randy: do you want the history squashed?
RP: that was my feeling
Randy: i’ve been working on it bit by bit as stuff happens upstream which
leads to lots of little commits. but i can reorg by logical group and
squash the log
RP: yes. in one case there were lots of commits to the rust version, then in
the end you end up with 2
Randy: someone from MS worked on getting the sdk stuff working
RP: given that next Monday is the feature freeze, let’s get the patched out
sooner, and worry about the sdk later
Randy: ok. last remaining issue is the pre-fetcher but i don’t know much
about it. looked at PaulB’s patches
PaulB: there are 3 methods floating around, i’ve focused on one of them that
i like
1. doing the download ahead of time in do_fetch()
2. let rust-bin do the downloads itself in do_compile() which i don’t like
3. haven’t looked at the last one yet
PaulB: i like 1 because it asks rust to output a cargo which the fetcher can
then act on
Randy: doesn’t rely on crates?
PaulB: i think it relies on crates for things that it can’t resolve. however
Andreas’ approach relies on getting bitbake to understand cargo-toml
file, not sure if that’s a good approach
Randy: are there any lessons with Go that we can use?
Scott: Bruce would be a good one to talk to
PaulB: my understanding with Go is that the code tends to all be placed
together in the git repository, so the fetch side is a little simpler
Randy: so given the approach we’re using is there anything that needs to be
added
PaulB: it needs testing
Randy: i have a team working on testing the rust compiler itself. they can
successfully execute 2/3 of the tests now (of which 99.9% pass). i have
a reproducibility test for rust hello world, but it takes a long time to
run. any tests you’re thinking of?
PaulB: fetcher tests. if you have a “crate://” in a URL, just making sure
it gets translated correctly to make sure it doesn’t bitrot
Randy: is that an -m3 or -m4 activity
RP: if we’ll get it in -m4 for sure we can wait until then. in oe-core
we’d want some sort of hello world (make sure compiler works and we can
run the binaries)
Randy: we have that already
RP: both for cross-compiling and target. then reproducibility tests. i’m
happy to build them up, as long as there’s a roadmap. for -m3 i think we
should get the baseline rust set and the crate fetcher
PaulB: crate fetcher overrides the wget fetcher and makes sure everything gets
put in the right place. so it just needs a couple test cases; a map of
inputs to outputs. i’ll resubmit the patch and include a list of tests
that we need to add
RP: if someone could reply to Andreas and let him know what’s going on and
why we’re going in a slightly different direction than the work he’s
submitted
PaulB: the fundamental unit is the recipe. devtool is the place for some of
the functionality not bitbake
Randy: building rust hello world works for all glibc qemu targets but some
breakage with musl (risc-v and powerpc) i think Khem is working on the
risc-v one. will that hold things up?
RP: no
PaulB: i have some slightly larger rust packages (larger than hello world)
that i think will test things a little more thoroughly, e.g. ripgrep
Randy: we’re testing that one already. should we add it to oe-core?
RP: it would be good to have something in oe-core to do testing
Randy: i think hello world would be good enough for oe-core and leave larger
tests for other layers
PaulB: there are rust things in oe-core (librsvg, etc) so i think oe-core will
have good test things already in them without having to add recipes just
for testing’s sake
Randy: things also seem to work well on ARM builders
Ross: yes, things are on-target

TrevorW: started work on 2021 YP conference. conversation moved to
conferences@lists.yoctoproject.org if you want to follow along or help

RP: fetch, workdir, can’t clean up workdir, config changes but can’t
cleanup. maybe we should fetch to a special dir and then just symlink
PaulB: would it be recipe-specific
RP: yes, it would be under $WORKDIR
PaulB: would make the archiver easier
TimO: there are a number of Go modules that don’t cleanup properly so maybe
this would help
ScottM: there are lots recipes that do post-processing on files in $WORKDIR
before moving them to the artifacts directory, so there could be breakage
there
PaulB: can we do it first thing next release
RP: we’ll give it a try and see
TrevorW: i think a lot of BSP layers will be affected
RP: i think there’s a lot of chance a lot of things (not just BSPs) will be
affected
ScottM: there are some BSP things that will be affected, but in AGL we’re
doing a lot of $WORKDIR manipulations that aren’t necessarily BSP
related as well
(several): overall it sounds like a good idea and a good cleanup to try

1401 - 1420 of 53871