【MYD-YA15XC-T开发板】 + 7、Yocto构建开发板镜像

TLLED

使用Yocto构建开发板镜像，折腾很长时间就是编译不过，今天换个电脑竟编译通过了，看来Yocto对电脑硬件要求较高啊。

一、编译过程

1.1、将资料\MYD-YA15XC-T\04_Sources\ya15xc-t-yocto-stm32mp1-5.4.31-1.0.0.tar文件解压到/home/Yocto文件下。
1.2、执行命令：DISTRO=openstlinux-eglfs MACHINE=myir-ya151c-t source layers/meta-myir-st-tiny/scripts/envsetup.sh生成build-openstlinuxeglfs-myir-ya151c-t文件夹。
1.3、将文件Yocto-qt-downloads.tar解压到/home/Yocto/build-openstlinuxeglfs-myir-ya151c-t下
1.4、执行命令：bitbake myir-image-core
1.5、等待。。。

编译时间根据电脑的配置，我编译的时间有点长。
1.6、编译输出过程：

hui@ubuntu:/home/Yocto/build-openstlinuxeglfs-myir-ya151c-t$ bitbake myir-image-core
NOTE: Started PRServer with DBfile: /home/Yocto/build-openstlinuxeglfs-myir-ya151c-t/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 35221, PID: 38995
Parsing recipes: 100% |######################################################################################################################################################################| Time: 0:01:42
Parsing of 2650 .bb files complete (0 cached, 2650 parsed). 3847 targets, 116 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.46.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "ubuntu-16.04"
TARGET_SYS = "arm-ostl-linux-gnueabi"
MACHINE = "myir-ya151c-t"
DISTRO = "openstlinux-eglfs"
DISTRO_VERSION = "3.1-snapshot-20211214"
TUNE_FEATURES = "arm vfp cortexa7 neon vfpv4 thumb callconvention-hard"
TARGET_FPU = "hard"
DISTRO_CODENAME = "dunfell"
ACCEPT_EULA_myir-ya151c-t = "1"
GCCVERSION = "9.%"
PREFERRED_PROVIDER_virtual/kernel = "linux-myir"
meta-oe
meta-gnome
meta-xfce
meta-initramfs
meta-multimedia
meta-networking
meta-webserver
meta-filesystems
meta-perl
meta-python
meta-st-stm32mp
meta-qt5
meta-st-openstlinux = "<unknown>:<unknown>"
meta-myir-st-tiny = "master:8791ebc550f9737384568077468a7dc30827965b"
meta = "<unknown>:<unknown>"
Initialising tasks: 100% |###################################################################################################################################################################| Time: 0:00:18
Sstate summary: Wanted 3107 Found 2244 Missed 863 Current 0 (72% match, 0% complete)
NOTE: Executing Tasks
WARNING: systemd-1_244.3-r0 do_package_qa: QA Issue: systemd: /init is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: systemd-1_244.3-r0 do_package_qa: QA Issue: systemd: /usr/bin/systemd-analyze is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: systemd-1_244.3-r0 do_package_qa: QA Issue: systemd: /lib/libnss_resolve.so.2 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: systemd-1_244.3-r0 do_package_qa: QA Issue: systemd: /usr/share/pkgconfig/systemd.pc is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/pkgconfig/udev.pc is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/pkgconfig/libudev.pc is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/pkgconfig/libsystemd.pc is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/libudev.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/libsystemd.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: systemd-1_244.3-r0 do_package_qa: QA Issue: systemd: /etc/resolv-conf.systemd is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /etc/tmpfiles.d/00-create-volatile.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /etc/pam.d/systemd-user is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /etc/systemd/pstore.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /etc/systemd/sleep.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /etc/systemd/resolved.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /etc/systemd/system.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /etc/systemd/networkd.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /etc/systemd/coredump.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /etc/systemd/user.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /etc/systemd/timesyncd.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /etc/systemd/logind.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /etc/systemd/journald.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /etc/X11/xinit/xinitrc.d/50-systemd-user.sh is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /sbin/telinit is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /sbin/runlevel is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /sbin/resolvconf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /sbin/halt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /sbin/reboot is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /sbin/shutdown is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /sbin/init is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /sbin/poweroff is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/factory/etc/nsswitch.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/factory/etc/issue is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/factory/etc/pam.d/system-auth is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/factory/etc/pam.d/other is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/systemd/language-fallback-map is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/systemd/kbd-model-map is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/dbus-1/system-services/org.freedesktop.network1.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/dbus-1/system-services/org.freedesktop.locale1.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/dbus-1/system-services/org.freedesktop.resolve1.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/dbus-1/system-services/org.freedesktop.login1.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/dbus-1/system-services/org.freedesktop.hostname1.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/dbus-1/system-services/org.freedesktop.timesync1.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/dbus-1/system-services/org.freedesktop.timedate1.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/dbus-1/system.d/org.freedesktop.network1.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/dbus-1/system.d/org.freedesktop.resolve1.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/dbus-1/system.d/org.freedesktop.systemd1.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/dbus-1/system.d/org.freedesktop.hostname1.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/dbus-1/system.d/org.freedesktop.timesync1.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/dbus-1/system.d/org.freedesktop.locale1.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/dbus-1/system.d/org.freedesktop.login1.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/dbus-1/system.d/org.freedesktop.timedate1.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/dbus-1/services/org.freedesktop.systemd1.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/polkit-1/actions/org.freedesktop.timedate1.policy is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/polkit-1/actions/org.freedesktop.login1.policy is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/polkit-1/actions/org.freedesktop.locale1.policy is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/polkit-1/actions/org.freedesktop.network1.policy is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/polkit-1/actions/org.freedesktop.resolve1.policy is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/polkit-1/actions/org.freedesktop.systemd1.policy is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/polkit-1/actions/org.freedesktop.hostname1.policy is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/polkit-1/rules.d/systemd-networkd.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/bin/resolvectl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/bin/systemd-mount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/bin/systemd-id128 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/bin/systemd-umount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/bin/systemd-resolve is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/bin/busctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/bin/systemd-socket-activate is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/bin/localectl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/bin/timedatectl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/bin/coredumpctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/bin/hostnamectl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/bin/bootctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/environment.d/99-environment.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/tmpfiles.d/systemd-tmp.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/tmpfiles.d/var.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/tmpfiles.d/home.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/tmpfiles.d/journal-nocow.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/tmpfiles.d/static-nodes-permissions.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/tmpfiles.d/legacy.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/tmpfiles.d/tmp.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/tmpfiles.d/systemd-nologin.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/tmpfiles.d/etc.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/tmpfiles.d/systemd.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/tmpfiles.d/x11.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/catalog/systemd.catalog is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/catalog/systemd.bg.catalog is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/catalog/systemd.de.catalog is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/catalog/systemd.ru.catalog is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/catalog/systemd.it.catalog is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/catalog/systemd.zh_CN.catalog is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/catalog/systemd.fr.catalog is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/catalog/systemd.be@latin.catalog is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/catalog/systemd.pl.catalog is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/catalog/systemd.pt_BR.catalog is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/catalog/systemd.zh_TW.catalog is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/catalog/systemd.be.catalog is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/user-environment-generators/30-systemd-environment-d-generator is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/user/sound.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/user/smartcard.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/user/sockets.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/user/systemd-exit.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/user/exit.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/user/timers.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/user/shutdown.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/user/systemd-tmpfiles-clean.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/user/default.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/user/printer.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/user/systemd-tmpfiles-setup.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/user/basic.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/user/graphical-session-pre.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/user/paths.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/user/graphical-session.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/user/systemd-tmpfiles-clean.timer is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/user/bluetooth.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/systemd/user-preset/90-systemd.preset is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/sysctl.d/50-default.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/sysctl.d/50-coredump.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/sysusers.d/basic.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/sysusers.d/systemd.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /bin/systemd-notify is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /bin/loginctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /bin/journalctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /bin/systemd-tmpfiles is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /bin/systemd-sysusers is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /bin/systemd-firstboot is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /bin/networkctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /bin/systemd-machine-id-setup is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /bin/systemctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/99-systemd.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/73-seat-late.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/71-seat.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/modprobe.d/systemd.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/security/pam_systemd.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-network-generator is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-user-sessions is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-fsck is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-sulogin-shell is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-journald is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-modules-load is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-hibernate-resume is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-networkd-wait-online is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-random-seed is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-timedated is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-timesyncd is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-user-runtime-dir is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-growfs is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-dissect is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-time-wait-sync is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-localed is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-shutdown is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/libsystemd-shared-244.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-logind is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-sysctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-coredump is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-pstore is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-hostnamed is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-update-done is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-networkd is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-makefs is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-backlight is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-volatile-root is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-boot-check-no-failures is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-quotacheck is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-bless-boot is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-remount-fs is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-update-utmp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/resolv.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-rfkill is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-resolved is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/network/80-wifi-station.network.example is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/network/80-container-ve.network is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/network/80-container-vz.network is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/network/80-wifi-ap.network.example is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/network/80-container-host0.network is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/network/80-wifi-adhoc.network is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system-generators/systemd-hibernate-resume-generator is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system-generators/systemd-debug-generator is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system-generators/systemd-getty-generator is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system-generators/systemd-run-generator is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system-generators/systemd-bless-boot-generator is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system-generators/systemd-fstab-generator is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system-generators/systemd-sysv-generator is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system-generators/systemd-rc-local-generator is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system-generators/systemd-system-update-generator is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/ntp-units.d/80-systemd-timesync.list is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system-preset/99-default.preset is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system-preset/90-systemd.preset is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-coredump@.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-sysctl.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-fsck@.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/dbus-org.freedesktop.locale1.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-timesyncd.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sound.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-rfkill.socket is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/runlevel4.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/syslog.socket is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/getty.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/suspend.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-journal-flush.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-hibernate-resume@.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-bless-boot.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/nss-lookup.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/hibernate.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/multi-user.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/halt.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/ldconfig.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/final.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-networkd.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/emergency.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/smartcard.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sockets.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/system-update-pre.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/initrd-fs.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/graphical.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/dev-hugepages.mount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-update-utmp-runlevel.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-exit.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/exit.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/umount.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/autovt@.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/debug-shell.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/runlevel2.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/timers.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-time-wait-sync.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-update-utmp.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-timedated.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-tmpfiles-setup-dev.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/getty@.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/initrd-root-fs.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sigpwr.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/dbus-org.freedesktop.login1.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/runlevel6.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/system-update.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/slices.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sys-kernel-debug.mount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/ctrl-alt-del.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-resolved.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-random-seed.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/hybrid-sleep.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sys-kernel-config.mount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-kexec.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/local-fs-pre.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/initrd-root-device.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-halt.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-modules-load.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-logind.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/shutdown.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/initrd-cleanup.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/tmp.mount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/runlevel5.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-rfkill.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/local-fs.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/rpcbind.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/rc-local.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-journald-audit.socket is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-journald-dev-log.socket is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/time-set.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/rescue.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/poweroff.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/user.slice is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/dbus-org.freedesktop.timedate1.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/nss-user-lookup.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/swap.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/dev-mqueue.mount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-hostnamed.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/runlevel1.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-journald.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/network.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-firstboot.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-tmpfiles-clean.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-boot-system-token.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/time-sync.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-network-generator.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/boot-complete.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-localed.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-sysusers.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/initrd-switch-root.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/runlevel3.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/runlevel0.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/default.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/dbus-org.freedesktop.hostname1.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/printer.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/system-update-cleanup.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/kexec.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-tmpfiles-setup.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/basic.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-networkd.socket is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/suspend-then-hibernate.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-remount-fs.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-poweroff.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-journald.socket is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/network-online.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/user-runtime-dir@.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-pstore.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/rescue.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/emergency.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-fsck-root.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/paths.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-machine-id-commit.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-backlight@.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/remote-fs.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-update-done.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/initrd-switch-root.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-boot-check-no-failures.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-user-sessions.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/container-getty@.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/reboot.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/initrd-parse-etc.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/kmod-static-nodes.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-quotacheck.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/initrd.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/console-getty.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/user@.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-reboot.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/quotaon.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-journal-catalog-update.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/getty-pre.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-coredump.socket is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-networkd-wait-online.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/remote-fs-pre.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-tmpfiles-clean.timer is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sys-fs-fuse-connections.mount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/bluetooth.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/network-pre.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-suspend-then-hibernate.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-volatile-root.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/rescue.target.wants/systemd-update-utmp-runlevel.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/user-.slice.d/10-defaults.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/multi-user.target.wants/getty.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/multi-user.target.wants/systemd-update-utmp-runlevel.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/multi-user.target.wants/systemd-logind.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/multi-user.target.wants/systemd-user-sessions.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/graphical.target.wants/systemd-update-utmp-runlevel.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/systemd-sysctl.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/systemd-journal-flush.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/ldconfig.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/dev-hugepages.mount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/systemd-update-utmp.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/systemd-tmpfiles-setup-dev.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/sys-kernel-debug.mount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/systemd-random-seed.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/sys-kernel-config.mount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/systemd-modules-load.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/dev-mqueue.mount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/systemd-journald.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/systemd-firstboot.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/systemd-boot-system-token.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/systemd-sysusers.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/systemd-tmpfiles-setup.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/systemd-machine-id-commit.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/systemd-update-done.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/kmod-static-nodes.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/systemd-journal-catalog-update.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/systemd-hwdb-update.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/sys-fs-fuse-connections.mount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sockets.target.wants/systemd-journald-audit.socket is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sockets.target.wants/systemd-journald-dev-log.socket is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sockets.target.wants/systemd-journald.socket is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sockets.target.wants/systemd-coredump.socket is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/timers.target.wants/systemd-tmpfiles-clean.timer is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/reboot.target.wants/systemd-update-utmp-runlevel.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/local-fs.target.wants/tmp.mount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/poweroff.target.wants/systemd-update-utmp-runlevel.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: systemd-1_244.3-r0 do_package_qa: QA Issue: systemd: /usr/share/zsh/site-functions/_systemd-analyze is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_hostnamectl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_machinectl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_localectl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_sd_hosts_or_user_at_host is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_sd_outputmodes is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_systemd-delta is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_loginctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_journalctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_systemd-run is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_timedatectl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_sd_machines is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_kernel-install is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_busctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_resolvectl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_udevadm is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_systemd-inhibit is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_networkctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_sd_unit_files is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_systemd is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_systemd-nspawn is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_coredumpctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_bootctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_systemctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/zsh/site-functions/_systemd-tmpfiles is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: systemd-1_244.3-r0 do_package_qa: QA Issue: systemd: /usr/share/bash-completion/completions/systemd-run is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/systemd-detect-virt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/loginctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/resolvectl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/systemd-cgtop is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/journalctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/kernel-install is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/systemd-delta is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/systemd-resolve is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/busctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/systemd-path is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/networkctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/localectl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/systemd-cat is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/machinectl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/timedatectl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/systemd-analyze is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/systemd-nspawn is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/systemd-cgls is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/coredumpctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/hostnamectl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/systemctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/bootctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: systemd-1_244.3-r0 do_package_qa: QA Issue: systemd: /usr/share/dbus-1/system-services/org.freedesktop.machine1.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/dbus-1/system.d/org.freedesktop.machine1.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/polkit-1/actions/org.freedesktop.machine1.policy is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/bin/systemd-nspawn is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/tmpfiles.d/systemd-nspawn.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /bin/machinectl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-machined is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-machined.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/var-lib-machines.mount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/machines.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/dbus-org.freedesktop.machine1.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-nspawn@.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/machine.slice is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/remote-fs.target.wants/var-lib-machines.mount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/machines.target.wants/var-lib-machines.mount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: systemd-1_244.3-r0 do_package_qa: QA Issue: systemd: /lib/libsystemd.so.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/libsystemd.so.0.27.1 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: systemd-1_244.3-r0 do_package_qa: QA Issue: systemd: /usr/lib/rpm/macros.d/macros.systemd is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: systemd-1_244.3-r0 do_package_qa: QA Issue: systemd: /lib/systemd/systemd-binfmt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/proc-sys-fs-binfmt_misc.mount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-binfmt.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/proc-sys-fs-binfmt_misc.automount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: systemd-1_244.3-r0 do_package_qa: QA Issue: systemd: /lib/udev/hwdb.d/20-usb-classes.hwdb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/hwdb.d/60-keyboard.hwdb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/hwdb.d/20-sdio-classes.hwdb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/hwdb.d/20-net-ifname.hwdb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/hwdb.d/70-mouse.hwdb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/hwdb.d/20-OUI.hwdb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/hwdb.d/20-pci-vendor-model.hwdb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/hwdb.d/20-vmbus-class.hwdb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/hwdb.d/70-pointingstick.hwdb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/hwdb.d/20-sdio-vendor-model.hwdb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/hwdb.d/70-touchpad.hwdb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/hwdb.d/20-acpi-vendor.hwdb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/hwdb.d/60-sensor.hwdb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/hwdb.d/70-joystick.hwdb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/hwdb.d/60-evdev.hwdb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/hwdb.d/20-usb-vendor-model.hwdb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/hwdb.d/20-pci-classes.hwdb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/hwdb.d/20-bluetooth-vendor-product.hwdb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: systemd-1_244.3-r0 do_package_qa: QA Issue: systemd: /lib/libnss_myhostname.so.2 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: systemd-1_244.3-r0 do_package_qa: QA Issue: systemd: /lib/libudev.so.1.6.16 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/libudev.so.1 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: systemd-1_244.3-r0 do_package_qa: QA Issue: systemd: /lib/systemd/systemd-vconsole-setup is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-vconsole-setup.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: systemd-1_244.3-r0 do_package_qa: QA Issue: systemd: /etc/udev/udev.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /etc/udev/rules.d/touchscreen.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /sbin/udevd is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /sbin/udevadm is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/libexec/udevadm is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/share/bash-completion/completions/udevadm is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /bin/systemd-hwdb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /bin/udevadm is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/ata_id is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/scsi_id is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/mtd_probe is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/fido_id is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/v4l_id is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/cdrom_id is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/60-persistent-input.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/60-persistent-v4l.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/64-btrfs.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/60-evdev.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/60-cdrom_id.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/80-drivers.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/50-udev-default.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/61-autosuspend-manual.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/75-net-description.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/60-persistent-alsa.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/60-sensor.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/80-net-setup-link.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/90-vconsole.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/60-drm.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/75-probe_mtd.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/78-sound-card.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/70-touchpad.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/60-fido-id.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/70-power-switch.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/60-block.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/60-serial.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/70-mouse.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/60-persistent-storage-tape.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/60-input-id.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/60-persistent-storage.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/70-joystick.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/udev/rules.d/60-autosuspend-chromiumos.rules is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-udevd is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/network/99-default.link is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-udevd-control.socket is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-udev-settle.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-udevd-kernel.socket is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/initrd-udevadm-cleanup-db.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-udevd.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-hwdb-update.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-udev-trigger.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/systemd-udevd.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/systemd-udev-trigger.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sockets.target.wants/systemd-udevd-control.socket is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sockets.target.wants/systemd-udevd-kernel.socket is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: systemd-1_244.3-r0 do_package_qa: QA Issue: systemd: /lib/libnss_systemd.so.2 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: systemd-1_244.3-r0 do_package_qa: QA Issue: systemd: /usr/bin/kernel-install is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/kernel/install.d/50-depmod.install is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/kernel/install.d/90-loaderentry.install is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/lib/kernel/install.d/00-entry-directory.install is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: systemd-1_244.3-r0 do_package_qa: QA Issue: systemd: /usr/bin/systemd-run is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/bin/systemd-detect-virt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/bin/systemd-cgtop is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/bin/systemd-delta is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/bin/systemd-path is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/bin/systemd-stdio-bridge is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/bin/systemd-cat is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /usr/bin/systemd-cgls is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /bin/systemd-escape is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /bin/systemd-ask-password is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /bin/systemd-inhibit is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /bin/systemd-tty-ask-password-agent is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-initctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-sleep is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-socket-proxyd is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-ac-power is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-reply-password is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/systemd-cgroups-agent is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-initctl.socket is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-ask-password-wall.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-initctl.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-ask-password-console.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-suspend.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-ask-password-console.path is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-ask-password-wall.path is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-hibernate.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/systemd-hybrid-sleep.service is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sleep.target is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/multi-user.target.wants/systemd-ask-password-wall.path is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sysinit.target.wants/systemd-ask-password-console.path is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
systemd: /lib/systemd/system/sockets.target.wants/systemd-initctl.socket is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: systemd-1_244.3-r0 do_package_qa: QA Issue: systemd: /lib/libnss_mymachines.so.2 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: st-initrd-1.0-r0 do_package: Manifest /home/Yocto/build-openstlinuxeglfs-myir-ya151c-t/tmp-glibc/sstate-control/manifest-x86_64_x86_64-nativesdk-st-image-resize-initrd.packagedata not found in myir_ya151c_t cortexa7t2hf-neon-vfpv4 cortexa7t2hf-neon cortexa7t2hf-vfp cortexa7hf-neon-vfpv4 cortexa7hf-neon cortexa7hf-vfp armv7vet2hf-neon-vfpv4 armv7vehf-neon-vfpv4 armv7vet2hf-neon armv7vehf-neon armv7vet2hf-vfp armv7vehf-vfp armv7at2hf-vfp armv7ahf-vfp armv6thf-vfp armv6hf-vfp armv5tehf-vfp armv5ehf-vfp armv5thf-vfp armv5hf-vfp allarch x86_64_x86_64-nativesdk (variant '')?
WARNING: myir-image-core-1.0-r0 do_image_complete: Missing 'EULA_FILE_ST' var : no image license copied...
WARNING: myir-image-core-1.0-r0 do_st_write_license_create_summary: IMG LIC SUM: File does not exist with open file /home/Yocto/build-openstlinuxeglfs-myir-ya151c-t/tmp-glibc/deploy/images/myir-ya151c-t/myir-image-core-openstlinux-eglfs-myir-ya151c-t.license
NOTE: Tasks Summary: Attempted 8559 tasks of which 4874 didn't need to be rerun and all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 55 seconds
Summary: There were 23 WARNING messages shown.
hui@ubuntu:/home/Yocto/build-openstlinuxeglfs-myir-ya151c-t$

复制代码

二、生成的镜像

编译完成后，会在/home/Yocto/build-openstlinuxeglfs-myir-ya151c-t/tmp-glibc/deploy/images/myir-ya151c-t文件下生成镜像文件

三、开发板烧写镜像

3.1、选择编译的镜像文件，

3.2、串口输出

四、开发板运行

显示屏显示界面

【MYD-YA15XC-T开发板】 + 7、Yocto构建开发板镜像

TLLED LV7

站长推荐 /3