Hi, I happen to have this recipe lying around. I have not upstreamed it for some reason (probably lack of time and I have not been using this package at the end, so

dhcp has been removed, thus removing its bbappend file. Signed-off-by: Chen Qi <Qi.Chen@...> --- recipes-connectivity/dhcp/dhcp_%.bbappend | 1 -

Update: I could able to see the e2fsprogs-native binaries generated under the below path. build/tmp/sysroots-components/x86_64/e2fsprogs-native/sbin The PATH variable in the file

Okay heres the bitbake file, the archive manually extracts to, but if i run bitbake nut SECTION = "console/network" DESCRIPTION = "Network UPS Tools is a collection of programs which provide a

Hi I wrote a recipe for adding a library to my image it compile correctly but I have issues in installing it and I got "-dev package contains non-symlink .so" error. I know default method for install

Hi There Thanks for your reply.As I already mentioned in my original post, this dependency is already present in the wic-tools BB file. The git log also shows the same as below commit

it seems you might be missing below commit https://git.openembedded.org/openembedded-core/commit/?id=d0ebcf62109d6a131e02cd4c0f04bba203ed6579 <hariprasath.gujulanelango@...> wrote:

Hello all I am trying to build Yocto based distribution for a custom target based on I.MX8. While creating the target image, I am facing the below error. The wic-tools recipe file already has

Yocto Technical Team Minutes, Engineering Sync, for September 1, 2020 archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == disclaimer == Best efforts are

Hello, we're using dunfell poky release and we need to bump meson from 0.53.2 to 0.55 because of cuda cross compilation issues in 0.53.2. After bump we start seeing build problem in glib-2.0 which

Hello, we're using dunfell poky release and we need to bump meson from 0.53.2 to 0.55 because of cuda cross compilation issues in 0.53.2. After bump we start seeing build problem in glib-2.0 which

Hello all! Yocto Project is pleased to announce the Yocto Project Virtual Summit 2020, a technical conference for engineers, open source technologists, students and academia in the OSS space.

Hello all! Yocto Project is pleased to announce the Yocto Project Virtual Summit 2020, a technical conference for engineers, open source technologists, students and academia in the OSS space.

Yocto Technical Team Minutes, Engineering Sync, for September 1, 2020 archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == disclaimer == Best efforts are

Enable buildhistory in both builds https://www.yoctoproject.org/docs/3.1/dev-manual/dev-manual.html#enabling-and-disabling-build-history once you have it enabled build the images (assuming you are

Hi Developers, I am migrating my code from Yocto Thud (4.19) Kernel to Yocto Zeus (5.4) Kernel. The recipes and conf files are essentially the same, but I am seeing a substantial increase in the

Hi, I'm using Rocko yocto for my project, in this when I'm including dahdi-linux I'm getting unneeded files error. Error logs: ERROR: dahdi-linux-3.1.0-r0 do_package: QA Issue: dahdi-linux:

Shared recipe should be the same as one from meta-oe :). So you can include it in your image and it should be build then. BR, marek -- as simple and primitive as

Hi Khem, thanks for your reply! Now I am a bit confused. Marek has send me another recipe: Do you know if that is allready fixed for kernel 5,2+ ? Best regards!

From: Mingli Yu <mingli.yu@...> Starting with GCC >= 10.x, -fno-common is used as default instead of -fcommon. Make the function definiton extern to fix the build failure. Set the default