**** BEGIN LOGGING AT Fri Jul 19 02:59:57 2019 Jul 19 03:48:44 New news from stackoverflow: Unable to mount root file system - nfs if the CONFIG_CGROUP is not enabled in Linux Kernel? Jul 19 06:33:28 Hi, I try to install the package "grpc" () on my yocto image. https://layers.openembedded.org/layerindex/recipe/86424/ Jul 19 06:34:19 However, bitbake cannot find the package. The specified layer is available on my local machine, and I added it to conf/bblayers.conf Jul 19 06:35:08 Other recipes of the layer (meta-networking) are available. Can anyone give me a hint? Jul 19 06:37:18 ERROR: Nothing PROVIDES 'grpc'. Close matches: grep grpc-go Jul 19 06:49:08 BBLAYERS ?= " \ (...) (...)/meta-openembedded/meta-oe \ (...)/meta-openembedded/meta-networking Jul 19 06:52:28 ThomasD13: The recipe is available on your disk? Jul 19 06:53:24 Chrusel: This is my bb config: https://pastebin.com/ByESFceh Jul 19 06:54:13 ThomasD13: pastebin is blocked by our company IT -.- Jul 19 06:54:42 Chrusel: ahhh okay I think I've got the problem... I messed up the root path of my poky variants.... Jul 19 06:55:11 shit, sorry. Didn't see that earlier... thank you for jumping in Jul 19 06:55:51 ThomasD13: your're welcome ;-) Jul 19 07:37:58 good morning Jul 19 10:04:17 aehs29: ah kaby lake. handily i have a kbl nuc on my desk. i'll knock up a core-image-minimal to see what happens here Jul 19 10:19:39 New news from stackoverflow: How to change image name in yocto? || Install a custom deb package as a bitbake recipe Jul 19 11:25:06 Hi all. I'm still struggling with this python issue. Jul 19 11:25:42 I'm trying to add ntpath and pathlib as a bbappend to the python3 recipe. Jul 19 11:26:33 If I add my additional packages to the python-3.5-manifest.inc file it works. Jul 19 11:26:54 If I instead use that exact same code within a bbappend to the main python3 recipe (the one that requires the inc file) Jul 19 11:26:57 It does not work. Jul 19 11:27:14 The recipes for the new packages are found, and nothing complains. Jul 19 11:27:24 But an empty RPM is all that is generated Jul 19 11:29:15 Since these are stock parts of python 3, I also don't know why they aren't part of the main recipe anyway? Jul 19 11:30:17 Khem looks to have done the work for this within the generate-manifest-3.5.py file. Jul 19 11:31:03 JoeR: you're really going at this from the wrong end Jul 19 11:31:15 oe-pkgdata-util find-path **/pathlib.py Jul 19 11:31:33 *without any of your changes* Jul 19 11:31:39 will tell you what package pathlib is in Jul 19 11:31:55 or, just depend on python3-modules, and you'll get the entire library Jul 19 11:33:24 It's not listed as part of python3-modules though. Jul 19 11:33:59 It's entirely absent from the Python3 recipes in my ancient Krogoth. Jul 19 11:33:59 python3-modules is an empty meta package that depends on all the others Jul 19 11:34:22 Yeah, I see it getting created by that script khem did, but it doesn't list pathlib Jul 19 11:34:28 so its in python3-misc Jul 19 11:34:50 oe-pkgdata-util will look up files in the built packages Jul 19 11:35:00 Cool, let me try that then. Jul 19 11:35:39 i'd drop your changes and build the pristine recipe first though Jul 19 11:36:30 Wow. I wish I knew this the whole time. Jul 19 11:36:42 Thanks, again. I'm always here saying thanks! Jul 19 11:39:08 np Jul 19 11:42:51 Incidentally, why does my approach not work at all? Is it because that file is already taken and owned by another recipe? Jul 19 11:51:51 any ideas what is wrong here: poky/meta/recipes-kernel/perf/perf.bb.do_clean, the basehash value changed from 91ce334f170ca8a5934155f2342ec46a to 73d2603423b0027ba93ecb090164458e. The metadata is not deterministic and this needs to be fixed. Jul 19 12:01:42 mcfrisk: Did you changed any files while building was in progress? Jul 19 12:03:30 is there a way to exclude recipes from parsing, without separate layers? I would like to create a layer suitable for a class of devices, just amalgamating all recipes in one place. Jul 19 12:03:30 Some recipes require e.g. nodejs, but will not be included in every image. I don't like pulling in the nodejs layer if unneccessary for a specific image … Jul 19 12:08:10 alessioigor: not intentionally. tried to recover a few times by wiping tmp and restarting build but result was the same. cleansstate also failed. now I removed all *:perf:* files from sstate and triggered a new build. some race condition somewhere.. Jul 19 12:39:41 jmiehe: a recipe being in an layer doesn't mean it will be in the images Jul 19 12:40:01 core-image-minima doesn't include the X server, but X is in oe-core Jul 19 12:50:06 New news from stackoverflow: How to change target image name in yocto? Jul 19 13:16:33 is there a preferred X11 Window Manager for a genericx86? Jul 19 13:20:10 New news from stackoverflow: do_patch can't find files Jul 19 13:24:18 I mean if I want something Desktop-like, not Sato Jul 19 13:24:41 what are using people at Intel? Jul 19 14:42:55 rburton, I figured what triggered the bug. apparently it was that the recipe replaced /usr/lib by STAGING_LIBDIR and /lib by STAGING_BASELIBDIR but the /lib also matched /usr/lib so it resulted in madness Jul 19 14:43:08 now I'm doing the replace with python's re.sub and it works fine Jul 19 15:20:28 New news from stackoverflow: Install packages from remote apt repository during build yocto Jul 19 15:34:00 mckoan: intel yocto users don't use desktop-like environments Jul 19 15:34:25 there's a xfce layer that is well tested Jul 19 15:35:44 rburton: thanks, I tested it but I don't like it. at the moment I switched to Sato Jul 19 15:43:32 Hi folks! I might have misheard it, but is there a Yocto summit (that's separate from the Yocto dev day) at ELC NA? Jul 19 15:47:27 mckoan: i've a plan to get gnome3 packaged up but that involves spare time, which i don't have Jul 19 16:05:50 rburton: lightweight is one of my needings Jul 19 16:06:23 I'll give Sato a chance Jul 19 16:27:12 its very much designed for a traditional PIM device that just happens to work on desktop-scale environments Jul 19 18:49:17 Are there any docs/examples using multiple toolchains in yocto? I want to use separate toolchain for the kernel vs some userspace applications Jul 19 18:50:13 Perhaps something can be done with multiconfig? Jul 19 19:41:06 rburton: Im assuming you already took a look at the bug Jul 19 19:41:45 rburton: once you check on your NUC, can you comment to see if we should enable i915 as built in? Jul 19 19:42:04 rburton: Idk if theres a reason why its not enabled already Jul 19 19:42:24 rburton: also it'd be nice if genericx86_64 worked out of the box as well Jul 19 19:43:33 rburton: again, unless theres some reason why we shouldnt Jul 19 19:43:57 * aehs29 goes afk Jul 19 19:45:34 rabbit9911: idk why you would do that, but yes you can use multiconfig to achieve something like that Jul 19 19:47:57 hi, I have defined small packagegroup which contains some features and sometimes (not always) I'm seeing issue like that: package packagegroup-test-features-1.0-r0.raspberrypi3 requires packagegroup-test-feature-update, but none of the providers can be installed Jul 19 19:48:03 when doing rootfs Jul 19 19:48:17 aehs29: To use an external llvm toolchain for example. Jul 19 19:48:18 I've tried to look and in deploy all ipks exists Jul 19 19:48:30 not sure how to debug this though Jul 19 19:48:32 any ideas? Jul 19 19:59:54 rabbit9911: both the ISS and clang layers have classes to pick toolchain per recipe Jul 19 20:00:02 no need to use multiconfig **** ENDING LOGGING AT Sat Jul 20 02:59:56 2019