@snorkys

Как исправить ошибку в создании образа Yocto с слоем dotnet?

Собственно уже не первый день пытаюсь собрать образ через Yocto Project под 32bit архитектуру arm с добавлением слоя dotnet.
Репозитории использую:
meta-dotnet-core, meta-openembedded, meta-security, poky

Слои из конфига bblayers.conf:
POKY_BBLAYERS_CONF_VERSION = "2"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
  /home/yocto/sources/poky/meta \
  /home/yocto/sources/poky/meta-poky \
  /home/yocto/sources/poky/meta-yocto-bsp \
  /home/yocto/sources/meta-openembedded/meta-oe \
  /home/yocto/sources/meta-openembedded/meta-multimedia \
  /home/yocto/sources/meta-openembedded/meta-networking \
  /home/yocto/sources/meta-openembedded/meta-python \
  /home/yocto/sources/meta-openembedded/meta-perl \
  /home/yocto/sources/meta-security \
  /home/yocto/sources/meta-dotnet-core \
  "

Изменения в конфиге local.conf :
MACHINE ?= "qemuarm"
CORE_IMAGE_EXTRA_INSTALL ?= "dotnet-core"

Сама ошибка при попытке сборки bitbake core-image-minimal:
Build Configuration:
BB_VERSION           = "1.40.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "arm-poky-linux-gnueabi"
MACHINE              = "qemuarm"
DISTRO               = "poky"
DISTRO_VERSION       = "2.6.4"
TUNE_FEATURES        = "arm armv5 thumb dsp"
TARGET_FPU           = "soft"
meta                 
meta-poky            
meta-yocto-bsp       = "thud:6c5a847a4514b8c1729511aae96374eb8679a152"
meta-oe              
meta-multimedia      
meta-networking      
meta-python          
meta-perl            = "thud:446bd615fd7cb9bc7a159fe5c2019ed08d1a7a93"
meta-security        = "thud:31dc4e7532fa7a82060e0b50e5eb8d0414aa7e93"
meta-dotnet-core     = "master:711d271b1a2284ea7cbb5b5ee519b8bec8199ada"

Initialising tasks: 100% |######################################################################################################################################################################################################################################################################################| Time: 0:00:01
Sstate summary: Wanted 3 Found 0 Missed 3 Current 763 (0% match, 99% complete)
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: dotnet-core-6.0.2-r0 do_package_qa: QA Issue: dotnet-core: /dotnet-core/usr/lib/ld-linux-armhf.so.3 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
dotnet-core: /dotnet-core/usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.2/ld-linux-armhf.so.3 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
ERROR: dotnet-core-6.0.2-r0 do_package_qa: QA Issue: /usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.2/libmscordbi.so contained in package dotnet-core requires ld-linux-armhf.so.3(GLIBC_2.4), but no providers found in RDEPENDS_dotnet-core? [file-rdeps]
ERROR: dotnet-core-6.0.2-r0 do_package_qa: QA Issue: /usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.2/libmscordbi.so contained in package dotnet-core requires ld-linux-armhf.so.3, but no providers found in RDEPENDS_dotnet-core? [file-rdeps]
ERROR: dotnet-core-6.0.2-r0 do_package_qa: QA run found fatal errors. Please consider fixing them.
ERROR: dotnet-core-6.0.2-r0 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in: /home/yocto/build/tmp/work/armv5e-poky-linux-gnueabi/dotnet-core/6.0.2-r0/temp/log.do_package_qa.3051893
ERROR: Task (/home/yocto/sources/meta-dotnet-core/recipes-runtime/dotnet-core/dotnet-core_6.0.2.bb:do_package_qa) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2481 tasks of which 2480 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/yocto/sources/meta-dotnet-core/recipes-runtime/dotnet-core/dotnet-core_6.0.2.bb:do_package_qa
Summary: There were 2 WARNING messages shown.
Summary: There were 4 ERROR messages shown, returning a non-zero exit code.
  • Вопрос задан
  • 114 просмотров
Пригласить эксперта
Ваш ответ на вопрос

Войдите, чтобы написать ответ

Войти через центр авторизации
Похожие вопросы