Hello, We also have the same issue with similar in-docker builds, a workaround for the issue is mentioned here: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14519 until the fix is backported to

No there isn't - with the yocto project you can build your own distribution not mimic other already available distributions. If you want to build Ubuntu you have to ask canonical.

I want to build ubuntu distro using yocto. Is there a way for that ?

Cheers :) you should also try this on bleeding edge master, it should work the same as hardknott, but if there are issues, you can make and send patches to fix them. Alex

Hello, our dunfell based yocto no longer builds in the pkgconfig-native section. I tried it in an Ubuntu 18.04 and Debian 10 Docker container. The build always aborts as follows: checking thread

Hi all, hi Alexander, I solved my problems. Things work fine now. Below I'm summing things up as documentation for myself and also others in case this pops up in someones search query. Am So, 17. Okt

Cc'd Paul Eggleton's current email. Perhaps the readme file in meta-qt4 needs updating. Thanks, -- Paul Barker https://pbarker.dev/

Bruce, I am running a 8 month old version of poky Dunfell, commit e32d854e. I can see the code in perf.bb where it copies over the kernel code to its directory, so I think

Hi Jared Please see [1] usually sending to the right mailing list and CCing the maintainers is the usual way to send patches [1] https://git.yoctoproject.org/cgit/cgit.cgi/meta-qt4/tree/README

Here is the patch if anybody is interested, should have attached that the first time.

How do I get meta-qt4 patches applied? I tried to contact the maintainer listed and the email comes back undeliverable. I have the needed patch but now way to deliver it.

<chuckkamas=yahoo.com@...> wrote: What release are you using ? We did have some issues with this in the past, but they should all be accounted for now. I can bitbake perf, bitbake

Hi all, I am trying to model a new recipe off of perf.bb to compile the usbip helper kernel code. I have been having issues with the work-shared/../kernel-source directory being empty, so I went

Signed-off-by: Anton Antonov <Anton.Antonov@...> --- meta-parsec/README.md | 23 +++++++++++++++---- .../parsec-service/parsec-service_0.8.1.bb | 10 ++++---- 2 files

From: Pavel Zhukov <pavel.zhukov@...> Signed-off-by: Pavel Zhukov <pavel.zhukov@...> --- README | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README

From: Pavel Zhukov <pavel.zhukov@...> Progress bar can overlap with products logos, added --disable-progress-bar configure option to disable progress bar completely without patching the

Fix layer index parsing issues with master & honister, and complete the move to Django 2.2 LTS. The following changes since commit 2314fb2811bc3753d9dd4459747d8d30369321ad: Add SPDX license

From: Changqing Li <changqing.li@...> Before this commit, it only support create layer on master branch, support import layer to other branch to fix following issue: For layer A, it only

From: Changqing Li <changqing.li@...> Add option -s to support send mail to admin when update_layer.py return non-zero value. So that admin can find issues ASAP. Signed-off-by: Changqing

Done. It too more than an hour (not 10 minutes) since I actuall read through many of the issues to decide if they are M1, M2 and if anyone on the team should be CCed. Phew!