**** BEGIN LOGGING AT Mon Sep 15 02:59:59 2014 Sep 15 03:38:35 Hm, following on from the conversation I overhead the other day, whats the formal way to enable ccache for yocto? I've tried setting CCACHE and CCACHE_DIR in local.conf and they don't seem to work? Sep 15 03:39:31 I'd set CCACHE='ccache ' and CCACHE_DIR ?= "${TOPDIR}/ccache" Sep 15 04:20:52 Why does udev ptest leave symlinks in the target sysroot that cause infinite loops? This causes qemu -L to hang when trying to use the sysroot for ld-linux Sep 15 07:18:37 hi guys Sep 15 07:18:44 I'm trying to compile a native recipe Sep 15 07:18:48 that needs qt Sep 15 07:19:08 but at configure it fails with: Project ERROR: Unknown module(s) in QT: gui Sep 15 07:19:29 although I see the ibQtgui library isn the i686-linux sysroot Sep 15 07:19:32 any idea? Sep 15 07:19:48 although I see the ibQtgui library is in the i686-linux sysroot Sep 15 07:19:53 typo :) Sep 15 07:49:22 hi embedded guys and girld Sep 15 07:50:43 I'm just starting off with yocto. Maybe i have some questions Sep 15 07:52:33 Also i will visit the Yocto day in Düsseldorf in one month. Anyone else? Sep 15 07:53:38 i think a whole lot of the regulars here will be around there. Sep 15 07:55:40 nice, I'm looking forward to it Sep 15 08:51:57 morning all Sep 15 08:52:14 (UMT) Sep 15 09:00:49 morning Sep 15 10:21:03 anybody gave xwayland a try under yocto? Sep 15 10:21:23 meaning, try to build weston with xwayland support Sep 15 10:21:34 without X11 in DISTRO_FEATURES Sep 15 10:23:27 you might need to enable x11 distro-feature if you want to build anything about x Sep 15 10:23:44 as disabling x11 DISTRO_FEATURE means none of the x11 libs will build Sep 15 10:24:47 we don't have direct support for building xwayland in the x server, but following the instructions at http://wayland.freedesktop.org/xserver.html should be fairly simple Sep 15 10:25:03 add a recipe for libepoxy, then add a packgeconfig to xserver for xwayland. Sep 15 10:25:20 I saw that, but if I have X11 in DISTRO_FEATURES, some packages that I want built for wayland may be configured wrong Sep 15 10:25:57 well you want to build xserver, so removing the x11 distro-feature is clearly not what you want to do Sep 15 10:26:29 surely the only package thats relevant is mesa, and that can happily build with wayland and x11 Sep 15 10:29:17 right, that seems about the only one Sep 15 10:29:19 thanks Sep 15 10:32:19 if you make it work, please send patches :) Sep 15 10:33:11 will do Sep 15 10:44:29 Hello, I need some guidance. I sent two patches to the mailing list, one to add support for mips32r2 and another one to add a CI20 machine config file. Maybe someone of you have read those emails, or replied them. Sep 15 10:46:25 For the patch to add support for mips32r2, I got a replied from one guy in the mailing list, and he is telling me that oe-core has already support for mips32r2. He told me to send my patch to the openembedded mailing list. But..., I'm a bit confused. Yocto doesn't have support for mips32r2, why should I send my patch to the openembedded mailing list if I want to add support for that in Yocto? Sep 15 10:47:59 oe-core is part of yocto Sep 15 10:49:51 rburton: so, does that mean if I download the YP Core - Daisy tarball, unpack it, etc., and I create a machine which uses mips32r2, will it work? Sep 15 10:49:57 the yocto list is for support Sep 15 10:50:30 i still stand by my point - we don't just add new machines to meta-yocto Sep 15 10:50:53 rburton: that's a different problem. Sep 15 10:50:59 if you can take the part of your patch that extends the existing mips32r2 support in oe-core and submit that to oe-core, then we can review that Sep 15 10:51:20 at the moment, the patch adds a new file that overrides the existing tunes in oe-core. Sep 15 10:52:28 rburton: I can. In fact, I have that patch ready. But I don't understand why you tell me oe-core is part of Yocto if I don't see the tune-mips32r2.inc file inside the YP Core - Daisy I have downloaded. Sep 15 10:55:07 vincent-: it looks to me like that was added after the daisy release Sep 15 10:55:30 so it is there in master, just not in a release version yet Sep 15 10:55:53 Uhm..., then I should be using Yocto from git and not from the released version. Sep 15 10:56:06 Right? Sep 15 10:56:31 vincent-: if you're submitting patches then you should work from git, yes Sep 15 10:57:08 Well, when I made the patches I was using git. Sep 15 10:57:14 And that file didn't exist. Sep 15 10:57:34 Ok, I cloned the daisy branch... Sep 15 11:00:24 right, and it's totally reasonable to do that Sep 15 11:01:00 unfortunately in this instance it's just that the support you're looking for was added after that release Sep 15 11:01:35 Yes, I have clone the master branch and now I see the file. Sep 15 11:03:41 *cloned Sep 15 11:03:55 i totally endorse working from stable branches, but when submitting patches its always worthwhile checking master, just in case what you've done has already been done :) Sep 15 11:04:13 So, the right procedure is to extend the file present in oe-core, and then it will get applied to Yocto as well. Is that right? Sep 15 11:04:55 (yocto isn't anything you can download) Sep 15 11:05:07 but yeah, if you've anything to add in the tune file you wrote Sep 15 11:05:20 the machine definition itself won't go into oe-core, as oe-core only contains virtual machines Sep 15 11:05:36 it also wont go into meta-yocto-bsp unless you're proposing that it replaces the existing MIPS machine Sep 15 11:05:36 all changes in OE-Core are merged back into the poky repository almost as soon as they land in OE-Core Sep 15 11:06:06 Well..., that tune file doesn't take into account the soft-float options. But..., I think is not worth to add it since it already supports the hard-float options, and that's what I need. Sep 15 11:06:22 but you can host a BSP layer on github or something, and submit it to the layer index. Sep 15 11:06:33 Hey hey Sep 15 11:06:41 Who was it playing around with ccache the other day? Sep 15 11:06:47 rburton: well, all I was talking about until now was for the mips32r2 patch. For the machine patch I have more doubts :-( Sep 15 11:10:11 Newbie question: My build for an ARM cortex-A8 with a tiny image broke in the shadow packages configure. It says posix_spawn is needed. Then i wanted to check it with the devshell. But inside the devshell it doesn't even find the arm-poky-linux-gnueabi command. Any ideas for the one or the other problem? Sep 15 11:11:39 rburton: for mi CI20 machine patch, you told me in the mailing list that it could live in a Yocto-compatible BSL layer outside of meta-yocto. What layer are you talking about? Sep 15 11:12:59 sven-tek: I'd recommend looking at temp/run.do_configure - that will show you exactly how configure is being run by the build system, and you can also run it directly from the devshell to repeat the task Sep 15 11:18:15 Exactly. I saw in the do_configure that it fails on the posix_spawn check. Then i wanted to repeat the configure, maybe play with the parameters. But this is where i am stuck, because the devshell doesn't make the compiler available, arm-poky-linux-gnueabi isn't known. Sep 15 11:19:54 vincent-: hi, I'm the one working on a mips32r2 machine Sep 15 11:22:22 Hi ant_work :D Sep 15 11:22:41 I don't know the details of your board, if it can be of any help pls look at http://cgit.openembedded.org/meta-handheld/tree/conf/machine/gcw0.conf Sep 15 11:22:41 ant_work: were you who replied me on the mailing list? Sep 15 11:22:53 yes Sep 15 11:23:10 This is my board: http://elinux.org/MIPS_Creator_CI20 Sep 15 11:23:14 vincent-: make your own layer Sep 15 11:23:53 it looks like you already hav ethe keys elements Sep 15 11:24:02 DEFAULTTUNE = "mips32r2el" Sep 15 11:24:02 and require conf/machine/include/tune-mips32r2.inc Sep 15 11:29:44 the gcw0 is a portable game console so its configuration is really specific Sep 15 11:32:40 rburton: oh..., I see. I'm too new to Yocto, so I don't know the proper way to do that yet. Sep 15 11:34:21 Hm, random question - in the yocto manual reading about systemd it refers to using sysvinit for rescue image but never actually says what a rescue image is! is that an old inconsistency? Sep 15 11:57:30 pev: as in, if you wanted to make a "rescue" image Sep 15 12:27:59 rburton: Ok, so it's not a specific mechanism in yocto, just if that's what you were trying to achieve via a minimal image? Sep 15 12:56:41 rburton: I guess I can use the conf/machine/my_machine.conf after doing "yocto-bsp create ..." Sep 15 13:39:11 In Yocto, is there a way to use a dev sysroot with sdk to start building from that point and not always recreate the essential things. Would also be interesting to distribute it as a stable starting starting point to the developers. Sep 15 13:40:16 sven-tek: we recommend shared state as a way to do that Sep 15 13:40:41 i.e. you share your sstate-cache and have others point to that using SSTATE_MIRRORS Sep 15 13:44:25 i guess having a jenkins server to feed and share the sstate-cache is the way to do it? How often will you want to start with a fresh cash? Sep 15 13:47:59 it depends on how frequently you update the metadata and what changes Sep 15 13:48:18 but yes, having a central server feed into it would be the way to do it Sep 15 13:53:00 "fresh cash" *banging head against the wall* Sep 15 14:21:09 Is there a way to run a custom script after build? Just before the rootfs gets packed into a .tar.bz2 file for instance. Sep 15 14:23:31 see ROOTFS_POSTPROCESS_COMMAND Sep 15 14:26:25 Thanks kergoth. Sep 15 14:27:16 I build two images with hob. Now bitbake doesn't run anymore and says "ERROR: ParseError in core-image: not a BitBake file". I don't know how this got broken, nor how to fix it. Sep 15 14:35:13 sven-tek: that sounds like a file called "core-image" has been created somewhere within the metadata - can you find out where that is? Sep 15 14:35:32 I can't say I've heard of this situation coming up before... Sep 15 14:38:13 vincent-: one more note about mips32r2: the distro used by that gcw0 is built with Buildroot. I've not yet looked at all the hacks they used to custom-tailor the code but one gcc patch could be of interest http://tinyurl.com/m3etsj7 Sep 15 14:38:53 ant_work: I don't have any problem with that. I can build the image for my machine with mips32r2, and it works fine because I have tested it. Sep 15 14:39:43 right, same here Sep 15 14:40:19 neverthless they have hand-crafted many things Sep 15 14:42:01 I didn't bench the Buildroot vs. OE/Yocto filesystems yet...still waiting for someone to fix kexec on jz47xx Sep 15 14:45:44 starting off with a different build folder seems to work. So it was not in the meta data. Sep 15 14:47:43 sven-tek: it may have been in the build directory Sep 15 14:49:04 Its a confusing problem. But i ain't got the time to track it down for now. Sep 15 17:07:56 yum search bitlbee Sep 15 17:08:01 haha Sep 15 17:08:11 wrong window Sep 15 17:45:45 if folks want to watch/contribute to yocto-ab documentation: http://goo.gl/IV11ZX Sep 15 21:33:22 hi guys, anyone that is looking into systemd? Sep 15 21:33:43 I'm checking it for size and found it to be too fat where it should not Sep 15 21:36:10 one of the issues is kmod being built with --enable-logging and --enable-debug that grows it a lot (from 130k to 530k, lib from 84k to 300k) Sep 15 21:50:25 k-s: adding PACKAGECONFIG options for those is trivial, patches welcome Sep 15 21:50:42 rburton: working on that, just need to understand better bitbake and recipes :-) Sep 15 21:50:56 so PACKAGECONFIG is magic to pass configure options Sep 15 21:51:07 so you'd do PACKAGECONFIG[debug] = "—enable-debug,—disable-debug" Sep 15 21:51:07 rburton: started 2 days ago to get my first build (other that typing commands people told me in the past years, as an user) Sep 15 21:51:32 and then setting PACKAGECONFIG to have or not have "debug" in would pass enable-debug or disable-debug Sep 15 21:52:00 rburton: i was trying to use the base.contains("PTEST_ENABLED"...) Sep 15 21:52:11 debug != ptest Sep 15 21:52:14 don't mix them Sep 15 21:52:27 i know, but it seems that this debug is only useful if ptest Sep 15 21:52:29 but ok Sep 15 21:52:35 got it :-) (easier as well) Sep 15 21:53:26 right, bed. g'night Sep 15 21:53:46 thanks Sep 15 22:52:34 ok, the PACKAGECONFIG worked for kmod and patch is ready. Sep 15 22:53:01 but that was small gain, now to save more I need to remove some packages that are being installed but they shouldn't Sep 15 22:53:19 like busybox-syslogd and busybox-udhcp if systemd is to be used Sep 15 22:53:26 what's the best way to do it? **** ENDING LOGGING AT Tue Sep 16 02:59:58 2014