Please do notice there's a new public article by RP: https://www.linux.com/audience/maintainer-confidential-opportunities-and-challenges-of-the-ubiquitous-but-under-resourced-yocto-project/ "Maintaine

This is different to the previous error. Yocto itself does not prevent the recipe from building, but something inside the component is producing an error during configuration. One of the screenshots m

The screenshot indicates the problem originates in libimxvpuapi2 recipe. So you should get more information by running 'bitbake libimxvpuapi2'. Alex

What happens if you bitbake libimx… thingy directly? Alex

meta-raspberrypi kernel comes from https://github.com/raspberrypi/linux and they stopped providing -rt options some time ago. Your options are to apply the -rt patchset to regular rpi kernel and enabl

#raspberrypi

One more thought: would shipping gcc-runtime also trigger the 'provide the source code for everything that has been linked with it' then as required by all gpl versions? The exception frees you from t

#gplv3 #yocto #llvm

Changing gcc to clang should be done for technical reasons, I would rather not give this advice to address what seems like an incomplete understanding of the licensing situation. Alex

#gplv3 #yocto #llvm

This is literally the first time I hear about gcc exception not being good enough. Your legal team holds the ultimate authority, but it’s most certainly not common practice. How did they justify it? A

#gplv3 #yocto #llvm

The GCC exception frees you from having to fulfil the terms of gpl3 in almost all cases. Links with details are easily obtainable with google search. Alex

#gplv3 #yocto #llvm

distutils has been removed from upcoming python 3.12, so I don't think anyone would be particularly interested in what that class is doing :) The concern should be what are you going to do with all th

<alexandre.belloni@...> wrote: I tried. This happens only if a 3-way merge is enabled: for existing files git will strip the leading directory as needed, but for newly introduced files it will

<alexandre.belloni@...> wrote: We never got to the bottom of what happened to that one. Part of the patch applied correctly, the other part did not. Alex

I'd rather teach make/ninja upstream to watch memory consumption and/or host pressure directly (e.g. similar to how it handles -l). And offer any resulting patches to upstream first. Alex

I've been making patches against an integrated poky checkout for many years, including bitbake patches. They're usually correctly picked up and applied; you only need to ensure you route them to corre

There is; the source code for wic and its tests are fully available to you, so you are welcome to implement the missing bits and submit them for review and inclusion. Also, we do not have a wic mainta

It helps if you show your build configuration, e.g. the output of 'bitbake -e core-image-full-cmdline'. Alex

By all means please do. Everyone will benefit from teaching make to abstain from starting new processes if RAM is tight, even people with xeon/epyc grade hardware. It's not that I don't want to spend

On Tue, 3 Jan 2023 at 16:24, Alexander Kanavin via lists.yoctoproject.org <alex.kanavin=gmail.com@...> wrote: I mean, one can use a virtual machine inside a windows laptop if that's

Sorry guys, but this is venturing into the ridiculous. If you embark on building a whole Linux distribution, you need to start with the correct tools for it. Alex

I have to note that even the most expensive 16 Gb RAM module is less than 100 Euro, and can be obtained for half that much. Surely you value your time more than that? Alex