There's this: #SDKMACHINE ?= "i686" ---John On 2022-04-01 16:22, Khem Raj wrote:

It’s complaining about SDKMACHINE setting which is a separate variable, can you check your local.conf if it’s set to something

I'm trying an experiment building yocto/OE on a Raspberry Pi 4 to host on the same RP4. Admittedly, a not practical platform for this purpose but it should work. I'm trying to target the ARM ISA for

Use python3-native to use 2to3 Fix build issue on some hosts with this error: (result, consumed) = self._buffer_decode(data, self.errors, final) | UnicodeDecodeError: 'utf-8' codec can't decode

I am currently trying to extend the meta-java framework with an openjdk-18 recipe. I encounter a problem with the [installed-vs-shipped] QA check which I can't cope with, I admit. The autotolls and

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Alexandre, Bruce, Luca, Michael, Randy, Richard, Saul, Stephen, Steve, Tim, Trevor ARs: - Richard to

Hello We are pleased to announce the Yocto Project 3.4.3 Release is now available for download.

Awesome! That is a very simple and quick reproducer! As per our conversation I quickly tried the following (not that I expected this to be a final solution, but just a poking-around kind of

We've been using shallow git tarballs for all recipes for years at Mentor, definitely speeds up fetches from local mirrors and reduces how much we need to ship to customers to allow them to use

Hi Armin, I noticed that this patch, as well as the version bump to 4.1.3, have landed in the dunfell-next branch of meta-security. Curiously though, the dunfell branch contains quite a few more

<richard.purdie@...> wrote: right, I think shallow clone should be default IMO for all git fetcher tarballs

From: Richard Purdie <richard.purdie@...> Fixes diffoscope-native failing in diffoscope tests on workers using buildtools: File

From: Richard Purdie <richard.purdie@...> This adds lz4c, zstd and pzstd for new tools requirements. Signed-off-by: Richard Purdie <richard.purdie@...> (cherry picked

This series updates to a more recent version of buildtools Tested over the past serveral weeks on autobuilder, most

The "good" news is I did work out how to reproduce this. bitbake keymaps -c clean bitbake keymaps bitbake keymaps -c unpack -f bitbake keymaps -c patch bitbake keymaps -c unpack -f bitbake keymaps -c

We don't have any support for "per-layer" overrides at this time which would be the way to do that. It is something I think we probably do want to consider adding but I haven't had the bandwidth to

Indeed, that would be concerning for us as well. Would it be possible to ignore PREMIRRORS based on the recipe layer? Alternatively, we could create blocklists for heavy packages that need to fetch

I would simply drop PREMIRRORS, this is actually a privacy concern for some of our customers that didn't realize they are leaking the names of their internal git repositories to

Hi Matthias, And keymaps follows the exact same pattern as modutils-initscripts and initscripts; namely that their sources are entirely contained in-tree: keymaps/ ├── files │  

Greetings ! Can anyone help me with the procedure , how I can fetch the source from a private gitlab account . Thanks in advance ! IMPORTANT: The contents of this email and any attachments are