**** BEGIN LOGGING AT Wed May 16 03:00:12 2018 **** BEGIN LOGGING AT Wed May 16 06:34:46 2018 May 16 08:39:38 hello guys. I need an information.. What is the purpose of NO_GENERIC_LICENSE[Firmware-cypress]="LICENCE.cypress" ? May 16 08:59:31 New news from stackoverflow: Adding graphic environment to yocto image May 16 10:02:03 hi all, I'm trying to use yocto for the first time on an imx28evk. I managed to finish the compilation phase of the core-image-minimal using bitbake. I'm confused about how to create the sd card. I attempted with wic but fails with a series of files not found. Some advice? Thanks in advance. May 16 10:03:13 MC___: can you put the fail log into a pastebin, please? May 16 10:06:11 of course.. https://pastebin.com/ruD7NLNn thanks. May 16 10:09:18 hello guys. I need an information.. What is the purpose of NO_GENERIC_LICENSE[Firmware-cypress]="LICENCE.cypress" ? May 16 10:09:26 looks like the wic script wants additional files that are not built by default, but thats merely guesswork May 16 12:28:15 hello, I just upgraded to yocto 2.5 sumo, and I have trouble with the RDEPENDS_kernel-base setting May 16 12:28:38 I used to set RDEPENDS_kernel-base = "" in my machine configuration, to prevent the kernel image to be installed on the rootfs May 16 12:28:53 this was working fine with rocko, but now with sumo I have the following error May 16 12:29:32 well, not really an error, but a warning May 16 12:29:54 WARNING: ... Variable key RDEPENDS_${KERNEL_PACKAGE_NAME}-base (${KERNEL_PACKAGE_NAME}-image) replaces original key RDEPENDS_kernel-base (). May 16 12:30:39 rrerolle: unless you're actually pulling the kernel into IMAGE_INSTALL one way or another, it really shouldn't be installed and hence no means needed to "prevent" it from being installed May 16 12:30:46 does anyone know what I'm experiencing this ? Why does the RDEPENDS from the kernel class take precedence over the one defined in my machine configuration ? May 16 12:31:14 as the message says you need to use RDEPENDS_${KERNEL_PACKAGE_NAME}-base now May 16 12:31:21 http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/classes/kernel.bbclass?id=5b4aab6b40cf21471442e21abc8051b38985de84 was the change May 16 12:31:31 but thats a terrible way to stop a kernel going into images May 16 12:31:49 ah, ok, that make sense...I thought ${KERNEL_PACKAGE_NAME} would resolve to "kernel" May 16 12:32:19 it would by default, the warning is that the name you're using will be overwritten by another unrelated variable May 16 12:33:52 do you have out-of-image kernels, or do you not want a kernel at all? May 16 12:33:59 (ie containers don't need kernels) May 16 12:34:30 * LetoThe2nd bites keyboard not to throw some container pun May 16 12:34:37 in fact I have a specific need, and I think now i'm getting this because of the workarounds I used so far May 16 12:34:55 what I wanted was the kernel to be installed on the rootfs, but *with* the embedded initramfs May 16 12:35:12 so this means, not the kernel-image package, since it doesn't embed the initramfs May 16 12:35:37 thus I created another package, which does provide a /boot/bzImage with the initramfs May 16 12:36:29 don't know if that makes sense ... but it's this package i'm trying to install...but I guess through some dependencies, kernel base gets installed as well, so I probably missed something May 16 12:41:07 # Allow machines to override this dependency if kernel image files are May 16 12:41:07 # not wanted in images as standard May 16 12:41:08 RDEPENDS_${KERNEL_PACKAGE_NAME}-base ?= "${KERNEL_PACKAGE_NAME}-image" May 16 12:41:51 that's precisely what I'm trying to do, so I don't understand the warning and why I cannot override this dependency :/ May 16 12:42:07 the ?= should allow me to override, isn't that right ? May 16 12:45:04 RDEPENDS_${KERNEL_PACKAGE_NAME}-base="" May 16 12:47:19 yes ok, I probably mistyped or left something over on my first try, it's working now, thanks ! **** BEGIN LOGGING AT Wed May 16 15:51:01 2018 May 16 16:29:40 I'm having some trouble getting protobuf to install correctly in my locally-built SDK. I can see the static libs in the installed SDK directory, but I don't have a protobuf.pc which (I believe) means that when I try to depend on it when building a project with the SDK it can't be found. Using protobuf 3.5.1 recipe from the OE layer repository but have older versions of protoc and protobuf-native. The closest I've May 16 16:29:41 come so far is adding an IMAGE_INSTALL_append to my local.conf but that still doesn't get me quite all the way there... is there a handy howto someone could point out? May 16 16:49:28 protobuf-dev should provide protobuf.pc May 16 16:57:24 hey all, say I want to write an "image" recipe that simply takes any deployed files from a set of packages created by other recipes and creates a .tar.gz of those files...I tried this with the base image class (image.bbclass), but the archive contains an entire rootfs May 16 16:57:42 khem: sorry if i'm not following, are you saying there should be a protobuf-dev recipe, or is it something i should depend on in one of the other recipes? May 16 16:58:17 emilyshaffer[m]: if you have included protobuf into your image then you should have .pc file in SDK May 16 16:59:11 khem: ahhh, so i probably missed it in the image recipe May 16 16:59:30 ebolton: you can munge the rootfs via a rootfs post processing function May 16 16:59:40 emilyshaffer[m]: seems likely May 16 17:00:27 tyvm! May 16 17:04:00 @khem: how? is there a way to get a list of deployed files from a recipe in another recipe? May 16 17:14:40 ebolton: you can do something like ROOTFS_POSTPROCESS_COMMAND += 'your_munging_func;' and then delete the uneeded files from the rootfs in the function your_munging_func() in image recipe May 16 17:31:13 New news from stackoverflow: Setting Linux Capabilities in Yocto ext4 Image May 16 18:39:52 ebolton: a tar.gz image is exactly what you want, surely May 16 18:43:42 appreciate the help guys, but again, getting an image is straight forward, the problem is getting an image that only contains files from specific recipe packages, I don't want the entire manifest from a typical rootfs, I think I can get there with a custom recipe that includes some functions from rootfs.py and manifest.py, it'll just take time May 16 18:47:49 ebolton: oh you don't want dependencies to be satisfied? May 16 18:48:33 in that case the sdk generation is a good example of something built using exact package lists i guess May 16 19:09:25 Does it make sense that the building uses rpm to package, but rpm utility is missing in target ? May 16 19:10:29 yes May 16 19:11:03 ranran: you need to add the package-management IMAGE_FEATURE to get rpm on target May 16 19:11:40 smurray - Ok. I understand. thanks May 16 21:49:40 rburton: do you want to give another shot at my gcc-8 branch May 16 22:12:57 https://www.openembedded.org/wiki/OEDEM_2018 May 16 22:13:04 Get your names on the list! May 16 22:16:21 khem: yeah its on the list of things to do May 16 22:16:32 spent the last 12 hours doing manual cve review May 16 22:24:28 manual CVE review seems tedious May 16 22:28:40 khem: yes! May 16 22:35:04 ouch May 16 22:35:41 kergoth: god its almost like someone should sell a commerical yocto which does security issue tracking/review/reports **** ENDING LOGGING AT Thu May 17 03:00:02 2018