$ bitbake-layers show-layers
NOTE: Starting bitbake server...
layer path priority
==========================================================================
meta /home/mickey/work/yocto/x86-hardknott/mb-hardknott/poky/meta 5
meta-poky /home/mickey/work/yocto/x86-hardknott/mb-hardknott/poky/meta-poky 5
meta-yocto-bsp /home/mickey/work/yocto/x86-hardknott/mb-hardknott/poky/meta-yocto-bsp 5
meta-arm-toolchain /home/mickey/work/yocto/x86-hardknott/mb-hardknott/poky/meta-arm/meta-arm-toolchain 5
meta-oe /home/mickey/work/yocto/x86-hardknott/mb-hardknott/poky/meta-openembedded/meta-oe 6
meta-python /home/mickey/work/yocto/x86-hardknott/mb-hardknott/poky/meta-openembedded/meta-python 7
meta-arm /home/mickey/work/yocto/x86-hardknott/mb-hardknott/poky/meta-arm/meta-arm 5
meta-zephyr /home/mickey/work/yocto/x86-hardknott/mb-hardknott/poky/meta-zephyr 6
mickey@yocto-build:~/work/yocto/x86-hardknott/mb-hardknott/build$ vim ./conf/local.conf
mickey@yocto-build:~/work/yocto/x86-hardknott/mb-hardknott/build$ bitbake core-image-base
Loading cache: 100% | | ETA: --:--:--
Loaded 0 entries from dependency cache.
Parsing recipes: 100% |###############################################################| Time: 0:00:34
Parsing of 2123 .bb files complete (0 cached, 2123 parsed). 3398 targets, 180 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing PROVIDES 'virtual/kernel'
linux-yocto PROVIDES virtual/kernel but was skipped: incompatible with machine microbit-v1 (not in COMPATIBLE_MACHINE)
linux-dummy PROVIDES virtual/kernel but was skipped: incompatible with host arm-poky-eabi (not in COMPATIBLE_HOST)
linux-yocto-rt PROVIDES virtual/kernel but was skipped: incompatible with machine microbit-v1 (not in COMPATIBLE_MACHINE)
linux-yocto-tiny PROVIDES virtual/kernel but was skipped: incompatible with machine microbit-v1 (not in COMPATIBLE_MACHINE)
linux-arm64-ack PROVIDES virtual/kernel but was skipped: incompatible with machine microbit-v1 (not in COMPATIBLE_MACHINE)
linux-yocto-dev PROVIDES virtual/kernel but was skipped: incompatible with machine microbit-v1 (not in COMPATIBLE_MACHINE)
linux-yocto PROVIDES virtual/kernel but was skipped: incompatible with machine microbit-v1 (not in COMPATIBLE_MACHINE)
linux-yocto-tiny PROVIDES virtual/kernel but was skipped: incompatible with machine microbit-v1 (not in COMPATIBLE_MACHINE)
linux-yocto-rt PROVIDES virtual/kernel but was skipped: incompatible with machine microbit-v1 (not in COMPATIBLE_MACHINE)
ERROR: Required build target 'core-image-base' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-base', 'virtual/kernel']
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
Last metadata expiration check: 0:00:01 ago on Mon 05 Jul 2021 03:35:45 PM UTC.
No match for argument: uim-gtk2.0
No match for argument: uim-gtk3
No match for argument: uim-xim
Error: Unable to find a match: uim-gtk2.0 uim-gtk3 uim-xim
ERROR: Logfile of failure stored in: /home/mickey/work/yocto/rpi-gatesgarth/build_kiosk/tmp/work/cortexa72-poky-linux/chromium-x11/89.0.4389.90-r0/temp/log.do_compile.3513135
NOTE: recipe chromium-x11-89.0.4389.90-r0: task do_compile: Failed
ERROR: Task (/home/mickey/work/yocto/rpi-gatesgarth/poky/meta-browser/meta-chromium/recipes-browser/chromium/chromium-x11_89.0.4389.90.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3513 tasks of which 3512 didn't need to be rerun and 1 failed.
log.do_compile.3513135である。最後の数字は実行時のプロセスIDとなっている。
ログファイルの調査
errorの文字列でログファイルを検索していくと下記のようなエラーがメッセージが見つかる。
これはmeta-clangがgatesgarthブランチ時のログ
clang-11: error: unable to execute command: Segmentation fault (core dumped)
clang-11: error: linker command failed due to signal (use -v to see invocation)
つぎのmeta-clangがmasterブランチの時のログ。
clang-12: error: unable to execute command: Segmentation fault (core dumped)
clang-12: error: linker command failed due to signal (use -v to see invocation)
# by using the ld-is-lld distro feature otherwise use gold linker
GN_ARGS += "${@bb.utils.contains('DISTRO_FEATURES', 'ld-is-lld', 'use_lld=true use_gold=false', 'use_lld=false use_gold=true', d)}
With the "read-only-rootfs" feature enabled, any attempt by the target to write to the root filesystem at runtime fails. Consequently, you must make sure that you configure processes and applications that attempt these types of writes do so to directories with write access (e.g. /tmp or /var/run).
