**** BEGIN LOGGING AT Thu Jan 15 03:00:00 2015 Jan 15 09:24:56 gabrbedd: create your own meta layer that contains a bbappend which does the override Jan 15 09:38:08 morning all Jan 15 09:40:22 hi bluelightning Jan 15 09:40:30 hi mckoan Jan 15 09:57:47 hey Jan 15 10:28:11 bluelightning: do you have an idea regarding the valgrind issue? Jan 15 10:28:52 I stumbled over it while debugging valgrind, because it segfaults when run via qemu-arm Jan 15 10:29:42 valgrind_3.10.1 and qemu_2.2.0 Jan 15 10:43:49 jaeckel: I don't, I'm afraid... I would suggest filing a bug at bugzilla.yoctoproject.org Jan 15 14:06:08 my build is plagued by a closed-source binary tool for the host (available for x86 + x86_64) that is needed at build-time. Up till now, we have made sure all developer machine have it installed on their host system, but i was wondering if this could instead be added as a -native recipe that just checks out the precompiled binaries and puts them in the x86 sysroot. So I tried this, but my recipe fails in Jan 15 14:06:10 "split_and_strip_files" with the error "File format not recognized" for the x86-64 binary. I've set my PACKAGE_ARCH to "x86_64". Is this a bad idea? Jan 15 14:23:50 mago_: that is odd... why would it be running that code at all for a native recipe? your recipe does "inherit native" right? Jan 15 14:24:06 *facepalm* no, it does not :) Jan 15 14:24:14 ah, that should help :) Jan 15 14:24:42 I guess one might assume that naming it -native would do that kind of thing automagically, unfortunately it doesn't ;) Jan 15 14:25:42 this tool contains precompiled binaries for both 32 and 64-bit systems and a shellscript that automatically uses the correct elf binary "under the hood". so my PACKAGE_ARCH is really both x86_64 and x86 i guess, is there any way i can express this in my recipe? Jan 15 14:26:15 it probably isn't worth worrying too much about Jan 15 14:27:44 i.e. you probably don't need to set PACKAGE_ARCH at all Jan 15 14:28:03 oh, okay. that's convenient Jan 15 15:45:53 abelloni, you work for Free Electrons? Jan 15 15:46:05 yep Jan 15 15:46:32 I saw that a bunch of you will be at FOSDEM and I was wondering if any of you would like to help with the OE stand Jan 15 15:47:46 We do not need a huge commitment, but it is nice to get more people involved Jan 15 15:54:23 Crofton|work: you mean the yocto build distro stand? Jan 15 15:54:40 * tbr was waiting for that comment Jan 15 15:54:41 stop it Jan 15 15:55:23 stop stringing the words yocto distribution linux build poky system OpenEmbedded together in random sequences Jan 15 15:55:35 * Crofton|work is sensitive Jan 15 15:55:40 case sensitive? Jan 15 15:55:46 oh I forgot tizen also Jan 15 15:58:24 Crofton|work: don't worry, they don't have a community, so nobody will notice Jan 15 15:58:38 koen notices, then he trolls me Jan 15 15:58:52 you're my AB rep Jan 15 15:59:29 I know Jan 15 15:59:59 I'm waiting on the rest of the emebedded devroom schedule to go up so I can check for more permutations Jan 15 16:00:29 I'm including example phrases in the internal OE training docs Jan 15 16:00:58 but I fear that spending 50 of the 60 minutes on terminology might be too much Jan 15 16:01:06 yep Jan 15 16:01:16 All chant Jan 15 16:01:24 OpenEmbedded is the build system Jan 15 16:01:34 Poky is the reference distribution Jan 15 16:01:37 crofton is our glorious leader Jan 15 16:01:39 Yocto is the Project Jan 15 16:01:55 reference-but-not-compatible distro you mean Jan 15 16:01:55 heh Jan 15 16:02:13 if we voted it would be compatible Jan 15 16:02:23 if wishes were fishes Jan 15 16:02:35 and a footnote meta-yocto should really be meta-poky Jan 15 16:02:47 If wishes were horses, we'd all be eating steak Jan 15 16:04:48 I would prefer beef Jan 15 16:05:02 my talk is at 9 on sunday Jan 15 16:05:24 just to deter trolls ;) Jan 15 16:05:43 what kind of help do you expect ? :) Jan 15 16:06:50 BTW, I'll be there with Thomas so I guess he will not help unless you allow him to put buildroot stickers all over the stand Jan 15 16:11:02 abelloni, basically help man the stand so people like bluelightning can get away for a while Jan 15 16:11:15 I have a devroom for sdr on Sunday Jan 15 16:11:38 He can put out buildroot stickers, but I will need to cover them with OE stickers Jan 15 16:11:48 Free Electrons stickers would be fine though :) Jan 15 16:12:07 yep free electrons stickers definitely welcome Jan 15 16:12:07 we don't have any :) Jan 15 16:12:24 that reminds me, I need to see about some more Yocto Project stickers Jan 15 16:12:36 rush order :) Jan 15 16:12:42 Crofton|work: I have a huge pile, don't worry Jan 15 16:12:44 :) Jan 15 16:12:49 ok good Jan 15 16:12:53 I jsut wanted to check Jan 15 16:13:16 Tracey sent me a big box for last year's FOSDEM and we barely used a quarter of them Jan 15 16:18:04 it might be a good idea to hide all 'yocto' mentions from the OE booth to reduce confusion Jan 15 16:20:41 I doubt that's going to make any difference on that front Jan 15 16:21:42 do we have to schedule now or will we see when we are there ? Jan 15 16:22:13 either works :) Jan 15 16:22:32 abelloni: it might be nice to try to organise it a bit better this year; the last few years we've just winged it :) Jan 15 16:23:13 but if we do we'll probably have to wait for more volunteers first Jan 15 16:24:40 abelloni: I guess the best thing to do now would be to figure out when you're available with respect to other things you want to do/see at FOSDEM Jan 15 16:25:48 yeha but the schedule is not up yet Jan 15 16:26:08 * Crofton|work beats phdeswer_ :) Jan 15 16:26:08 ah right, that would be helpful for that yes :) Jan 15 16:26:44 Crofton|work: I think they are waiting for people to confirm Jan 15 16:26:50 Ueah Jan 15 16:39:27 what recipe do I need to add to get "use URI::Escape;" to work in perl? I tried perl-module-uri, but that didn't work. Jan 15 16:44:47 awozniak: liburi-perl I think Jan 15 16:47:21 I'm using multilib, and have noticed that lib32-* does not seem to work in packagegroup RDEPENDs, is that expected behavior? Jan 15 16:47:44 bluelightning: that worked, but now it's failing to find Carp.pm. I have no idea what that is Jan 15 16:48:05 some kind of perl junk... Jan 15 16:48:49 awozniak: I think perl-module-carp will get you that one Jan 15 16:48:51 awozniak: I'm not entirely sure myself, obviously it's a missing dependency - is that perhaps one of the modules provided as part of the standard perl distribution and we've split it out to a perl-module- package? Jan 15 16:49:27 ERROR: Nothing PROVIDES 'perl-module-carp'. Jan 15 16:50:03 awozniak: it would be a runtime package name, so you can't do bitbake perl-module-carp Jan 15 16:50:26 awozniak: but you could add it to RDEPENDS_${PN} in the liburi-perl recipe, or to IMAGE_INSTALL Jan 15 16:51:19 so say I do that, and rebuild. Would I then find a perl-module-carp ipk somewhere? Jan 15 16:53:52 that's the theory... Jan 15 16:54:27 did you check your ip deploy dir for perl packages? Jan 15 16:54:27 well, bitbake perl will ensure you find such a package if one is indeed expected to be there Jan 15 16:54:33 *ipk even Jan 15 16:55:20 huh, it's there. maybe it gets built but not installed. Jan 15 16:55:57 note that in cases such as these where you have a number of module or plugin packages that are effectively dynamically produced, the recipe will claim to satisfy any demand for any module/plugin package (perl-module-* in this case), so the build may start with that in RDEPENDS_${PN} or IMAGE_INSTALL - but that doesn't guarantee that that package will be there Jan 15 16:56:47 but a quick "git grep perl-module-carp" tells me that at least one other recipe already RDEPENDS on that so it should work just fine Jan 15 18:07:51 Thanks bluelightning, that worked. Any clues on where to find JSON.pm? There's a perl-module-json-pp and perl-module-json-pp-boolean, but neither of them have it, and I don't see a perl-module-json Jan 15 18:13:38 any idea why meta-selinux has swig 2.0.10 and meta-oe has 3.0.2? Jan 15 18:13:54 awozniak: I'm not sure, sorry; we may or may not have it - if it's external check the layer index Jan 15 18:14:01 bbl Jan 15 19:08:10 awozniak: maybe it got missde in the packaging? you could try a bitbake motherlode-of-perl-crap -c install and see if it's there Jan 15 19:29:03 yep were waiting for confirmations. Normally all FOSDEM submissions we got should have the people behind it emailed etc... Jan 15 21:49:31 I'm using latest dizzy and noticed that the libxml2-utils package ends up empty and /usr/bin/{xmlcatalog,xmllint} end up in the libxml2 package, not immediately obvious what's wrong... Jan 15 21:51:49 the FILES_${PN}-utils definition in the recipe looks correct **** BEGIN LOGGING AT Thu Jan 15 22:43:37 2015 **** BEGIN LOGGING AT Thu Jan 15 22:48:32 2015 **** BEGIN LOGGING AT Thu Jan 15 23:02:32 2015 **** ENDING LOGGING AT Fri Jan 16 02:59:58 2015