Thanks for the response. Yes, I tried to set both in local.conif or distro, none of works. There was no PREFERRED_PROVIDER_virtual/kernel, nor PREFERRED_VERSION_linux-yocto setup. Thank you. Kind

Is the PREFERRED_PROVIDER_virtual/kernel set to linux-yocto? You need to set the PREFERRED_VERSION for kernel that you are using ... bitbake -e virtual/kernel output should help see how it's being

Hi, I replaced Linux kernel version from 4.19 by 5.10 bb file, but it still built 4.19 zImage, I add PREFERRED_VERSION_linux-yocto = "5.10%" in local.conf, it still built 4.19 zImage. Where the linux

FWIW this doesn't sound right to me. pyc files (in __pycache__) would cache the code, not data so I don't see how these values would be preserved there. I don't doubt you're seeing some kind of issue

On Sun, 2021-01-03 at 10:44 -0800, Paul D. DeRocco wrote: I've been resurrecting an old Pyro project under Gatesgarth. It's an Intel 32-bit system that needs maximum speed, so I decided to try to

Current Dev Position: YP 3.3 M2 development Next Deadline: 18th January 2021 YP 3.3 M2 build Next Team Meetings: Bug Triage meeting Thursday Jan. 7th at 7:30am PDT

Hi, Where to download Yocto receipt for kernel version 5.10? To update a stable version, should I update Yocto version to 3.3 or 3.1? Thank you. Kind regards, - j

* add support for mingw32 * Engines are installed in a slightly different path, which is urgly, patch it to make the path shorter * remove runtime dependency from perl for mingw nativesdk since

All, YP M+ or high bugs which moved to a new milestone in WW01 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 11449 Allow overriding classes to

All, Below is the list as of top 48 bug owners as of the end of WW01 of who have open medium or higher bugs and enhancements against YP 3.3. There are 81 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

All, Just a reminder we will hold the monthly Yocto Project Technical Meeting at 8am PST tomorrow. (1/5) Yocto Project Technical Team Meeting: We encourage people attending the meeting to

Those are not test cases then, surely. If you want to run actions after test cases to collect log files then I'd implement that as a decorator on the test cases. Ross

I'd say improving the actual test ordering function is the way to go, yes. Not sure how the ordering 'hint' should be like, but maybe setting an integer priority via a decorator would

I'm not familiar with x32 myself but Debian has an x32port which should give you a working kernel config to start from. https://wiki.debian.org/X32Port --

Hi all, I have a few oeqa test cases, which always should run last in a test suite (log and file collectors for instance). Due to the ordering of the test case discovery I had to name all those tests

Hi all, I have a bunch of custom testcases (oeqa/runtime/cases) which are interacting with "d" from the build host - basically fetching some info while executing the test, e.g. foo =

Hi Hongxu, I'm getting issue when building tensorflow-estimator (I add small changes to be able to build this patches on top of dunfell) and I'm getting: | /bin/bash -c

Bonjour, j'essaye d'ajouter le aom plugin au niveau de la gstreamer1.0-plugins-bad. J'ai basculé sur gatesgarth version. Je commence à faire lebuild. J'avais un problème de lisence. Je l'ai

/opt/poky/3.2.1/i64/sysroots/core2-64-poky-linux/usr/include/sys/cdefs.h:453 /opt/poky/3.2.1/i64/sysroots/core2-64-poky-linux/usr/include/features.h:465, /opt/poky/3.2.1/i64/sysroots/core2-64-poky-lin