Shouldn't this be just qt3 like BBFILE_* variables above? Regards,

Cannot LAYERSERIES_CORENAMES added in rocko be used for that?

Signed-off-by: Martin Jansa <Martin.Jansa@...> --- conf/layer.conf | 2 ++ 1 file changed, 2 insertions(+) diff --git a/conf/layer.conf b/conf/layer.conf index f5601bb..3d614dc 100644 --- a/conf/

KERNEL_MODULE_AUTOLOAD_remove should work, check with bitbake -e to confirm that it was correctly applied. It's also possible to blacklist it with: module_conf_<module-name> = "blacklist <module-name>

From: Martin Jansa <martin.jansa@...> * fixes: WARNING: nettle-2.7.1-r0 do_patch: Some of the context lines in patches were ignored. This can lead to incorrectly applied patches. The context lin

It's applied in PACKAGECONFIG_CONFARGS variable and various bbclasses (and also various recipes) use this variable where needed, see git grep: meta/classes/base.bbclass: appendVar('PACKAGECONFIG_CONFA

https://github.com/agherzan/meta-raspberrypi/pull/188

Signed-off-by: Martin Jansa <Martin.Jansa@...> --- recipes-kernel/linux/linux-raspberrypi.inc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/recipes-kernel/linux/linux-r

FWIW: here nativesdk-libepoxy fails in do_configure already since meson conversion FileNotFoundError: [Errno 2] No such file or directory: 'TOPDIR/tmp-glibc/work/x86_64-nativesdk-oesdk-linux/nativesdk

I'm using oe-core/scripts/sstate-diff-machines.sh script (which calls bitbake -S) to generate "snapshots" of sstate signatures for interesting builds (in our case daily official builds) and then every

I'm seeing the same build errors in linux-raspberrypi with various versions of Gentoo and Ubuntu (mostly tested with 14.04 and 16.04), I doubt that this issue is specific for Fedora 27.

I don't know what version of Yocto you're using, but if it's older than 2.3 (which does filter what binaries are seen from the host system with HOSTTOOLS), then your build is probably autodetecting sw

I think you can disable version-going-backwards check as any other QA check by removing it from WARN_QA and ERROR_QA variables. Even with AUTOINC you should use PR service to get increasing AUTOINC nu

Similar QA issue is shown when you use:LOCALE_GENERATION_WITH_CROSS-LOCALEDEF_forcevariable = "0" which is needed to build glibc-locale with pyro on hosts with glibc-2.26 (with ENABLE_BINARY_LOCALE_GE

It should go to bitbake-devel ML and the subject should say bitbake branch (which is 1.34 not pyro).

Be aware that when you provide python-native, it's more likely that swig-native will be detected in sysroot as well and then u-boot will fail to build libfdt python library. To prevent this autodetect

In theory you can set QT_PACKAGES_ARCH to MACHINE_ARCH in rpi-base.inc to make it explicit, but that's also really bad (as e.g. rpi2 and rpi3 will each build it's own qtwebengine and all it's deps eve

* this reverts commit 04b37dbdb79638b17a670280058400ffaf1b6ccb. * this makes qtbase and everything which depends on some qt* recipe to be effectivelly MACHINE_ARCH Signed-off-by: Martin Jansa <Martin.

null and nothing can also be matched in MACHINE names, so to make sure people should use: COMPATIBLE_MACHINE = "(^$)"

Yes, GNU gold (GNU Binutils 2.29.0.20170912) 1.14