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
🙈️ 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
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
nd effort!
Am Mittwoch, dem 05.02.2025 um 15:38 + 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
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
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
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
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
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
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
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:"
Kernel packages may not always use the kernel-module- prefix. However,
those listed in DEPENDS will consistently add Module.symvers to the
STAGING_INCDIR.
Signed-off-by: Daniel Chaves
---
meta/classes-recipe/module.bbclass | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
dif
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.
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
Daniel via
lists.yoctoproject.org<http://lists.yoctoproject.org>
mailto:vrag...@lists.yoctoproject.org>>
wrote:
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
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
16 matches
Mail list logo