**** BEGIN LOGGING AT Mon Feb 05 03:00:02 2018 Feb 05 03:50:09 New news from stackoverflow: How to install module 'ws' with 'Node.js'? Feb 05 06:54:14 is meta-ide-support still supported in rocko ? I used this, to setup a build system derived toolchain, and then build my app from outside yocto. But now it fails, it cannot find cmake. Feb 05 06:55:17 It looks it's related to the recipe specific sysroots introduced in pyro Feb 05 07:28:57 Hi, guys! Can you help me with LIC_FILES_CHKSUM? I created my own recipe and got "LIC_FILES_CHKSUM points to an invalid file: /mnt/home/USER/wrlinux-x/build/tmp-glibc/work/mipsisa64r6el-wrs-linux/PACKNAME/git-r0/PACKNAME-git/COPYING [license-checksum]" Feb 05 07:30:08 i know that my license file places in /mnt/home/USER/wrlinux-x/build/tmp-glibc/work/mipsisa64r6el-wrs-linux/PACKNAME/git-r0/git/COPYING Feb 05 07:30:38 how to describe it in bitbake recipe? Feb 05 08:05:11 ok. it was easy) Feb 05 08:05:33 i have no more questions) Feb 05 08:28:56 good morning Feb 05 09:32:09 Where should feature requeste for bitbake be directed? Feb 05 09:44:25 sveinse: probably bugzilla Feb 05 10:27:47 Good Morning, Feb 05 10:27:48 If I may ask Feb 05 10:28:18 Yocto expects a "supported" Linux version to be build Feb 05 10:28:44 How yocto project deals with testing/running older versions ? Feb 05 10:29:10 Do you use Ubuntu LTS to build all versions? Or old Debian/Fedora run in VM? Feb 05 10:29:14 or Docker ? Feb 05 10:39:45 lukma: older YP versions may not run on newer Linux hosts Feb 05 10:51:41 mckoan: Yes, I do know :) Feb 05 10:52:07 The question is - what is the perferable way for building them ? Feb 05 10:52:33 I saw one approach to have "set in stone" different Ubuntu LTS versions as VM's Feb 05 10:53:08 lukma: thats an obvious approach, yes. Feb 05 10:53:11 (as it may happen that I would need to make some adjustments in the future) Feb 05 10:53:59 LetoThe2nd: But I was wondering if maybe yocto team has some other (maybe better approach) for their QA Feb 05 10:54:23 lukma: we test currently supported yocto releases on supported linux distros, by doing full builds Feb 05 10:54:34 RP, I'm looking for a feature where an interrupted bitbake is allowed to finish its current recipes, not just tasks. Does bitbake have such a feature? Feb 05 10:55:00 kanavin: But do you run them (supported distros) as VMs? Feb 05 10:55:33 lukma: maybe or maybe not, it's all in the cloud from my perspective :) Feb 05 10:55:50 kanavin: s/cloud/fog/ Feb 05 10:55:51 :-) Feb 05 10:55:58 This would be nice particularely on large recipes, where finishing the recipe would push the results to the sstate cache. This would in turn save time next erased and restarted build, since it can be found in the statecache Feb 05 10:57:34 lukma: do have a transition plan in place for both the host distro version, and yocto release in production use. you do not want to accumulate technical debt that way. Feb 05 11:00:12 sveinse: it does not and I'd probably be reluctant to add that due to the complexity and hardcoding ;/ Feb 05 11:00:21 kanavin: So your recommendation is to continually move forward with in-production yocto and build host ? Feb 05 11:01:09 RP: ok. thanks Feb 05 11:01:56 sveinse: I understand the desire but it adds a lot of complexity and multiple code paths which is something I'm wary of Feb 05 11:02:13 is meta-ide-support still supported in rocko ? I used this, to setup a build system derived toolchain, and then build my app from outside yocto. But now it fails, it cannot find cmake. Feb 05 11:02:14 It looks it's related to the recipe specific sysroots introduced in pyro Feb 05 11:02:40 RP: yes sure. It's a convenience thing, and I fully understand the complexity argument. Feb 05 11:03:42 lukma: I guess my recommendation is to have a thorough automated test suite and run it both against released yocto branch and yocto master :) Feb 05 11:04:26 kanavin: I' Feb 05 11:04:38 m wondering how many companies uses such approach Feb 05 11:04:57 and how many others will have yocto 2.0 with ancient LTS ubuntu in VM........ Feb 05 11:05:06 as far as you know, does exist a YP BSP for BeagleBone BLUE ? Feb 05 11:05:18 (because it worked..... 10 years) Feb 05 11:05:46 Is it possible to enquire the number of SetScene and RunQueue tasks without actually executing anything? In the context of building a progress bar in the build system. Feb 05 11:05:47 mckoan: I only saw BBB support for yp-2.4.1 Feb 05 11:06:10 lukma: then customers ask for a kernel update because meltdown and what are they going to do :) Feb 05 11:06:11 lukma: yes, I know, thx Feb 05 11:06:40 kanavin: There will be a problem....... Feb 05 11:07:09 And following question -> is it possible to backport meltdown/spectre patches on our customized 3.10 kernel ? :) Feb 05 11:07:40 lukma: ask the maintainer of your customized kernel :) Feb 05 11:08:06 lukma: if that's a yes|no question then the answer is yes. It's only software :) Feb 05 11:08:34 kanavin: :-) Feb 05 11:14:09 * mckoan found the proper BB-blue kernel https://github.com/beagleboard/linux/blob/4.14/arch/arm/boot/dts/am335x-boneblue.dts Feb 05 11:21:32 New news from stackoverflow: Device (iMX6) is not available from external network Feb 05 11:29:21 lukma: "If you rely on any other kernel tree other than 4.4, 4.9, or 4.14 right now, and you do not have a distribution supporting you, you are out of luck. The lack of patches to resolve the Meltdown problem is so minor compared to the hundreds of other known exploits and bugs that your kernel version currently contains. You need to worry about that more than anything else at this moment, and get your Feb 05 11:29:27 systems up to date first." http://www.kroah.com/log/blog/2018/01/06/meltdown-status/ Feb 05 11:31:54 mcfrisk: Thanks for reply Feb 05 11:32:03 I do use LTS kernels (4.9 now) Feb 05 11:32:20 I was just wondering how yocto QA team deals with having the matrix Feb 05 11:32:37 of supported linux distro versions and versions of released yp's Feb 05 11:32:55 for example we do have 2.3.3, 2.2.x 2.4.1 Feb 05 11:33:11 and for example - for 2.4.x recommended distro is debian 8,9 Feb 05 11:33:19 but for 2.3.x only debian 8 Feb 05 11:36:27 and yp 2.4.x has some issues when compiled from scratch on debian 8 Feb 05 11:50:28 lukma: standardize the build environment for yocto, also helps with leaks from build env to product. lxc, docker, plain chroot are available for that. Feb 05 12:17:11 Does anyone know what this error message means? "checking dynamic linker characteristics... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES." Feb 05 12:21:44 New news from stackoverflow: build system derived toolchain in Yocto Feb 05 13:57:41 hello, when trying to source the environment for a Yocto Rocko SDK I get a message "Empty filename passed to function". What might be the problem? Feb 05 13:59:20 trying to source environment right after installing it: https://pastebin.com/tMfP6BCZ Feb 05 14:07:41 eduardas_m: is your shell something not bash? Feb 05 14:08:14 rburton: no, it's regular bash on Kubuntu 16.04 Feb 05 14:09:43 rburton: can INHERIT += " rm_work" somehow mess up populate_sdk? Because that is one of the more prominent recent changes I made Feb 05 14:09:55 shouldn't do Feb 05 14:11:04 rburton: I also started using meta-qt5 master instead of rocko branch... I've heard that mixing releases is not supported, but the image itself built well Feb 05 14:12:13 wanted to get Qt 5.10 Feb 05 14:13:26 i guess you'll have to read the script to find out why it fails Feb 05 14:13:50 set -x will make it print the lines as it runs them Feb 05 14:16:24 rburton: where exactly do you mean to set -x? Feb 05 14:16:35 . /opt/fslc-qt5-10/2.4.1/environment-setup-armv7at2hf-neon-fslc-linux-gnueabi -x ? Feb 05 14:16:51 set -x; . /opt/blaa/blaa Feb 05 14:16:56 should work... Feb 05 14:19:05 rburton: thank you. was not aware of that. here is the output: https://pastebin.com/FVVkLPb0 Feb 05 14:19:36 looks meta-qt5 related Feb 05 14:19:43 yeah Feb 05 14:20:44 rburton: any recommendations other than reverting to rocko branch? Feb 05 14:20:55 no idea, never used qt5 Feb 05 14:21:05 switching to rocko qt5 would tell you if it was a problem in master or not Feb 05 14:21:38 rburton: I actually used the rocko branch before... populate_sdk used to work fine Feb 05 14:23:14 RP: I have 4.14 and 4.15 ready to go for linux yocto, but lttng-modules is failing to build for mips64 ... the resolution isn't trivial. I may send a RTF while I work on it. Since I have a feeling that no one else is building mips64 at the moment. :D Feb 05 14:24:52 rburton: thank you for the advice. probably will be more careful when mixing branches in the future Feb 05 14:27:08 zeddii: sounds good, thanks. We can run that up on the autobuilder, see if there are any other issues Feb 05 14:27:22 eduardas_m: regular bash on Kubuntu 16.04 is 'dash' Feb 05 14:30:37 mckoan: well, on ubuntu /bin/sh is dash but the user's shell is bash Feb 05 14:30:43 i was wondering if the shell was zsh or similar Feb 05 14:31:39 mckoan: interesting, did not know that Feb 05 14:32:33 same on debian fwiw Feb 05 14:32:35 lrwxrwxrwx 1 root root 4 Jan 24 2017 /bin/sh -> dash Feb 05 14:33:16 but passwd has the shell as /bin/bash so you still get a proper shell Feb 05 14:33:16 eduardas_m: AFAIK Yocto required $ sudo dpkg-reconfigure dash in older versions, so I'm still doing that Feb 05 14:33:23 mckoan: fixed long ago Feb 05 14:33:39 actually I'm uncertain it is still required with latest version like rocko Feb 05 14:33:55 rburton: good to know, thx Feb 05 14:33:59 regressing that is a bug, and there's a tool to scan sh blocks in recipes for bashisms Feb 05 14:45:05 JaMa: hello, I have seen you do work in meta-qt5 master branch... trying to use master branch with other layers set to rocko... populate_sdk does not work for me, sourcing environment seems broken: https://pastebin.com/FVVkLPb0 Is it just me or is master branch currently not fully usable? Feb 05 14:46:04 JaMa: notice "Empty filename passed to function" line Feb 05 15:52:30 New news from stackoverflow: ABI mismatch when building go project with a yocto recipe Feb 05 16:47:51 Are the directions for getting access to poky-contrib still up to date: https://wiki.yoctoproject.org/wiki/Poky_Contributions ? I e-mailed Michael Halstead but haven't heard back. Feb 05 16:48:06 Hey, so I would like to always enable ahci on BIOS on bootup. Currently doing this manually. Is there a way to setup my yocto files so that the .hddimg does this automatically? Feb 05 16:48:56 JPEWhacker, I'll track down your e-mail right now. One moment. Feb 05 16:49:26 halstead, Thanks! Feb 05 16:51:58 JPEWhacker, Found it. I'll set up jpew/ now. You'll have a response shortly. Feb 05 16:52:40 New news from stackoverflow: Add mondgoc and libbson to yocto distribution Feb 05 16:55:28 RP: I did manage to get lttng-modules building against v4.15, so I'll do a bit more testing and send my series with those fixes as well. Feb 05 17:03:16 zeddii: nice :) Feb 05 20:17:43 hi all Feb 06 01:00:16 why is "poky" pronounced "pah-kee Feb 06 01:00:18 "" Feb 06 01:00:41 (just curious what the etymology of it is, and I other than how to pronounce it, I don't see *why* to pronounce it that way) Feb 06 01:11:48 hello, I am getting a dnf error during do_populate_sdk_ext. (do_populate_sdk_ext: Could not invoke dnf. Disk Requirements: At least 224MB more space needed on the ____ filesystem), but there is 300+G on the specified filesystem, /tmp has over 10G. Any Ideas? Feb 06 01:13:58 I have a working bsp layer for my adzs-sc589-ezlite board. What is involved in being able to invoke runqemu adsz-sc589-ezlite? Feb 06 01:14:54 I was looking at the meta-raspberrypi layer but couldn;t find any reference to qemu. Does anyone know if that bsp produces runqemu artifacts? Feb 06 02:34:54 * armpit_IST hmm, why is COMPATIBLE_HOST not working on my system **** ENDING LOGGING AT Tue Feb 06 03:00:04 2018