**** BEGIN LOGGING AT Fri Oct 06 03:00:01 2017 Oct 06 06:29:38 hi.. i get "NameError: global name 'd' is not defined" when using d.getVar in python function registered with addhandler Oct 06 06:31:32 i did it like buildstats.bbclass: https://github.com/kraj/poky/blob/master/meta/classes/buildstats.bbclass#L109 Oct 06 06:34:56 oh! got it! since i am on fido, i changed to use e.data.getVar like buildstats from fido branch Oct 06 07:00:12 morning all Oct 06 07:01:22 is there a way to build ssh server with moduli (/etc/ssh/moduli) ? Oct 06 07:01:46 at this point a moduli can be found there but i have some trouble with it Oct 06 07:01:56 and each time i need to re-generate it: Oct 06 07:02:16 ssh-keygen -G moduli-1024.candidates -b 1024 Oct 06 07:02:16 ssh-keygen -T moduli-1024 -f moduli-1024.candidates cp moduli-1024 moduli Oct 06 07:02:25 thanks Oct 06 07:53:36 Hi all. I have a problem today... I made an image recipe which require another one. But the image_install of the required one isn't included into the new image recipe. Is it normal? Oct 06 08:14:57 Maybe i found the problem Oct 06 08:15:11 i require two images... Oct 06 08:15:40 I guess, it doesn't like the fact of requiring two images. Oct 06 08:20:38 ChrysD: the image recipes are likely setting the IMAGE_INSTALL variable (via = ...)? you likely want them to append to the IMAGE_INSTALL via += or _append Oct 06 08:22:40 nrossi : they all have IMAGE_INSTALL+= Oct 06 08:23:26 ChrysD: check that the final value is what you expect ... with bitbake -e Oct 06 08:25:41 nrossi : i found the problem Oct 06 08:25:50 nrossi : i didn't expected that the problem was from there Oct 06 08:26:27 nrossi : The architecture : My new image => Require : Image n°1 from core image minal and Image n°2 from core image minimal Oct 06 08:26:43 nrossi : but core image minimal is just only IMAGE_INSTALL Oct 06 08:26:58 so when bitbake do the 2nd required one, it will erase the first one Oct 06 08:27:24 nrossi : i've checked for the intermediary images but didn't expect that core-image-minimal use IMAGE_iNSTALL= Oct 06 08:28:21 ChrysD: :), btw in most cases you should just use the 'packagegroup-*' instead of including/requiring other images Oct 06 08:29:07 nrossi : Yeah, i wanted to do a russian doll. Oct 06 08:29:30 nrossi : But maybe i should consider doing packagegroup Oct 06 08:29:41 ChrysD: i see, matryoshka style recipes :) Oct 06 08:30:13 nrossi : usually i do an image recipe like 'client-image' Oct 06 08:30:23 nrossi : and i have another one which is 'client-image-debug' Oct 06 08:30:35 nrossi : which i add many tools for debugging. Oct 06 08:30:37 ChrysD: do look at packagegroups, it will probably save you a bunch of pain with regards to images setting other variables (like IMAGE_ROOTFS_SIZE) Oct 06 08:31:34 ChrysD: have at look at packagegroup-base.bb, will show you a good example of how you can construct sets of groups for that sort of thing Oct 06 08:32:41 nrossi : yeah, because my new image = Client-image + my image with debug tools. So i will still do the "client-image-debug" but instead of requiring my image with debug tools i should add the debugtools with packagegroup Oct 06 08:32:44 nrossi : thank you Oct 06 09:00:07 nrossi : Myabe even in my case i don't really need the "real"packagroup. I could just do a recipe which rdepends my debug tools and i can call that package "debug-tools" no? What does packagegroup gives as advantages? Oct 06 09:27:56 What is the default dhcp client in Yocto? Oct 06 09:29:19 Does anyone here know anything about python and dbus? I've upgraded to pyro, and my 'gi' mainloop seems to be gone. I grepped the recipes and I could not find anything about it. Does anyone know what is the recommended approach for dbus mainloops in py these days? Oct 06 09:40:35 Does anyone know if there is a python-gi package provided by any recipe? Oct 06 09:41:05 Grep turns up empty. Perhaps gobject-introspection_*.bb, but I'm not sure Oct 06 09:43:27 sveinse: there is http://layers.openembedded.org/layerindex/recipe/51352/ Oct 06 09:43:42 and http://layers.openembedded.org/layerindex/branch/master/recipes/?q=gobject Oct 06 09:46:13 At this point I wish it would be possible to search and list all packages and files within a recipe, like most distos have. I do know yocto is not a distro, but finding where to find what provides a specific file is much harder Oct 06 09:46:23 Thanks, baali Oct 06 09:48:53 sveinse: assuming you've built it already this is trivial. but i presume you're looking for a web site or similar? Oct 06 09:50:07 rburton: Yes, when it's built it's easy. But this time I'm looking for a (python) file which I don't know what is provided by Oct 06 09:50:15 what file? Oct 06 09:50:39 I'm looking for /usr/lib/python2.7/site-packages/gi/* Oct 06 09:50:46 python-gobject Oct 06 09:51:24 erm, python-pygobject Oct 06 09:51:52 you may need to resort to meta-python for the py2 version if you're using a version of oe which has dropped the py2 recipes Oct 06 09:51:53 right, so this has been moved away from poky and oe then Oct 06 09:52:29 https://layers.openembedded.org/layerindex/recipe/51352/ Oct 06 09:52:32 we used this in krogoth without any additional layers. But this is fine, now I know what layer to use Oct 06 09:52:50 thanks Oct 06 09:53:27 maybe someone needs to write a tool to take a world pkgdata dump and generate a web site that lists all the packages and files Oct 06 09:53:45 so you can run it on your krogoth based system and get a nice index you can then search Oct 06 09:53:56 rburton: that would be awfully nice, yes Oct 06 09:54:14 we're using pyro now, and that's why I need this extra layer Oct 06 09:54:59 if i were you i'd do a known good build with krogoth so you have a reference of what files/packages/recipes are used Oct 06 09:55:20 though presumably you had a dependency on python-pygobject somewhere to get that file in the image in the first place Oct 06 09:55:37 rburton: is there a way to instruct bb to build everything in a layer? Oct 06 09:55:42 bitbake world Oct 06 09:55:54 right, great Oct 06 09:57:19 that does indeed help a lot -- for the known layers Oct 06 09:57:28 thanks guys Oct 06 10:13:36 sveinse : and most of the cases, grep + find doesn't help because file come from an upstream link and not locally :s Oct 06 10:17:55 hi. can i edit the .templateconf file so that my own layer can supply an additional bblayers.conf.sample file and it gets combined with the original bblayers? Oct 06 10:18:53 i'm trying to make my own combolayer which by adds the contained layers by default, but i want to keep the samples in meta-poky original if possible, and would rather extend the configuration Oct 06 10:19:28 peacememories : when you start a build, you can tell which bblayers.conf.sample you want Oct 06 10:19:53 when running bitbake? or when running oe-init-build-env? Oct 06 10:20:22 i mean i could just edit .templateconf and change the directory referenced there completely. that wouldn't be too bad i guess Oct 06 10:20:54 peacememories : when you run a fresh build Oct 06 10:21:07 peacememories : so when you run oe-init-build-env for first time Oct 06 10:21:24 okay, thanks for the info :) Oct 06 10:21:53 i think Oct 06 10:21:59 when you call oe-init-build-env Oct 06 10:22:07 you have something like TEMPLATECONF = Oct 06 10:22:12 and you can specify the conf on your layer Oct 06 10:22:17 But i'm not sure Oct 06 10:22:44 the TEMPLATECONF is actually also set by the .templateconf file, that doesn't seem too big of a problem :) Oct 06 10:22:50 http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#creating-a-custom-template-configuration-directory Oct 06 10:23:31 thanks for the link, i'll read that for now :) Oct 06 10:23:46 oh yeah i see that i have templateconf.cfg file which i can modify it. Oct 06 10:25:09 peacememories: https://github.com/rossburton/customdistro is an example of a super-minimal custom distro that overrides a few things like that Oct 06 10:25:18 peacememories: using submodules to pull in bitbake and oe-core Oct 06 10:25:35 thanks Oct 06 10:25:59 rburton : so for you is better to have an env script instead of telling oe-init with the TEMPLATECONF variable? Oct 06 10:27:08 ChrysD_: custom env script means you don't need to remember to set TEMPLATECONFI every time Oct 06 10:27:23 all it does is set templateconf and call the real init script Oct 06 10:27:36 it also means that the script is located in the repo root instead of inside openembedded-core in this case^^ Oct 06 10:27:43 yes, because its not part of oe-core Oct 06 10:27:51 that was just an example i did for someone a while ago Oct 06 10:27:55 Hi guys, I am trying to add exfat filesystem support to my yocto image. I've installed fuse-exfat and exfat-utils, my config kernel has CONFIG_FUSE_FS=m but my mount attemps are still failing: mount /dev/sda1 /media ends with mount: unknown filesystem type 'exfat Oct 06 10:28:07 but oe-init-build-env actually checks for a .templateconf file in oeroot to set its templateconfig, so i would prefer that approach to writing a custom init script Oct 06 10:28:21 despite so, mount.exfat /dev/sda1 /media works like a charm Oct 06 10:28:56 peacememories: sure, i probably forgot that exists :) Oct 06 10:29:28 so the problem is: I use libmount in an application that manages usb mounts/umounts Oct 06 10:30:14 and my mount() attemps with exfat filesystems are failing Oct 06 10:31:29 for what I've read and tested on my laptop, mount internally will invoke mount.exfat when fstype==exfat Oct 06 10:32:55 does any of you have any hints about? Oct 06 10:33:27 note that I use mount from utils-linux, not the busybox one Oct 06 11:23:55 Mhh... Having bitbake -e telling that your package is in IMAGE_INSTALL but they are not in the image produced :s Oct 06 12:16:47 ChrysD: check your image .manifest Oct 06 12:26:31 zero_note : it is. Oct 06 12:27:48 zero_note : But that's not even the problem. I get two project, which both have image recipe that require the core image minimal and having the same local.conf but in one hand you have one kernel module that is loaded automically and the other one not... And i'm trying to find out why. :s Oct 06 12:31:40 ChrysD: are you able to load the module using modprobe in the image where the module is not automatically loaded? Oct 06 12:32:54 zero_note Oct 06 12:32:58 zero_note : yeah Oct 06 12:33:04 zero_note : it's inside Oct 06 12:34:50 ChrysD: ok, is there any .conf in /etc/modules-load.d/ ? Oct 06 12:35:04 zero_note : in the first image, i have 7 kernel modules loaded + one other. But in case of the second image, you have only the 7 kernel modules loaded Oct 06 12:35:33 zero_note : in both distribution i don't have modules-load.d Oct 06 12:39:34 ChrysD: this sounds strange to me. You don't have it neither in /run or /usr/lib ? Oct 06 12:40:12 zero_note : nope Oct 06 12:42:49 ChrysD: are you using systemd as init system? Oct 06 12:44:17 zero_note : not Oct 06 12:46:45 ChrysD: so you should have some scripts in /etc/init.d which are responsible of kernel module loading Oct 06 12:47:00 hi all Oct 06 12:47:06 and you should have /etc/modules Oct 06 12:47:17 zero_note : i don't Oct 06 12:47:36 sorry for asking again, but guess no one was alive at the time i posed the question innitially Oct 06 12:47:39 (10:01:21 AM) Costin: is there a way to build ssh server with moduli (/etc/ssh/moduli) ? Oct 06 12:47:39 (10:01:45 AM) Costin: at this point a moduli can be found there but i have some trouble with it Oct 06 12:47:39 (10:01:56 AM) Costin: and each time i need to re-generate it: Oct 06 12:47:39 (10:02:15 AM) Costin: ssh-keygen -G moduli-1024.candidates -b 1024 Oct 06 12:47:39 (10:02:15 AM) Costin: ssh-keygen -T moduli-1024 -f moduli-1024.candidates cp moduli-1024 moduli Oct 06 12:47:39 (10:02:25 AM) Costin: thanks Oct 06 12:48:35 ChrysD: I am sorry, but at this point I can't understand how your out-of-tree modules are being loaded Oct 06 12:49:06 zero_note : Yeah that's my point ahah Oct 06 12:49:11 ChrysD: :D Oct 06 12:49:32 zero_note : with the same kernel Oct 06 12:50:51 ChrysD: something about your kernel cmdline? Oct 06 12:51:24 zero_note : what is funny, is that for the image which load automatically, the image is base d on core-image-minimal directly and the distro is poky with only my added layer .. ahah Oct 06 12:51:45 I know that module options can be set there, but I am not sure about loading/blacklisting Oct 06 12:52:46 zero_note : same kernel cmdline Oct 06 12:55:21 Hi, one of my custom recipes need a environment variable set. The env var contains a path to some libs it need for compilation. What's the correct way to set an env var? Oct 06 13:02:36 I'm having fun with a package that gets included in the rootfs image in different versions depending on whether it was a clean build or if it has already been built before we included the new version in our own layer. The older version is still getting provided by a BSP layer; we'd prefer not to modify the BSP if it can be avoided. I have a hunch that the difference in PACKAGE_ARCH (the BSP provides per-machine / pe Oct 06 13:02:36 r-SoC packages whereas the recipe in our own layer outputs a single package for all our boards) has something to do with the indeterminism. I'd appreciate if somebody could point me towards the logic that decides which exact package ends up on the system (or maybe even knows how to solve it, preferably without crude hacks). Oct 06 13:06:17 zero_note : maybe with udev Oct 06 13:12:22 hello. It is just me or the browsing of the package does not work on the following webpage: https://www.yoctoproject.org/toaster/image-recipe-details.html Oct 06 13:13:13 The 'next' button or the 'show rows' does not work. It only shows the first 10 package and that is it.. Oct 06 13:13:57 where can I report this minor issue ? Oct 06 13:14:06 i don't think it's an issue Oct 06 13:14:11 Toaster is locally. Oct 06 13:14:21 SO maybe the toaster in yoctoproject is just an "example" Oct 06 13:14:29 But i'm not sure of what i'm saying as i don't use toaster Oct 06 13:19:35 hello, what do I have to do to make mkfs.vfat usable during the do_install task of my recipe? Oct 06 13:20:05 I get mkfs.vfat: not found during do_install Oct 06 13:21:09 here is my recipe: https://pastebin.com/BX3XVKci Oct 06 13:23:32 eduardas_m: DEPENDS += "dosfstools-native" might do the trick. Oct 06 13:30:57 silbe: thank you, mkfs.vfat is now usable Oct 06 13:35:35 silbe, eduardas_m: that sounds like we may have a missing dependency Oct 06 13:45:07 RP: I am using Yocto Pyro Freescale community BSP if you are wondering Oct 06 13:49:56 Is it OK to submit a patch to OE-core that makes a recipe depend on something provided by another layer if it is hidden by PACKAGECONFIG (and off by default?) Oct 06 13:51:03 JPEWhacker: yes, absolutely Oct 06 13:51:20 JPEWhacker: I think we already have such things in oe-core Oct 06 13:51:37 kanavin: Thanks! Oct 06 13:51:57 JPEWhacker: if you could also add a comment pointing out where the thing is Oct 06 13:53:03 kanavin: Sure. Oct 06 13:54:15 khem: go-dep and go-helloworld fail with musl - known issue? Oct 06 14:04:08 if someone of you guys was wondering about my complains for unknown exfat filesystem, the answer (and fix) is commit f291c5e076e907a0b80cfc4f4967d90fdd9b46de from meta-openembedded master Oct 06 14:04:30 It is correct that bitbake -e does the same process as bitbake --parse-only would, right? Oct 06 14:39:45 Is there a rule in bitbake that assigns the content of VAR_foobar into VAR if MACHINE=foobar unless VAR is otherwise set ? Oct 06 14:40:16 yes, there has to be Oct 06 14:44:18 what is the proper way of getting the number of the Yocto release in a bitbake recipe so that I can modify some scripts with the release string during do_configure? Oct 06 14:44:35 is there a variable for that? Oct 06 15:19:51 RP: Wouldn't think so (missing dependency in poky). The recipe posted inherited from image_types, but not from image so it's a just regular recipe with no default dependencies. Oct 06 15:45:48 silbe: right, fair enough Oct 06 17:46:00 Does pyro allow for a generic environment to run a recipe under? What I mean is that we build three images for three MACHINE, and this work all fine. But at the final steps, we would like to run a recipe which can fetch all three machine outputs into a common end-user installer, but I really havent found any good way to do this from bitbake yet. Today we do this outside Yocto, but it is difficult, as you'd Oct 06 17:46:06 want the variables from bitbake in it. Any ideas or pointers? Oct 06 17:47:09 I mean, I have a python program which parses bitbake -e into something that can be used by other build frameworks such as make for it to execute the final processing :o Oct 06 17:50:36 sveinse: I think you may want to look at what core-image-minimal does for core-image-minimal-initramfs, it may be useful to emulate that in some way Oct 06 17:51:06 sveinse: but you'd still be using a hack Oct 06 17:51:20 aehs29: right. yes Oct 06 17:52:21 It might be possible with BBMULTICONFIG Oct 06 17:52:40 is there a no-arch MACHINE, or perhaps a host machine setting you may use for running these special recipes? Oct 06 17:52:53 sveinse, yeah... thats kind of what you would need... Oct 06 17:55:59 because, due to (per MACHINE) pseudo, you will have to fetch the artefacts from deploy/ and unpack them, rather than fetching from tmp/work, so what MACHINE you're running under is not really that important. However, these recipes makes no sense unless all of the MACHINE outputs have been run, a dependency which I don't know is supported in bb yet. Oct 06 17:58:08 I dream of writing bitbake customer-image, which then can propegate into multiple MACHINEs and build all and the same recipe images for all of them and then run the collector/image installer recipe in the end. Oct 06 18:20:05 FWIW I found the provider selection logic in bitbake/lib/bb/providers.py but couldn't figure out (within reasonable time) how PACKAGE_ARCH comes into play (maybe somewhere inside the cache implementation?). As a work-around I've now made our own recipe machine/SoC-specific as well; this seems to fix this issue. Not great (especially as it means I only have a partial understanding of the issue), but still better than Oct 06 18:20:06 known build consistency issues. Oct 06 19:03:12 so 2.5 is sumo is it a tribute to bit wrestlers :) Oct 06 19:18:28 khem, yes, Yocto is getting bigger and is still agile Oct 06 19:20:49 RP is going to have to wear a Mawashi when it releases Oct 06 19:30:10 Does RP name these? Who ever does is my hero.... best game ever Oct 06 19:41:27 armpit: he yes Oct 06 20:00:50 Anyone know where the Wic kickstart files reside in the YP source repositories? I found 4 in poky/meta-yocto-bsp/wic. There should be more available. Oct 06 20:05:47 scottrif, inside Poky distro? Oct 06 20:06:34 yes - Actually I just got an answer in a private chat. Oct 06 20:08:24 k Oct 06 22:03:44 JPEWhacker: the names are my doing, yes :) **** ENDING LOGGING AT Sat Oct 07 02:59:59 2017