Hi, <apoplawski=kan-therm.com@...> wrote: OK so adding PSEUDO_DISABLE=1 doesn't solve an issue. It's the same like before. Any idea what was changed and why it was working in

Hi, I have a similar problem. First, you need to disable pseudo before executing. On begin of the line containing sudo cryptsetup add environment variable definition: PSEUDO_DISABLED=1. This,

Hi, In my layer I have two older versions of glibc in addition to the 2.35 provided by kirkstone, and a the global conf for the build directory sets GLIBCVERSION to select which one to use.

I am new to Yocto, and am trying to build core-image-minimal with multilib using the latest Kirkstone release. The image builds ok without the multilib config entries, but adding the entries

Current Dev Position: YP 4.2 M1 Next Deadline: 5th December 2022 YP 4.2 Build Next Team Meetings: Bug Triage meeting Thursday November 24th 7:30 am PDT

I think your major concern is “I have multiple version for opencv, but bibake installed the version 3.4.3 default.”. It’s because layers have different layer priorities specified by

You need to look up PREFERRED_VERSION rather. Alex

I have multiple version for opencv, but bibake installed the version 3.4.3 default.=== Matching recipes: ===opencv: meta-rcar-gen3-adas

Hi, I have a class where I create a custom image with cryptsetup and for that purpose I'm using sudo. AFAIK using sudo in image creation should be OK as it runs in pseudo. sudo calls works fine in

All, YP M+ or high bugs which moved to a new milestone in WW47 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 14896 Current autobuilder code

All, The below were the owners of enhancements or bugs closed during the last

All, Below is the list as of top 31 bug owners as of the end of WW47 of who have open medium or higher bugs and enhancements against YP 4.2. There are 108 possible work days left until the final

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

Hello, build mingw sdk get follow error: configure: error: linux/capability.h is required in order to build libcap-ng $ SDKMACHINE=x86_64-mingw” bitbake my-image -c populate_sdk We use kernel

Applied to meta-rockchip master (with Quentin's Reviewed-by). Thanks!

Applied to meta-rockchip master, kirkstone, and honister. Thanks!

Hi Sébastien, The logic seems reasonable to me, yes. We could have used the deploy directory instead and depend on the do_deploy task instead of the do_populate_sysroot but I think it is actually

In this case I have no idea unfortunately. Does a regular kernel work? Alex

You have to find them yourself with gut bisect I would say. Too many things have changed. Alex

I see. Any particular fixes you can point me to that may be relevant also for musl?