busybox is most likely the one providing it in ${base_bindir} Recent busybox upgrade probably moved this file. There is also conflict on /usr/bin/setfattr between busybox and attr now.

There are 2 packages using u-a for nice, but one is using {bindir} and 2nd one is using {base_bindir} coreutils is using bindir, find what's using ${base_bindir} and change one of them to use the same

Follow the READMEs and don't mix layers from different branches. You need to checkout all repositories with layers from the same branch to be compatible. Now you're mixing newer meta-oe branch with ol

Check with bitbake -g what's pulling gcc-runtime into the image, if your whole userspace should be 32bit, then lib32-gcc-runtime will be enough. My multilib builds contain only following 64bit builds:

It's not as simple as that in some cases, there are some components which are pulled in 64bit version even when building lib32-foo-image. Some are easy to override from the config e.g.: ROOTFS_PKGMANA

OK, so it's only visited links, not linked from ML or wiki or whatever, right? How huge the database is? I've checked our internal instance and on relatively slow VM we have: 47 472 724 Post_buildstat

I'm just curious, how are you tracking which reports were viewed or linked to (and linked from where)? I often use a link to http://errors.yoctoproject.org in the mailing list or the recipes/commit me

See ./recipes-bsp/tegra-binaries/tegra-shared-binaries.inc It's disabling standard do_fetch, do_unpack, do_patch and replacing them with tegra-binaries:do_unpack tegra-binaries:do_preconfigure which p

Always use bitbake -e to verify that the file://nvpmodel.conf ends where you expect it to end (and if it doesn't the history will show you why not).

This issue wasn't caused by gcc upgrade, it was caused by: https://patchwork.openembedded.org/patch/150269/ which was included in the same batch of updates when I've included these RFT changes. I've s

The fix from you worked for me, thanks! Just FYI if someone needs similar fix, backporting this: https://patchwork.kernel.org/patch/9170055/ fixed the issue for me, now I have successful kernel build.

Try backporting this change: https://github.com/torvalds/linux/commit/474c90156c8dcc2fa815e6716cc9394d7930cb9c

Only for thumb? makes me a bit sad that thumb override was dropped by you in 351443d71eb246a946b41f12b54d57b36fe1574e

Should I send v2 adding -fomit-frame-pointer instead of removing -fno-omit-frame-pointer? The v1 fixes the issue for me with default config + DEBUG_BUILD.

see http://lists.openembedded.org/pipermail/openembedded-core/2018-May/150654.html

4.20 doesn't fail with DEBUG_BUILD, because inject-nf.c test is new in 4.22: https://github.com/strace/strace/commit/58598cd7f6e23e531d71bfe5a4e35f898a4f3b2d#diff-dc01d20c1e55f8adf7536cb46d4481e1 What

It was with raspberrypi3, thumb (Thumb2) enabled in DISTRO, there is already -fno-omit-frame-pointer in the default command line for it, adding -fomit-frame-pointer at the end fixes it: docker-lge @ ~

I'm trying to find out what's different in the builds where it was failing, will provide more info later. I've sent fix as well: http://lists.openembedded.org/pipermail/openembedded-core/2018-May/1505

My initial tests show couple issues, but usually caused by other changes in that branch, not the gcc-8 itself. 1) strace-4.22 from http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/

This might help you: https://github.com/webosose/meta-webosose/blob/master/meta-webos/recipes-core/glib-2.0/glib-2.0/0002-gdbus-codegen-also-replace-character-with-underscore.patch