00:10.26 | *** join/#oe kgilmer (~kgilmer@65.209.23.146) |
01:09.14 | *** join/#oe jkridner (~jkridner@c-98-250-189-79.hsd1.mi.comcast.net) |
01:09.14 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
01:11.11 | *** join/#oe kgilmer (~kgilmer@65.209.23.146) |
02:04.30 | *** join/#oe Shawn286 (~Shawn@unaffiliated/shawn156) |
02:09.31 | *** join/#oe s3v3n62mm (~s3v3n62mm@p5DDC0C7F.dip0.t-ipconnect.de) |
02:12.09 | *** join/#oe kgilmer (~kgilmer@65.209.23.146) |
03:12.53 | *** join/#oe kgilmer (~kgilmer@65.209.23.146) |
03:24.05 | *** join/#oe pompomJuice (~pompomJui@41.0.38.138) |
03:32.46 | *** join/#oe NvrBst (~NvrBst@gateway/tor-sasl/nvrbst) |
03:36.36 | *** join/#oe crxz0193 (~crxz0193@203.247.149.152) |
04:04.03 | *** join/#oe crxz0193 (~crxz0193@203.247.149.152) |
04:04.09 | *** join/#oe nitink (nitink@nat/intel/x-nqdhdtxjqwqyfmks) |
04:13.26 | *** join/#oe kgilmer (~kgilmer@65.209.23.146) |
05:14.10 | *** join/#oe kgilmer (~kgilmer@65.209.23.146) |
05:32.33 | *** join/#oe kroon (~kroon@fw.mikrodidakt.se) |
05:44.59 | *** join/#oe ecloud_ (quassel@nat/digia/x-fbjnomiliqmjyxjd) |
05:48.54 | *** join/#oe muppe (~Marko@ip050-115.seclan.com) |
06:02.32 | *** join/#oe fusman (~fahad@39.42.81.148) |
06:14.54 | *** join/#oe kgilmer (~kgilmer@65.209.23.146) |
06:37.57 | *** join/#oe mago_ (~mago@c193-14-123-186.cust.tele2.se) |
06:39.41 | mago_ | how does runtime dependencies work? if I do RDEPENDS = "something", I can't seem to find a corresponding recipe for "something"? |
06:40.13 | mago_ | from OEs perspective, what is the difference between a build-time and a run-time dependency? |
06:42.00 | *** join/#oe adelcast (~adelcast@130.164.62.193) |
06:43.22 | kroon | mago_, I believe a single recipe can produce multiple packages, -dbg, -dev or even custom named packages. all these can be added as RDEPENDS |
06:48.27 | *** join/#oe dany (~Thunderbi@sestofw01.enea.se) |
06:50.30 | *** join/#oe lamikr (~lamikr@145.247.15.238) |
06:56.27 | *** join/#oe jbrianceau_away (uid10952@gateway/web/irccloud.com/x-fxvvxbkoazdmrkar) |
07:05.24 | *** join/#oe rob_w (~bob@unaffiliated/rob-w/x-1112029) |
07:15.49 | *** join/#oe kgilmer (~kgilmer@65.209.23.146) |
07:16.21 | *** join/#oe florian (~fuchs@port-217-146-132-69.static.qsc.de) |
07:16.21 | *** join/#oe florian (~fuchs@Maemo/community/contributor/florian) |
07:26.20 | mckoan | good morning |
07:26.24 | pompomJuice | howdy |
07:26.46 | pompomJuice | I need help mckoan. Can you help me? |
07:27.12 | mckoan | ~ask |
07:27.12 | infobot | 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. |
07:29.05 | pompomJuice | meta-angstrom/conf/distro/angstrom-v2012.12.conf contains an entry -> PREFERRED_VERSION_systemd = "208%" |
07:29.24 | pompomJuice | I am running 2.6.37 which only works up to 204 |
07:29.59 | pompomJuice | in my setup-scripts/conf/local.conf I have PREFERRED_VERSION_systemd = "204%" |
07:30.22 | pompomJuice | bitbake mechanisms how ever know better and always selects the higher number |
07:30.47 | pompomJuice | what is the correct method of fixing this issue |
07:31.13 | pompomJuice | ? |
07:31.41 | mckoan | pompomJuice: do you have systemd 204 in any of your metalayers? |
07:31.48 | pompomJuice | no |
07:32.05 | mckoan | pompomJuice: so you have to create your recipe for that |
07:32.12 | pompomJuice | I did |
07:32.35 | pompomJuice | basically just copied and changed the recipy name from to 204 |
07:32.56 | pompomJuice | my meta layer is at priority 14 |
07:33.00 | pompomJuice | higher than angstrom |
07:33.04 | pompomJuice | that also has no effect |
07:33.20 | pompomJuice | I tried to troll the bitbake code |
07:33.29 | pompomJuice | but I donno who codes like that |
07:33.35 | pompomJuice | I cant make out a thing |
07:33.48 | pompomJuice | python is my cuppa tea |
07:34.18 | pompomJuice | Tried to understand that part of the code, but I could not find a hack I could implement |
07:36.04 | *** join/#oe crxz0193 (~crxz0193@203.247.149.152) |
07:37.22 | mckoan | pompomJuice: please pastebin your recipe and the original one (208) |
07:37.42 | pompomJuice | ok |
07:42.16 | *** join/#oe fusman (~fahad@110.93.212.98) |
07:44.54 | afournier | morning all ! |
07:47.26 | pompomJuice | This is my recipy -> systemd_204.bb -> http://pastebin.com/Wy9WvHcj |
07:47.55 | pompomJuice | http://pastebin.com/rafNNKdt -> systemd_208.bb |
07:49.10 | pompomJuice | 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 |
07:49.27 | *** join/#oe shoragan (~shoragan@debian/developer/shoragan) |
07:49.49 | pompomJuice | damage version control to be more spesific |
07:50.08 | *** join/#oe Jafura (~Jean-Fran@host-213-213-229-139.brutele.be) |
07:56.21 | pompomJuice | What I can see from the code is this: |
07:56.26 | pompomJuice | move 1 is -> # Find the highest priority provider with a PREFERRED_VERSION set |
07:56.40 | pompomJuice | move 2 is -> # Find the latest version of the highest priority provider |
07:57.14 | pompomJuice | 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? |
07:57.30 | mckoan | hi afournier |
07:57.37 | afournier | hi |
07:57.46 | mckoan | pompomJuice: actually what is your problem? |
07:57.58 | mckoan | pompomJuice: is your recipe ignored? |
07:58.01 | pompomJuice | I cannot make bitbake select the 204 version |
07:58.04 | pompomJuice | yea |
07:58.11 | pompomJuice | when I run it in debug mode |
07:58.16 | pompomJuice | it finds the 204,208 |
07:58.24 | pompomJuice | but selects the 208 |
07:58.45 | *** part/#oe muppe (~Marko@ip050-115.seclan.com) |
07:58.48 | mckoan | pompomJuice: try setting PREFERRED_VERSION_systemd = "204" in your image recipe |
07:59.01 | pompomJuice | maybe I should ask this.. where can I put the line PREFERRED_VERSION_systemd inside my meta layer? |
07:59.09 | afournier | 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 ? |
07:59.14 | koen | pompomJuice: PREFERRED_VERSION is a global var, image recipes can't set global vars |
07:59.19 | mckoan | pompomJuice: have you created a new layer? |
07:59.23 | pompomJuice | yes |
07:59.32 | koen | mckoan: and even if images could, it's a DISTRO setting, which should never to into image recipes |
07:59.33 | pompomJuice | one that adds our stuff to the image |
07:59.50 | pompomJuice | and that meta-layer contains a directory systemd_204/systemd_204.bb |
07:59.54 | *** join/#oe ao2 (~ao2@host168-93-dynamic.59-82-r.retail.telecomitalia.it) |
08:00.02 | pompomJuice | that meta layer has priority 14 highest of all |
08:00.11 | mckoan | pompomJuice: have you added your layer to bblayers.conf? |
08:00.20 | pompomJuice | let me check |
08:00.33 | mckoan | koen: yep, thx |
08:00.52 | pompomJuice | # These layers hold machine specific content, aka Board Support Packages |
08:00.52 | pompomJuice | BSPLAYERS ?= " \ |
08:00.52 | pompomJuice | <PROTECTED> |
08:00.52 | pompomJuice | <PROTECTED> |
08:00.52 | pompomJuice | " |
08:01.02 | pompomJuice | the recipy resides in meta-ctlab |
08:01.07 | pompomJuice | our layer |
08:01.58 | mckoan | pompomJuice: do you mean BBLAYERS ? is there a typo? |
08:02.00 | pompomJuice | that layers adds customization to a standard angstrom image. (older kernel + rowboat + ti ) |
08:02.28 | pompomJuice | no type |
08:02.32 | pompomJuice | im copy pasting |
08:02.44 | mckoan | pompomJuice: maybe Angstrom specific |
08:02.54 | pompomJuice | yea it is angstrom spesific |
08:02.58 | pompomJuice | because angstrom |
08:03.00 | pompomJuice | contains a file |
08:03.19 | pompomJuice | that makes it select 208 |
08:03.45 | pompomJuice | [09:22] <pompomJuice> meta-angstrom/conf/distro/angstrom-v2012.12.conf contains an entry -> PREFERRED_VERSION_systemd = "208%" |
08:04.21 | pompomJuice | I do not understand that part of bitbake |
08:04.30 | pompomJuice | what file must I add that overrides that setting? |
08:04.40 | mckoan | pompomJuice: so try replacing this line (at distro level) |
08:04.57 | pompomJuice | do you mean edit that file? |
08:05.30 | mckoan | pompomJuice: yes, just to check if your recipe is selected |
08:05.40 | pompomJuice | Yea it does |
08:06.00 | pompomJuice | as isaid if you run bitbake in debug mode it show that it finds both recipies, but selects 208 as the winner |
08:06.14 | mckoan | pompomJuice: as koen said it's a DISTRO setting, so angstrom-v2012.12.conf is the distro config file |
08:06.49 | pompomJuice | koen? I did not see him say anything |
08:06.54 | mckoan | pompomJuice: set PREFERRED_VERSION_systemd = "204%" in angstrom-v2012.12.conf |
08:06.57 | pompomJuice | let me check since he is the maker |
08:07.09 | pompomJuice | ok but where do I put that file? |
08:07.22 | mckoan | 10:04 < koen> mckoan: and even if images could, it's a DISTRO setting, which should never to into image recipes |
08:07.28 | pompomJuice | I cant edit the file inside the distro becaue then oebb update becomes angry |
08:07.58 | pompomJuice | Then I cannot suck in angstrom changes automagically anymore :( |
08:08.24 | mckoan | pompomJuice: I don't know I don't use Angstrom |
08:08.32 | pompomJuice | ok how do I override the distro config file? |
08:08.58 | koen | try local.conf first |
08:09.03 | pompomJuice | from inside meta-ctlab, my customizations layer |
08:09.07 | koen | then migrate it to your distro layer |
08:09.08 | pompomJuice | I dont wanna edit the distro |
08:09.25 | pompomJuice | how? sorry im bitbake noob |
08:09.31 | pompomJuice | less than 6 month XP with this |
08:09.36 | koen | but I'd think that backporting the patches to 2.6.37 would be a better idea for future proofing |
08:09.52 | koen | (well, migrating to a newer kernel would be even better, but you mentioned TI silicon) |
08:10.25 | pompomJuice | 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) |
08:10.46 | pompomJuice | then they hacked the android |
08:10.53 | pompomJuice | then everything got locked in |
08:11.01 | pompomJuice | then boss man cannot understand it takes time |
08:11.06 | pompomJuice | fires the guy that does all the magic |
08:11.09 | pompomJuice | now im stuck with it |
08:11.42 | pompomJuice | so yea its working nicely actually |
08:11.49 | pompomJuice | I got it upgraded as far I could |
08:11.56 | pompomJuice | took it from 1.3 to 1.5 |
08:12.08 | pompomJuice | the new angstrom is sweet! |
08:12.18 | pompomJuice | major difference between 1.5 and 1.3 |
08:12.29 | pompomJuice | our device runs much happier on 1.5 |
08:12.54 | pompomJuice | mostly because it now has armhf and mono 3.4 with sgen and lvm |
08:12.56 | pompomJuice | lvvm |
08:15.18 | pompomJuice | this yocto movement is clearly showing results |
08:16.30 | *** join/#oe kgilmer (~kgilmer@65.209.23.146) |
08:17.52 | pompomJuice | 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? |
08:18.07 | pompomJuice | layer.conf( |
08:18.11 | pompomJuice | layer.conf* |
08:19.10 | afournier | ok SSH_AGENT_PID and SSH_AUTH_SOCK are lost when bitbake executes bitbake-worker |
08:20.31 | koen | pompomJuice: try local.conf first, then try migrating it |
08:20.43 | koen | pompomJuice: layer ordering and priorities are hard to get right |
08:23.04 | pompomJuice | 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 |
08:23.12 | pompomJuice | il pull some more leavers and see what happens... |
08:25.10 | *** join/#oe fusman (~fahad@110.93.212.98) |
08:31.11 | afournier | 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 |
08:31.49 | pompomJuice | 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"? |
08:37.15 | koen | pompomJuice: no, I meant setting the variable in your layer.conf and then trying to tweak the priority |
08:37.19 | afournier | ok the problem was that BB_ENV_EXTRAWHITE was lost when i init oe :) fixed ! |
08:37.33 | koen | pompomJuice: and you might also need to move it up or down in bblayers.conf |
08:37.53 | koen | it usually takes me a few days to figure that out |
08:38.00 | koen | like I said, it's not trivial :( |
08:38.53 | pompomJuice | yea the tweak inside layer.conf does not work |
08:39.02 | pompomJuice | That is why I am here. Usually that works. |
08:39.23 | pompomJuice | I presumed that since the tweak does not work it is a bug |
08:39.47 | koen | bblayers.conf and angstroms layer.conf are structured to make such overrides hard to do |
08:39.54 | pompomJuice | I see |
08:40.01 | koen | since in general, it won't be angstrom anymore |
08:40.10 | pompomJuice | yea it is not angstrom |
08:40.25 | koen | but as you noticed, making changes to make your platform work are also very hard to do outside of local.conf |
08:40.33 | pompomJuice | So another soultion might be to just change the value inside the angstrom layer, but how would you suggest I handle version control then? |
08:40.41 | koen | I'm open for suggestions to make your use case easier, though |
08:40.50 | pompomJuice | ok so it has to be inside that local.conf, gotcha |
08:41.01 | pompomJuice | well |
08:41.09 | koen | local.conf works 99% of the time for things like this |
08:41.26 | pompomJuice | yea I have lots of preferred versions setup |
08:41.30 | pompomJuice | its just that one that is jamming |
08:41.58 | pompomJuice | ok so you have roughtly explained what levers there are to pull so let me go do that for a while |
08:46.17 | mago_ | from OEs perspective, what is the difference between a build-time and a run-time dependency? |
08:46.53 | pompomJuice | Well for one it affects in what order things build and if they build concurrently. |
08:47.38 | pompomJuice | and whether it does a populate_sysroots before building another package |
08:47.55 | pompomJuice | or a setscene |
08:47.58 | pompomJuice | or something |
08:50.05 | *** join/#oe phdeswer (~phdeswer@a88-112-199-213.elisa-laajakaista.fi) |
08:51.20 | pompomJuice | 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! |
08:52.02 | pompomJuice | causes a hellova mission |
08:52.11 | *** join/#oe kuldeepdhaka (~kuldeepdh@unaffiliated/kuldeepdhaka) |
08:55.48 | *** join/#oe anarsoul (~anarsoul@178.124.194.242) |
09:07.40 | *** join/#oe crxz0193 (~crxz0193@203.247.149.152) |
09:07.50 | *** join/#oe jackmitch|home (~Thunderbi@cpc22-cmbg15-2-0-cust21.5-4.cable.virginm.net) |
09:17.11 | *** join/#oe kgilmer (~kgilmer@65.209.23.146) |
09:21.19 | *** join/#oe stefan_schmidt (~stefan@p20030048092A05BBF2DEF1FFFE6228F7.dip0.t-ipconnect.de) |
09:28.56 | *** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
09:31.29 | *** join/#oe eballetbo (~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net) |
09:41.21 | *** join/#oe blitz00 (~stefans@188.26.163.173) |
09:41.21 | *** join/#oe blitz00 (~stefans@unaffiliated/blitz00) |
09:45.08 | *** join/#oe stefan_schmidt (~stefan@p20030048095B07BBF2DEF1FFFE6228F7.dip0.t-ipconnect.de) |
10:09.25 | *** join/#oe fusman (~fahad@110.93.212.98) |
10:18.10 | *** join/#oe kgilmer (~kgilmer@65.209.23.146) |
10:19.06 | *** join/#oe ao2 (~ao2@host196-140-dynamic.3-79-r.retail.telecomitalia.it) |
10:38.55 | *** join/#oe Leatherface- (~leatherfa@2001:470:dd7d:0:c940:fc55:eee5:40c9) |
10:50.57 | *** join/#oe joey_saint (~jjm@128.224.252.2) |
11:18.49 | *** join/#oe kgilmer (~kgilmer@65.209.23.146) |
11:27.28 | *** join/#oe ao2 (~ao2@87.13.159.24) |
11:48.28 | *** join/#oe kbart (~KBart@213.197.143.19) |
11:49.02 | *** join/#oe ao2 (~ao2@host83-100-dynamic.59-82-r.retail.telecomitalia.it) |
11:50.54 | *** join/#oe kroon (~kroon@193.15.174.198) |
12:19.39 | *** join/#oe kgilmer (~kgilmer@65.209.23.146) |
12:22.30 | *** join/#oe bluelightning_ (~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209) |
12:22.31 | *** join/#oe bluelightning_ (~paul@pdpc/supporter/professional/bluelightning) |
12:29.56 | *** join/#oe roric (~roric@gbg.gatekeeper.cybercomhosting.com) |
12:31.09 | *** join/#oe jkridner (~jkridner@c-98-250-189-79.hsd1.mi.comcast.net) |
12:31.09 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
12:31.34 | *** join/#oe RagBal (~RagBal@zimbra.welvaarts.com) |
12:33.44 | pompomJuice | sup noobies |
12:33.49 | pompomJuice | I found a workaround |
12:34.21 | pompomJuice | or it might be legit since there is no documentation on how to do it correctly |
12:34.25 | pompomJuice | so yea it's not a hack |
12:35.37 | pompomJuice | 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" |
12:36.24 | pompomJuice | then pupulate angstrom-duo-v2013.12.conf with ... |
12:36.29 | pompomJuice | ANGSTROM_BASE = "${TOPDIR}/sources/meta-angstrom" |
12:36.29 | pompomJuice | include ${ANGSTROM_BASE}/conf/distro/angstrom-v2013.12.conf |
12:36.29 | pompomJuice | PREFERRED_VERSION_systemd = "204" |
12:36.31 | pompomJuice | poof it works |
12:37.40 | pompomJuice | it even makes sense |
12:38.11 | pompomJuice | basically you override the distro stuff like you would append to a recipy.inc file |
12:44.57 | *** join/#oe jkridner (~jkridner@c-98-250-189-79.hsd1.mi.comcast.net) |
12:44.58 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
12:47.24 | *** join/#oe Bertux (~fabio@it09.itsm.ufsm.br) |
12:50.27 | *** join/#oe bertux_ (~fabio@it09.itsm.ufsm.br) |
12:52.38 | *** join/#oe bertux (~fabio@it09.itsm.ufsm.br) |
12:52.54 | *** join/#oe sr105|away (~sr105@65349hfc19.tampabay.res.rr.com) |
12:54.22 | pompomJuice | anyone here have any clue why these files are included in the angstrom git repo -> cache/bb_persist_data.sqlite3 & cache/prserv.sqlite3 |
12:54.33 | pompomJuice | those things look like temp files |
12:56.05 | *** join/#oe ao2 (~ao2@host190-137-dynamic.10-87-r.retail.telecomitalia.it) |
13:20.04 | *** join/#oe kgilmer (~kgilmer@65.209.23.146) |
13:23.57 | *** join/#oe kgilmer (~kgilmer@65.209.23.146) |
13:27.40 | *** join/#oe pdp7 (~pdp7@asciipr0n.com) |
14:20.12 | *** join/#oe nslu2-log (~nslu2-log@140.211.169.184) |
14:20.33 | *** join/#oe mario-go` (~user@email.parenteses.org) |
14:23.38 | koen | pompomJuice: to keep the PRSERV synced between the autobuilder and users |
14:48.42 | *** join/#oe kuldeepdhaka (~kuldeepdh@unaffiliated/kuldeepdhaka) |
14:56.21 | mckoan | mind.it |
14:56.31 | mckoan | oops |
14:56.58 | mario-goulart | we-dont-mind.it :-) |
14:57.06 | mckoan | :-D |
14:58.04 | *** join/#oe sr105|away (~sr105@65349hfc19.tampabay.res.rr.com) |
15:01.14 | *** join/#oe blilly (~blilly1@c-50-170-54-92.hsd1.wa.comcast.net) |
15:16.26 | *** join/#oe mago_ (~mago@c193-14-123-186.cust.tele2.se) |
15:30.09 | *** join/#oe ao2 (~ao2@host154-147-dynamic.6-87-r.retail.telecomitalia.it) |
15:33.44 | *** join/#oe tlwoerner (~trevor@linaro/tlwoerner) |
15:35.37 | *** join/#oe Rootert (~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl) |
15:36.07 | *** join/#oe RagBal_ (~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl) |
15:37.42 | mago_ | 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 "<not supported> cycles". Is this something I need to enable extra support for in the OE build? E.g tweak the kernel config or whatnot |
15:47.30 | nerdboy | moin |
15:47.38 | *** join/#oe Rootert (~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl) |
15:48.08 | *** join/#oe RagBal_ (~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl) |
15:56.30 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
15:57.46 | *** join/#oe roric (~roric@c-107ae455.213-3-64736c14.cust.bredbandsbolaget.se) |
16:00.46 | *** join/#oe ao2 (~ao2@2001:1418:117::1) |
16:10.42 | *** join/#oe DJWillis (~djwillis@cpc2-trow6-2-0-cust204.aztw.cable.virginm.net) |
16:25.31 | *** join/#oe hrw (~hrw@unaffiliated/hrw) |
16:27.46 | *** join/#oe jackmitch|home (~Thunderbi@cpc22-cmbg15-2-0-cust21.5-4.cable.virginm.net) |
16:30.36 | *** join/#oe mwester (~mwester@184-158-62-138.dyn.centurytel.net) |
16:30.37 | *** join/#oe mwester (~mwester@nslu2-linux/mwester) |
16:44.03 | *** join/#oe dos1 (~dos@unaffiliated/dos1) |
16:45.43 | *** join/#oe Rootert (~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl) |
16:46.13 | *** join/#oe hrw (~hrw@unaffiliated/hrw) |
16:46.43 | *** join/#oe RagBal_ (~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl) |
16:58.08 | *** join/#oe hrw (~hrw@unaffiliated/hrw) |
17:00.25 | *** join/#oe joey_saint (~jjm@24-246-4-250.cable.teksavvy.com) |
17:18.13 | *** join/#oe Crofton (~balister@64.186.172.226) |
17:21.54 | *** join/#oe kurre2 (~tomimo@xdsl-83-150-88-111.nebulazone.fi) |
17:25.53 | *** join/#oe jkridner (~jkridner@c-98-250-189-79.hsd1.mi.comcast.net) |
17:25.53 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
17:34.25 | *** join/#oe darknighte (~darknight@pdpc/supporter/professional/darknighte) |
17:35.42 | *** join/#oe rob_w (~rob@unaffiliated/rob-w/x-1112029) |
17:38.15 | *** join/#oe CMoH (~cipi@78.96.95.69) |
17:38.15 | *** join/#oe CMoH (~cipi@unaffiliated/c-moh) |
17:46.29 | *** join/#oe dv__ (~quassel@chello080108088242.14.11.vie.surfer.at) |
17:47.06 | *** join/#oe kgilmer (~kgilmer@65.209.23.146) |
17:50.26 | *** join/#oe kgilmer (~kgilmer@65.209.23.146) |
18:05.08 | *** join/#oe NightMonkey (~NightrMon@c-67-171-66-194.hsd1.pa.comcast.net) |
18:05.09 | *** join/#oe NightMonkey (~NightrMon@pdpc/supporter/professional/nightmonkey) |
18:11.51 | *** join/#oe kroon (~kroon@89-253-118-72.customers.ownit.se) |
18:45.03 | *** join/#oe balister_ (~balister@64.186.172.226) |
18:57.36 | *** join/#oe fabo (~fabo@a91-152-78-194.elisa-laajakaista.fi) |
18:57.37 | *** join/#oe fabo (~fabo@linaro/fabo) |
19:14.42 | *** join/#oe lamikr (~lamikr@pilppa.org) |
19:35.34 | Daemon404 | g 32 |
19:40.21 | nerdboy | Crofton: thanks for reminding me i need a new bike... |
19:41.00 | Crofton | the proper number of bikes to own is N+1 |
19:41.08 | Crofton | where N is the number you currently own |
19:41.59 | nerdboy | i'm a gentoo guy, so that would be 2N+1 |
19:42.50 | nerdboy | and thanks for letting me crash the party, i had a really good time |
19:43.29 | *** join/#oe jackmitch|home (~Thunderbi@cpc22-cmbg15-2-0-cust21.5-4.cable.virginm.net) |
19:46.44 | *** join/#oe eFfeM (~frans@c73189.upc-c.chello.nl) |
19:48.01 | *** join/#oe ldnunes (~ldnunes_@177.194.208.225) |
19:48.57 | *** join/#oe florian (~fuchs@sign-4db6a2e4.pool.mediaWays.net) |
19:48.57 | *** join/#oe florian (~fuchs@Maemo/community/contributor/florian) |
19:50.56 | *** join/#oe ldnunes (~ldnunes_@177.194.208.225) |
20:25.03 | *** join/#oe CMoH|notebook (~cipi@78.96.95.69) |
20:25.03 | *** join/#oe CMoH|notebook (~cipi@unaffiliated/c-moh) |
20:50.37 | *** join/#oe nitink (~nitink@134.134.137.71) |
21:26.15 | *** join/#oe stefan_schmidt (~stefan@p2003004809389DBBF2DEF1FFFE6228F7.dip0.t-ipconnect.de) |
21:27.33 | *** join/#oe NvrBst (~NvrBst@gateway/tor-sasl/nvrbst) |
21:36.56 | *** join/#oe darkschneider (~gab@93-32-59-224.ip32.fastwebnet.it) |
21:56.10 | *** join/#oe ant_home (~andrea@host56-254-dynamic.11-79-r.retail.telecomitalia.it) |
22:00.20 | *** join/#oe NvrBst (~NvrBst@gateway/tor-sasl/nvrbst) |
22:01.58 | *** join/#oe DJWillis (~djwillis@cpc2-trow6-2-0-cust204.aztw.cable.virginm.net) |
22:07.15 | *** join/#oe dvhart (~dvhart@134.134.137.71) |
22:23.05 | *** join/#oe sr105|away (~sr105@65349hfc19.tampabay.res.rr.com) |
23:29.14 | Crofton | hmm, what version of bitbake to use with daisy |
23:33.45 | kergoth | Crofton: pretty sure you want 1.22, but you can always check poky to see what was integrated on its daisy branch |
23:34.09 | kergoth | Crofton: http://git.yoctoproject.org/cgit.cgi/poky/tree/bitbake/lib/bb/__init__.py?h=daisy#n24 |
23:35.28 | Crofton | That should be probably be documented better |
23:35.49 | kergoth | Picked up a cheap as dirt nooelec r820t to poke at gnuradio one of these days :) |
23:35.56 | kergoth | it would surprise me if it wasn't mentioned in the yocto 1.6 release notes |
23:36.02 | Crofton | cool |
23:36.34 | kergoth | huh, nope, not in the release notes. that seems like a definite oversight |
23:36.38 | kergoth | https://www.yoctoproject.org/download/yocto-project-16 |
23:36.52 | kergoth | has the info on the poky version, but the components inside poky |
23:36.59 | kergoth | s/but the/but not the/ |
23:37.37 | Crofton | no tag in bitbake |
23:38.11 | Crofton | <PROTECTED> |
23:38.18 | Crofton | hmm |
23:38.35 | Crofton | maybe I forgot to push something at hoime .... |
23:45.09 | nerdboy | crofton... |
23:49.20 | *** join/#oe Crofton (~balister@64.186.172.226) |
23:49.32 | paulbarker | kergoth, Crofton: https://wiki.yoctoproject.org/wiki/Releases |
23:49.42 | paulbarker | Only place I know with that info |
23:49.56 | kergoth | ah, good call. should still get added to the release notes i think, but that's a useful ilnk |
23:49.58 | kergoth | link |
23:50.05 | Crofton | dok |
23:50.11 | Crofton | I was looking for a bb tag |
23:50.44 | kergoth | bitbake only has tags for its own branches and releases, which are version based, not the name-based poky branching/release scheme |
23:51.33 | Crofton | I'm working on getting my meta-sdr build switched to daisy branches |
23:51.42 | Crofton | starting build testing this week |
23:54.01 | kergoth | ah yeah, I just did that with my public layers not too long ago. fun fun |