Can't build 6.x.y from source, yocto-kernel-tools is missing

I’m trying to build a custom 6.8, but get a bitbake failure:

bitbake torizon-core-docker
Loading cache: 100% |########################################################################################################################################################################################################################################################################################| Time: 0:00:00
Loaded 4723 entries from dependency cache.
WARNING: No recipes in default available for:
/code/torizon/verdin-imx8mp/oe-core-6.x.y/build-torizon/conf/../../layers/meta-toradex-security/recipes-tpm2/tpm2-tools/tpm2-tools_%.bbappend
/code/torizon/verdin-imx8mp/oe-core-6.x.y/build-torizon/conf/../../layers/meta-toradex-nxp/recipes-bsp/imx-mkimage/imx-mkimage_1.0.bbappend
/code/torizon/verdin-imx8mp/oe-core-6.x.y/build-torizon/conf/../../layers/meta-toradex-nxp/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.20.0.imx.bbappend
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = “2.0.0”
BUILD_SYS = “x86_64-linux”
NATIVELSBSTRING = “universal”
TARGET_SYS = “aarch64-tdx-linux”
MACHINE = “verdin-imx8mp”
DISTRO = “torizon”
DISTRO_VERSION = “6.8.3-devel-20250829143243+build.0”
TUNE_FEATURES = “aarch64 armv8a crc cortexa53”
TARGET_FPU = “”
meta-toradex-torizon = “HEAD:d585dfe69d6345d1c4dd31f20efdecfacb9e38ad”
meta-toradex-security = “HEAD:2bfed3bda0e14984c0c466299a4ec2e39054cd40”
meta-toradex-distro = “HEAD:f6693039ee411b6fe29e4f4c881c200e38fb21f1”
meta-toradex-bsp-common = “HEAD:ee2f05ac1b4a475c9009dab919cbdc81b1811f0f”
meta-oe
meta-networking
meta-filesystems
meta-python
meta-perl = “HEAD:06fc0278f10d630838d703dde707bbf0e2999873”
meta-virtualization = “HEAD:3e4dba95e6b5f5f68d0b3a5899b106c89da59428”
meta-updater = “HEAD:3d57c37509fef259c5a5c150b88466ff367e305f”
meta-toradex-nxp = “HEAD:ecf38142ee883129ea3a0184b4e995fe1c5d4066”
meta-freescale = “HEAD:ccb66d5754fb3027670e15d33b5dd63daffaf2eb”
meta-freescale-3rdparty = “HEAD:48516272d97f9415e0ee3ab54a923e4c40143e69”
meta-yocto-bsp
meta-poky = “HEAD:0bf3dcef1caa80fb047bf9c3514314ab658e30ea”
meta-security = “HEAD:b9cf9cd639bc8d1b4828eb0bd012b71486d35176”
meta-toradex-ti = “HEAD:dbc38a01a31ad1e6d996e51f69df49c55de2e002”
meta-arm-toolchain
meta-arm = “HEAD:10c27f061b22af78e17a23cf540b69501afc7160”
meta-ti-bsp
meta-ti-extras = “HEAD:52018a8d730b2977d7163bf56c398905ef9115ac”
meta = “HEAD:d9f424921179a52ffe053411c44f20e44e7deba1”

Initialising tasks: 100% |###################################################################################################################################################################################################################################################################################| Time: 0:00:02
Sstate summary: Wanted 2217 Local 20 Mirrors 0 Missed 2197 Current 274 (0% match, 11% complete)
NOTE: Executing Tasks
ERROR: kern-tools-native-0.3+gitAUTOINC+2d01f24bc7-r0 do_unpack: Bitbake Fetcher Error: UnpackError(‘No up to date source found: clone directory not available or not up to date: /code/torizon/verdin-imx8mp/oe-core-6.x.y/downloads/git2/git.yoctoproject.org.yocto-kernel-tools.git; shallow clone not enabled’, ‘git://git.yoctoproject.org/yocto-kernel-tools.git;branch=master’)
ERROR: Logfile of failure stored in: /code/torizon/verdin-imx8mp/oe-core-6.x.y/build-torizon/tmp/work/x86_64-linux/kern-tools-native/0.3+gitAUTOINC+2d01f24bc7-r0/temp/log.do_unpack.1910479
ERROR: Task (/code/torizon/verdin-imx8mp/oe-core-6.x.y/build-torizon/conf/../../layers/openembedded-core/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb:do_unpack) failed with exit code ‘1’
NOTE: Tasks Summary: Attempted 889 tasks of which 865 didn’t need to be rerun and 1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 4 seconds

Summary: 1 task failed:
/code/torizon/verdin-imx8mp/oe-core-6.x.y/build-torizon/conf/../../layers/openembedded-core/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb:do_unpack
Summary: There was 1 WARNING message.
Summary: There was 1 ERROR message, returning a non-zero exit code.

This log is for trying 6.8.3.

The do_fetch fails looking for this: git://git.yoctoproject.org/yocto-kernel-tools.git;branch=master, which appears to not be on the interwebs anymore. I can’t find reference on the yocto project for why this is missing or moved or renamed, etc.

There’s a mirror I could probably use I found here: GitHub - ebe-forks/yocto-kernel-tools: Mirror of git.yoctoproject.org/yocto-kernel-tools.git, however I’m not into trusting random mirrors found on a google search.

It would be better if toradex had a fix for this that they’ve validated. For now, I’m getting by with a stock image for my testing (my real issue is validating a custom carrier board for the imx8mp using native HDMI).

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer? :+1: :-1:


Torizon OS 6.8 Build Issue with kern-tools-native

The error you’re encountering with the git://git.yoctoproject.org/yocto-kernel-tools.git repository is a known upstream issue where the Yocto Project repository has become unavailable(1).

Recommended Solution

For building custom Torizon OS images, I recommend using the containerized build approach rather than native builds, as it provides better isolation and dependency management(2).

Containerized Build Setup

  1. Set up the containerized environment(2):
mkdir ~/yocto-workdir
docker run --rm -it --name=crops -v ~/yocto-workdir:/workdir --workdir=/workdir -e MACHINE=verdin-imx8mp -e IMAGE=torizon-docker torizon/crops:kirkstone-6.x.y startup-tdx.sh
  1. The containerized build includes all necessary dependencies and should resolve the kern-tools-native fetch issues(2).

Alternative: Use TorizonCore Builder

For your use case of validating a custom carrier board with native HDMI on the iMX8MP, consider using TorizonCore Builder instead of building from source(3):

  1. Create a configuration file(3):
torizoncore-builder build --create-template
  1. Configure for your hardware by editing the generated tcbuild.yaml file(3).

  2. Build the custom image(3):

torizoncore-builder build

Build Environment Requirements

When building Torizon OS from source, ensure you have the proper prerequisites(2):

  • Linux host with Yocto/OpenEmbedded prerequisites
  • Proper Git configuration
  • Required disk space and memory

The containerized approach eliminates most host-specific dependency issues and provides a validated build environment that Toradex maintains.

Best regards, Toradex AI Assistant.

Greetings @TxSpace,

The do_fetch fails looking for this: git://git.yoctoproject.org/yocto-kernel-tools.git;branch=master, which appears to not be on the interwebs anymore.

How did you come to this conclusion? I can see and access the repository just fine at the expected URL here: Making sure you're not a bot!

Cloning the repository works fine as well. We also don’t see any issues related to yocto-kernel-tools in our automated internal builds.

Looking at your error log the issue wasn’t that the repository wasn’t found but seems to be this line:

UnpackError(‘No up to date source found: clone directory not available or not up to date: /code/torizon/verdin-imx8mp/oe-core-6.x.y/downloads/git2/git.yoctoproject.org.yocto-kernel-tools.git; shallow clone not enabled’, ‘git://git.yoctoproject.org/yocto-kernel-tools.git;branch=master’)

Some research suggest that perhaps it may be an issue with the build environment. Though nothing specific was noted as a root cause. What is your build environment like? For example are you building in a containerized environment or a Linux distro? What kind of distro?

Has this Yocto build worked for you in the past?

Best Regards,
Jeremias

Hi @TxSpace ,

I wanted to check in how this issue was going. Any questions for us on this?

Best regards,

Sorry for the delay, I had to work on another project for a while.

I’m running on ubuntu, non containerized build. I use the same environement to build 7.x.y for aquila-am69 with no issues.

Please address my question about you not being able to access: Making sure you're not a bot!

You claim you can’t access this repository and that’s the crux of your issue. But I can access this just fine.

I’m running on ubuntu, non containerized build.

What version of Ubuntu are you using?

I use the same environement to build 7.x.y for aquila-am69 with no issues.

Is it 6.x.y you are having issues building for or Verdin-imx8mp? For example can you build Verdin-imx8mp on 7.x.y? Can you build for some other machine on 6.x.y?

Best Regards,
Jeremias

I think I agree with you, there was some internet issue where momentarily that wasn’t available. I did this command to clear that package out and force the re-fetch, and it gets past that with no issue now:

bitbake -c cleanall kern-tools-native

But to specifically address your question, yes I can see the package:
ping git.yoctoproject.org
PING sanjose.wlsource.codeaurora.org (38.108.68.163) 56(84) bytes of data.
64 bytes from 38.108.68.163: icmp_seq=1 ttl=42 time=125 ms
64 bytes from 38.108.68.163: icmp_seq=2 ttl=42 time=62.1 ms
64 bytes from 38.108.68.163: icmp_seq=3 ttl=42 time=109 ms
^C
sanjose.wlsource.codeaurora.org ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2021ms
rtt min/avg/max/mdev = 62.069/98.784/125.031/26.748 ms

git ls-remote git://git.yoctoproject.org/yocto-kernel-tools.git
fe67c98d2e9b74af44d0c4b660fa18e3a95e7edd HEAD
462e7771fa78f6e399e40a9029461d3917c2724f refs/heads/danny
2bbbaaa00cc70887d6d6f745b9425890d522d240 refs/heads/denzil
2700c5d1c214766f01e68bdfa25049fa1a5960bc refs/heads/dylan
ef512be425d2309eb02e87f87fc258d1973c56fd refs/heads/dylan-test
fe67c98d2e9b74af44d0c4b660fa18e3a95e7edd refs/heads/master
4b5de9011b31ff92ba2b6e052ab818b09affd905 refs/heads/master-next
b7642a7c3f685850ffbb961313e6a593adb05370 refs/heads/master-test
89821213a5df891254f40c9ddccdcfd780d25c3f refs/heads/master-test2
83cab24662cb64e6db03e7111b4eb8932df5b6f8 refs/heads/morty
a3362549a581da6e0e8e43f5c7f23ffd05130f70 refs/heads/new-config
e3e5e2e42411c0f3c21c9d278267d99c6fd22a90 refs/heads/pyro
9bb704df0a86578b8ae1f4c85e45089bef28e026 refs/heads/tools-ng
52b06c4b040b7052b6b3fede17d14de8dea854a6 refs/meta/cgit
a04138a02644eada0d012196e5ac3db4f516114d refs/tags/danny-release
71ffb08c20022610363e68f9243350b7da020825 refs/tags/dylan-release
90598a5fae1172e3f7782a1b02f7b7518efd32c8 refs/tags/v0.3

I do have a working build now. I got an error about elfutils using deprecated flags for curl, but that was easy enough to work around by getting rid of -Werror compile flag. Thanks.

Thank you for checking and confirming. So sounds like you are all good to go then?

Best Regards,
Jeremias