**** BEGIN LOGGING AT Sun Oct 29 03:00:01 2017 Oct 29 05:58:57 Is yocto krogoth fully compatible with Ubuntu 16.04? Oct 29 05:59:41 I am having trouble building krogoth on Ubuntu 16.04. https://paste.ubuntu.com/25842227/ Oct 29 06:00:08 I can build it without any issue at Ubuntu 14.04 Oct 29 06:00:57 But, it always fails at same place while building in Ubuntu 16.04 Oct 29 06:02:20 I installed same required packets to both PC Oct 29 06:03:17 But, it fails on Ubuntu 16.04, yet the building is completed any errors at 14.04 Oct 29 06:03:23 Any idea? Oct 29 06:03:43 Again: error message is here https://paste.ubuntu.com/25842227/ Oct 29 06:35:01 it looks like it might be building host tool for signing which might use openssl from host and I think not many people here are using linux-msm Oct 29 06:35:31 so I wouldn't be surprised if it's broken, openssl ABI was changed few times in OE builds, might be similar in Ubuntu releases Oct 29 10:15:39 xman: I always build MACHINE=beaglebone wuth YP krogoth under Ubuntu 16.04 on my laptop Oct 29 10:15:52 xman: loks like an issue with your kernel Oct 29 10:17:30 xman: as JaMa said ;-) Oct 29 16:01:37 How come is building on Ubuntu succeed, but it fails Ubuntu 16.04? I think yocto uses openssl from sysroot directory not from host Oct 29 20:38:50 Hello Oct 29 20:40:09 I'm trying to build a image for genericx86 using rocko and froma x86_64 machibe Oct 29 20:40:29 I want to use the realtime preemt kernel Oct 29 20:40:59 but I get this Oct 29 20:41:02 http://dpaste.com/2KYQSD9 Oct 29 20:41:09 QA Issue: Architecture did not match (x86-64, expected x86) Oct 29 20:59:47 TurBoss[m]: hmm, that is unusual... it appears as if it's using the host compiler but that would be highly unusual Oct 29 21:00:05 TurBoss[m]: have you made any changes? any special configuration you have set? Oct 29 21:00:17 the normal kernel works Oct 29 21:00:41 just add the prefered kernel provider to yocto-linux-rt Oct 29 21:00:54 ok, I might give that a try here Oct 29 21:01:28 Thanks Oct 29 21:06:19 TurBoss[m]: hmm, when I try with that configuration I get an error that linux-yocto-rt isn't compatible with genericx86 - did you add a bbappend/other configuration to enable that? Oct 29 21:06:33 sek Oct 29 21:07:28 http://dpaste.com/1YPXHJB Oct 29 21:07:31 this Oct 29 21:07:54 and meta-intel in bblayers but not sure if really needed Oct 29 21:18:59 TurBoss[m]: so that's clearly not enough, you can't just declare the recipe to be compatible - in any case what you are setting is going to be system-wide and not specific to the linux-yocto-rt recipe Oct 29 21:19:19 oh Oct 29 21:19:31 so I'm doin it wrong? Oct 29 21:20:42 if you set COMPATIBLE_MACHINE_genericx86 = "genericx86" in your configuration, that will cause *every* recipe to be marked as compatible, you don't want that Oct 29 21:21:04 but the real issue is that COMPATIBLE_MACHINE is just a marker for compatible recipes, it doesn't actually do anything to make them compatible Oct 29 21:22:11 ok Oct 29 21:22:34 so yocto-linux-rt is not compatible with genericx86? Oct 29 21:22:54 it seems not by default, no - I'd never looked into it until now Oct 29 21:23:07 if you want to make it so, that would be possible, but you'd need to do it properly Oct 29 21:23:44 what you need to do is create a linux-yocto-rt_4.12.bbappend, similar to the linux-yocto_4.12.bbappend in meta-yocto-bsp Oct 29 21:24:14 under conf dir? Oct 29 21:24:38 ah no Oct 29 21:24:39 :D Oct 29 21:24:55 right, it needs to be picked up as with other bbappends Oct 29 21:25:16 meta-yocto-bsp/recipes-kernel/linux/ would be one place although strictly speaking you should create your own layer Oct 29 21:26:18 here's where it gets a bit complicated though - you need to set the right SRCREV / KMACHINE / etc. to get the -rt patchset and build for the correct machine Oct 29 21:27:28 I wonder if you could just borrow some stuff from meta-intel/common/recipes-kernel/linux/linux-yocto-rt_4.12.bbappend, that might work (the core2-32-intel-common stuff) Oct 29 21:27:54 alternatively of course you could just build for intel-core2-32 instead of genericx86 and then you wouldn't need to do any of this Oct 29 21:28:56 ok Oct 29 21:28:56 http://dpaste.com/18YT1PV Oct 29 21:30:16 Ok Oct 29 21:30:24 I'm thinking on move to x86_64 Oct 29 21:30:24 hehe Oct 29 21:31:05 bluelightning: Thanks **** ENDING LOGGING AT Mon Oct 30 03:00:01 2017