**** BEGIN LOGGING AT Mon May 05 03:00:00 2014 May 05 06:39:41 how does runtime dependencies work? if I do RDEPENDS = "something", I can't seem to find a corresponding recipe for "something"? May 05 06:40:13 from OEs perspective, what is the difference between a build-time and a run-time dependency? May 05 06:43:22 mago_, I believe a single recipe can produce multiple packages, -dbg, -dev or even custom named packages. all these can be added as RDEPENDS May 05 07:26:20 good morning May 05 07:26:24 howdy May 05 07:26:46 I need help mckoan. Can you help me? May 05 07:27:12 ~ask May 05 07:27:12 Questions in the channel should be specific, informative, complete, concise, and on-topic. Don't ask if you can ask a question first. Don't ask if a person is there; just ask what you intended to ask them. Better questions more frequently yield better answers. We are all here voluntarily or against our will. May 05 07:29:05 meta-angstrom/conf/distro/angstrom-v2012.12.conf contains an entry -> PREFERRED_VERSION_systemd = "208%" May 05 07:29:24 I am running 2.6.37 which only works up to 204 May 05 07:29:59 in my setup-scripts/conf/local.conf I have PREFERRED_VERSION_systemd = "204%" May 05 07:30:22 bitbake mechanisms how ever know better and always selects the higher number May 05 07:30:47 what is the correct method of fixing this issue May 05 07:31:13 ? May 05 07:31:41 pompomJuice: do you have systemd 204 in any of your metalayers? May 05 07:31:48 no May 05 07:32:05 pompomJuice: so you have to create your recipe for that May 05 07:32:12 I did May 05 07:32:35 basically just copied and changed the recipy name from to 204 May 05 07:32:56 my meta layer is at priority 14 May 05 07:33:00 higher than angstrom May 05 07:33:04 that also has no effect May 05 07:33:20 I tried to troll the bitbake code May 05 07:33:29 but I donno who codes like that May 05 07:33:35 I cant make out a thing May 05 07:33:48 python is my cuppa tea May 05 07:34:18 Tried to understand that part of the code, but I could not find a hack I could implement May 05 07:37:22 pompomJuice: please pastebin your recipe and the original one (208) May 05 07:37:42 ok May 05 07:44:54 morning all ! May 05 07:47:26 This is my recipy -> systemd_204.bb -> http://pastebin.com/Wy9WvHcj May 05 07:47:55 http://pastebin.com/rafNNKdt -> systemd_208.bb May 05 07:49:10 obviously I can just hack it out of that conf file, but I want to do it correctly and I cannot think of a way to remove that preferred_version=208 from the angstrom recipies without damaging the entire system May 05 07:49:49 damage version control to be more spesific May 05 07:56:21 What I can see from the code is this: May 05 07:56:26 move 1 is -> # Find the highest priority provider with a PREFERRED_VERSION set May 05 07:56:40 move 2 is -> # Find the latest version of the highest priority provider May 05 07:57:14 where is this priority it speaks of? Because my preferred version is set in that local.conf that is not inside my lvl 14 priority meta-layer? May 05 07:57:30 hi afournier May 05 07:57:37 hi May 05 07:57:46 pompomJuice: actually what is your problem? May 05 07:57:58 pompomJuice: is your recipe ignored? May 05 07:58:01 I cannot make bitbake select the 204 version May 05 07:58:04 yea May 05 07:58:11 when I run it in debug mode May 05 07:58:16 it finds the 204,208 May 05 07:58:24 but selects the 208 May 05 07:58:48 pompomJuice: try setting PREFERRED_VERSION_systemd = "204" in your image recipe May 05 07:59:01 maybe I should ask this.. where can I put the line PREFERRED_VERSION_systemd inside my meta layer? May 05 07:59:09 when running bitbake my environ has both SSH_AGENT_PID and SSH_AUTH_SOCK defined, but when it gets to the fetcher those variables are not exported... val = d.getVar('SSH_AGENT_PID', True) returns None, is it normal ? May 05 07:59:14 pompomJuice: PREFERRED_VERSION is a global var, image recipes can't set global vars May 05 07:59:19 pompomJuice: have you created a new layer? May 05 07:59:23 yes May 05 07:59:32 mckoan: and even if images could, it's a DISTRO setting, which should never to into image recipes May 05 07:59:33 one that adds our stuff to the image May 05 07:59:50 and that meta-layer contains a directory systemd_204/systemd_204.bb May 05 08:00:02 that meta layer has priority 14 highest of all May 05 08:00:11 pompomJuice: have you added your layer to bblayers.conf? May 05 08:00:20 let me check May 05 08:00:33 koen: yep, thx May 05 08:00:52 # These layers hold machine specific content, aka Board Support Packages May 05 08:00:52 BSPLAYERS ?= " \ May 05 08:00:52 ${TOPDIR}/sources/meta-ti \ May 05 08:00:52 ${TOPDIR}/sources/meta-ctlab \ May 05 08:00:52 " May 05 08:01:02 the recipy resides in meta-ctlab May 05 08:01:07 our layer May 05 08:01:58 pompomJuice: do you mean BBLAYERS ? is there a typo? May 05 08:02:00 that layers adds customization to a standard angstrom image. (older kernel + rowboat + ti ) May 05 08:02:28 no type May 05 08:02:32 im copy pasting May 05 08:02:44 pompomJuice: maybe Angstrom specific May 05 08:02:54 yea it is angstrom spesific May 05 08:02:58 because angstrom May 05 08:03:00 contains a file May 05 08:03:19 that makes it select 208 May 05 08:03:45 [09:22] meta-angstrom/conf/distro/angstrom-v2012.12.conf contains an entry -> PREFERRED_VERSION_systemd = "208%" May 05 08:04:21 I do not understand that part of bitbake May 05 08:04:30 what file must I add that overrides that setting? May 05 08:04:40 pompomJuice: so try replacing this line (at distro level) May 05 08:04:57 do you mean edit that file? May 05 08:05:30 pompomJuice: yes, just to check if your recipe is selected May 05 08:05:40 Yea it does May 05 08:06:00 as isaid if you run bitbake in debug mode it show that it finds both recipies, but selects 208 as the winner May 05 08:06:14 pompomJuice: as koen said it's a DISTRO setting, so angstrom-v2012.12.conf is the distro config file May 05 08:06:49 koen? I did not see him say anything May 05 08:06:54 pompomJuice: set PREFERRED_VERSION_systemd = "204%" in angstrom-v2012.12.conf May 05 08:06:57 let me check since he is the maker May 05 08:07:09 ok but where do I put that file? May 05 08:07:22 10:04 < koen> mckoan: and even if images could, it's a DISTRO setting, which should never to into image recipes May 05 08:07:28 I cant edit the file inside the distro becaue then oebb update becomes angry May 05 08:07:58 Then I cannot suck in angstrom changes automagically anymore :( May 05 08:08:24 pompomJuice: I don't know I don't use Angstrom May 05 08:08:32 ok how do I override the distro config file? May 05 08:08:58 try local.conf first May 05 08:09:03 from inside meta-ctlab, my customizations layer May 05 08:09:07 then migrate it to your distro layer May 05 08:09:08 I dont wanna edit the distro May 05 08:09:25 how? sorry im bitbake noob May 05 08:09:31 less than 6 month XP with this May 05 08:09:36 but I'd think that backporting the patches to 2.6.37 would be a better idea for future proofing May 05 08:09:52 (well, migrating to a newer kernel would be even better, but you mentioned TI silicon) May 05 08:10:25 iunfortunately, I inherited a project where they hacked a 2.6.37 to be able to run android on it (since android requires some extra kernel stuff and the kernels were not the same) May 05 08:10:46 then they hacked the android May 05 08:10:53 then everything got locked in May 05 08:11:01 then boss man cannot understand it takes time May 05 08:11:06 fires the guy that does all the magic May 05 08:11:09 now im stuck with it May 05 08:11:42 so yea its working nicely actually May 05 08:11:49 I got it upgraded as far I could May 05 08:11:56 took it from 1.3 to 1.5 May 05 08:12:08 the new angstrom is sweet! May 05 08:12:18 major difference between 1.5 and 1.3 May 05 08:12:29 our device runs much happier on 1.5 May 05 08:12:54 mostly because it now has armhf and mono 3.4 with sgen and lvm May 05 08:12:56 lvvm May 05 08:15:18 this yocto movement is clearly showing results May 05 08:17:52 ok so I am guess that inside sources/meta-ctlab/conf/ayer.conf is the place those things must be? Not in setup-scripts/conf/local.conf? May 05 08:18:07 layer.conf( May 05 08:18:11 layer.conf* May 05 08:19:10 ok SSH_AGENT_PID and SSH_AUTH_SOCK are lost when bitbake executes bitbake-worker May 05 08:20:31 pompomJuice: try local.conf first, then try migrating it May 05 08:20:43 pompomJuice: layer ordering and priorities are hard to get right May 05 08:23:04 ok that is all I needed to know, since that is what I am trying to do and i have no idea what I am doing. At least now I know that I don't know and it's not trivial May 05 08:23:12 il pull some more leavers and see what happens... May 05 08:31:11 adding SSH_AUTH_SOCK and SSH_AGENT_PID in preserved_envvars_exported() fix my problem but i don't think i should fix it like this May 05 08:31:49 ok so I copied the distro folder to my own meta-layer/conf but that has no effect. Is that what you mean by "migrate"? May 05 08:37:15 pompomJuice: no, I meant setting the variable in your layer.conf and then trying to tweak the priority May 05 08:37:19 ok the problem was that BB_ENV_EXTRAWHITE was lost when i init oe :) fixed ! May 05 08:37:33 pompomJuice: and you might also need to move it up or down in bblayers.conf May 05 08:37:53 it usually takes me a few days to figure that out May 05 08:38:00 like I said, it's not trivial :( May 05 08:38:53 yea the tweak inside layer.conf does not work May 05 08:39:02 That is why I am here. Usually that works. May 05 08:39:23 I presumed that since the tweak does not work it is a bug May 05 08:39:47 bblayers.conf and angstroms layer.conf are structured to make such overrides hard to do May 05 08:39:54 I see May 05 08:40:01 since in general, it won't be angstrom anymore May 05 08:40:10 yea it is not angstrom May 05 08:40:25 but as you noticed, making changes to make your platform work are also very hard to do outside of local.conf May 05 08:40:33 So another soultion might be to just change the value inside the angstrom layer, but how would you suggest I handle version control then? May 05 08:40:41 I'm open for suggestions to make your use case easier, though May 05 08:40:50 ok so it has to be inside that local.conf, gotcha May 05 08:41:01 well May 05 08:41:09 local.conf works 99% of the time for things like this May 05 08:41:26 yea I have lots of preferred versions setup May 05 08:41:30 its just that one that is jamming May 05 08:41:58 ok so you have roughtly explained what levers there are to pull so let me go do that for a while May 05 08:46:17 from OEs perspective, what is the difference between a build-time and a run-time dependency? May 05 08:46:53 Well for one it affects in what order things build and if they build concurrently. May 05 08:47:38 and whether it does a populate_sysroots before building another package May 05 08:47:55 or a setscene May 05 08:47:59 or something May 05 08:51:20 Also whomever has to knowlege or power to change this. Bitbake's insane system is to harsh on files that look like libFoo.so ( as supposed to libFoo.so.1 which is handled correctly). Some software such as mono produce just .so files that get shuffled into other foo-dev packages which breaks everything. That rule is to strict! May 05 08:52:02 causes a hellova mission May 05 12:33:44 sup noobies May 05 12:33:49 I found a workaround May 05 12:34:21 or it might be legit since there is no documentation on how to do it correctly May 05 12:34:25 so yea it's not a hack May 05 12:35:37 inside conf/local.conf change this line to your own located in meta-foo/conf/distro/ angstrom-duo-v2013.12 -> DISTRO = "angstrom-duo-v2013.12" May 05 12:36:24 then pupulate angstrom-duo-v2013.12.conf with ... May 05 12:36:27 ANGSTROM_BASE = "${TOPDIR}/sources/meta-angstrom" May 05 12:36:27 include ${ANGSTROM_BASE}/conf/distro/angstrom-v2013.12.conf May 05 12:36:27 PREFERRED_VERSION_systemd = "204" May 05 12:36:31 poof it works May 05 12:37:40 it even makes sense May 05 12:38:11 basically you override the distro stuff like you would append to a recipy.inc file May 05 12:54:22 anyone here have any clue why these files are included in the angstrom git repo -> cache/bb_persist_data.sqlite3 & cache/prserv.sqlite3 May 05 12:54:33 those things look like temp files **** BEGIN LOGGING AT Mon May 05 14:20:12 2014 May 05 14:23:38 pompomJuice: to keep the PRSERV synced between the autobuilder and users May 05 14:56:21 mind.it May 05 14:56:31 oops May 05 14:56:58 we-dont-mind.it :-) May 05 14:57:06 :-D May 05 15:37:42 is the linux "perf" tool not supported on ARM v7 Cortex A8? I tried enabling the profiling tools by enabling the image feature "tools-profile", and when I run the "perf" tool on my target, it prints " cycles". Is this something I need to enable extra support for in the OE build? E.g tweak the kernel config or whatnot May 05 15:47:30 moin May 05 19:35:34 g 32 May 05 19:40:21 Crofton: thanks for reminding me i need a new bike... May 05 19:41:00 the proper number of bikes to own is N+1 May 05 19:41:08 where N is the number you currently own May 05 19:41:59 i'm a gentoo guy, so that would be 2N+1 May 05 19:42:50 and thanks for letting me crash the party, i had a really good time May 05 23:29:14 hmm, what version of bitbake to use with daisy May 05 23:33:45 Crofton: pretty sure you want 1.22, but you can always check poky to see what was integrated on its daisy branch May 05 23:34:09 Crofton: http://git.yoctoproject.org/cgit.cgi/poky/tree/bitbake/lib/bb/__init__.py?h=daisy#n24 May 05 23:35:28 That should be probably be documented better May 05 23:35:49 Picked up a cheap as dirt nooelec r820t to poke at gnuradio one of these days :) May 05 23:35:56 it would surprise me if it wasn't mentioned in the yocto 1.6 release notes May 05 23:36:02 cool May 05 23:36:34 huh, nope, not in the release notes. that seems like a definite oversight May 05 23:36:38 https://www.yoctoproject.org/download/yocto-project-16 May 05 23:36:52 has the info on the poky version, but the components inside poky May 05 23:36:59 s/but the/but not the/ May 05 23:37:37 no tag in bitbake May 05 23:38:11 /home/balister/oe-core/oe-core/../meta-xilinx/recipes-kernel/linux/linux-yocto_3.8.bbappend May 05 23:38:19 hmm May 05 23:38:35 maybe I forgot to push something at hoime .... May 05 23:45:09 crofton... May 05 23:49:32 kergoth, Crofton: https://wiki.yoctoproject.org/wiki/Releases May 05 23:49:42 Only place I know with that info May 05 23:49:56 ah, good call. should still get added to the release notes i think, but that's a useful ilnk May 05 23:49:58 link May 05 23:50:05 dok May 05 23:50:11 I was looking for a bb tag May 05 23:50:44 bitbake only has tags for its own branches and releases, which are version based, not the name-based poky branching/release scheme May 05 23:51:33 I'm working on getting my meta-sdr build switched to daisy branches May 05 23:51:42 starting build testing this week May 05 23:54:01 ah yeah, I just did that with my public layers not too long ago. fun fun May 06 00:14:44 okay, i'll bite May 06 00:15:27 what is vim selinux support? for working with policy files? May 06 01:02:56 Crofton: is there any reason why bitbake couldn't have a corresponding release tag? May 06 01:03:10 * nerdboy thinks that's actually a pretty good idea May 06 01:03:52 plus a signed tag is a pretty nice entity May 06 01:04:06 about as permanent as anything gets in git... May 06 01:05:24 pretty sure it already gets release tags May 06 01:05:28 for bitbake releases, not poky releases May 06 01:05:39 poky just happens to include bitbake May 06 01:05:40 i was thinking the latter May 06 01:06:45 my guess is it would normally be head of a bitbake release branch May 06 01:07:02 but it wouldn't have to be... May 06 01:09:37 i'm just putting on my if-i-was-release-manager hat May 06 01:10:02 * nerdboy is used to wearing a large stack of hats May 06 01:10:25 er, queue, depending May 06 01:10:38 May 06 02:43:47 tough crowd. i usually kill in #gentoo-dev ... **** ENDING LOGGING AT Tue May 06 02:59:58 2014