**** BEGIN LOGGING AT Thu May 10 03:00:01 2018
May 10 07:55:52 <johann> hello
May 10 08:21:00 <johann> Testing 1 2 3 Testing 1 2 3
May 10 08:31:00 <johann> Have you ever considered the advantages of a time shared condominium?
May 10 09:57:52 <fberg> hello guys ! I'm trying to bitbake this library: https://github.com/joan2937/pigpio with this recipe: https://pastebin.com/gK6Khb4T. Bitbake returns with the following error: | pigpio.c:34:10: fatal error: stdio.h: No such file or directory
May 10 09:57:52 <fberg> |  #include <stdio.h>
May 10 09:59:34 <RP> rburton: | /var/tmp/rpm-tmp.aaWGsi: line 7:  1022 Segmentation fault      /sbin/ldconfig in https://autobuilder.yocto.io/builders/nightly-arm-lsb/builds/999/steps/Running%20Sanity%20Tests/logs/stdio :/
May 10 09:59:56 <rburton> grrr
May 10 10:00:44 <fberg> Maybe some CFLAGS are not set correctly.. Does anyone have any idea ?
May 10 10:00:57 <RP> rburton: systemd is also bust in -next:https://autobuilder.yocto.io/builders/nightly-qa-extras/builds/1004/steps/BuildImages_13/logs/stdio :(
May 10 10:01:16 <rburton> yeah was just looking at that
May 10 10:01:29 <RP> rburton: the musl failures are this new QA test
May 10 10:02:37 <rburton> RP: i'll chase down systemd now and either fix or drop
May 10 10:06:09 <RP> rburton: thanks, I'll figure out this musl issue
May 10 10:36:58 <kuzulis> Hi guys. Is yocto 'poky' release a stable? Because it fails to compile the e2fsprogs-native
May 10 10:37:19 <rburton> kuzulis: the releases are yes
May 10 10:37:41 <rburton> kuzulis: its quite likely that you're using an older release with a modern distro, which means new gcc/glibc which means old software fails to build
May 10 10:37:51 <rburton> so tell us more information to help
May 10 10:41:36 <kuzulis> I use ubuntu 18 on a host.. And try to build the yocto 'poky'.
May 10 10:41:42 <kuzulis> This is a build log: https://pastebin.com/DjMtbWV1
May 10 10:47:33 <kuzulis> Seems it is similar to: https://github.com/openwrt/openwrt/pull/781
May 10 10:53:53 <rburton> kuzulis: what version of poky?
May 10 10:55:36 <kuzulis> rburton: Seems, pyro
May 10 10:56:20 <kuzulis> 17.0
May 10 10:56:57 <rburton> latest ubuntu supported by pyro is 16.10 (because pyro is old)
May 10 10:57:31 <rburton> either move to a newer poky release (and hope that it works on ubuntu 18.04) or fix the problem with e2fsprogs yourself
May 10 10:57:54 <rburton> as 18.04 is literally weeks old, expect lots of software to fail to build on it
May 10 11:02:47 <kuzulis> rburton: How is possible to fix it? e.g. try to exclude e2fsprogs?
May 10 11:02:56 <rburton> kuzulis: you can't skip that, no
May 10 11:03:15 <rburton> dig into the e2fsprogs changes in newer releases and see if you can spot a patch that fixes the problem
May 10 11:04:28 <kanavin> rburton: there is some kind of strange perception problem with YP users. They tend to think everything should be done from 'regular' recipes, but image recipes must not be touched ever :-/
May 10 11:04:42 <kanavin> (re latest yocto ml thread)
May 10 11:04:54 <rburton> kanavin: yes
May 10 11:06:51 <kuzulis> rburton: As I can see, there are the 1.44.x new version of e2fsprogs.. but 'pyro' uses 1.43.4.. Is it possible to configure the yocto to use a newest version?
May 10 11:07:10 <rburton> RP: if you cherry-pick the two systemd patches in mut (one unrelated, and then mine afterwards) then systemd should be fixed
May 10 11:07:41 <rburton> kuzulis: easier to just switch to a newer release
May 10 11:08:04 <kuzulis> rburton: Do you mean a newer release of youcto?
May 10 11:08:06 <rburton> yes
May 10 11:08:25 <rburton> ubuntu 18.04 isn't a supported distro for pyro, so its not a great surprise it doesn't work.
May 10 11:08:40 <rburton> the fix is probably a simple backport if you have an hour to spend on it
May 10 11:08:42 <JaMa> heh, I agree that it's better to switch to newer release, but often it's not so easy :)
May 10 11:08:47 <kuzulis> rburton: No no, I mean, I want to use a 'pyro' :)
May 10 11:09:14 <rburton> then spend an hour finding the fix, backporting it, and submitting it for pyro so everyone else has it
May 10 11:09:17 <kuzulis> rburton: Because I don't know how to switch to a new release of youcto
May 10 11:09:28 <JaMa> I'm using morty on 18.04 and it works fine
May 10 11:09:47 <rburton> JaMa: genuinely surprised that works!
May 10 11:10:22 <kuzulis> Ohh.. thanks.. I will try then a 'morty' too.. :)
May 10 11:10:31 <kuzulis> Thanks, guys. ;)
May 10 11:10:42 <rburton> https://wiki.yoctoproject.org/wiki/Releases <-- morty is even older!
May 10 11:10:43 <JaMa> kuzulis: morty is older than pyro, so it should work with pyro
May 10 11:10:56 <kuzulis> rburton: Yes.. I see
May 10 11:11:12 <JaMa> kuzulis: I'm actually building all releases since morty on 18.04 and haven't seen e2fsprogs-native failure in my builds
May 10 11:17:51 <acrap> Hi, folks! Can you help me? I am looking for explanation where toolchain is in Yocto. May be somebody have useful links about it...
May 10 11:18:17 <acrap> I mean gcc,g++ etc
May 10 11:19:16 <rburton> acrap: meta/recipes-devtools/
May 10 11:19:32 <rburton> find . -name gcc*.bb would find it
May 10 11:20:39 <acrap> rburton: i am talking about toolchain on host
May 10 11:20:52 <rburton> we use the host compiler to build a cross compiler
May 10 11:21:11 <rburton> if you mean where is the built cross compiler, it's in the sysroot
May 10 11:22:00 <acrap> rburton: then, cross compiler is copied to sysroot-components. Am i right?
May 10 11:22:25 <rburton> recipes build and get deployed into sysroot-components
May 10 11:22:43 <rburton> the components are then used to assemble a per-recipe sysroot
May 10 11:24:13 <acrap> rburton: I hope I can find it somewhere in documentation... Could you know where I can find the explanation?
May 10 11:24:21 <rburton> explanation for what?
May 10 11:24:31 <rburton> stuff builds, ends up in sysroot-components
May 10 11:24:48 <rburton> when a recipe says it depends on foo and bar, foo and bar from sysroots-components are linked into the recipe's sysroot
May 10 11:27:00 <kuzulis> JaMa: Seems, the 'morty' compiles.. at least, it still not failed. :)
May 10 11:32:22 <rburton> armpit: can you push tags to your distcc clone?  no tags upsets the upstream checker code (which i'll also try and fix)
May 10 11:46:33 <kanavin> rburton: there was never a tag for 3.2 from what I recall, we should just go back to official repo and 3.3 instead
May 10 11:46:54 <rburton> kanavin: distcc was special indeed
May 10 11:47:01 <rburton> we should update to 3.3 now
May 10 11:47:12 <rburton> (the sha we were using was deleted)
May 10 11:48:05 <kanavin> yup
May 10 12:01:28 <RP> rburton: https://autobuilder.yocto.io/builders/nightly-mips-lsb/builds/988/steps/Running%20Sanity%20Tests/logs/stdio - another ldconfig segfault. Why would ldconfig segv on -lsb ?
May 10 12:02:17 <RP> actually of course it faults on non-IA.
May 10 12:02:39 <RP> question is more why the behaviour difference lsb compared to non-lsb
May 10 12:03:42 <RP> kanavin: any ideas on why we're seeing postinst differences lsb to non-lsb :/
May 10 12:06:51 <rburton> more bits being installed in lsb?
May 10 12:08:57 <RP> rburton: yes, that could be
May 10 12:11:29 <kanavin> RP: is that specific to mips, lsb or both?
May 10 12:11:57 <RP> kanavin: its happened on mips-lsb and arm-lsb both on debian8 but not on ppc-lsb or any non-lsb
May 10 12:14:47 <kanavin> RP: note that the failing test is being executed in a chroot, when installing libc6 there 'from scratch'.
May 10 12:15:29 <kanavin> RP: maybe in that situation ldconfig needs more than just its own package files (libc library) to execute?
May 10 12:15:35 <RP> kanavin: right, I'm just puzzled about why it works in some cases and not in others
May 10 12:15:55 <RP> kanavin: the difference bothers me more than it working or not working :)
May 10 12:16:43 <kanavin> RP: maybe security flags have something to do with it
May 10 12:25:50 <RP> kanavin: also could be
May 10 12:29:52 <kanavin> RP: the short answer is I don't know :) creating a rootfs on target is uncharted territory :)
May 10 12:32:02 <yocti> New news from stackoverflow: flashing yocto image to raspberrypi-cm3 <https://stackoverflow.com/questions/50272528/flashing-yocto-image-to-raspberrypi-cm3>
May 10 13:04:24 <JaMa> rburton: wrt busybox, any special setting in your build or generit nodistro build?
May 10 13:04:44 <rburton> general poky, but poky doesn't change busybox afaik
May 10 13:05:00 <JaMa> it built fine here in various configs before I've sent it to the list
May 10 13:05:10 <rburton> hm
May 10 13:05:30 <JaMa> I'll try a bit more
May 10 13:06:28 <JaMa> http://lists.busybox.net/pipermail/busybox/2001-July/038270.html flashback from 2001
May 10 13:06:56 <JaMa> were you building with musl by any chance?
May 10 13:38:10 <rburton> JaMa: nope. oh, but mut, so other stuff is queued.
May 10 13:42:09 <johann> tits
May 10 16:16:06 <johann> butts
May 10 16:30:21 <RP> rburton: new qemu: "runqemu - ERROR - Failed to run qemu: corrupted double-linked list"
May 10 16:30:35 <RP> rburton: so I'm even more worried about the qemu upgrade now
May 10 16:31:53 <rburton> yeah lets just drop that
May 10 16:43:53 <khem> rburton: poky distro layer does have busybox bbappend it adds defconfig for poky-tiny
May 10 16:46:12 <RP> rburton: that error may mean out of diskspace btw
May 10 16:47:32 <kergoth> hmm
May 10 17:02:11 <RP> rburton: now my non-lsb image fails the same way in that test
May 10 17:02:25 * RP gives the autobuilder a long hard stare
May 10 19:46:09 <JaMa> rburton_: I was able to reproduce that qemu build issue, it's caused by https://github.com/qemu/qemu/commit/2ec78706d188df7d3dab43d07b19b05ef7800a44 I'll check what's the minimal needed subset of my jansa/qemu branch to make sdl2 usable, because qemu without any graphics support (without x11 in DISTRO_FEATURES) might be a bit useless for some use cases
May 10 20:59:44 <rburton> JaMa: i use headless qemu, it's fine
May 10 20:59:49 <rburton> JaMa: you just vnc in
May 10 20:59:53 <rburton> (my build machine is headless)
May 10 21:04:54 <JaMa> rburton: ok
May 10 21:05:41 <JaMa> rburton: makes more sense for qemu-native, but target can be headless as well
May 10 21:05:50 <rburton> yeah
May 10 23:34:10 <yocti> New news from stackoverflow: To build custom BSP layer using Yocto for a bare metal board [closed] <https://stackoverflow.com/questions/50172362/to-build-custom-bsp-layer-using-yocto-for-a-bare-metal-board>
May 11 00:04:15 <yocti> New news from stackoverflow: flashing yocto image to cm3 emmc <https://stackoverflow.com/questions/50283118/flashing-yocto-image-to-cm3-emmc>
**** ENDING LOGGING AT Fri May 11 03:00:03 2018