In some cases Wine (and Windows proper) struggle with very long paths; in particular the way that gcc invokes the 'cc1' subprogram is limited in how deep the path to the subprogram can be. This can ca

Bitbake is going to upgrade the minimum python to 3.8, so Ubuntu 18.04 needs to use buildtools tarball to remain compatible Signed-off-by: Joshua Watt <JPEWhacker@...> --- config.json | 7 ++++++

Bitbake is going to upgrade the minimum python to 3.8, so Ubuntu 18.04 needs to use buildtools tarball to remain compatible Signed-off-by: Joshua Watt <JPEWhacker@...> --- config.json | 4 +++- 1

This is correct; it's hard for upstream to test every possible combination for reproducibility. We do try to get some decent coverage, but ultimately if you really care about reproducible builds, you

Ya, I queued it in master-next. Let me run it through the AB then we can merge it <Muhammad_Hamza@...> wrote:

Ya, I'll push one now <mark.hatle@...> wrote:

The changes to split classes into global vs. image specific contexts has broken the inclusion of `wine` and `wineserver` host tools for testing MinGW SDKs. This is because testsdk is an image specific

Your set version function looks like it's running from the logs, so don't think your function is directly causing a problem. My guess is something else later is crashing or something else unrelated?

#kirkstone #python #bitbake

<martin.leduc=luminator.com@...> wrote: Can you provide a little more detail about how it crashes? Also, I'm not quite clear what you mean by "works like a charm with Warrior"; it s

#kirkstone #python #bitbake

This appears to be the actual error: python3:do_create_spdx can't find the recipe-gnu-config-native.spdx.json. I'm not sure why that would be the case though; do_create_spdx for gnu-config-native shou

CC'd the mailing list Can you check if it works without any additional layers? Also would it be possible to get your local.conf?

That patch in question fixed a regression in systemd behavior that was introduced at some point that broke the non-polkit behavior. I was able to get it fixed, but I also suspect that fighting against

You might be better off trying to use a container to build, but with a host that old, even that might be hard. There are several container solutions for the project, including: * crops - https://githu

I agree. I assume the change is simple enough to make that we can bring them back easily if we think it might be helpful is some scenario? Also, just to clarify, those workers will still contribute to

<trevor.gamblin@...> wrote: Merged as 52d5f76f54eac384f9480dffe96df089d9ee8f33 in OE-core

<michael.opdenacker@...> wrote: This usually happens when there is a sstate archive (.tar.zst), but no corresponding siginfo file (.tar.zst.siginfo). The sstate code assumes the siginfo file i

Michael, I noticed that the https://www.yoctoproject.org/reproducible-build-results/ website went down (it always shows "Error fetching test results"). I did a little debugging and I think that the CO

<abeltran@...> wrote: Looks like the loop is: nativesdk-clang-glue.bb:do_create_spdx -> clang_git.bb:do_create_spdx -> clang-crosssdk_git.bb:do_create_spdx -> nativesdk-clang-glue.bb:d

This is good, thanks. Is the libnsl2 also tied to some feature? Perhaps you can explain why it needs to be removed from MinGW

Yes, that's a good idea. Sinan, please make that change in meta-oe, then change this patch to remove it from PACKAGECONFIG