**** BEGIN LOGGING AT Fri Mar 21 02:59:58 2014 Mar 21 08:43:59 good morning Mar 21 10:04:56 what is the proper way to make a recipe that will be automatically rebuilt each time I build it? i.e. with a higher version? I tried to set PRINC := "${@int(DATETIME)}" but then when bilding multimachine configuration (package arch is set to machine arch) I get "recipe is trying to change PR from 'r20140321095212' to 'r20140321091120'. This will cause do_package_write_* failures since the incorrect data will be used and they will be unable to find the rig Mar 21 10:05:00 any hints? Mar 21 10:20:12 make one or more tasks nostamp Mar 21 10:20:46 hi koen :) been a while Mar 21 10:21:13 how do I figure out which tasks are critical for this error? Mar 21 10:22:37 I suspect making configure or compile nostamp would do the trick Mar 21 10:23:49 thanks! let me try Mar 21 10:26:00 if i want to make an environment variable available to Bitbake, but not necessarily to all recipes, what is the best approach? I wish to reference env. variable FOO from my layer.conf, which is parsed by bitbake upon startup. I do not however see that individual recipes need access to FOO, therefore I do not think adding FOO to BB_ENV_EXTRAWHITE is the correct way here? Mar 21 10:33:38 I did consider something like FOO = "${@d.getVar('BB_ORIGENV', False).getVar('FOO', False)}" in my bitbake.conf, but for whatever reason ${FOO} is undefined at the point where bblayers.conf is read. Perhaps bitbake.conf is not read until after bblayers.conf is parsed, in which case i guess you are limited to use just a few variables inside bblayers.conf Mar 21 10:34:12 if I print ${FOO} at a later stage, for example by doing "bitbake -e myrecipe", it does have a correct value Mar 21 10:53:18 morning all Mar 21 10:56:51 gm Mar 21 10:58:29 hi Crofton|work Mar 21 11:49:23 koen: thanks a lot, looks like your suggestion worked Mar 21 11:55:29 morning bluelightning Mar 21 11:55:37 hi mago_ Mar 21 12:47:14 is there a way to list all "images" that can be generated? basically, i'd like to list all bitbake tasks which have no children in the dependency graph Mar 21 12:47:57 i noticed the "hob" gui is capable of listing all available images, i assume it shows all tasks which inherit from some specific image base? Mar 21 13:26:06 mago_: all targets (i.e. recipes) yes; although it does so using an internal api Mar 21 13:26:23 it checks for all targets that inherit from image.bbclass Mar 21 13:32:09 i noticed i could use bitbake-layers show-recipes and grep for "*-image*", seem to get me close enough to what i wanted Mar 21 20:03:47 otavio, you think 09ab3a00598d06e3a1bf871811c2ac37359c74da in oe-core master would break fsl sd images ? cause I'm seeing a weird tty error on boot now.. Mar 21 20:14:58 oh gawd, this game again. I need to figure out where this Yocto build put... pretty much anything. Mar 21 20:20:19 actually the first time I boot the image its ok, but the second time the systemd service for dev-ttymxc0.device hangs Mar 21 20:42:08 kroon: I don't think so Mar 21 20:42:17 but I didn't try it Mar 21 20:43:17 otavio, yeah, i'm more inclined to thinking its due to the systemd update. Mar 21 20:44:32 hmm, koen's suggestion did not work after all :( what is the way to create an "autoincremented pr" package, i.e. one that will be built each time? I'm getting "Recipe xxx is trying to change PR from 'r20140321204225' to 'r20140321204143'. This will cause do_package_write_* failures since the incorrect data will be used and they will be unable to find the right workdir." koen suggested to try and set do_configure/do_compile to nostamp and it did build then Mar 21 20:44:41 the next build it failed again Mar 21 20:44:52 this all worked in an 1.5 year old core Mar 21 20:46:30 so something must have changed but I can't seem to find a way around it Mar 21 21:52:00 always fun when running a from-scratch... http://i.imgur.com/K6Ro2eF.png **** ENDING LOGGING AT Sat Mar 22 02:59:59 2014