**** BEGIN LOGGING AT Wed Dec 10 02:59:59 2014 Dec 10 07:28:37 kergoth: packported a few patches regarding BUILD_DD but none of them worked on 1.5.x. I'll just backport the gcc-4.9 binutils build fixes. Many of the features I see interesting or useful in yocto/bitbake are often broken, sigh. Dec 10 07:28:55 /BUILD_DD/BUILD_CC/ Dec 10 07:47:00 Good Morning Dec 10 08:01:29 good morning Dec 10 08:27:34 anyone has luck with clang+llvm in yocto? Dec 10 08:44:17 anyone has luck with clang+llvm in yocto? Dec 10 08:45:55 morning all Dec 10 08:49:36 bluelightning: good morning Dec 10 08:50:31 hi chankit Dec 10 08:52:10 bluelightning: do you know of anyone who has luck with clang+llvm? Dec 10 08:59:30 bluelightning: I started off from http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-core/llvm/llvm.inc..then I modified it to include clang, clang tools and compiler-rt. Dec 10 09:01:33 I was close to accomplishing this but when I tried to include llvm inside my actual image I got nothing provides libllvm3.3-clang...and I'm stuck here now Dec 10 09:03:35 chankit: I've not done anything with clang/llvm I'm afraid Dec 10 09:11:41 bluelightning: ok then...let me try removing the process of adding RDEPENDS and see if it works Dec 10 09:43:01 <_valle_> Hi everyone! Dec 10 10:16:53 <_valle_> I would like to do something after do_rootfs is done just before the images are created. How could I do this? Dec 10 10:19:13 _valle_: generally you would add a shell function and then add a call to that to ROOTFS_POSTPROCESS_COMMAND Dec 10 10:20:02 _valle_: http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-ROOTFS_POSTPROCESS_COMMAND Dec 10 10:57:22 How to i do a kernel menuconfig, I am using beaglebone recipes and trying "bitbake -c menuconfig" but i get a "Nothing to do" Dec 10 10:59:27 shouldn't it be "bitbake virtual/linux -c menuconfig", so bitbake knows *which* menuconfig you're actually talking about? Dec 10 11:03:00 maybe but doesn't work in my case, still trying to figure out yocto.. Dec 10 11:06:30 zenx: perhaps you are hitting https://bugzilla.yoctoproject.org/show_bug.cgi?id=6880 Dec 10 11:06:32 Bug 6880: normal, Medium+, 1.8 M2, richard.purdie, IN PROGRESS REVIEW , Redhat/Fedora Shellshock Fix Leads To oe_terminal breakage Dec 10 11:10:06 the fix is now in master: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=eb2ea6fd2d2dc626ead13de1ec334d4220651612 Dec 10 11:29:25 rburton: good; I can handle it Dec 10 11:29:34 rburton: when do you intend to push it? Dec 10 11:30:32 otavio: today, assuming i can work out the last few problems Dec 10 11:34:36 asking again: how to find out planned task execution order? bitbake -g shows the graph but it's too big to be displayed, and I want to add a post processing steps to do magic with generated package ipk repository Dec 10 11:37:38 mcfrisk: there is no set order per se, tasks are scheduled as their dependencies allow Dec 10 11:50:22 but there are a number of predefined tasks, and they are executed in specific order. My question is what is this execution order. Dec 10 11:50:50 e.g. after which task is the ipk repo complete? Dec 10 11:51:36 or after which task is an image file complete, though there I think I saw some post process variable to hook into Dec 10 11:52:31 mcfrisk: creating the image happens during do_rootfs Dec 10 11:53:19 mcfrisk: there are various variables that allow you to inject commands into do_rootfs, e.g. ROOTFS_POSTPROCESS_COMMAND, IMAGE_PREPROCESS_COMMAND, etc. Dec 10 11:53:30 but not for package repo... Dec 10 11:53:34 which one you would use depends on when exactly you need your commands to be executed Dec 10 11:54:40 well the package repo isn't a thing that is considered on its own in our normal build process - each package is written out by individual recipes; however during do_rootfs we do reindex the package feeds as suitable for the image Dec 10 11:55:09 what is the "magic" you are intending to do? Dec 10 11:55:34 tar the ipk repo Dec 10 12:09:37 mcfrisk: well, you could add it after the do_rootfs image task for example Dec 10 12:10:05 the do_rootfs task runs as soon as it considers the repository ready Dec 10 12:11:57 RP: ok, what about multiple bitbake image targets? Are all images executed in parallel? Or is do_rootfs called only when all packages from all targets are done? Dec 10 12:14:45 mcfrisk: in that case you'd need to add a target which depends on all the images you're interested in Dec 10 12:17:46 RP: yep, that's we have. And all post processing then needs to be in this package. Or the post processing can stay in other scripts which are called after bitbake is done, since knowing when everything is done is tricky within bitbake/yocto. I see package-index is also just a special recipe... Dec 10 12:36:43 <_valle_> bluelightning: Thank you! Dec 10 12:37:00 anyone tried to update glib-2.0 to 2.42? Dec 10 12:38:38 bboozzoo: no but it should be trivial as we have 2.40 in master already. patches welcome! Dec 10 12:40:32 ok, what I'm trying to do seems impossible with yocto/bitbake, e.g. execute various post processing commands after ipk repo is done (tar repo), after all images are done (tar images), after all builds are done (tar logs). I will execute these in wrapper scripts instead. Dec 10 13:32:39 Hello, how can i find out what version of kernel does yocto buils ? Dec 10 13:44:45 Hello, how can i find out what version of kernel does yocto build ? Dec 10 13:45:49 cross fingers and repeat the question every 10 minutes Dec 10 13:45:56 or you can try bitbake -e virtual/kernel Dec 10 13:48:09 bitbake -s should list it as well Dec 10 13:48:24 as linux- Dec 10 13:48:29 thank you Dec 10 13:56:43 JaMa: *crossesfingers* what are next saturdays lottery winning numbers? Dec 10 14:03:23 LetoThe2nd: 4, 8, 15, 16, 23 and 42 Dec 10 14:06:16 ddalex: thanks! Dec 10 14:06:49 hmm wait! which lottery? Dec 10 14:09:20 JaMa: ++ Dec 10 16:26:18 I need to support multiple boards (with different BSP layers), and each one is going to have its own /etc/fstab. I'm not sure how to express this in bitbake recipes. Dec 10 16:26:36 The base-files recipe in poky will install /etc/fstab, and there's no easy way to remove that without forking the recipe. Dec 10 16:26:45 I can do a .bbappend to get it to use *my* fstab in the BSP layer, but then I can't have more than one BSP layer enabled at one time. Dec 10 16:26:49 Any ideas on how to solve this? Dec 10 16:30:04 gabrbedd: .bbappend and machine overrides? Dec 10 16:33:39 joseppc: yeah, koen in #oe said the same. Looking into that, now. Dec 10 16:34:02 ah, ok Dec 10 19:54:17 I'm using yocto and I try to mount an SPI Flash memory, I added IMAGE_INSTALL_append = " mtd-utils" when I try to mount my mtd the os says that jffs2 is not a supported filesystem and mkfs.jffs2 doesn't exist. Does anyone knows why? Dec 10 20:00:17 mtetreault: well IMAGE_INSTALL doesn't change your kernel config Dec 10 21:10:36 zecke: How should I modify the kernel to enable the jffs2 support then? In my defconfig the CONFIG_JFFS2_FS is set to yes. I thought that was supposed to enabled the jffs2 **** ENDING LOGGING AT Thu Dec 11 02:59:58 2014