**** BEGIN LOGGING AT Thu Jan 02 02:59:59 2014 Jan 02 08:41:12 RP: have you seen my git patch? What do you think about it? Jan 02 13:19:10 Hi everydoby. If I add "linux-firmware" to my image I get "Computing transaction...error: Can't install linux-firmware-1:0.0+git0+600caefd83-r0@all: no package provides /bin/bash". It looks like I'm not alone. http://www.jann.cc/2012/08/08/building_freescale_s_community_yocto_bsp_for_the_olinuxino.html Have you got any suggestions? Jan 02 13:19:38 I'm building for i.MX28 Jan 02 13:43:42 mmm... looks like linux-firmware requires bash. Why? Jan 02 17:05:48 why is the kernel *never* rebuilt for local modifications just if I reconfigure or I manually delete it? Jan 02 17:05:51 it is dead tiring. :/ Jan 02 17:07:22 I am trying to build the images after deleting them manually from the deployment folder (that may be wrong though) Jan 02 17:08:40 what is the best way with bitbake to rebuild an image with custom modifications in the workdir, e.g. an additional printf? Jan 02 18:04:24 hi there Jan 02 18:05:10 I have a image recipe containing mostly 'IMAGE_INSTALL' entries. Now I need to have 2 images sharing the same 'IMAGE_INSTALL' entries. Can I put them into some.conf file and in both image recipes inherit that conf file? Jan 02 18:09:35 anybody? Jan 02 18:12:53 .in file? Jan 02 18:13:01 .inc file Jan 02 18:14:58 I think I can do: image_base.bb with all IMAGE_INSTALL inside and then image1 with 'require image_base.bb' and image2 with the same Jan 02 18:15:28 that's what initramfs-kexecboot-klibc-image.bb does in meta-oe Jan 02 18:16:08 you can do whatever you want. bitbake doesn't care what the name is of the file you include other than having a sane extension. but that said, if the thing you're including isn't a useful recipe on its own, as Crofton|work points out, the extension should be .inc rather than .bb Jan 02 18:16:56 you could also have a base image and require it, then append more stuff Jan 02 18:17:06 probably several way to get the same result Jan 02 18:17:08 kergoth: right now I have only one image recipe which is usefull recipe. I just have to do another image recipe which inherits everything + adds some more stuff Jan 02 18:17:23 cool Jan 02 19:51:52 * mranostay yawns Jan 02 21:51:12 okay, that's just silly. if you run bitbake -C , it errors indicating it can't invalidate a nostamp task, rather than continuing. IMO it should just continue, since clearly bitbake will treat it as though it was invalidated anyway, such an operation would be a no-op Jan 02 22:09:19 https://github.com/kergoth/oe-test-scripts#leaky-layer-tests not sure if this'll be of any use to anyone else, but I found a need for it Jan 02 22:19:13 kergoth: interesting, you obvious found some! Jan 02 22:23:34 kergoth: maybe just a INFO or WARNING? Jan 02 22:29:19 course, the downside is the use of whatchanged means it only tests the recipes involved with a particular target, not everything being appended. but its okay as a first pass **** ENDING LOGGING AT Fri Jan 03 02:59:58 2014