**** BEGIN LOGGING AT Wed Apr 23 02:59:58 2014 Apr 23 03:09:05 hi everybody. Does anyone knows how can i install, or if it's possible to, opencv in yocto? thanks in advance!! Apr 23 05:22:45 startingNow: you have to add some layers from meta-openembedded repo to your yocto project Apr 23 05:23:49 startingNow: e.g. look at http://layers.openembedded.org/layerindex/branch/master/recipes/?q=opencv Apr 23 05:23:56 it comes from meta-oe layer Apr 23 05:52:36 hi, could I run stellarium on vivante ? Apr 23 07:30:11 Is there a way to force bitbake to recompile the RunQueue? Apr 23 08:27:22 fun observation: building inside a docker instance fails for package_rpm, and succeeds for package_ipk and package_deb. looks like a host pollution problem, as tries to write to /.dockerinit Apr 23 08:58:20 morning all Apr 23 10:00:01 morning Apr 23 10:00:33 how save is it to assume that eglibc, gcc and other package versions are not going to change anymore on the 1.6 branch until release? Apr 23 10:00:58 no versions will change on 1.6 Apr 23 10:00:58 *especially* the toolchain Apr 23 10:01:22 OK, thank you! Apr 23 10:11:48 Hi all, I've got a post-1.6 version upgrade for opkg, should I send this to the mailing list now or hold off until after the 1.6 release date? Apr 23 10:39:35 paulbarker: you can send it now Apr 23 10:54:38 RP: I'll give it a quick re-test now and send it. Cheers Apr 23 11:46:39 can anyone give me a short pointer to an example how to handle malformed source archives? e.g. that do not honour the name-X.Y directory convention inside Apr 23 11:47:32 override do_extract? Apr 23 12:04:56 Hi Yocto-guys. I'd like to update http://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-benchmark/glmark2/glmark2_2012.12.bb to latest upstream version. My problem is the configure step is done with "./waf configure --with-flavors=x11-gl,x11-glesv2" instead of "./waf configure --enable-gl --enable-glesv2", and "./waf configure --with-flavors=x11-gl --with-flavors=x11-glesv2" is not an accepted format. Apr 23 12:06:09 How can I express the PACKAGECONFIG[...] parameters, so that if both gl and gles2 are present I obtain "--with-flavors=x11-gl,x11-glesv2" as the configure parameter? Apr 23 12:35:23 LetoThe2nd: there's a URL parameter for that, one sec Apr 23 12:36:07 LetoThe2nd: ;subdir=yourdesiredsubdirname Apr 23 12:43:59 bluelightning: ah perfect, thanks! Apr 23 12:44:16 <_gpg_> hello Apr 23 12:44:46 hi _gpg_ Apr 23 12:45:10 <_gpg_> tell me please, i'm trying to browse source content of https://github.com/Freescale/meta-fsl-demos/tree/master/recipes-graphics/fsl-gpu-sdk i don't have any linux machine yet, do you know of i can checkout/online read the content without having yocto installed ? Apr 23 12:46:15 _gpg_: like, https://raw.githubusercontent.com/Freescale/meta-fsl-demos/master/recipes-graphics/fsl-gpu-sdk/fsl-gpu-sdk_1.1.bb Apr 23 12:46:18 ? Apr 23 12:47:11 <_gpg_> LetoThe2nd: Well i'm quiet confused (and completely new to yocto), i'm interested in the source code contained in this fsl-gpu-sdk Apr 23 12:48:09 <_gpg_> LetoThe2nd: reading some patch notes from the mailing list, there are some sample about the imx6 2d API (gco2d) that's not widely available, but i found some references in fsl-gpu-sdk. Apr 23 12:48:59 <_gpg_> _gpg_: i don't know where to (if possible) i can download the entier graphics recipe source code Apr 23 12:49:48 the recipe is only a just that: a recipe how to build the source. the source itself for the fsl-gpu-sdk resides in a tar somewhere else Apr 23 12:50:10 it says: SRC_URI = "${FSL_MIRROR}/${PN}-${PV}.bin;fsl-eula=true" Apr 23 12:50:32 <_gpg_> Denwid: i see, thanks Apr 23 13:14:38 hi there Apr 23 13:14:52 how do I add -staticdev pkgs to image? Apr 23 13:17:08 you want *all* of them? Apr 23 13:17:18 yeah, doesn't that make sense? Apr 23 13:17:43 I did image with gcc and dev-pkgs, so I think adding '-staticdev' would be fine Apr 23 13:24:21 one way would be to add support for staticdev-pkgs, alongside dev-pkgs Apr 23 13:24:28 and send the patch, obviously. Apr 23 13:24:52 you can also use complementary-globs to create this in your own layer Apr 23 13:25:09 SDKIMAGE_FEATURES += "staticdev-pkgs" Apr 23 13:25:10 COMPLEMENTARY_GLOB[staticdev-pkgs] = "*-staticdev" Apr 23 13:25:19 is that in local.conf going to work? Apr 23 13:25:26 oh there's already a staticdev-pkgs Apr 23 13:25:32 yes, then. Apr 23 13:39:44 when compiling a relatively trivial package, a specific linker flag is not found. the library is provided by another trivial package. is there something that i have to check/do (besides setting the DEPENDS) so i can link against the other package? Apr 23 13:40:45 inherit something? pkgconfig? Apr 23 13:48:10 LetoThe2nd: inherit pkgconfig if the configure script uses pkgconfig, otherwise just add the right DEPENDS Apr 23 13:48:20 pastebin of logs will be useful though Apr 23 13:50:17 rburton: sure, but which one? the compile of the dependent recipe just breaks with ...poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.1/ld: cannot find -ludns Apr 23 13:50:39 rburton: so do_install or do_populate_sysroot logs of udns, maybe? Apr 23 13:51:53 LetoThe2nd: the recipe that needs udns should just DEPENDS=udns, or whateve the recipe is called Apr 23 13:52:14 rburton: yes, it has DEPENDS = "openssl udns" Apr 23 13:52:23 so your trivial package of udns isn't actually working Apr 23 13:52:30 as its not actually putting the libraries into the sysroot Apr 23 13:52:41 I'm trying to do a clean build, I nuked my tmp directory and now I'm getting an odd error, Can't install gst-fsl-plugin-3.0.9-r0@nitrogen6x: no package provides libfslvpuwrap.so.3 Apr 23 13:53:02 rburton: ok so do_install of udns or do_populate_install of udns are to be looked at? Apr 23 13:53:15 but that plugin is in my sources/meta-fsl-arm/recipies-multimedia Apr 23 13:53:30 any ideas why it would suddenly be "missing" Apr 23 13:55:29 LetoThe2nd: i'd say your do_install isn't working correctly Apr 23 14:00:59 rburton: i think i found it. udns builds only a static lib by default Apr 23 14:01:09 there you go :) Apr 23 14:03:20 so if i want to call "make shared" instead of just "make", do i have to override co_compile, or is it just some variable to set? Apr 23 14:12:17 you need to override do_compile Apr 23 14:12:28 do_compile() { oe_runmake shared } Apr 23 14:14:46 rburton: did that, then i get | NOTE: make -j 4 -e MAKEFLAGS= shared Apr 23 14:14:46 | make: *** No rule to make target `shared'. Stop. Apr 23 14:15:09 rburton: running the same command in the unpacked source dir works, though Apr 23 14:19:13 LetoThe2nd: you'd have to look at the do_compile log to see why that was - maybe its running in the wrong directory? Apr 23 14:19:23 i note that udns looks like but isn't autotools Apr 23 14:19:50 rburton: yeah correct, thats why no inherit autotools is set Apr 23 14:20:09 anyways gotta run.. thanks a lot for your input, i'll probably dig deeper tomorrow Apr 23 14:33:51 Hey all, I've got a module recipe thats based on hello-mod.bb but it appears that this builds against linux-libc-headers in the sys rootfs rather than those from my kernel which patches various common headers. I'm sure this should be obvious but can't spot it... Apr 23 14:36:38 pev, people trip over the linux-libc-headers thing frequently and unfortunately, there is a long sordid history of why it needs to be this way (RP recently added some explanation to a BZ entry). I suppose we need to dust that off and stick it in the kernel dev manual Apr 23 14:37:05 pev, if your module depends on your specific kernel - for the time being - I would recommend you include it as part of your kernel build. Apr 23 14:39:07 Hm, is there no workaround? Its separate as I'm rebuilding constantly during development and is standalone... Apr 23 14:39:41 Surely other recipes for modules distributed outside the kernel must build against custom kernels? Apr 23 14:41:28 I don't have a workaround right now - we do need to look into this though, I just don't have an immediate solution for you. Apr 23 14:41:51 You can spend some time looking at hello-mod and seeing what you can do to get it to use the headers from the kernel build Apr 23 14:42:25 note that if it requires changes that only exist in your patched kernel - it really isn't "standalone" - but maybe that's splitting hairs Apr 23 14:42:47 Please open a bug with as much detail as you can provide so it doesn't get lost in the noise Apr 23 14:43:52 Depends on your perspective - I'm pretty sure the number of boards that build from a mainline kernel source can be counted on the fingers of one foot... ;-) Apr 23 14:54:42 it's a semantic difference in your usage of "standalone" - but, whatever. Please open a bug. While apps need to build against libcheaders, I think it's reasonable to expect the modules to build against the kernel sources. Apr 23 14:55:46 What section should I file against for meta-skeleton as I think filing against hello-mod makes sense to anchor the issue... Apr 23 14:56:07 That's fine, yup. Apr 23 14:58:11 Build System & Metadata > Layers : Component : layers ? Apr 23 16:05:36 <|RFA|> Does anybody here knows a stable version of a Yocto with a ported OpenCV?? PVT, please Apr 23 16:18:05 guys, I spotted somewhere auto-calculated values for variables BB_NUMBER_THREADS and PARALLEL_MAKE Apr 23 16:18:15 where do I find these? Apr 23 16:18:26 right now I'm still using hardcoded values Apr 23 16:21:10 It was in a setup script IIRC Apr 23 16:21:13 meta-yocto/conf/local.conf.sample:BB_NUMBER_THREADS ?= "${@oe.utils.cpu_count()}" Apr 23 16:21:46 i wonder if those defaults should move to bitbake.conf Apr 23 16:21:56 base/setup-environment Apr 23 16:22:17 Thats in the fsl-community-bsp Apr 23 16:22:45 but that just uses the reported count of CPU's Apr 23 16:23:17 rburton: cool, thanks Apr 23 16:24:02 hey rburton , do you know anything about overriding the include path when building modules out of tree? Its driving me nuts... :-/ Apr 23 16:25:17 nope, sorry Apr 23 16:26:23 rburton: I thought that myself, then the ones in the sample file can be set up to be uncommented to set it to a specific value if desired Apr 23 16:26:50 (re BB_NUMBER_THREADS / PARALLEL_MAKE) Apr 23 16:26:52 bluelightning: or even just remove them from local.conf and move to local.conf.sample.extended Apr 23 16:27:30 * rburton files a bug Apr 23 16:30:23 bluelightning: 6217 fwiw Apr 23 17:50:48 Should I be able to addtask foo after do_package_write_ipk and expect foo to run? It shows up in the list of tasks and I can run it manually. But it does not run in the course of a package build. Apr 23 17:52:59 jet__: you might need to add "before do_build" to get that to happen Apr 23 17:53:12 Thanks. I will give that a try Apr 23 17:54:16 Perfect...thank you! Apr 23 17:55:28 no problem Apr 23 17:58:51 jet__: if you add the task without 'before' some other task which is already being run, you'd still be able to run it manually via bitbake -c. it's useful from time to time for opt-in functionality :) Apr 23 17:58:53 mm, chai Apr 23 18:04:16 tx kergoth Apr 23 19:04:45 Hi. Given a machine and a package name, how can I get from bitbake the recipe filename? I'm adapting some code from bitbake-layers to do that, which seemed to work initially, but then some recipe versions don't match what I expect. Maybe the comment http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/bitbake/bin/bitbake-layers#n238 is related to the problems I'm facing. Why are some recipes skipped? Apr 23 19:09:36 mario-goulart: I dont think bitbake-layers can sieve packages from recipes Apr 23 19:10:07 my hack approach is always search for dir in build tree Apr 23 19:10:31 I have a bb subcommand which can search for recipes or packages Apr 23 19:10:37 that code could be of interest Apr 23 19:11:05 https://github.com/kergoth/bb/blob/master/libexec/bb-search Apr 23 19:11:12 khem: I actually need metadata from bitbake, taking machine, COMPATIBLE_MACHINE, SOC_FAMILY and all that stuff into account. Apr 23 19:11:13 hasn't been touched in a long time now, though Apr 23 19:11:48 I think the bb-search stuff will be precisely what you're looking for Apr 23 19:11:52 afk, food Apr 23 19:12:27 Hmmm! Thanks, kergoth. Have a nice meal. :-) Apr 23 19:14:04 let me know how it goes, I'm interested in such things :) Apr 23 19:14:19 * kergoth hopes we actually get the subcommand-based bitbake ui / interactive shell going for the next yocto release Apr 23 19:14:27 Alright. Thanks a lot. Apr 23 19:15:00 https://github.com/kergoth/bb#examples has an example of what search and the other subcommands do, for reference Apr 23 19:15:41 iirc bb-list might be able to list runtime targets too, but i can't remember, it's been a while Apr 23 19:21:04 kergoth: I see "Provider and pn aren't always correctly mapped back and forth" in Known Issues. That sounds a bit scary for my purposes (I want to know exactly providers and PNs). Does that hold for all tools? Apr 23 19:21:46 Honestly I don't recall. It's not particularly difficult to look up all the provides for a given pn, it's just a matter of remembering which your'e using to index each of the lookup tables in the bitbake runqueue data Apr 23 19:22:22 iirc the big offender was whatdepends, iirc it just used what hte user asked for directly in the lookups, meaning when it mapped dependencies, it didn't check for them all Apr 23 19:22:29 i expect for something as simple as search, it's a nonissue Apr 23 19:22:39 Alright. I'll dig into it. bb looks amazingly useful. Apr 23 19:22:44 it was the dependencies that were key, a dep can be on any provide, not just the PN of hte recipe Apr 23 19:22:50 cool Apr 23 19:25:29 I *really* need to fix whatdepends to also support runtime dependencies, or add whatrdepends Apr 23 19:25:33 critical need there Apr 23 19:49:24 kergoth: where can I find bb-* functionality ? Apr 23 19:53:49 khem: scroll up, i linked mario-goulart to it Apr 23 19:53:57 github.com/kergoth/bb Apr 23 20:45:12 where should kernel configuration modifications go? into the bsp layer? Apr 23 20:45:49 most likely **** ENDING LOGGING AT Thu Apr 24 02:59:58 2014