I will need to test but, that appears to have done the trick... root@sbcb-default gdb clinfo GNU gdb (GDB) 8.3.1 Copyright (C) 2019 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or

Hello: I’d like to build clinfo w/ “-g” option to do some debugging with GDB… I am looking at: meta-openembedded/meta-oe/recipes-support/opencl/clinfo_2.2.18.04.06.bb I created a “bbapend” file to mod

Thanks Tim, subscribed…

Thanks Richard, will do…

So, my only change to my build is the INHERIT =+ “cve-check”… No issue seen until this line added… Can someone tell me why when I build from scratch, clean, I see the following error ? Who’s certifica

When building in cve-check to see what is reported, it generated all blank/empty report files… Can someone explain this ?, my local.conf does have the proper modification (INHERIT += “cve-check”). 10:

I am currently building in cve-check to see what is reported, and I was curious if Yocto might provide any CVE based patch repositories ? Is there a yocto page somewhere that goes over this side of th

Thanks again...

When you say: " you might have to look into this kernel recipe and ensure that it has enabled merging configs feature from kernel" Are you talking about inheriting from "kernel-yocto" in order to work

Under my aarm64 platform ../recipes-core/images I have a file “aiox-swdebugfs.inc” Which basically contains: EXTRAPATHS_prepend := "$(THISDIR}/files:" LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/

How do override/modify the kernel .config file generated when building for linux-intel-rt (PREEMPT_RT) ? I dumped /proc/config.gz and it is always the default configuration my changes/updates are neve

I have 2 platforms one with a standard kernel the other using PREEMPT_RT kernel… both work as expected. All things being equal, when I add docker container support to both platforms, the standard kern

Never mind was able to work this out…

I am building with zeus 3.0.4, Intel based… I trying to learn how to introduce a patch to files brought in by packages under “dynamic –layers”… my bbappend appears not to be applying my test patch (ev

Is there a CPP conflict due to : ./tmp/work/corei7-64-poky-linux/intel-graphics-compiler/1.0.11-r0/git/inc/common/UFO/portable_compiler.h Is this a name space issue ?

Anybody ? It appears to be a CPP issue in the IGC code… but not sure why. The “__syscall_slong_t” definition appears to be getting resolved out correctly when I replace the array with individual varia

I am building zeus with basic OpenCL support for centos 7.x, and using GNU 8.3.1 compiler and see the following Error when IGC is built, I see the same error when building with GNU 5.3.1… Is this a kn

Thank you, this explains/fixes an anomaly I saw while building under Jenkins...

How does yocto determine the locations/paths to the “hosttools” ? Is there precedence order established for locating the “hosttools” ?, and how would one update the search list so as to pick the tool

Is it possible to use BBMASK to remove from builds ?