**** BEGIN LOGGING AT Mon Sep 04 03:00:00 2017 Sep 04 07:07:47 good morning Sep 04 07:54:33 in The Old Days (1.4), is there a way to enable creation of rootfs/sdk manifests? Sep 04 09:14:17 koen: is ti-dmai-dev sufficient in my toolchain-target sdk recipe to develop apps that use the dsp? Sep 04 09:15:24 no idea, I haven't touched DSP stuff in over 5 years now Sep 04 09:20:53 koen: oh how good that must be :) Sep 04 09:22:19 I'm working with pyro these days, but occasionally something needs to be done on our legacy product. Sep 04 09:22:32 hurts every time :) Sep 04 09:23:50 I know the feeling :) Sep 04 09:42:19 this is from that old build, but perhaps someone remembers what fixes this: https://pastebin.com/G8vjdStk Sep 04 09:49:03 tasslehoff: is that actually enabled as a module in the kernel? Sep 04 09:49:47 tasslehoff: that error will happen any time a kernel module is in RDEPENDS (or IMAGE_INSTALL) and no such module is enabled, since the kernel claims it provides kernel-module-* Sep 04 09:50:29 is "dsplinkk" a typo? Sep 04 09:53:57 bluelightning: not a typo. I think perhaps it is because an empty package is not created Sep 04 09:55:02 tasslehoff: another possibility occurred to me - is that an external kernel module that is being "satisfied" by the kernel and therefore the real recipe isn't being built? Sep 04 09:56:28 bluelightning: it is indeed an external module. the recipe is built I think, but I get "Not creating empty archive for kernel-module-dsplinkk" Sep 04 09:56:40 ah ok Sep 04 09:56:50 If I can just manage to enable the empty archives, I hope all will be well :) Sep 04 10:54:36 I added ALLOW_EMPTY_${PN} and ALLOW_EMPTY_${PN}-dev in the recipe. Is that correct? It still does not create the empty archive. Sep 04 11:05:04 assign to "1"? Sep 04 11:14:37 rburton: I did that, but I (ofc) had to write ALLOW_EMPTY_kernel-modules-dsplinkk instead Sep 04 11:15:05 yeah you need to specify the exact package that you want to be allowed empty Sep 04 11:15:59 rburton: yeah. at first I thought it would affect all packages created by that recipe, but that would not have been very flexible :) Sep 04 11:41:18 Hey! How would I go about setting a recipe local variable from a (python) task so that it can be used from within a later task? Is it even possible with the way variables are scoped? Sep 04 11:41:31 Specifically what I would like to do is add a couple of things to the SYSTEMD_SERVICE_${PN} from an earlier task. Sep 05 02:16:08 Question: if I wanted to instrument some of the code being built by bitbake (say, a library like musl), is there a way to alter the code in-situ without redownloading it from the source? **** ENDING LOGGING AT Tue Sep 05 03:00:00 2017