Hi Alessandro, I never worked with node-red in yocto, so I can't speak specifically for that, but I encountered similar situations before. Here is what I usually do when I need to change a file in a r

Hi all, I recently upgraded my project from dunfell 3.1.5 to 3.1.6 and saw errors about pseudo path mismatches on various build machines. Removing TMPDIR solved the problem, but I did some digging to

Hi Zakaria Probably the image manifest is what you are looking for? From https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#image-generation-dev-environment : The manifest file (.m

#yocto #linux

Are you using vim to edit the files? If yes, then take a look at "backup files": https://vimhelp.org/editing.txt.html#backup Be aware that vim possibly creates swap and undo files, too. https://vimhel

#cm3 #dunfell

lists.yoctoproject.org wrote: This is the official download page for the RT patches: https://wiki.linuxfoundation.org/realtime/preempt_rt_versions There is also a section about which patches are activ

Is your kernel actually configured with cgroups support? You need CONFIG_CGROUPS and many of the child configs. From your error message I suspect you're missing CONFIG_CGROUP_DEVICE, but that's just a

lists.yoctoproject.org wrote: The log indicates that it is missing a dependency which ships "rpc/rpc.h". Some googling turned up this discussion on the openembedded-core mailing list: https://lists.op

#yocto #kernel #zeus

Hi Steve lists.yoctoproject.org wrote: I'm not sure to what lines you refer by "banner", so I just wrote my thoughts to both below. Both are probably produced by getty, either util-linux-agetty or sys

#yocto

Hi Vijay Reading and following the section about "Writing a New Recipe" in the manual is probably a good starting point: https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#new-reci

#python #toolchain

On a related note, the do_install reference in the manual gives some advice on how to use cp and tar without contaminating the build. The relevant part: Safe methods for installing files include the f

Hi Mike, lists.yoctoproject.org wrote: I usually search on the OpenEmbedded layer index: http://layers.openembedded.org/layerindex/branch/master/recipes/?q=tailscale Seems like you are right, there se

#yocto #golang

Hi JH, on Zeus it's very likely _not_ libubootenv that you need, you should try to install u-boot-fw-utils. As Yann wrote, the tools are in libubootenv since Dunfell, which is newer than Zeus.

Is there a reason why you don't use a bbappend file with your patch in it in a custom layer? Something like this: package_ver.bbappend -------------------- FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}

By googling the error message I found a thread where somebody has the same question, but I wouldn't recommend following the advice there (running the yocto build as root). How do you extract the root

I encountered the same problem when building a custom kernel. It works perfectly fine when I'm building it outside of yocto. First, I want to document the steps I followed. My yocto version is thud. I