查看: 7051|回复: 0

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

[复制链接]
  • TA的每日心情
    开心
    4 天前
  • 签到天数: 1082 天

    连续签到: 3 天

    [LV.10]以坛为家III

    发表于 2021-12-14 21:45:09 | 显示全部楼层 |阅读模式
    分享到:
         使用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、编译输出过程:
    1. hui@ubuntu:/home/Yocto/build-openstlinuxeglfs-myir-ya151c-t$ bitbake myir-image-core
    2. NOTE: Started PRServer with DBfile: /home/Yocto/build-openstlinuxeglfs-myir-ya151c-t/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 35221, PID: 38995
    3. Parsing recipes: 100% |######################################################################################################################################################################| Time: 0:01:42
    4. Parsing of 2650 .bb files complete (0 cached, 2650 parsed). 3847 targets, 116 skipped, 0 masked, 0 errors.
    5. NOTE: Resolving any missing task queue dependencies

    6. Build Configuration:
    7. BB_VERSION           = "1.46.0"
    8. BUILD_SYS            = "x86_64-linux"
    9. NATIVELSBSTRING      = "ubuntu-16.04"
    10. TARGET_SYS           = "arm-ostl-linux-gnueabi"
    11. MACHINE              = "myir-ya151c-t"
    12. DISTRO               = "openstlinux-eglfs"
    13. DISTRO_VERSION       = "3.1-snapshot-20211214"
    14. TUNE_FEATURES        = "arm vfp cortexa7 neon vfpv4 thumb callconvention-hard"
    15. TARGET_FPU           = "hard"
    16. DISTRO_CODENAME      = "dunfell"
    17. ACCEPT_EULA_myir-ya151c-t = "1"
    18. GCCVERSION           = "9.%"
    19. PREFERRED_PROVIDER_virtual/kernel = "linux-myir"
    20. meta-oe              
    21. meta-gnome           
    22. meta-xfce            
    23. meta-initramfs      
    24. meta-multimedia      
    25. meta-networking      
    26. meta-webserver      
    27. meta-filesystems     
    28. meta-perl            
    29. meta-python         
    30. meta-st-stm32mp      
    31. meta-qt5            
    32. meta-st-openstlinux  = "<unknown>:<unknown>"
    33. meta-myir-st-tiny    = "master:8791ebc550f9737384568077468a7dc30827965b"
    34. meta                 = "<unknown>:<unknown>"

    35. Initialising tasks: 100% |###################################################################################################################################################################| Time: 0:00:18
    36. Sstate summary: Wanted 3107 Found 2244 Missed 863 Current 0 (72% match, 0% complete)
    37. NOTE: Executing Tasks
    38. 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]
    39. 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]
    40. 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]
    41. 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
    42. 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
    43. 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
    44. 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
    45. 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
    46. 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]
    47. 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
    48. 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
    49. 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
    50. 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
    51. 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
    52. 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
    53. 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
    54. 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
    55. 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
    56. 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
    57. 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
    58. 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
    59. 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
    60. 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
    61. systemd: /sbin/telinit is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
    62. systemd: /sbin/runlevel is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
    63. systemd: /sbin/resolvconf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
    64. systemd: /sbin/halt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
    65. systemd: /sbin/reboot is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
    66. systemd: /sbin/shutdown is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
    67. systemd: /sbin/init is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
    68. systemd: /sbin/poweroff is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
    69. 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
    70. 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
    71. 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
    72. 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
    73. 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
    74. 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
    75. 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
    76. 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
    77. 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
    78. 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
    79. 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
    80. 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
    81. 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
    82. 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
    83. 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
    84. 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
    85. 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
    86. 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
    87. 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
    88. 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
    89. 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
    90. 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
    91. 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
    92. 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
    93. 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
    94. 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
    95. 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
    96. 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
    97. 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
    98. 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
    99. 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
    100. 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
    101. 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
    102. 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
    103. 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
    104. 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
    105. 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
    106. 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
    107. 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
    108. 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
    109. 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
    110. 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
    111. 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
    112. 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
    113. 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
    114. 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
    115. 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
    116. 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
    117. 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
    118. 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
    119. 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
    120. 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
    121. 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
    122. 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
    123. 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
    124. 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
    125. 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
    126. 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
    127. 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
    128. 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
    129. 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
    130. 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
    131. 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
    132. 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
    133. 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
    134. 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
    135. 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
    136. 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
    137. 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
    138. 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
    139. 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
    140. 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
    141. 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
    142. 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
    143. 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
    144. 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
    145. 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
    146. 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
    147. 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
    148. 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
    149. 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
    150. 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
    151. 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
    152. 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
    153. 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
    154. 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
    155. 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
    156. 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
    157. 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
    158. 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
    159. 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
    160. systemd: /bin/loginctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
    161. systemd: /bin/journalctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
    162. 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
    163. 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
    164. 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
    165. systemd: /bin/networkctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
    166. 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
    167. systemd: /bin/systemctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
    168. 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
    169. 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
    170. 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
    171. 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
    172. 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
    173. 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
    174. 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
    175. 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
    176. 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
    177. 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
    178. 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
    179. 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
    180. 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
    181. 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
    182. 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
    183. 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
    184. 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
    185. 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
    186. 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
    187. 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
    188. 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
    189. 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
    190. 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
    191. 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
    192. 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
    193. 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
    194. 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
    195. 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
    196. 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
    197. 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
    198. 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
    199. 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
    200. 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
    201. 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
    202. 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
    203. 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
    204. 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
    205. 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
    206. 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
    207. 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
    208. 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
    209. 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
    210. 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
    211. 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
    212. 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
    213. 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
    214. 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
    215. 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
    216. 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
    217. 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
    218. 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
    219. 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
    220. 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
    221. 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
    222. 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
    223. 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
    224. 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
    225. 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
    226. 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
    227. 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
    228. 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
    229. 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
    230. 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
    231. 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
    232. 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
    233. 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
    234. 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
    235. 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
    236. 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
    237. 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
    238. 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
    239. 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
    240. 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
    241. 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
    242. 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
    243. 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
    244. 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
    245. 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
    246. 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
    247. 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
    248. 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
    249. 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
    250. 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
    251. 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
    252. 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
    253. 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
    254. 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
    255. 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
    256. 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
    257. 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
    258. 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
    259. 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
    260. 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
    261. 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
    262. 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
    263. 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
    264. 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
    265. 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
    266. 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
    267. 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
    268. 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
    269. 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
    270. 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
    271. 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
    272. 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
    273. 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
    274. 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
    275. 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
    276. 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
    277. 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
    278. 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
    279. 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
    280. 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
    281. 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
    282. 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
    283. 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
    284. 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
    285. 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
    286. 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
    287. 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
    288. 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
    289. 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
    290. 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
    291. 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
    292. 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
    293. 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
    294. 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
    295. 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
    296. 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
    297. 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
    298. 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
    299. 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
    300. 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
    301. 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
    302. 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
    303. 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
    304. 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
    305. 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
    306. 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
    307. 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
    308. 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
    309. 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
    310. 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
    311. 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
    312. 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
    313. 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
    314. 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
    315. 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
    316. 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
    317. 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
    318. 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
    319. 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
    320. 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
    321. 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
    322. 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
    323. 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
    324. 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
    325. 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
    326. 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
    327. 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
    328. 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
    329. 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
    330. 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
    331. 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
    332. 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
    333. 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
    334. 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
    335. 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
    336. 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
    337. 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
    338. 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
    339. 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
    340. 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
    341. 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
    342. 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
    343. 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
    344. 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
    345. 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
    346. 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
    347. 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
    348. 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
    349. 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
    350. 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
    351. 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
    352. 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
    353. 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
    354. 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
    355. 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
    356. 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
    357. 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
    358. 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
    359. 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
    360. 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
    361. 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
    362. 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
    363. 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
    364. 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
    365. 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
    366. 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
    367. 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
    368. 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
    369. 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
    370. 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
    371. 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
    372. 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
    373. 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
    374. 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
    375. 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
    376. 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
    377. 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
    378. 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
    379. 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
    380. 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
    381. 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
    382. 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
    383. 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
    384. 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
    385. 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
    386. 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
    387. 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
    388. 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
    389. 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
    390. 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
    391. 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
    392. 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
    393. 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
    394. 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
    395. 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
    396. 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
    397. 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
    398. 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
    399. 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
    400. 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
    401. 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
    402. 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
    403. 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
    404. 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]
    405. 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
    406. 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
    407. 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
    408. 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
    409. 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
    410. 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
    411. 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
    412. 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
    413. 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
    414. 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
    415. 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
    416. 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
    417. 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
    418. 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
    419. 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
    420. 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
    421. 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
    422. 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
    423. 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
    424. 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
    425. 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
    426. 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
    427. 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
    428. 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
    429. 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]
    430. 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
    431. 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
    432. 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
    433. 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
    434. 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
    435. 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
    436. 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
    437. 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
    438. 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
    439. 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
    440. 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
    441. 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
    442. 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
    443. 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
    444. 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
    445. 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
    446. 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
    447. 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
    448. 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
    449. 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
    450. 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
    451. 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
    452. 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]
    453. 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
    454. 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
    455. 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
    456. 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
    457. 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
    458. systemd: /bin/machinectl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
    459. 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
    460. 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
    461. 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
    462. 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
    463. 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
    464. 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
    465. 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
    466. 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
    467. 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]
    468. 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
    469. 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]
    470. 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]
    471. 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
    472. 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
    473. 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
    474. 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]
    475. 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
    476. 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
    477. 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
    478. 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
    479. 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
    480. 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
    481. 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
    482. 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
    483. 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
    484. 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
    485. 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
    486. 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
    487. 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
    488. 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
    489. 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
    490. 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
    491. 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
    492. 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]
    493. 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]
    494. 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
    495. 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]
    496. 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
    497. 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]
    498. 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
    499. 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
    500. systemd: /sbin/udevd is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
    501. systemd: /sbin/udevadm is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
    502. 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
    503. 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
    504. 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
    505. systemd: /bin/udevadm is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
    506. 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
    507. 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
    508. 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
    509. 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
    510. 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
    511. 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
    512. 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
    513. 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
    514. 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
    515. 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
    516. 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
    517. 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
    518. 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
    519. 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
    520. 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
    521. 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
    522. 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
    523. 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
    524. 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
    525. 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
    526. 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
    527. 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
    528. 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
    529. 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
    530. 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
    531. 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
    532. 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
    533. 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
    534. 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
    535. 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
    536. 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
    537. 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
    538. 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
    539. 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
    540. 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
    541. 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
    542. 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
    543. 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
    544. 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
    545. 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
    546. 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
    547. 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
    548. 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
    549. 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
    550. 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
    551. 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]
    552. 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]
    553. 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
    554. 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
    555. 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
    556. 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]
    557. 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
    558. 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
    559. 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
    560. 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
    561. 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
    562. 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
    563. 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
    564. 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
    565. 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
    566. 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
    567. 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
    568. 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
    569. 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
    570. 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
    571. 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
    572. 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
    573. 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
    574. 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
    575. 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
    576. 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
    577. 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
    578. 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
    579. 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
    580. 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
    581. 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
    582. 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
    583. 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
    584. 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
    585. 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
    586. 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
    587. 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]
    588. 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]
    589. 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 '')?
    590. WARNING: myir-image-core-1.0-r0 do_image_complete: Missing 'EULA_FILE_ST' var : no image license copied...
    591. 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
    592. NOTE: Tasks Summary: Attempted 8559 tasks of which 4874 didn't need to be rerun and all succeeded.
    593. NOTE: Writing buildhistory
    594. NOTE: Writing buildhistory took: 55 seconds

    595. Summary: There were 23 WARNING messages shown.
    596. hui@ubuntu:/home/Yocto/build-openstlinuxeglfs-myir-ya151c-t$
    复制代码

       二、生成的镜像


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


       三、开发板烧写镜像


        3.1、选择编译的镜像文件,
        111.png


        3.2、串口输出
        112.png

        四、开发板运行


        显示屏显示界面
        113.jpg
    回复

    举报

    您需要登录后才可以回帖 注册/登录

    本版积分规则

    关闭

    站长推荐上一条 1/2 下一条

    【预约|参会享"豪"礼】2025慕尼黑上海设备展
    “2025慕尼黑上海电子生产设备展”将于2025年03月26-28日上海新国际博览中心开幕诚邀您的光临!

    查看 »

    手机版|小黑屋|与非网

    GMT+8, 2025-3-4 02:52 , Processed in 0.105150 second(s), 16 queries , MemCache On.

    ICP经营许可证 苏B2-20140176  苏ICP备14012660号-2   苏州灵动帧格网络科技有限公司 版权所有.

    苏公网安备 32059002001037号

    Powered by Discuz! X3.4

    Copyright © 2001-2024, Tencent Cloud.