You can add fallback rules to MIRRORS (either globally or per-recipe). See the last few lines of meta/classes/mirrors.bbclass as an example.

<patrick.boettcher@...> wrote: You can't directly influence the build of one recipe (ie dt-utils) by making a change in another recipe (ie the image recipe), so the DEPENDS and RDEPENDS style ch

The correct way to turn on syslog in busybox is to ensure that "file://syslog.cfg" is included in SRC_URI. However, it looks like it's included by default so in your case you may need to find and disa

From the log of the failing command, the cross compiler is being called without a --sysroot option, which usually means the CC value set by the build environment is being ignored or over-ridden. I gue

The Yocto project supports building distros based on OpenEmbedded. You can't use Yocto to build SUSE. (You can use Yocto to build an OpenEmbedded based distro on a SUSE host... but if I understand cor

The documentation for NATIVELSBSTRING perhaps hasn't caught up with recent changes in it's definition and usage. If you see "universal" it means native recipes are being compiled against a version of

The key point is when the QA test is run. In the case of "already-stripped", the test is run as part of split_and_strip_files() in package.bbclass, ie as part of the normal stripping process. As Ross

<open.source@...> wrote: Is the double v really required?

<Krzysztof.Dudziak@...> wrote: Yes, I agree. That part of the documentation could certainly be improved.

<Krzysztof.Dudziak@...> wrote: Looks like a mistake in the documentation. Native only recipes (ie recipes which use "inherit native" rather than BBCLASSEXTEND) should have "-native" as a suffi

<Jeremy.Overesch@...> wrote: I think you are mixing up "LICENSE" and "LICENSE_FLAGS". The two don't really work together. It's partly explained in: https://www.yoctoproject.org/docs/2.4/me

This is just the wrong syntax. PACKAGECONFIG is not a list of configure options. It's a list of "features" to enable, which are then translated into appropriate configure options (and dependencies) ba

It shouldn't - at least not unless you've over-ridden the default location of the downloads directory and placed it under tmp? The default locations are: DL_DIR ?= "${TOPDIR}/downloads" SSTATE_DIR ?=

They are conditional over-rides of the value of PACKAGECONFIG. The first over-ride takes effect when building the recipe for the target (ie the "normal" way to build a recipe, where the sources are cr

Yes, it is. Do your errors go away if you do that?

To understand what's happening it's worth also reading the SUMMARY for core-image-minimal: SUMMARY = "A small image just capable of allowing a device to boot" and comparing to core-image-base: SUMMARY

This isn't supported directly. However, if you look in meta/classes/image_types.bbclass -> oe_mkext234fs() you will find the commands which are run for the ext4 image type. By copying and extending th

Actually poky users probably do leave quite a detailed trail each time they build anything due to the default PREMIRRORS in the poky distro config. The downloads.yoctoproject.org logs could probably r

* Version 3.3.30 (released 2018-07-16) ** libgnutls: Corrected infinite loop when an incorrect PIN was provided via pin-value or pin-source. ** gnutls-cli: backported the --sni-hostname option. This a

Depends on what you mean by "update". Backporting a patch is generally considered updating, but I guess you could argue either way. What I'm saying is that upstream oe-core contains a change to the bu