**** BEGIN LOGGING AT Sat Feb 23 02:59:58 2013 Feb 23 11:45:19 I have a binary-only package that also contains a prebuilt kernel module. I tried to use cp ${S}/themodule.ko ${D}/lib/modules/${KERNEL_VERSION}/kernel/drivers/ in do_install(), but it doesnt work - ${KERNEL_VERSION} is empty Feb 23 11:45:39 any idea on how to accomplish this? installing the .ko file to the modules directory? Feb 23 12:27:53 dv_: Which classes do you inherit? Feb 23 12:28:47 none, I found the modules class, but it seemed as it that one is for recipes which build modules, and thats not what I want. Feb 23 12:29:30 currently I am installing regular binary-only shared libraries and this kernel module in the same recipe. would it be perhaps better to split this up? Feb 23 12:29:52 dv_: KERNEL_VERSION is exported by a bbclass. if you do not inherit it.. :) Feb 23 12:30:07 dv_: at least in OE-core there is a module-base Feb 23 12:31:09 ah! perfect! I think thats what I need Feb 23 12:31:13 thanks Feb 23 12:31:59 also, are you familiar with HOSTCC related problems in u-boot? I am trying to add a recipe for a customized u-boot, but I get errors like "strip: Unable to recognise the format of the input file `doimage'" Feb 23 12:32:46 the recipe is small: http://pastie.org/6321738 perhaps it is something wrong with the fork itself? Feb 23 12:37:26 why do you think it has anything to do with HOSTCC? Feb 23 12:38:02 in my bbappend for u-boot (from the time of edison) I set UBOOT_MACHINE, UBOOT_IMAGE, UBOOT_SYMLINK.. Feb 23 12:38:16 because of the error Feb 23 12:38:35 it seems it builds with the cross compiler and tries to strip that with the host stri Feb 23 12:38:38 *strip Feb 23 12:38:49 without u-boot.inc nobody can say something Feb 23 12:39:05 and since this happens in the uboot tools/ directory, I figure the stuff over there should be built with the hostcc, not the cross one Feb 23 12:39:20 oh, okay, it is the u-boot.inc from yocto Feb 23 12:40:09 here it is: http://pastie.org/6321760 Feb 23 12:41:57 and the log Feb 23 12:43:31 http://pastie.org/6321773 Feb 23 12:45:20 hm looks like its taking strip from host system Feb 23 12:45:32 you could try to set it explicit Feb 23 12:46:42 but first look into the Makefiles of u-boot if you can override strip Feb 23 12:46:46 okay, but this is what confuses me. these tools, are they supposed to be used on the host system later on, or are they for the target? Feb 23 12:47:03 depends Feb 23 12:49:03 now I get the same with a different tool: strip: Unable to recognise the format of the input file `gen_eth_addr' Feb 23 12:49:14 and looking at the Makefile, it is evident this one is supposed to be built with HOSTCC Feb 23 12:49:38 see https://github.com/rabeeh/u-boot/blob/master/tools/Makefile#L172 Feb 23 12:51:30 so your u-boot tree differs from mainline Feb 23 12:51:57 yeah , seems so :/ Feb 23 12:52:12 I'll ditch the u-boot.inc then, and adapt its contents to my recipe Feb 23 16:06:02 Hello. Feb 23 16:06:32 I'm writing recipe which will provide two additional packages: Feb 23 16:06:33 PACKAGES =+ "${PN}-ania16 ${PN}-andreas16" Feb 23 16:07:02 It is possible to specify different post install actions for each package? Feb 23 16:07:34 yes Feb 23 16:08:01 add _${PN}-ania16 or _${PN}-andreas16 to the post_installs Feb 23 16:09:57 pkg_postinst_${PN}-ania16, right? Feb 23 16:10:02 yes Feb 23 16:10:53 Is there any bitbake manual available? Feb 23 16:11:08 yes Feb 23 16:11:22 and yocoto documentation Feb 23 23:46:54 I have recipe file foo-data.bb Feb 23 23:47:02 And recipe foo.bb Feb 23 23:47:31 What is the correct way to put *something* in foo.bb to build foo-data.bb and make it available in reposiory, but not included in image? Feb 23 23:57:35 otwieracz: typically you would use RSUGGESTS for that sort of thing but I don't know if RSUGGESTS will actually cause foo-data to be built Feb 23 23:57:56 there is OPTIONAL_PACKAGES in my image/ Feb 23 23:58:02 s/\//./ **** ENDING LOGGING AT Sun Feb 24 02:59:58 2013