another data point, matches exactly what i'm referring to: https://github.com/curl/curl/issues/9055 rday

on admittedly unsupported ubuntu 22.04 platform but it's clear this is a known issue as it's pretty much identical to what one reads here:

in your fortran app recipe you have to add DEPENDS = "libgfortran"

Hello, I'm trying to compile libgfortran for a Xilinx Zynq SoC, which uses the arm-xilinx-linux-gnueabi toolchain. I have added FORTRAN:forcevariable = ",fortran" to my local.conf, which causes

This issue is understood, documented and resolved so I closed the defect with a short explanation. ../Randy -- # Randy MacLeod# Wind River Linux

Maybe ‘deprecated’ isn’t quite the right word to use here. However, meta-gpl2 is unmaintained. It has no active maintainers, and is worked on only when absolutely needed: in the last year

Where and how the decision was made? Alex

meta-gplv2 is deprecated, so remove it from the autobuilder in master. Signed-off-by: Ross Burton <ross.burton@...> --- config.json | 11 ----------- 1 file changed, 11 deletions(-) diff --git

The meta-gplv2 layer is deprecated in master, so remove it from the check-layer job. Signed-off-by: Ross Burton <ross.burton@...> --- config.json | 5 +---- 1 file changed, 1 insertion(+), 4

Re-adding yocto@. It’s not always a trivial “this version”, there’s a fairly complex expression in the CVE (see the CPE entry) which needs to be evaluated. Or there may not be a fixed

Hello Gaurav, The CVE STATUS "Patched" means that there was an issue in the past, but it is either fixed or otherwise mitigated. Open issues are marked as "Unpatched". If you'd like to see only

is there anything i am missing here .

Hi all I am building a yocto BSP for an Intel system. The system is using rauc for updating and contains three sections, rescue, A and B, where A/B is the actual SW running. Since the system is Intel

Hi Rashmi, You only need to add ;protocol=https to your SRC_URI which starts with git://. git:// in SRC_URI is NOT the protocol used to download the sources, it is the way Bitbake knows which

Hello, I am building a software image and it fails when fetching a repository form GitLab. https://github.com/ajstarks/openvg Initially I was using git:// protocol to fetch the files but due to the

Current Dev Position: YP 4.1 M2 Next Deadline: 11th July 2022 YP 4.1 M2 Build Next Team Meetings: Bug Triage meeting Thursday July 7th 7:30 am PDT

I’m not sure I understand what your concern is. We have version 1.6.0, the CVE was fixed in 1.3.3, so the security issue has been patched. The status is “patched” even if there’s not a

I used the cve check class by including it in the local.conf and then ran the bitbake build process for my image. I got a log of all the detected CVEs in the packages used in the build. However, on

Perhaps it is time we split the master build from the stable releases and used different buildtools tarballs for them? That has it's own set of challenges of course too. Cheers, Richard

This addresses the failure with wayland 1.21: | ../wayland-1.21.0/tests/meson.build:2:1: ERROR: Problem encountered: -Dtests=true requires -Dlibraries=true Signed-off-by: Alexander Kanavin