**** BEGIN LOGGING AT Thu Jun 16 02:59:58 2016 Jun 16 04:52:45 Im using a beaglebone black , it seems like the default images do not have support for the LCD3 cape, does anyone know how to enable this? or where should I be looking for it?, my best guess is meta-ti but I took a quick look and didnt find anything Jun 16 04:53:43 should I simply use the linux-ti kernel? Jun 16 05:47:53 I am building a pretty vanilla yocto image for the imx7 Sabre board (iMX7DSABRE). I am using the meta-fsl-arm layer from github and using the krogoth branch for all. The kernel is not booting, boot log here http://pastebin.com/mDMg3430 . After some googling it seems it has to do with the security settings and one poster said to add CONFIG_MX7_SEC to config. I am wondering where that define should be put in the Yocto tree? Jun 16 08:42:48 does bitbake / bitbake-layers have any commands to list licences? Jun 16 13:25:49 kergoth: Thanks for explanation, I think I will go for my custom distro.conf later on. But I regret that yocto is missing something like possiblity to create additiona utility meta-layer for that purposes some automatic actions would enclosed, but in this way I actually create new distro, new rules. But mine would be just for building purposes... nvm, I got it now and accept that. Jun 16 13:33:00 question, I got my custom qemu machine defined in project layer, however it does not fit in any way to runqemu options like qemuarm and so on. Are there plans for extending runqemu for custom qemu machine ? Jun 16 13:40:02 zeddii, I've got a good one for you Jun 16 13:40:22 the update for linunx-yocto-dev seems to make emmc dodgy on a custom borad I have Jun 16 13:41:19 mastier: yes, there's patches around to let BSPs extend its logic Jun 16 13:41:28 mastier: not ready yet, so for now you'll need to fork runqemu Jun 16 13:42:11 rburton: when they are about to be released ? 2.2 or later ? Jun 16 13:55:10 mastier: when they're ready, but hopefully 2.2 Jun 16 14:07:51 Crofton|work, interesting. I did just push 4.7-rc3 if that's of any interest Jun 16 14:08:04 rburton: thanks for info, I'll check them out Jun 16 14:08:23 hmm, builing for this project on krogoth Jun 16 14:09:54 I need to make some real progress before I can try that :) Jun 16 15:23:56 my recipe declares DISTRO_FEATURES_remove = "x11 wayland directfb" Jun 16 15:24:39 There's not much point to that. A recipe can't affect other recipes, so that'll only change how your recipe builds, and there are almost certainly better ways to do that. Jun 16 15:25:28 i see Jun 16 15:25:45 how do I remove these features then? Jun 16 15:26:23 HAS_X11 = "${@bb.utils.contains("DISTRO_FEATURES", "x11", "yes", "no", d)}" Jun 16 15:26:26 do it in a global config file, not a random recipe Jun 16 15:26:45 local.conf Jun 16 15:26:47 if you're doing it from an append, you could just bypass or disable the logic that's conditional upon distro features Jun 16 15:28:50 sorry, i don't follow Jun 16 15:29:48 the recipe I declare the _remove is my top level project recipe, not an append Jun 16 15:30:18 or are you suggesting I use an append to disable these features? Jun 16 15:37:12 "top level project recipe" doesn't make sense Jun 16 15:37:43 distro features are policy, they affect many, many recipes, and as such can only be set in configuration metadata, which is global, and therefore flows down to all recipes Jun 16 15:37:54 distro .conf would be ideal, but local.conf would work if need be Jun 16 15:38:49 thanks kergoth Jun 16 15:39:06 np Jun 16 15:43:16 zeddii, fwiw I am no longer sure it is a kernel version issue Jun 16 15:43:27 fscking heisenbugs Jun 16 15:44:28 :D Jun 16 15:55:02 I'm on the verge of burning this board with fire Jun 16 15:56:18 Crofton|work: x86 or arm? Jun 16 15:56:26 arm Jun 16 15:56:29 go for it Jun 16 15:56:34 rofl Jun 16 15:56:44 every little helps! Jun 16 17:37:52 Hi people. I've recently updated my distro and as a result gcc 6.1.1 was installed. With that version of gcc the yocto is not able to be built. Fail at 1xx. task - glibc. Fixing and patching programs along the way seems to be a long way to go.... Jun 16 17:37:52 Is there any option to use host compiler different than default "gcc"? For example "gcc-4.9"? Is there some suffix variable, that would append "-4.9"? Thank You a lot! Jun 16 17:38:57 you can choose the prefered version Jun 16 17:39:05 he's talking about the host compiler, not target Jun 16 17:39:07 there are variables for the host compiler. BUILD_CC, BUILD_CXX< etc. see meta/conf/bitbake.conf Jun 16 17:40:54 okay I'll try it. :) :) thanks Jun 16 18:44:29 Theremin: which version of OE are you on ? Jun 16 18:44:43 master should work fine with gcc6 on build host Jun 16 18:46:28 There were bunch of package updates which can not be backported to release branches although I think it will be good to get atleast 2.1 release be buildable on build hosts which have gcc6 Jun 16 18:48:06 Hello! I would like to add a kernel parameter on boot. Unfortunately, searching "cmdline", "bootargs", or "init=" in the doc returns no result. Is there a variable to define kernel boot parameters? I'm using standard poky distro. Jun 16 18:55:14 francis, largely depends on the arch and hence bootloader. e.g. x86 --> grub, powerpc --> u-boot. Jun 16 18:55:45 paulg_: arm board with sdcard Jun 16 18:58:27 chances are there is a board specific README for whatever BSP you are using that will lay out how the sdcard is populated and with what. Jun 16 18:59:33 but it will be board and bootloader specific, so you won't find generic steps in the generic yocto docs. Jun 16 19:00:48 OK, I'll check, thanks. In this case, it seems to be defined directly in the CONFIG_CMDLINE of the kernel. Jun 16 19:01:13 yah, that is by far the least user friendly place to set the kernel command line. Jun 16 19:04:06 but if that is what you are faced with currently, then "bitbake -c menuconfig linux-yocto" will let you futz with the existing setting. Jun 16 19:04:47 then recompile and redeploy the updated zImage or whatever you are booting. Jun 16 19:12:29 paulg_: did just that, thanks! When searching to use u-boot, I came to this patch: http://comments.gmane.org/gmane.linux.embedded.yocto.general/30150 Jun 16 19:12:45 Does not seems to be merged yet, or is it? Jun 16 19:17:27 khem: jethro 14.0.2 ... I'll try the most recent master. Thanks. Adjusting BUILD_CC/CXX did not help :-/ some options have been unknown. Therefore it failed. It seemed like it used 6.1 flags on 4.9 gcc. Jun 16 19:18:25 it failed on building simple program as a part of the configuration step of m4-native.. Jun 16 19:37:59 sorry, I forgot to remove CFLAGS from local config.. however, now I am moving on master. Thank you for help Jun 16 20:54:38 paulg, when enabling u-boot with the latest meta-raspberrypi, looks like a file is missing: build/tmp/work/raspberrypi3-poky-linux-gnueabi/u-boot-rpi/git-r0/git/include/linux/compiler-gcc.h:87:30: fatal error: linux/compiler-gcc5.h: No such file or directory Jun 16 20:56:06 Maybe the patches above fixes the issue? Jun 16 21:09:45 francis, that smells like the r-pi folks haven't caught up to the gcc-6 changes. Jun 16 21:10:28 ok, i'll investigate, thanks! Jun 16 21:15:26 francis: if this were gcc-6 related i would expect an error message that would say "linux/compiler-gcc6.h: No such file or directory" Jun 16 21:39:52 tlwoerner, if they hard coded a gcc5 reference in their layer then it would fail when we stopped putting that gcc5 header into the sysroot... Jun 16 21:40:19 i.e. when we moved to gcc-6 Jun 16 21:42:05 ok, well, it's worst than that, u-boot-rpi uses git version from 2012 https://github.com/gonzoua/u-boot-pi/tree/rpi Jun 16 21:44:06 I think that's why Paul Parker got rid of it: http://comments.gmane.org/gmane.linux.embedded.yocto.general/30150 Jun 16 21:45:21 I'll try the patches to see if they work Jun 16 21:45:58 could be ; I've had nothing to do with the r-pi boards. Jun 16 21:54:04 kind of surprised the u-boot is using such an ancient baseline tho... **** ENDING LOGGING AT Fri Jun 17 02:59:58 2016