**** BEGIN LOGGING AT Wed Dec 09 03:00:26 2015 Dec 09 09:34:38 meta-oe changes still on hold, at least one more week for test-dependencies build to finish.. Building recipe: ltp (1236/2503) Dec 09 12:42:58 Hello, I am trying to package octave and I am having an issue with the "install". The package builds two versions of mkoctfile (a binary to create octave packages) Dec 09 12:43:09 one build for the target, and one for the host Dec 09 12:43:45 how dow I install the host version in the staging dir, so it can be used to cross compile octave pkgs Dec 09 12:51:26 ? Dec 09 13:12:07 ribalda: did you look at http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#ref-classes-native ? Dec 09 13:29:01 funman: I was trying to avoid it.... Dec 09 13:29:11 but apparently I cannot ;) Dec 09 13:29:46 I wanted to use the already build native binaries Dec 09 13:30:45 also it is a hell of dependencies Dec 09 19:55:42 hi, is there a way to do something like PROVIDES_${PN} += from outside of the recipe itself? Dec 09 19:56:00 where exactly are you wanting to do it? Dec 09 19:56:21 you can use a bbappend, or you can use an override to do it from local.conf or some other config file (PROVIDES_${PN}_append_pn-recipename = " foo") Dec 09 19:58:37 kergoth: from a tcmode-external-*, just to map all initial* / linux-headers / glibc to the binary toolchain... (but then preferably without modifying the libc recipes) Dec 09 19:59:01 kergoth: thanks I will give a try... Dec 09 19:59:08 that's an odd choice, why not just do what meta-sourcery and meta-linaro and others do? Dec 09 20:00:26 kergoth: ah it is for the pet project, libc6-dev is a auto generated recipe extracting a deb image Dec 09 20:02:12 kergoth: I actually "stole" the recipes from meta-sourcery, but the target libraries are coming from the target not the cross toolchain.. Dec 09 20:03:05 i'd just fork the external layer and adjust the provides and preferences to align with your deb recipes, but you could do it from the tcmode too, yes Dec 09 20:18:48 kergoth: this seems to work PROVIDES_append_pn-libc6-dev = " virtual/libc linux-libc-headers virtual/${TARGET_PREFIX}compilerlibs virtual/${TARGET_PREFIX}libc-for-gcc" Dec 09 20:19:05 sounds about right Dec 09 20:19:48 its likely you'll hit issues relating to the fact that you have split out multiple recipes from what is one recipe in the core, so your dep graph could be missing bits. worst case you could create a new recipe that deps on your other recieps and does the needed provides, though Dec 09 20:19:51 * kergoth shrugs Dec 09 20:40:59 kergoth: we will see, I guess I will hit in one or more issues anyway ;) Dec 09 21:07:11 kergoth: ah now I understand what you meant I guess, the split of libc6.bb and libc6-dev.bb, that can be easily changed.. it is auto generated.... Dec 09 21:07:39 right, libc6 is virtuallibc, but libc6-dev is linux-libc-headers, etc Dec 09 21:08:00 but yeah, you could either change how they're generated, or just create empty wrapper recipes that depend on the pieces and set provides in that Dec 09 21:08:36 the assumption by the build is that once virtual/libc has been built, both the c library and its headers are available in the sysroot, of course Dec 09 21:31:11 kergoth: it works good enough for my hacking, see https://github.com/jhofstee/meta-bin-deb/commit/f3c057b83b910bfa6edc64d895208f67290ad848#diff-368a4a9359252ef559db6882f887a894R155 Dec 09 22:01:01 kergoth: happen to know how to prevent a package being created in deploy/*? **** ENDING LOGGING AT Thu Dec 10 02:59:59 2015