All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on

On the AB at typhoon.yocto.io only LANG=en_US.UTF-8 is set. I don't know why LC_ALL or LANGUAGE need to be set on your cluster for builds to succeed. Should we link to

Signed-off-by: Trevor Gamblin <trevor.gamblin@...> --- README-Guide.md | 94 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 94 insertions(+) diff --git a/README-Guide.md

upstream vendors provided me with a git repo of ALL necessary layers with the understanding that I'd clone the repo locally and disable network access, using only our local cloned repo in

Hi Yann, I've added this one to master, thanks! I'm still playing around with the others, thanks for your patience :-)

Hi Can you try this patch ( if you are using master ) and see if that helps diff --git a/recipes-devtools/clang/clang_git.bb b/recipes-devtools/clang/clang_git.bb index b8986be..b0c81f1 100644 ---

I have posted the top level CMakeList.txt in the first post, which added a sub directory INCLUDE_DIRECTORIES(include) # Add the sources to the target add_subdirectory(src) that has one

Hello, I need Clang compiler apart from currently available default gcc compiler as I am trying to compile eBPF which will run on my custom yocto which is based on core-image-minimal. Therefore I

just noticed this is meta-virt layer, file layer.conf: # The dynamic-layers directory hosts extensions and layer-specific # modifications. # # The .bbappend and .bb files are included if the

Hello, We are pleased to announce the Yocto Project 3.2.3 (gatesgarth-24.0.3) Release is now available for

i just noticed that both of the layers meta-secure-core and meta-security: https://github.com/jiazhang0/meta-secure-core https://git.yoctoproject.org/cgit/cgit.cgi/meta-security seem to include a

Observed same error.

Thank you Chuck Wolber for valuable response. Yeah I have tried it with cleanstate on opencv and build it again but still did not worked.

Did you try doing a cleansstate on opencv and attempting the build again? ..Ch:W.. -- "Perfection must be reached by degrees; she requires the slow hand of time." - Voltaire

For Arm EXT SDK support: Can I modify the EXT SDK build env paths from “sdk-extra.conf” so as to reference the “vivado” env? Is there a way to build in support so the “module load”

Observing following error while generationg rootfs with Packages of opencv 2.4 and 3.1 RROR: opencv-3.1+gitAUTOINC+92387b1ef8-r0 do_package: Error executing a python function in exec_python_func()

Thanks for your patience… I was able to followed your advice and I am now able to build and install the Extended SDK for our Intel platform… Can you tell me when building for Arm/Xilinx

My thoughts on this after working on this for the nanopi-m4 have changed a bit: it looks like the existing kmeta system already provides us with everything we need: - the kmeta BSP mechanism already

From: Yann Dirson <yann@...> This second iteration adds support for KBUILD_DEFCONFIG=3D"", as well as a loosely-related patch to avoid touching KCONFIG_MODE. Kernel weight: - standard

From: Yann Dirson <yann@...> This patch provides "standard" and "tiny" BSP. There is still much work to be done in dispatching feature to individual scc files - the more boards we can