Hm, I was thinking about that.. but it looks a messy job, setup all these toolchains etc.. is it worth it? I'm actually satisfied by Arago, I only need to use different kernel and change version of some packages

bluelightning: naw, did not drill down that far. There was like one message on a site that someone identified the problem. I tried later drivers but did not resolve the issue. so, I patched gettext (bbappend) to skip those tests and force the proper result.

"However one case where it showed up was when building udev > 164 with kernels where accept4 call was not wired for arm e.g. since udev looked up definition of SOCK_CLOEXEC which it found but that 2.6.32 kernel really did not support it."

obviously there will always be problems like this, but if anyone can suggest places where the build system doesn't catch and report errors/misconfiguration in an appropriate way, we'd really love to hear about it

Well, this is the linux-yocto-custom which gets a strange name, I'm assuming that 'FILES_${PN}' is correct? work directory struct looks odd: '...linux-yocto-custom/3.4.74+gitAUTOINC+c26a9a9684-r6/linux'