**** BEGIN LOGGING AT Mon Jul 08 02:59:59 2013 Jul 08 07:55:34 good morning Jul 08 08:47:03 morning all Jul 08 08:51:24 Good morning bluelightning. Jul 08 08:51:33 hi halstead Jul 08 08:51:50 halstead: you're up late - hope all is well? Jul 08 08:52:32 bluelightning, indeed but all is well. Just sending out bug graphs and build locations. :) Jul 08 13:25:47 Hi folks Jul 08 13:26:03 otavio: hi otavio Jul 08 13:27:27 I am trying to find /which/ package includes a library inside of rootfs, using rpm ... any tip? Jul 08 13:27:47 * otavio is horrible with rpm Jul 08 13:28:04 which package that provides a .so.X? Jul 08 13:28:10 rpm -qf /path/to/file Jul 08 13:28:25 will show you the rpm that installed that file Jul 08 13:30:36 otavio: I finally got around to submitting that Qt Creator recipe to meta-oe after a month. I didn't forget. =) Jul 08 13:31:13 Net147: yes I noticed; but it seems it were done to run /in target/ no? Jul 08 13:31:24 otavio: correct Jul 08 13:31:34 erbo: right but I want to figure out /whatdepends/ on the lib Jul 08 13:34:19 otavio: did you have a use case for building Qt Creator for host? Jul 08 13:34:19 otavio: try rpm -q --what-requires Jul 08 13:36:00 otavio: Qt Creator should be pretty well supported already by existing distributions Jul 08 13:36:12 otavio: e.g. rpm -q --what-requires libcurl.so.5 Jul 08 13:41:31 Net147: I think might be interesting would be Qt Creator integration for the SDK Jul 08 13:42:12 bluelightning: could be useful Jul 08 13:42:34 bluelightning: Qt Creator already has support to deploy to remote target and run Jul 08 13:44:21 bluelightning: I think it was also brought up in one of the past Yocto presentations Jul 08 13:44:50 right, there have been various discussions; AFAIK nobody has got around to looking into it Jul 08 13:44:56 (yet) Jul 08 13:45:12 it's on my todo list but that list is quite long unfortunately :( Jul 08 13:45:41 bluelightning: do we build our own Eclipse? Jul 08 13:46:55 Net147: no, but we do have a plugin that we build for it Jul 08 13:48:17 Hi guys, using yocto 1.4. I need to install firmware for Centrino 6205 and Centrino 135. There is a recipe for 6205: meta-intel/common/recipes-kernel/linux-firmware/linux-firmware_git.bbappend, but there is no recipe for other one. I would like to avoid installing whole linux-firmware package. Any hints? Jul 08 13:48:54 bluelightning: surprisingly I have never used Eclipse for embedded Linux development... Jul 08 13:49:12 for 6205 I simply do IMAGE_INSTALL += "linux-firmware-iwlwifi-6000g2a-5" Jul 08 13:50:32 Krz: you can make your own bbappend and package it separately Jul 08 13:53:33 Krz: indeed, what tf said... however we would probably like to integrate that change into the core at some point (as we have done for the existing meta-intel bbappend in master) Jul 08 13:53:46 so I understand there is only one bbappend like 6205 for some reason? there is no out of the box functionality of installing single firmware supports? Jul 08 13:54:06 Krz: it hasn't been completely split out into sub-packages no Jul 08 13:54:07 Krz: the packaging is bit random Jul 08 13:54:21 ok. I got it Jul 08 13:54:58 Net147: nor me... but I have to admit haven't used Qt Creator much either Jul 08 14:00:02 bluelightning: I use Qt Creator every day for developing desktop applications Jul 08 14:05:27 one more question about firmware - if the change (single package for Centrino 135) is to be upstreamed I presume I should implement it in existing meta-intel/common/recipes-kernel/linux-firmware/linux-firmware_git.bbappend ? Jul 08 14:07:06 Krz: that's certainly how the upstream submission should be done in generally, but not that the linux-firmware.bbappend in meta-intel has gone in master. Jul 08 14:13:45 rburton: I wonder if there is some more sensible/obvious way of packagaging the fw Jul 08 14:14:29 tf: having a way to pull in all fw ever would help Jul 08 14:14:35 hm Jul 08 14:14:46 i wonder if we can make the kernel depend on firmware depending on what modules are enabled Jul 08 14:15:13 one of the problems is there is no consistency in the fw naming and stuff Jul 08 14:15:46 but it feels like either there should be only one package, or it should be split dynamically so each fw is in it's own package Jul 08 14:16:02 with one big package, you can expect the end users to do their own thing Jul 08 14:16:03 tf: i'm of the opinion that we should split it completely Jul 08 14:16:07 yeah Jul 08 14:16:13 I'd lean that way Jul 08 14:16:13 with a meta-package that pulls it all in Jul 08 14:16:28 isn't the problem that we can't be sure how to split it? Jul 08 14:16:53 i.e. don't some of the firmware sets come in multiple files? Jul 08 14:16:59 that much is true Jul 08 14:17:11 there's several iwl firmwares Jul 08 14:19:49 bluelightning: maybe at leas split it by 'brand'? Jul 08 14:27:06 hi to all! I've got a recipe that builds dbg rpm with the header files inside that refer to the path on my yocto environment and not to /usr/include. the same recipe builds a dev rpm file with the headers correctly placed in /usr/include... maybe I've done something wrong, but I don't know where... Jul 08 14:28:19 soldoKyn: did you by any chance include $D in the FILES_ variable? Jul 08 14:28:32 there should be no $D there Jul 08 14:43:31 tf: uhm...there was no ${D} in FILES_ variable, and your solution it seemed perfect to me...but adding ${D} to FILES_ variable didn't sove the problem... Jul 08 14:44:14 Hi! I am trying to build fsl-image-minimal with one extra file added to it. How do I do that? please help Jul 08 14:45:47 soldoKyn: paths in FILES are always based on / relative to ${D}, adding it would make it look for ${D}/${D}/path, which would not be ideal Jul 08 14:47:27 Hi all : How does one neatly add and remove features from Busybox within yocto? Is there a 'proper' way to do it or do you just have to hack the config files? Jul 08 14:49:10 kergoth: ok, sorry...so I was right before my last modification since there was no ${D} in any FILES_ variable... but I cannot figure out why in dbg rpm all the links to the headers file are relative to ${D}... Jul 08 14:56:11 erbo: the problem I need to do it in host Jul 08 15:35:07 soldoKyn: the install of the package itself must be putting it into ${D}/${D} erroneously Jul 08 15:35:55 pev: you would bbappend the busybox recipe in a custom layer and provide your own configuration Jul 08 15:38:46 bluelightning: maybe I have to change something in do_install? Jul 08 15:39:16 evanp: I think this might be what you were looking for a week or so ago: http://lists.openembedded.org/pipermail/openembedded-core/2013-July/080884.html Jul 08 15:40:02 soldoKyn: possibly, depends upon the software you're building; some take a path at configure time Jul 08 16:00:39 JaMa: have you seen any rm_work / sstate interaction issues of the like reported here: https://lists.yoctoproject.org/pipermail/yocto/2013-July/017128.html Jul 08 16:17:38 Hi, I still cannot fix the problem with Qt5's qtwebkit - https://github.com/meta-qt5/meta-qt5/issues/19. All binaries are building and work fine on my device, but it's impossible to create a package. Jul 08 16:32:34 bluelightning: nope Jul 08 16:32:55 hmm ok... I wonder what could be going wrong Jul 08 16:33:28 bluelightning: I'm using ipk format, but I would notice empty .ipk files too Jul 08 16:34:01 bluelightning: only issue I'm aware of is unexpected do_package_setscene executions Jul 08 16:34:29 trollixx: you can skip that RPATH qa check or debug a bit more why that fix doesn't work Jul 08 17:19:20 JaMa: how can I skip this check? I tried to debug, sed expression seems to work. Jul 08 17:19:49 JaMa: So it changes makefiles, but rpath check anyway fails. Jul 08 17:20:24 trollixx: INSANE_SKIP_${PN} or change WARN_QA, ERROR_QA in your distro config Jul 08 17:20:40 trollixx: I've replied a bit more in that issue on github Jul 08 17:24:29 JaMa: good, thanks, will try to debug it more. I want to try to build 5.1 first. Jul 08 17:27:19 trollixx: have you seen my branch with 5.1? Jul 08 17:27:40 qtdecarative is failing in that, but otherwise it's a good start Jul 08 17:28:22 JaMa: see it now, thanks) Jul 08 17:47:54 erbo: so I cannot run rpm in target but need to make host rpm tool to check deploy database; how I can do that? Jul 08 17:51:48 otavio: you might want to look at how buildhistory gathers installed package info at image creation time Jul 08 17:52:02 otavio: when using the rpm backend, that invokes rpm on the host Jul 08 17:52:06 humm; in the class? Jul 08 17:52:49 otavio: we call a generic named shell function list_installed_packages that is defined in the package_* classes Jul 08 20:57:02 sgw1: you around? Jul 08 21:13:05 sgw1, is the email I am supposed to be responding to from Robert the genext2fs removal from May 15? Jul 09 02:31:11 hi all Jul 09 02:34:20 Is anybody there? Jul 09 02:44:21 patient guy **** ENDING LOGGING AT Tue Jul 09 03:00:00 2013