Yocto build issue for 5.7.2 version

Hi Team,
I’m trying to build Torizon core docker (version 5.7.2) using YOCTO . I followed the steps mentioned in the website. I’m getting the below error while building the docker, Kindly help me out in resolving the below error.

WARNING: libdrm-2.4.102.imx-r0 do_fetch: Failed to fetch URL git://source.codeaurora.org/external/imx/libdrm-imx.git;protocol=https;nobranch=1;branch=libdrm-imx-2.4.102, attempting MIRRORS if available
ERROR: libdrm-2.4.102.imx-r0 do_fetch: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export DBUS_SESSION_BUS_ADDRESS=“unix:path=/run/user/1002/bus”; export PATH=“/home/servicebuild4/Desktop/Yocto/torizon-core-v2/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/servicebuild4/Desktop/Yocto/torizon-core-v2/build/tmp/work/aarch64-mx8mp-tdx-linux/libdrm/2.4.102.imx-r0/recipe-sysroot-native/usr/bin/python3-native:/home/servicebuild4/Desktop/Yocto/torizon-core-v2/layers/openembedded-core/scripts:/home/servicebuild4/Desktop/Yocto/torizon-core-v2/build/tmp/work/aarch64-mx8mp-tdx-linux/libdrm/2.4.102.imx-r0/recipe-sysroot-native/usr/bin/aarch64-tdx-linux:/home/servicebuild4/Desktop/Yocto/torizon-core-v2/build/tmp/work/aarch64-mx8mp-tdx-linux/libdrm/2.4.102.imx-r0/recipe-sysroot/usr/bin/crossscripts:/home/servicebuild4/Desktop/Yocto/torizon-core-v2/build/tmp/work/aarch64-mx8mp-tdx-linux/libdrm/2.4.102.imx-r0/recipe-sysroot-native/usr/sbin:/home/servicebuild4/Desktop/Yocto/torizon-core-v2/build/tmp/work/aarch64-mx8mp-tdx-linux/libdrm/2.4.102.imx-r0/recipe-sysroot-native/usr/bin:/home/servicebuild4/Desktop/Yocto/torizon-core-v2/build/tmp/work/aarch64-mx8mp-tdx-linux/libdrm/2.4.102.imx-r0/recipe-sysroot-native/sbin:/home/servicebuild4/Desktop/Yocto/torizon-core-v2/build/tmp/work/aarch64-mx8mp-tdx-linux/libdrm/2.4.102.imx-r0/recipe-sysroot-native/bin:/home/servicebuild4/Desktop/Yocto/torizon-core-v2/layers/openembedded-core/bitbake/bin:/home/servicebuild4/Desktop/Yocto/torizon-core-v2/build/tmp/hosttools”; export HOME=“/home/servicebuild4”; LANG=C git -c core.fsyncobjectfiles=0 clone --bare --mirror https://source.codeaurora.org/external/imx/libdrm-imx.git /home/servicebuild4/Desktop/Yocto/torizon-core-v2/downloads/git2/source.codeaurora.org.external.imx.libdrm-imx.git --progress failed with exit code 128, no output
ERROR: libdrm-2.4.102.imx-r0 do_fetch: Bitbake Fetcher Error: FetchError(‘Unable to fetch URL from any source.’, ‘git://source.codeaurora.org/external/imx/libdrm-imx.git;protocol=https;nobranch=1;branch=libdrm-imx-2.4.102’)
ERROR: Logfile of failure stored in: /home/servicebuild4/Desktop/Yocto/torizon-core-v2/build/tmp/work/aarch64-mx8mp-tdx-linux/libdrm/2.4.102.imx-r0/temp/log.do_fetch.23500
ERROR: Task (/home/servicebuild4/Desktop/Yocto/torizon-core-v2/build/conf/…/…/layers/meta-toradex-nxp/backports/recipes-graphics/drm/libdrm_2.4.102.imx.bb:do_fetch) failed with exit code ‘1’

Greetings @sapthagiri,

It appears the issue is related to this: https://bye.codeaurora.org/

That recipe pointed to a repo hosted on codeaurora, which as you can see no longer exists. NXP who maintains the repo now hosts their repos on Github. You can try modifying/updating the recipe so that it now points to the new location.

Another option is to configure mirrors in your build like so: toradex-mirrors.bbclass « classes - meta-toradex-demos.git - Toradex BSP layer, recipes for the demo images

These mirrors are currently not configured in the TorizonCore build by default.

Best Regards,
Jeremias

1 Like

@ sapthagiri

I am not sure about the Torizon Core Builder but I was facing the same issue while compiling Yocto using Bitbake based on BSP 5.7.2.

I have added these lines to the conf/local.conf file and it solved the problem:

MIRRORS += " \
    git://source.codeaurora.org/external/imx/ git://github.com/nxp-imx/;protocol=https \n \
    https://source.codeaurora.org/external/imx/ https://github.com/nxp-imx/ \n \
    http://source.codeaurora.org/external/imx/ http://github.com/nxp-imx/ \n \
    gitsm://source.codeaurora.org/external/imx/ gitsm://github.com/nxp-imx/;protocol=https \n \
"

Hope it works for you, too.

Regards,
Aditya

2 Likes