**** BEGIN LOGGING AT Wed Jan 04 03:00:02 2017
Jan 04 07:30:53 <Tofe> Herrie: once I'll fix this wlan kernel module in the rootfs, I think it will be time to merge all this. Jenkins is back on track right?
Jan 04 07:32:48 <Tofe> Herrie: once I'll fix this wlan kernel module in the rootfs, I think it will be time to merge all this. Jenkins is back on track right?
Jan 04 08:18:24 <Herrie|2> morning'
Jan 04 08:18:42 <Herrie> Tofe: Yeah Jenkins in behaving again :)
Jan 04 08:58:46 <Tofe> Morning :)
Jan 04 08:59:42 <Tofe> Herrie: ok, then I'll adjust a bit the source URI for some recipes (kernel, hybris hal), I'll find the missing piece for the wlan module for mako, and it should be ok.
Jan 04 09:00:06 <Tofe> We can even PR the maguro migration too.
Jan 04 09:25:46 <Tofe> Ah, looks like I should do something like this: https://github.com/shr-distribution/meta-smartphone/blob/krogoth/meta-openmoko/conf/machine/om-gta01.conf#L34
Jan 04 09:25:54 <Tofe> Will try tonight.
Jan 04 11:26:09 <Herrie> Tofe: OK :)
Jan 04 11:46:13 <Herrie> Tofe: With the new leaner approach, you think it would be feasible to use the regular OE GCC toolchain instead of the old 4.7 GCC one or we'll still need the old one?
Jan 04 12:31:39 <Tofe> Herrie: we're using the old 4.7 for which build?
Jan 04 13:49:26 <Herrie> Tofe: that's what we used to build the http://build.webos-ports.org/cm-wop-10.1/ files
Jan 04 13:49:44 <Herrie> With the "old method". It needed to have some separate Jenkins jobs for this as well
Jan 04 13:49:59 <Herrie> Ideally we would have it fully integrated I'd say?
Jan 04 14:29:01 <Tofe> Herrie: I didn't use any trick to build the hybris HAL, but I'm pretty sure the CM12.1 build still uses GCC 4.8 or similar
Jan 04 14:29:31 <Tofe> For mako you need the patches I added in order to build it with gcc 5
Jan 04 14:29:45 <Tofe> For maguro too, I guess
Jan 04 14:30:07 <Tofe> So I don't have a clue whether it builds with OE toolchain or not...
Jan 04 14:49:28 <Herrie> Tofe: Kernel was always built with OE I think, so hence we needed the GCC 5 patch etc
Jan 04 14:49:42 <Herrie> However the CM bits in the past were always separate if I'm correct using GCC 4.7
Jan 04 14:50:05 <Herrie> Not sure if we're building a lot less with the new approach so patching might be feasible or we're still doing the 20+ GB bits :P
Jan 04 15:52:45 <Tofe> It still downloads quite a bit, but the build is really fast, now. It takes about 5min on my computer.
Jan 04 15:53:53 <Herrie> Tofe: That's really quick. I guess it does a lot less compared to before... Might be an idea to try it with GCC5 sometime.
Jan 04 15:53:55 <Tofe> But do you really want to integrate this into the main build ? It will mean downloading a lot more, just to generate this
Jan 04 15:54:12 <Herrie> Tofe: More that we don't need a separate toolchain for it
Jan 04 15:54:34 <Herrie> Newer GCC will also give some minor performance tweaks as well it seems. Not a lot though
Jan 04 15:54:39 <Herrie> Tofe: You seen: http://webos.rocks/
Jan 04 15:54:48 <Herrie> This is what Choorp created in AngularJS :P
Jan 04 15:55:04 <Tofe> I don't remember having installed gcc 4.7 on my ubuntu, and I though it used the one from prebuilts
Jan 04 15:56:46 <Tofe> oh oh, nice web site!
Jan 04 15:57:42 <Herrie> Though I think he could spend his time more wisely on helping us with some EnyoJS or other JS bits :P
Jan 04 17:35:01 <Tofe> Herrie: it's what I thought: it uses prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi-* to build the target; so there is another toolchain, but it's embedded in the dowloaded content
Jan 04 18:09:29 * DougReeder checks in
Jan 04 19:06:13 <Tofe> Herrie:  PRs should now be quite in order
**** ENDING LOGGING AT Thu Jan 05 03:00:00 2017