Sunday, 2013-07-14

*** smartin <smartin!> has joined #yocto00:09
*** mulhern <mulhern!> has quit IRC00:10
*** smartin_ <smartin_!> has quit IRC00:10
*** _julian <_julian!> has joined #yocto00:22
*** _julian_ <_julian_!> has quit IRC00:23
*** jbaxter <jbaxter!> has quit IRC00:36
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC00:38
*** mitz <mitz!> has quit IRC00:45
*** FlamesOfEternity <FlamesOfEternity!> has quit IRC00:46
*** FlamesOfEternity <FlamesOfEternity!> has joined #yocto00:47
*** smartin_ <smartin_!> has joined #yocto01:09
*** smartin <smartin!> has quit IRC01:10
*** mulhern <mulhern!> has joined #yocto01:21
*** mulhern <mulhern!> has quit IRC01:26
*** zenlinux <zenlinux!> has quit IRC02:03
*** zenlinux <zenlinux!> has joined #yocto02:05
*** smartin_ <smartin_!> has quit IRC02:07
*** smartin <smartin!> has joined #yocto02:08
*** silviof1 <silviof1!> has quit IRC02:12
*** silviof1 <silviof1!> has joined #yocto02:26
*** klinger <klinger!> has quit IRC03:33
*** zenlinux <zenlinux!> has quit IRC03:42
*** klinger <klinger!> has joined #yocto03:47
*** andyross <andyross!> has joined #yocto04:09
*** zeddii_home_ <zeddii_home_!> has joined #yocto04:21
*** zeddii_home <zeddii_home!> has quit IRC04:21
*** zeddii_home_ is now known as zeddii_home04:21
*** crazy_imp <crazy_imp!> has quit IRC04:38
*** crazy_imp <crazy_imp!> has joined #yocto04:42
*** mitz <mitz!> has joined #yocto04:44
*** andyross <andyross!> has quit IRC05:05
*** andyross <andyross!> has joined #yocto05:05
*** zecke <zecke!> has joined #yocto05:25
*** behanw <behanw!> has quit IRC05:35
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto06:46
*** smartin_ <smartin_!> has joined #yocto06:49
*** smartin <smartin!> has quit IRC06:50
*** nitink <nitink!nitink@nat/intel/x-sfsqehbirnpdcywd> has quit IRC07:31
*** forcev <forcev!> has quit IRC07:40
*** mitz <mitz!> has quit IRC07:44
*** mitz <mitz!> has joined #yocto07:46
*** nitink <nitink!nitink@nat/intel/x-qinnilldlvzmcord> has joined #yocto07:49
*** zeddii_home <zeddii_home!> has quit IRC07:51
*** nitink <nitink!nitink@nat/intel/x-qinnilldlvzmcord> has quit IRC08:04
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has joined #yocto08:10
*** nitink <nitink!~nitink@> has joined #yocto08:13
*** honschu <honschu!> has joined #yocto08:25
*** honschu <honschu!~honschu@shackspace/j4fun> has joined #yocto08:25
*** smartin <smartin!> has joined #yocto08:28
*** honschu_ <honschu_!~honschu@shackspace/j4fun> has quit IRC08:28
*** nitink <nitink!~nitink@> has quit IRC08:35
*** jbaxter <jbaxter!> has joined #yocto08:45
*** jbaxter <jbaxter!> has quit IRC08:46
*** Crofton <Crofton!> has quit IRC08:48
*** nitink <nitink!~nitink@> has joined #yocto08:48
*** eren <eren!~eren@unaffiliated/eren> has quit IRC09:19
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto09:19
*** zecke <zecke!> has quit IRC09:54
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has quit IRC10:04
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has joined #yocto10:05
*** zecke <zecke!> has joined #yocto10:53
*** swex__ <swex__!~swex@> has joined #yocto11:00
*** swex_ <swex_!~swex@> has quit IRC11:03
*** mulhern <mulhern!> has joined #yocto11:24
*** scot <scot!> has quit IRC11:29
*** scot <scot!> has joined #yocto11:30
*** mulhern <mulhern!> has quit IRC11:43
*** exosyst <exosyst!~nick@> has joined #yocto11:52
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC11:54
*** mulhern <mulhern!> has joined #yocto12:03
*** scot <scot!> has quit IRC12:12
*** scot <scot!> has joined #yocto12:12
*** smartin__ <smartin__!> has joined #yocto12:14
*** smartin_ <smartin_!> has quit IRC12:15
*** _julian_ <_julian_!> has joined #yocto12:15
*** _julian <_julian!> has quit IRC12:16
*** Daemon404 <Daemon404!~who_knows@pdpc/supporter/student/Daemon404> has quit IRC12:23
*** mulhern <mulhern!> has quit IRC12:43
*** mulhern <mulhern!> has joined #yocto12:45
*** scot <scot!> has quit IRC12:58
*** scot <scot!> has joined #yocto12:59
*** andyross <andyross!> has joined #yocto13:08
*** zeddii_home <zeddii_home!> has joined #yocto13:14
*** mulhern <mulhern!> has quit IRC13:16
*** mulhern <mulhern!> has joined #yocto13:21
*** mulhern <mulhern!> has quit IRC13:38
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto13:39
*** andyross <andyross!> has quit IRC13:41
*** eren <eren!~eren@unaffiliated/eren> has quit IRC13:45
*** zeddii_home <zeddii_home!> has quit IRC13:46
*** zeddii_home <zeddii_home!> has joined #yocto13:46
*** andyross <andyross!> has joined #yocto13:48
*** zeddii_home <zeddii_home!> has quit IRC13:52
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto13:53
*** andyross <andyross!> has quit IRC14:08
*** Bagder <Bagder!~daniel@> has joined #yocto14:24
*** Bagder <Bagder!~daniel@rockbox/developer/bagder> has joined #yocto14:24
pev_Have any of you guys had a random problem with "unknown package" when building an image? My recipe builds totally fine when bitbaking on its own, but when I add it to my image I get this "unknown package" error. Not sure where to start to debug...!14:29
*** jmpdelos <jmpdelos!> has quit IRC14:39
*** jmpdelos <jmpdelos!> has joined #yocto14:56
bluelightningpev_: could it be because the main package for the recipe is currently empty and thus an output package for it is never produced?14:59
pev_Ive just been trying a simple test case to see if I can work out what's going on15:06
bluelightningpev_: you've installed the library into two subdirectories; I think that will mean the default value of FILES_${PN} won't pick it up15:07
bluelightningpev_: you can check by looking in packages-split in the workdir for the recipe15:08
*** Crofton <Crofton!> has joined #yocto15:10
pev_bluelightning: Two subdirectories? should just go into ${D}${libdor}/libtest/modules?15:25
pev_bluelightning: What am I lookinf for in packages-split? Sorry, not sure what you mean by that...15:26
*** phantoxeD <phantoxeD!> has joined #yocto15:26
bluelightningpev_: that's where you can see which files ended up in each package15:26
pev_Thats why I was confued - the .so doesn't seem to be in there at all, just the .c file!15:27
pev_So I need to debug my .so until I see the .so end up in there correctly?15:27
pev_Sorry, debug the .bb rather15:28
bluelightningpev_: the default value of FILES_${PN} only includes "${libdir}/lib*${SOLIBS}" for libraries (where ${SOLIBS} is ".so.*")15:28
bluelightningpev_: so if you want the installed library to be picked up you need to add "${libdir}/libtest" or similar to FILES_${PN}15:29
bluelightningaren't you getting unshipped file warnings when building the recipe?15:29
pev_Ah, yes - I was but hadn't realised that was the meaning!15:30
bluelightningok, just checking :)15:31
*** phantoxeD <phantoxeD!> has quit IRC15:31
bluelightningpev_: btw in our discussion the other day I forgot to mention that $D (note though, not ${D}) is set when postinstalls run on the host15:32
bluelightningpev_: thus you can use $D in paths to make the script work in both places (or check where it is running if you need to)15:32
bluelightningbut maybe you already figured that out15:32
pev_Ah, cheers - not yet, I've been trying to get the full build working first (ie this error) before I can move onto debuggint the .conf file munging!15:35
*** behanw <behanw!> has joined #yocto15:40
*** fin <fin!5b99dd1b@gateway/web/freenode/ip.> has joined #yocto15:44
*** exosyst <exosyst!~nick@> has quit IRC15:50
*** smartin__ <smartin__!> has quit IRC15:58
*** smartin_ <smartin_!> has joined #yocto16:04
*** fin <fin!5b99dd1b@gateway/web/freenode/ip.> has quit IRC16:17
*** zenlinux <zenlinux!> has joined #yocto16:23
*** phantoxeD <phantoxeD!> has joined #yocto16:33
pev_So i added FILES_${PN} = "${libdir}/libtest"16:36
pev_and now i get16:37
pev_ERROR: QA Issue: non debug package contains .debug directory: lib-test path /work/armv7a-vfp-neon-amltd-linux-gnueabi/lib-test/1.0-r6/packages-split/lib-test/usr/lib/libtest/modules/.debug/lib-test.so16:37
zeckepev_: yes, you have a debug file in your package. debug files need to be in -dbg packages16:39
pev_zecke, Is that something that was created automatically? What should I do then? I'm just building from a trivially simple makefile!16:41
zeckepev_: maybe change your glob to "${libdir}/libtest/*.so" ?16:43
zeckepev_: or make sure the -dbg package is before your -libtest package in PACKAGES16:44
pev_sorry, glob?16:46
pev_On the package front I'm only wanting to make one thing...!16:47
pev_It's such a simple thing, how hard can it be! :-/16:47
zeckepev_: "man glob", we are building on the shoulders of giants.16:49
pev_zecke :
pev_It should be that simple?!16:49
*** phantoxeD <phantoxeD!> has quit IRC16:50
pev_zecke: Oh you mean the glob for the package.. Gotcha16:50
zeckepev_: I don't see the "FILES_${PN}" you apparently added. ;)16:50
bluelightningpev_: files are picked up in the order declared in PACKAGES16:51
pev_FILES_${PN}           = "${libdir}/libtest/modules/"16:52
pev_If i change to : FILES_${PN}           = "${libdir}/libtest/modules/*${SOLIBS}"16:52
pev_I get ERROR: Error executing a python function in /workdrive/projects/vibe/src/opt/amltd/poky/meta-vibe/recipes-skeleton/lib-test/
pev_and a load of nasty debug16:53
bluelightningpev_: can you pastebin it?16:53
bluelightningpev_: add this to remove the QA issue: FILES_${PN}-dbg += "${libdir}/libtest/modules/.debug"16:54
*** zenlinux <zenlinux!> has quit IRC16:55
pev_FILES_${PN} = "${libdir}/libtest/modules/"16:56
pev_FILES_${PN}-dbg += "${libdir}/libtest/modules/.debug"16:56
pev_Generates the python error16:56
bluelightningpev_: that is odd... try bitbake -c clean lib-test and then try again16:58
pev_would incrementing PR help the same? I've been doing that16:58
pev_same pyth error after clean16:59
pev_actually - given that I've incremented PR to r11 now - why does the python error say "Exception: OSError: [Errno 2] No such file or directory: '/workdrive/projects/vibe/src/vibe_p81_build/tmp/work/armv7a-vfp-neon-amltd-linux-gnueabi/lib-test/1.0-r4/packages-split/lib-test-dbg'"17:00
pev_knickers == twisted17:01
pev_Is there any more heavy cleaning I can do than -c clean thats a step down from rebuilding everything as I don't want to wait 30 mins...!?17:02
bluelightningpev_: bitbake -c cleansstate lib-test17:03
bluelightningbut we're already getting into quite odd behaviour, this shouldn't be happening17:03
bluelightningFWIW I am trying your recipe here17:03
pev_cleanstate : still gives same pyth error after!17:03
pev_Thanks - it's appreciated! Still mindboggled Im tripped up by something so apparently simple! :-D17:04
bluelightningpev_: you're sure you only have one copy of this recipe accessible from this build configuration?17:07
pev_bluelightning,  find . -name "lib-test*.bb" says yes17:08
bluelightningok, I just built it here and it built fine17:10
bluelightningyou could try bitbake -e lib-test | less and see what the values of PR and PKGR are17:12
pev_both at r1117:13
pev_So you tested the version I pastebinned plus the two FILES_lines as above?17:15
bluelightningpev_: yep, exactly that17:15
bluelightningpev_: what about PKGDEST? what does it say that is at?17:16
pev_too late - ive just run through deleting all the dirs manually...17:16
*** doerrpau <doerrpau!> has left #yocto17:17
bluelightninghmm, I was hoping we could debug it17:17
bluelightningoh well17:17
*** doerrpau <doerrpau!> has joined #yocto17:17
pev_No doubt I'll manage to break it again before too long...17:18
bluelightningpev_: are you using a custom DISTRO, poky, or something else?17:19
pev_Its a version of poky - came from some developer here. Its yocto 1.4 with what looks to be a load of stuff from current git put in as well17:20
bluelightningah ok17:21
bluelightningreason I asked is I wonder if the PR server is enabled17:21
pev_Thats waaaay out of my depth... Easy to check?17:21
bluelightning(just trying to think how PR could not be the value you expect it to be)17:21
bluelightningI think bitbake -e | grep ^PRSERV17:22
pev_that shows no matches17:23
pev_OK, so while that now seems to build the recipe ok17:24
bluelightninghmm ok... that's what I'd expect if it was not enabled17:24
pev_I still cant get it into the image....17:24
bluelightningpev_: if you look in packages-split does the main lib-test package have any files in it?17:24
pev_Hm, no the .so, no17:25
pev_so back to the original supposition then! :-D17:25
bluelightningFILES_${PN} must still be incorrect hen17:25
bluelightninghere the main package does have the file in it17:26
pev_I'd used the *{SOLIBS} but it seemed not to match. Gone back to just the dir17:27
bluelightningright, ${SOLIBS} is designed for versioned libraries, which this isn't17:27
pev_Aha. Gotcha17:28
pev_Yep, that looks like it's now working, thanks. Now try that with my actual recipe!17:29
*** mulhern <mulhern!> has joined #yocto17:35
*** mitz <mitz!> has quit IRC17:48
*** scot <scot!> has quit IRC17:55
*** scot <scot!> has joined #yocto17:55
*** mulhern <mulhern!> has quit IRC18:15
*** seebs <seebs!> has quit IRC18:20
*** seebs <seebs!> has joined #yocto18:49
*** zeddii_home <zeddii_home!> has joined #yocto18:50
*** smartin__ <smartin__!> has joined #yocto19:05
*** smartin_ <smartin_!> has quit IRC19:06
*** dnil <dnil!> has joined #yocto19:18
*** seebs <seebs!> has quit IRC19:32
*** munch <munch!> has joined #yocto19:51
*** nerdboy <nerdboy!> has joined #yocto19:51
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto19:52
*** brickrisk <brickrisk!> has joined #yocto19:54
brickriskI'm receiving this when attempting a build of meta-toolchain-qte I have bzip built so I'm confused?19:57
*** mulhern <mulhern!> has joined #yocto19:58
brickriskoops pastebin didn't get the whole thing19:59
brickriskends on cannot satisfy the following dependencies libz2 (>= 1.0.6)19:59
brickriskI can do bitbake bzip2 -c devshell and I verified that it is building the 1.0.6 version20:01
*** zeddii_home <zeddii_home!> has quit IRC20:04
*** zecke <zecke!> has quit IRC20:08
*** zecke <zecke!> has joined #yocto20:09
*** seebs <seebs!> has joined #yocto20:11
*** brickrisk <brickrisk!> has quit IRC20:15
*** mulhern <mulhern!> has quit IRC20:16
*** davest <davest!~Adium@> has joined #yocto20:16
*** smartin <smartin!> has quit IRC20:23
*** mulhern <mulhern!> has joined #yocto20:28
dnilIs there a common recommendation for handling configuration of package features? I'm trying to lean how to write recipes by packaging linphone, this software however has the option to enable or disable video calls. How should that be handled?20:29
dnilAlways including the video feature would add quite a list of dependencies, which I guess is not always OK.20:31
zeckednil: e.g. if the video functionality is just a plugin.. always build it but put into a different package20:35
zeckednil: when it influences the core.. then it is more difficult20:35
*** ant_home <ant_home!> has joined #yocto20:35
dnilzecke, it influences the core as well as libs that linphone depends on.20:36
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has quit IRC20:37
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has joined #yocto20:37
zeckednil: then it is a difficult call. If you need video right now, enable it, otherwise not? but that is just my opinion.. maybe there are more specific rules nowadays20:38
dnilzecke, Yes, that is what I have done for now. Just curious if there exist any existing best practice how to handle this. One idea I had in this case was to check the machine features for the existence of a screen and allow that to decide video on/off.20:43
bluelightningdnil: we have a mechanism called PACKAGECONFIG which can be used on a per-recipe basis to enable/disable functionality particularly where it might add additional dependencies20:53
*** eren <eren!~eren@unaffiliated/eren> has quit IRC20:54
dnilbluelightning, OK thanks. Found it in the manual now. I will look into that , sounds like what I need20:55
*** zecke <zecke!> has quit IRC21:10
*** davest <davest!~Adium@> has quit IRC21:13
*** erbo <erbo!> has quit IRC21:17
*** roxell <roxell!~roxell@linaro/roxell> has quit IRC21:18
*** erbo <erbo!> has joined #yocto21:18
*** roxell <roxell!~roxell@linaro/roxell> has joined #yocto21:21
*** mitz <mitz!> has joined #yocto21:54
*** zenlinux <zenlinux!> has joined #yocto22:02
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto22:13
*** mulhern <mulhern!> has joined #yocto22:20
*** phantoxeD <phantoxeD!> has joined #yocto22:27
*** sgarman <sgarman!> has joined #yocto22:57
*** sgarman <sgarman!> has quit IRC22:58
*** Bagder <Bagder!~daniel@rockbox/developer/bagder> has quit IRC23:14
*** phantoxeD <phantoxeD!> has quit IRC23:14
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC23:16
*** Bagder <Bagder!~daniel@> has joined #yocto23:17
*** Bagder <Bagder!~daniel@rockbox/developer/bagder> has joined #yocto23:17
*** jmpdelos <jmpdelos!> has quit IRC23:26
*** munch <munch!> has quit IRC23:32
*** zeddii_home <zeddii_home!> has joined #yocto23:32
*** zenlinux <zenlinux!> has quit IRC23:33
*** sgarman <sgarman!> has joined #yocto23:33
*** sgarman <sgarman!> has quit IRC23:36
*** sgarman <sgarman!> has joined #yocto23:36
*** pev_ <pev_!~pev@> has quit IRC23:37
*** mitz <mitz!> has quit IRC23:44
*** mitz <mitz!> has joined #yocto23:45
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC23:51
*** tlwoerner <tlwoerner!~tlwoerner@linaro/tlwoerner> has joined #yocto23:58

Generated by 2.11.0 by Marius Gedminas - find it at!