[yocto] cargo does not build currently

Hi all Some problem with the build of cargo just popped up. I am doing currently builds on the master branches. It turns out after a sync of my sources cargo does not build anymore. It spits weird error messages that it cannot find the crate for libc: can't find crate for `libc` Somehow thing

Re: [yocto] PROVIDES virtual/kernel but was skipped: incompatible with machine

🙈️ It was an error in the MACHINEOVERRIDES assignment. Sorry for the noise. Am Freitag, dem 07.02.2025 um 11:50 + schrieb David Daniel via lists.yoctoproject.org: > Hi all > I have a weird problem with my image that just popped up - I have a > custom machine (called bf133) that pro

[yocto] PROVIDES virtual/kernel but was skipped: incompatible with machine

Hi all I have a weird problem with my image that just popped up - I have a custom machine (called bf133) that provides the kernel recipe (as linux-bf133) wherein I specify the the machine as compatible. For some reason though bitbake spits an error that the kernel is incompatible with that machine

Re: [yocto] imx-boot / u-boot for iMX95

nd effort! Am Mittwoch, dem 05.02.2025 um 15:38 +0000 schrieb David Daniel via lists.yoctoproject.org: > Thanks a lot! I will try that tomorrow and see what I can find out. > > Am Mittwoch, dem 05.02.2025 um 15:15 +0100 schrieb Gyorgy Sarvari: > > One generic thought, which may

Re: [yocto] imx-boot / u-boot for iMX95

etween the recipes. These signatures supposed to > contain most (all?) relevant functions, variables and their values > used > for the task. At the first time I'd especially concentrate on > variable > names containing "BOOT", and maybe on the compiler flags. > &g

Re: [yocto] imx-boot / u-boot for iMX95

Thank you for your inputs! I can see that both imx-boot binaries begin with the same hex content, the tenth byte whatsoever is 01 in my build and 00 in the build from Variscite. Then from the 23rd byte some more differences and then the same bytes again. Lots of blocks with the same content but sti

[yocto] imx-boot / u-boot for iMX95

Hi all We received an iMX95 Dart evalkit board from Variscite and I am preparing our bsp layer for the machine that will be derived from that board. Now I wanted to integrate u-boot and imx-boot into our image and went ahead and took a look at Variscites layers - they already provide some setup for

Re: [yocto] kernel append file with dts in SRC_URI and subdir

rieb Quentin Schulz: > Hi David, > > On 1/27/25 12:12 PM, David Daniel via lists.yoctoproject.org wrote: > > Hi > > > > I am trying to figure out why the following snippet of a kernel > > .bbappend file does not populate the cus

Re: [yocto] kernel append file with dts in SRC_URI and subdir

it doesn't check if the content conflicts or not :) > > On 27.01.25 15:33, David Daniel via lists.yoctoproject.org wrote: > > Ah I see. That's weird though, as the name is unique, it shouldn't > > collide with any existing file. But adding as a patch sounds > > reas

Re: [yocto] kernel append file with dts in SRC_URI and subdir

ng, it is possible that your dts > file > overwritten by the actual kernel source. > > Try adding it as a patch? > > On 27.01.25 12:12, David Daniel via lists.yoctoproject.org wrote: > > Hi > > > > I am trying to figure out why the following snippet of a

[yocto] kernel append file with dts in SRC_URI and subdir

Hi I am trying to figure out why the following snippet of a kernel .bbappend file does not populate the custom device tree source file in the proper location: FILESEXTRAPATHS:prepend := "${THISDIR}/files:"

Re: [yocto] vmlinux has relocations in .text

s up. Does this now mean that my build ignores the QA of textrel for all packages? Am Dienstag, dem 06.08.2024 um 10:58 -0700 schrieb Khem Raj: On Tue, Aug 6, 2024 at 2:49 AM David Daniel via lists.yoctoproject.org<http://lists.yoctoproject.org> mailto:vrag...@lists.yoctoproject.

[yocto] vmlinux has relocations in .text

Hi everybody I am updating my setup for a custom system and I'm getting an error now with the kernel. Everything works until packaging of the kernel, I now get the error that the kernel image contains relocations in .text: ERROR: linux-bf133-6.6.44-r0 do_package_qa: QA Issue: kernel-vmlinux: ELF

Re: [yocto] Missing patch status (upstream status)

Am Montag, dem 05.08.2024 um 16:02 +0300 schrieb Alexander Kanavin: Can you publish the layer the patch is in? Or at least attach the complete patch file and recipe that bitbake is complaining about. It’s a simple check with a regex and should just work. Alex On Mon 5. Aug 2024 at 15.37, David

[yocto] Missing patch status (upstream status)

Hi all I realized that my project does not build anymore. Now a patch status is required - but even when I put it in (the patch status), the error does not go away: ERROR: bootcommander-1.0-r0 do_patch: QA Issue: Missing Upstream-Status in patch /mnt/data/yocto/bf133/meta-bf133/recipes-bsp/bootco

Re: [yocto] SPDX generation fails every second time the image is created

: David Daniel Cc: yocto@lists.yoctoproject.org Betreff: Re: [yocto] SPDX generation fails every second time the image is created David, I just pushed a patch to the ML to provide better debugging when this happens; it will at least tell us which document is missing. Is there any way you can run

Re: [yocto] Documentation: How to build multiple packages from one source repository

Am Donnerstag, dem 14.09.2023 um 14:01 +0200 schrieb Alexander Kanavin: > On Thu, 14 Sept 2023 at 13:57, David Daniel > wrote: > > I could create two recipes - but that would mean, the same sources > > are > > downloaded twice, am I right? > > Two recipes seem

[yocto] Documentation: How to build multiple packages from one source repository

Hi everybody I am a newcomer currently trying to figure out, how I can build a library and a binary from one source repository in one recipe. The reason for the "one recipe" is that both, the library and the binary come from the same source repository (OpenBLT). The problem is, that the project is

Re: [yocto] SDK build generally broken?

ing syntax: TOOLCHAIN_HOST_TASK:append = " nativesdk-cmake" That was why in my case the whole TOOLCHAIN_HOST_TASK was completely overwritten with nativesdk-cmake. Regards Dave Am Mittwoch, dem 23.08.2023 um 15:20 + schrieb David Daniel: > Thanks a lot for your answers and your t

[yocto] Asking for root password with debug-tweaks, empty-root-password and serial-autologin-root

Hello I am having a strange issue with the image that is asking for root password, even though debug-tweaks is set. Since this did stopped working I started setting empty-root-password and serial-autologin-root in despair - but I always get asked for a root password that is not set, so I can neve

Re: [yocto] SDK build generally broken?

. At least here adding this task breaks the SDK and it is not needed at all. So I am happily building again. Best Regards David Am Dienstag, dem 22.08.2023 um 09:36 +0100 schrieb Richard Purdie: > On Tue, 2023-08-22 at 06:58 +, David Daniel wrote: > > Thanks for your reply! I cannot t

[yocto] SDK build generally broken?

Hello everybody Has anyone successfully built an SDK lately? I cannot build any SDK, neither for my image nor for core-image-minimal. If I define my own image I get the error (I already wrote - nobody any idea?) that the dummy-sdk package is to be built for a different architecture: x86_64_nati

[yocto] package target-sdk-provides-dummy-1.0-r0.sdk_provides_dummy_target is intended for a different architecture

Hi there I am new to Yocto and I am still struggling to build the SDK - I am on the master branch, after I had different problems with missing dependencies and configure failures in mickledore I went to master. Here I can successfully build core-image-full-cmdline without problems. Everything is f

[yocto] Cannot build the SDK anymore

Hi there I have a problem with a fresh build in that I was able to successfully build the image and the SDK. After changing some options (unfortunately I don't remember what 🙈️) I now get an error trying to build the SDK that the «sdk_provides_dummy_target» is for a different architecture. I foun