Hi, So after a little bit of research, I've implemented this feature in poky. The way buildroot works, is that it doesn't create any .pyc files during the build process of single packages but has a

This is a bug and this should be fixed to use full machine name for override since we do not have nezha SoC override No it’s unrelated

the SRC_URI line: SRC_URI:append:nezha = " \ ... seems odd since the machine name is actually "nezha-allwinner-d1", not just "nezha". i checked and the two listed patches there don't appear to be

It is. It was great fun to find the path to disable it when I also had this issue :) Philip >

newlib fails to compile for nios2 architecture. Work around this by using glibc instead. Signed-off-by: Jon Mason <jon.mason@...> --- meta-zephyr-bsp/conf/machine/qemu-nios2.conf | 2 ++

This series is adding Gitlab CI to meta-zephyr. I've been running a version of this on my personal gitlab for some time (see https://gitlab.com/jonmason00/meta-zephyr/-/pipelines). This will allow

Mostly stolen from meta-arm Signed-off-by: Jon Mason <jon.mason@...> --- .gitlab-ci.yml | 101 +++++++++++++++++++++++++++++++++++++ ci/96b-avenger96.yml | 6 +++

Issue being tracked at https://bugzilla.yoctoproject.org/show_bug.cgi?id=14803 Signed-off-by: Jon Mason <jon.mason@...> --- ci/base.yml | 1 + 1 file changed, 1 insertion(+) diff --git

Perhaps it’s using locked sstate which might be the reason

Hi We are pleased to announce the Yocto Project 4.0.2 Release is now available for

I am using Xilinx's Petalinux tool, which uses honister under the hood. Xilinx maintains an sstate cache for Petalinux, which is quite convenient for cutting down build times, but apparently setting

Probably, but again if you need a function from a library you include it on linker cmdline if it’s intrinsics then compiler driver doing the needed is best way Preferably without introducing

so while i'm still trying to wrap my head around all this, what *would* be the ideal resolution for this? the link above suggests the simple solution of introducing a gcc config

this would mean that you want to rely on side effects of -pthread which may work with gcc but may not work with clang or other compiler drivers. The issue you have is that some variables are needing

as i read it, this issue is also related to -pthread versus -lpthread: https://blog.jiejiss.com/A-RISC-V-gcc-pitfall-revealed-by-a-glibc-update/ rday

You shouldn't have to disable the sstate cache but glad you got it working. Which release series is that with? It does sound like there is a bug to fix somewhere in there. Cheers, Richard

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Steve Sakoman, Joshua Watt, Saul Wold, Alexandre Belloni, Paulo Neves, Richard Purdie, Aryaman Gupta, Randy Macleod,

it does indeed fix the curl build error, thanks. i haven't tested its operation yet, but getting a build was all i was after at the moment. rday

does backporting https://github.com/curl/curl/commit/50efb0822aa0e0ab165158dd0a26e65a2290e6d2 to curl help ?

Problem solved: the issue was actually that I was using a network sstate cache, and the cached output of gcc-cross did not contain gfortran. Disabling the sstate cache for gcc-cross causes gfortran to