**** BEGIN LOGGING AT Sat Nov 25 03:00:01 2017 Nov 25 05:28:49 nope.. adjusting the concurrency settings just moved all the failing packages to the back. guess i'll try a different theory. :-D Nov 25 07:22:45 Morning! Nov 25 07:23:25 Any ideas on this? Gettings some errors with gcc-cross-initial-arm when trying to build the kernel for my aarch64 kernel: https://bpaste.net/show/18e506ea0341 Nov 25 07:41:24 Morning! Nov 25 07:43:50 Herrie: "*** Configuration arm-webos-linux-gnu not supported" ? Nov 25 07:44:37 Tofe: Yeah I saw that Nov 25 07:44:44 Just not sure where this comes from :P Nov 25 07:45:01 Searching on Google and github for arm-webos-linux-gnu doesn't give me much clues Nov 25 07:45:08 It's a bit hard to see what exactly is the reason of the failure Nov 25 07:48:50 Tofe: I'm not really at home in compilers ;) Nov 25 07:48:53 So for me even harder Nov 25 07:49:01 I tried cleaning tmp-glibc Nov 25 07:49:02 Herrie: maybe you can compare your recipe with the one for rpi3 Nov 25 07:49:16 I'm pretty sure it's an issue like that Nov 25 07:49:21 Yeah Nov 25 07:51:19 Tofe: https://github.com/agherzan/meta-raspberrypi/blob/master/recipes-kernel/linux/linux-raspberrypi.inc#L159 ? Nov 25 07:55:43 wow, it's more complex than I thought Nov 25 07:56:19 isn't it the configure step that's failing ? Nov 25 07:56:36 ah but wait, it's not about the kernel, silly me Nov 25 07:56:59 Tofe: It's gcc toolchain Nov 25 07:57:03 exactly Nov 25 07:57:20 so... check your machine.conf, I'd say (w.r.t. rpi3 too) Nov 25 07:59:09 Let me try rpi3-64 Nov 25 07:59:26 like https://github.com/agherzan/meta-raspberrypi/blob/master/conf/machine/raspberrypi3-64.conf#L9 Nov 25 08:02:03 I have that one just @ end of recipe might try moving it up Nov 25 20:45:42 Tofe: Not really sure what's the issue Nov 25 20:45:59 Didn't have much time today since we had a family event and guests only just left Nov 25 21:06:43 Tofe: Seems I needed to remove TARGET_ARCH = "arm" from mido.conf Nov 25 21:06:48 Now the toolchain is OK Nov 25 21:39:06 Now getting "make[2]: *** No rule to make target 'zImage-dtb'. Stop." on the kernel Nov 25 21:39:24 Trying without the KERNEL_IMAGETYPE = "zImage-dtb" Nov 25 21:44:20 That also doesn't work. Based on https://github.com/Herrie82/android_kernel_xiaomi_msm8953/blob/pgz-14.1/arch/arm64/boot/Makefile#L19 it should just be "Image" ? Nov 25 22:00:16 Ok when I make KERNEL_IMAGETYPE = "Image" it builds Nov 25 22:00:43 Without issues just some warning/qa issues about built not shipped Nov 25 22:00:49 So not a bad start Nov 25 22:03:29 Let's see if I have a chance tomorrow for the Halium bits Nov 26 01:33:08 Hi all, I've got a rather unique situation and I hope someone here might be able to help. Nov 26 01:33:16 I'm trying to get the LuneOS UI ported over to run on top of postmarketOS (https://postmarketos.org/). I've made pretty good progress (https://github.com/postmarketOS/pmbootstrap/issues/629), but I've finally gotten stuck. Nov 26 01:33:30 I'm trying to start luna-next (after the two ls-hubd instances, LunaSysService, LunaSysMgr, and luna-prefs-service), but all I get is the pulsing LuneOS logo, it never proceeds to the lock screen or home screen. Nov 26 01:33:37 At one point, I had mocked out LunaSysService/LunaSysMgr by using test qml files, and that brought me to the lock screen, but after I put the real thing in place, it doesn't get that far. Nov 26 01:33:45 Is there something obvious I'm missing? Maybe a missing component or service I didn't start? Nov 26 01:33:53 I've tried digging into the luna-next/luna-next-cardshell code but nothing obvious jumped out at me. Is there a good reference for the components needed to get luna-next up and running? Nov 26 01:36:52 The only logs I get out of luna-next are here: https://pastebin.com/tKqKecYx Nov 26 01:37:13 ls-monitor does show messages being passed back and forth between luna-next and LunaSysService though. **** ENDING LOGGING AT Sun Nov 26 03:00:00 2017