**** BEGIN LOGGING AT Mon Feb 01 02:59:58 2016 Feb 01 08:20:35 kergoth: morning. do you want (me) to take more action on what we fiddled with yesterday? I have a feeling a patch is needed. Feb 01 08:33:10 good morning Feb 01 09:15:01 it seems all the source code of programs bundled with the SDK is available in the SDK sysroot. How can I prevent this? Feb 01 09:21:36 i don't really see why the C code needs to be part of the -dbg package, isn't it enough with a non-stripped object built with -g ? Feb 01 19:34:47 hi, on my, perhaps not so update to data, danny branch I get warnings about "The recipe is trying to install files into a shared area when those files already exist. Those files are" for none arch specific packages... Feb 01 19:35:32 multi-machine build? Feb 01 19:35:45 I don't get them on fido / jethro so it is fixed somewhere, does someone have a hint where this is solved? Feb 01 19:35:54 yup, multi machine Feb 01 19:36:29 most likely it's being rebuilt when teh machine changed. i.e. a non-arch-specific recipe depending on a machine-specific recipe Feb 01 19:36:43 or a hidden machine dependency, i.e. the recip eis marked as arch independent, but references machien Feb 01 19:40:25 ok, thanks, I will check Feb 01 19:44:53 (and it is up to date not up to data...) Feb 01 19:50:40 kergoth: happen to know what this does, do_deploy[stamp-extra-info] = "${MACHINE}" in deploy.bbclass? Feb 01 19:55:29 nevermind, google knows http://lists.openembedded.org/pipermail/openembedded-core/2015-September/111177.html Feb 01 20:21:05 khem: ping Feb 02 00:51:35 I'm trying to create a recipe for a custom application that needs to be compiled with an other library headers, but I don't know how to do this... The other library recipe is successfully built but I have no idea how to dynamically derive its include path. Maybe there's a misunderstanding here, but how can I solve this? **** ENDING LOGGING AT Tue Feb 02 02:59:58 2016