Tuesday, 2014-03-04

*** staylor <staylor!~staylor@> has quit IRC00:10
*** h725 <h725!~pizzaman@PLAID.CYLAB.CMU.EDU> has joined #yocto00:11
*** d_s_e <d_s_e!~d.s.e@2001:a60:143f:b901:fdd7:9c2a:eaf6:1497> has quit IRC00:12
-YoctoAutoBuilder- build #69 of nightly-fsl-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-arm-lsb/builds/6900:13
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC00:15
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC00:15
-YoctoAutoBuilder- build #69 of nightly-x86 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86/builds/6900:24
*** jwhitmore_ <jwhitmore_!~jwhitmore@> has quit IRC00:31
*** staylor <staylor!~staylor@> has joined #yocto00:47
*** sameo <sameo!~samuel@> has quit IRC00:48
-YoctoAutoBuilder- build #68 of nightly-fsl-arm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-arm/builds/6800:52
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has quit IRC00:56
*** mulhern_ <mulhern_!~mulhern@> has joined #yocto01:02
*** mulhern_ <mulhern_!~mulhern@> has quit IRC01:08
*** Garibaldi <Garibaldi!~adalton@cpe-065-190-086-231.nc.res.rr.com> has joined #yocto01:12
*** seebs <seebs!~seebs@home.seebs.net> has quit IRC01:33
*** seebs <seebs!~seebs@home.seebs.net> has joined #yocto01:37
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has quit IRC02:00
*** staylor <staylor!~staylor@> has quit IRC02:17
*** staylor <staylor!~staylor@> has joined #yocto02:18
*** Squix <Squix!~Squix__@p021.net112139202.tokai.or.jp> has joined #yocto02:20
*** mansano <mansano!~marcelo@> has joined #yocto02:22
*** mansano <mansano!~marcelo@> has left #yocto02:22
*** mansano <mansano!~marcelo@> has joined #yocto02:22
*** Garibaldi <Garibaldi!~adalton@cpe-065-190-086-231.nc.res.rr.com> has quit IRC02:27
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC02:32
*** mitz <mitz!~mitz@rt.miraclelinux.com> has quit IRC04:20
*** mitz <mitz!~mitz@rt.miraclelinux.com> has joined #yocto04:22
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto04:22
*** nitink <nitink!nitink@nat/intel/x-txkbxlzinzmwzqdi> has quit IRC04:36
*** nitink <nitink!~nitink@> has joined #yocto04:45
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC04:46
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto04:47
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC05:05
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto05:15
*** agust <agust!~agust@p4FC4663E.dip0.t-ipconnect.de> has joined #yocto05:31
*** nitink <nitink!~nitink@> has quit IRC05:40
*** SorenHolm <SorenHolm!~quassel@5634f347.rev.stofanet.dk> has joined #yocto05:54
*** jamestunnicliff_ is now known as jamestunnicliffe05:54
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC06:05
*** sakoman <sakoman!~steve@static-74-41-60-154.dsl1.pco.ca.frontiernet.net> has quit IRC06:27
*** fp <fp!~Chaudhary@> has joined #yocto06:27
*** fp <fp!~Chaudhary@> has quit IRC06:30
*** kbart <kbart!~KBart@> has joined #yocto06:32
*** sakoman <sakoman!~steve@static-74-41-60-154.dsl1.pco.ca.frontiernet.net> has joined #yocto06:36
*** SorenHolm <SorenHolm!~quassel@5634f347.rev.stofanet.dk> has quit IRC06:43
*** Marex_ <Marex_!~Marex@> has quit IRC07:15
*** Marex <Marex!~Marex@> has joined #yocto07:15
*** pocek <pocek!pock@77-254-176-159.adsl.inetia.pl> has quit IRC07:19
*** Marex <Marex!~Marex@> has quit IRC07:19
*** Marex <Marex!~Marex@> has joined #yocto07:21
*** pocek <pocek!pock@> has joined #yocto07:22
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto07:28
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has joined #yocto07:30
*** SorenHolm <SorenHolm!~quassel@cpe.ge-0-2-0-950.faaqnqu1.dk.customer.tdc.net> has joined #yocto07:34
*** Denwid <Denwid!c2cc4225@gateway/web/freenode/ip.> has quit IRC07:35
*** diego_r <diego_r!~diego@host65-246-static.10-188-b.business.telecomitalia.it> has joined #yocto07:42
*** tasslehoff <tasslehoff!~tasslehof@> has joined #yocto08:00
*** eballetbo <eballetbo!~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net> has joined #yocto08:10
*** zeeblex <zeeblex!~apalalax@> has joined #yocto08:13
*** rhn <rhn!~rhn@unaffiliated/rhn> has joined #yocto08:19
*** florian_kc <florian_kc!~fuchs@port-217-146-132-69.static.qsc.de> has joined #yocto08:30
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto08:30
*** florian_kc is now known as florina08:32
*** florina is now known as florian08:32
*** smartin <smartin!~smartin@> has joined #yocto08:51
*** fp <fp!~Chaudhary@> has joined #yocto08:55
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto08:55
*** beaver_545 <beaver_545!~stuart@> has joined #yocto08:57
*** hasselmm <hasselmm!~mathias@> has joined #yocto08:58
*** fp <fp!~Chaudhary@> has quit IRC08:59
*** Jin|away is now known as Jin^eLD09:06
*** aragua <aragua!~aragua@232-28-190-109.dsl.ovh.fr> has joined #yocto09:07
*** d_s_e <d_s_e!~d.s.e@2001:a60:14d6:7601:49d4:1199:c8d7:d491> has joined #yocto09:09
*** g1zer0 <g1zer0!~gizero@host168-65-static.12-87-b.business.telecomitalia.it> has joined #yocto09:10
*** mckoan|away is now known as mckoan09:10
mckoangood morning09:10
florianhi mckoan09:13
*** jwhitmore_ <jwhitmore_!~jwhitmore@> has joined #yocto09:15
Jin^eLDthe message: "WARNING: The recipe xxxx is trying to install files into a shared area when those files already exist." - how serious is this warning and what is the correct way around it?09:16
Jin^eLDI'm doing multimachine builds09:16
*** aragua <aragua!~aragua@232-28-190-109.dsl.ovh.fr> has quit IRC09:21
*** aragua <aragua!~aragua@232-28-190-109.dsl.ovh.fr> has joined #yocto09:22
*** Bryanstein <Bryanstein!~Bryanstei@shellium/admin/bryanstein> has quit IRC09:27
*** Bryanstein <Bryanstein!~Bryanstei@shellium/admin/bryanstein> has joined #yocto09:35
*** Net147 <Net147!~Net147@60-242-179-244.static.tpgi.com.au> has joined #yocto09:42
*** Marex <Marex!~Marex@> has quit IRC09:48
*** Marex <Marex!~Marex@> has joined #yocto09:48
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto09:51
*** sameo <sameo!~samuel@> has joined #yocto09:52
*** ant_work <ant_work!~ant__@host54-128-static.10-188-b.business.telecomitalia.it> has joined #yocto09:56
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has quit IRC09:57
*** belen <belen!~Adium@> has joined #yocto09:58
*** ddalex <ddalex!~ddalex@> has joined #yocto10:01
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto10:12
*** maxin <maxin!~maxin@c83-251-182-100.bredband.comhem.se> has joined #yocto10:17
*** jwhitmore_ <jwhitmore_!~jwhitmore@> has quit IRC10:27
*** mihai <mihai!~mihai@> has joined #yocto10:28
*** bluelightning <bluelightning!~paul@> has joined #yocto10:32
*** bluelightning <bluelightning!~paul@> has quit IRC10:32
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto10:32
Jin^eLD...so, anyone doing multimachine builds?10:34
*** jwhitmore_ <jwhitmore_!~jwhitmore@> has joined #yocto10:35
bluelightningmorning all10:36
Net147bluelightning: moin10:37
bluelightninghi Net14710:39
bluelightningJin^eLD: JaMa does I think10:40
Jin^eLDhi bluelightning10:40
bluelightninghi Jin^eLD10:40
bluelightning(on a regular basis that is)10:40
Jin^eLDI was trying to find out more about the warning10:41
Jin^eLD The recipe xxxx is trying to install files into a shared area when those files already exist.10:41
Jin^eLDand on how to deal with it10:41
Jin^eLDJaMa: ping10:41
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto10:44
lpappbluelightning: thanks for commenting on the bugreport.10:44
ant_workJin^eLD: was maybe shadow?10:45
Jin^eLDant_work: sorry, I don't understand what you are trying to tell me? what shadow?10:45
Jin^eLDI get this warning on several packages of mine10:46
ant_workafaik I've seen that about shadow or mayb eshadow-native10:46
*** misza222 <misza222!~misza@> has joined #yocto10:47
*** mulhern_ <mulhern_!~mulhern@> has joined #yocto10:49
Jin^eLDah, you mean the recipes10:51
Jin^eLDwell, no, I get it with some self-made recipes that I was using on a 1 year old OE-core/angstrom10:51
Jin^eLDI am converting to yocto now10:51
Jin^eLDand I saw that some recipes produce this warning when I build the same layer/distro for a different machine10:51
*** yenal <yenal!~yenal@unaffiliated/yenal> has joined #yocto11:00
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has quit IRC11:27
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has joined #yocto11:34
misza222Hi guys, I'm trying to follow http://www.yoctoproject.org/docs/latest/adt-manual/adt-manual.html#adt-package to package to the image, but I find it very confusing11:50
*** lpapp <lpapp!~lpapp@kde/lpapp> has left #yocto11:50
*** jwhitmore_ <jwhitmore_!~jwhitmore@> has quit IRC11:51
misza222any better tutorial that you know of which explains how to add something to the image?11:51
bluelightningmisza222: the ADT is for building applications separately from the build system - are you rather more interested in writing a recipe to integrate some software into the build system so it gets into the image perhaps?11:53
misza222bluelightning, exactly :)11:53
bluelightningmisza222: this might help: http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#new-recipe-writing-a-new-recipe11:54
bluelightning(this is from the in-development manual but should be almost completely applicable to current/older versions)11:55
misza222thanks bluelightning I'll try that11:55
*** yenal <yenal!~yenal@unaffiliated/yenal> has quit IRC11:58
*** Squix <Squix!~Squix__@p021.net112139202.tokai.or.jp> has quit IRC12:22
JaMaJin^eLD: pong12:32
JaMaJin^eLD: yes it's quite serious12:32
JaMaJin^eLD: it means that multiple recipes are trying to stage the same file which will cause undeterministic content of sysroot12:33
JaMabecause the recipe which will depend on those files will never know who staged it there last time12:33
*** arky <arky!~arky@> has joined #yocto12:45
Jin^eLDJaMa: so what is the correct way to solve it?12:47
*** yenal <yenal!~yenal@unaffiliated/yenal> has joined #yocto12:47
Jin^eLDis it complaining about the same recipe12:48
Jin^eLDor is it complaining about different recipes?12:48
Jin^eLDI think I get it now12:48
Jin^eLDif I read carefully it prints the two offending recipes12:48
Jin^eLDso two independent recipes try to stage things, correct?12:48
Jin^eLDthank you, I think I got the idea now12:48
*** Squix <Squix!~Squix__@p021.net112139202.tokai.or.jp> has joined #yocto12:58
*** _darknighte_ <_darknighte_!~darknight@pdpc/supporter/professional/darknighte> has joined #yocto13:06
JaMaJin^eLD: yes you need to make sure that only one of them is ever built (e.g. with PNBLACKLIST for your distro) when they are "alternatives" for something or you need to use unique filenames (e.g. if you need to stage 2 versions of something.. look at nodejs example in meta-oe)13:10
Jin^eLDJaMa: although I am noticing that the warning does not always print where the conflict is https://pastebin.mozilla.org/446635313:11
Jin^eLDfor instance I have only one "bootsetup" ipk13:11
JaMaJin^eLD: and this problem isn't really related to multi-machine13:11
JaMaJin^eLD: this one is because you've changed PACKAGE_ARCH13:11
JaMaI guess13:12
Jin^eLDwhat do you mean "changed"? i.e. made it package specific or vice versa?13:12
JaMabecause the path shows "all" but manifest armv7a-vfp-neon13:12
yoctiBug 4102: normal, Medium+, 1.6, richard.purdie, REOPENED , Incremental builds do not work well when renaming recipes or changing architecture.13:13
Jin^eLDactually that was a clean build13:14
Jin^eLDi.e. clean machine 1, then without cleaning machine 213:14
Jin^eLDbut without further package changes13:14
*** joeythesaint <joeythesaint!~jjm@> has joined #yocto13:15
Jin^eLDbut I'll try again to be sure I did not mess up13:15
Jin^eLDand I will keep an eye on the bug, thank you for the hints13:15
*** SorenHolm <SorenHolm!~quassel@cpe.ge-0-2-0-950.faaqnqu1.dk.customer.tdc.net> has quit IRC13:18
Net147bluelightning: is it normal for package versions to go backwards if you say, make a change, run build, undo the the change, run build again?13:20
Net147bluelightning: at some point today I had hundreds of packages go back a rev13:21
Net147bluelightning: when doing setscene13:21
*** SorenHolm <SorenHolm!~quassel@cpe.ge-0-2-0-950.faaqnqu1.dk.customer.tdc.net> has joined #yocto13:22
*** misza222_ <misza222_!~misza@> has joined #yocto13:29
*** misza222 <misza222!~misza@> has quit IRC13:29
*** misza222_ <misza222_!~misza@> has quit IRC13:35
bluelightningNet147: depends what the change is...13:36
Net147bluelightning: I don't recall...13:36
Net147bluelightning: but I have seen it happen before in the past13:37
*** maxin <maxin!~maxin@c83-251-182-100.bredband.comhem.se> has quit IRC13:38
*** maxin <maxin!~maxin@c83-251-182-100.bredband.comhem.se> has joined #yocto13:38
bluelightningI can see how it might be happening - reverting to a previous version -> signatures go back to a previous value (for which a deploy-ipk sstate package exists) -> final package gets the old version13:38
bluelightningwhich technically wouldn't be incorrect behaviour for most cases13:38
*** jwhitmore_ <jwhitmore_!~jwhitmore@> has joined #yocto13:39
Net147bluelightning: it would just break package feeds13:39
bluelightningthe alternative is to always increment no matter what13:40
bluelightningwhich means you could never reproduce the same PR value of course13:40
bluelightning(and maybe that's not a problem)13:40
Net147not sure if this has been answered previously, but is there a way to modify and build a package without having packages that depend on it automatically rebuilt later? for changes that maintain ABI compatibility13:42
bluelightningNet147: there isn't I'm afraid; not that I'm aware of13:42
bluelightningif you are maintaining a feed from which targets will upgrade, it's probably worth avoiding thinking about tmp/deploy/{ipk|rpm|deb} as feeds to be published verbatim13:43
bluelightningyou always have the option of being selective about what you put into your feed13:44
Net147I only intend to use the feed for development at the moment13:44
bluelightningthe difficulty is we have no way of saying "this change is safe" whilst retaining the ability for other changes to trigger rebuilds13:44
mckoanthey forgot Belen though13:45
*** misza222 <misza222!~misza@> has joined #yocto13:46
Net147bluelightning: I guess a workaround for the rev going backwards is to add some variable that you manually increment if you revert to a previous version13:47
bluelightningNet147: if you can guarantee that a particular dependency between two recipes should never cause a rebuild (i.e. no ABI exists, or it's guaranteed never to change) you can use SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS or SIGGEN_EXCLUDERECIPES_ABISAFE depending on the situation13:47
bluelightningNet147: that's PR - even with the PR server you can still manually increment PR in the recipe, in a bbappend or even from a conf file using e.g. PR_pn-something = "r11"13:48
*** arky <arky!~arky@> has quit IRC13:48
misza222Hi again, I transfer image files to the sd card (ext3 formatted), I get grub splash, but during the boot I get an error with message "VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0): error -6".  Does anybody have an idea what I am doing wrong?13:48
bluelightningmisza222: either that's the wrong device, or there's no mmc driver loaded13:49
misza222bluelightning, do you think that it may expect another partition (I only have 1) on the SD?13:51
bluelightningmisza222: it depends on the machine, but often you have a small partition containing the bootloader/kernel (possibly FAT32 formatted) and then an EXT3/4 partition with the root filesystem in it13:53
bluelightningmisza222: which target machine is this for?13:53
*** yenal <yenal!~yenal@unaffiliated/yenal> has quit IRC14:01
*** Net147 <Net147!~Net147@60-242-179-244.static.tpgi.com.au> has quit IRC14:05
misza222bluelightning, it's for intel galileo14:05
bluelightningmisza222: ah right; so yes, there should be two partitions as I described above14:07
misza222bluelightning, thanks, I will try that :)14:08
belenmckoan: I am waaaaay to new to make the list. Maybe in 5 years or so :)14:10
mckoanbelen: ;-)14:11
*** BSDCat <BSDCat!~unique@calvin.idempot.net> has joined #yocto14:11
*** Marex <Marex!~Marex@> has quit IRC14:13
*** belen <belen!~Adium@> has quit IRC14:13
*** Marex <Marex!~Marex@> has joined #yocto14:14
*** kapare <kapare!4443360a@gateway/web/freenode/ip.> has joined #yocto14:17
*** jjardon__ is now known as jjardon14:19
*** kapare <kapare!4443360a@gateway/web/freenode/ip.> has joined #yocto14:19
*** belen <belen!~Adium@> has joined #yocto14:20
LetoThe2ndis there any magic in poky/oe-init-build-env that keeps it from begins used in a python-started subshell?14:28
LetoThe2ndbecause subprocess.call(". poky/oe-init-build-env", shell=True) break with /bin/sh: 43: .: Can't open /mnt/data/jd/blubber/scripts/oe-buildenv-internal14:29
bluelightningLetoThe2nd: I don't think so, but it would be worth just looking at the script to see where it might be going wrong14:32
bluelightning(it's not a long script)14:32
LetoThe2ndbluelightning: hm, its the part where . $OEROOT/scripts/oe-buildenv-internal gets called14:36
bluelightningLetoThe2nd: the question is why isn't OEROOT getting the right value?14:38
LetoThe2ndthe interesting part is that OEROOT seems to be set to the directory from where its called.14:38
LetoThe2ndwhereas when i manually do . poky/xxx, it changes into the poky dir14:39
LetoThe2ndwill drill a bit deeper and then report back ;)14:41
*** OlivierG <OlivierG!oguiter@nat/intel/x-kuafkbkyykejcooc> has joined #yocto14:41
rburtonLetoThe2nd: do a chdir first?14:42
rburtonor just a cd in fact14:42
LetoThe2ndrburton: the pwd is correct, thats why i'm wondering14:43
*** slips <slips!~slips@> has quit IRC14:43
*** slips <slips!~slips@> has joined #yocto14:46
*** reallife <reallife!~reallife@ool-4b7ff55a.static.optonline.net> has quit IRC14:47
*** reallife <reallife!~reallife@ool-4b7ff55a.static.optonline.net> has joined #yocto14:47
zibriI'm seeing some strange behavior of _remove on EXTRA_OECONF. the bbnote line before invoking ./configure has the expected value, but the actual invokation does not.14:51
zibriany ideas? :/14:51
*** flynn378 <flynn378!80db310e@gateway/web/freenode/ip.> has joined #yocto14:51
*** Ratheesh <Ratheesh!48a3d966@gateway/web/freenode/ip.> has joined #yocto14:53
*** belen <belen!~Adium@> has quit IRC14:56
LetoThe2ndseems like BASH_SOURCE does not get set14:57
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has quit IRC14:59
*** belen <belen!Adium@nat/intel/x-sfxdewzwuanhltgf> has joined #yocto14:59
misza222bluelightning, it worked, thanks again15:03
*** g1zer0 <g1zer0!~gizero@host168-65-static.12-87-b.business.telecomitalia.it> has quit IRC15:03
RatheeshHi list15:04
Ratheeshif  i dont specify   do_install ()  routine  in my  recipe file ....   will it call default install  routine of the package  ....i mean  "make install"  of that pkg15:06
rburtonRatheesh: no, as there's no convention outside of autotools for how a make file installs.  if you are using automake/autoconf then inherit autotools and it will install for you.15:08
Ratheeshoh...so if i dont inherit any  .bb , i have to do a install of my own15:09
Ratheeshright ?15:09
*** SorenHolm <SorenHolm!~quassel@cpe.ge-0-2-0-950.faaqnqu1.dk.customer.tdc.net> has quit IRC15:09
Ratheeshi meant to say  .bbclass15:10
rburtonthere is no convention in make for how to do an install, so the default can't have something that works15:10
bluelightningmisza222: no problem15:11
*** Noor <Noor!~noor@> has quit IRC15:14
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto15:15
*** oneQubit <oneQubit!~oneQubit@c-98-231-154-140.hsd1.md.comcast.net> has joined #yocto15:17
*** kbart <kbart!~KBart@> has quit IRC15:19
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has joined #yocto15:19
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC15:20
*** misza222 <misza222!~misza@> has quit IRC15:20
*** tasslehoff <tasslehoff!~tasslehof@> has quit IRC15:23
*** Noor1 <Noor1!~noor@> has joined #yocto15:25
*** pocek_ <pocek_!pock@77-254-122-244.adsl.inetia.pl> has joined #yocto15:26
*** pocek <pocek!pock@> has quit IRC15:29
*** jwhitmore_ <jwhitmore_!~jwhitmore@> has quit IRC15:30
*** jwhitmore_ <jwhitmore_!~jwhitmore@> has joined #yocto15:35
*** staylor <staylor!~staylor@> has quit IRC15:36
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC15:39
*** Noor <Noor!~quassel@> has joined #yocto15:41
*** jwhitmore_ <jwhitmore_!~jwhitmore@> has quit IRC15:43
*** jwhitmore_ <jwhitmore_!~jwhitmore@> has joined #yocto15:46
*** _darknighte_ is now known as darknighte15:46
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has joined #yocto15:48
*** Piziwate <Piziwate!3e02bf43@gateway/web/freenode/ip.> has joined #yocto15:51
PiziwateHello every body ! Does somebody know how to modify kernel configuration with a recipe for meta-ti (kernel 3.12.10 - linux-ti-staging) ?15:52
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has quit IRC15:53
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has joined #yocto15:54
*** vali_enea <vali_enea!bc1b56bf@gateway/web/freenode/ip.> has joined #yocto15:54
sjolleyYPTM:           Participant passcode:         42001078             Dial-in number:         1.972.995.7777             US Toll Free number:         1.877.561.682815:55
*** Noor1 <Noor1!~noor@> has quit IRC15:55
vali_eneaYPTM: Vali Cobelea in the call15:56
halsteadYPTM: Michael on the call.15:56
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-wciblfxpjmgeexjq> has joined #yocto15:57
rburtonYPTM: ross on the call15:58
frayYPTM: Mark on the call15:58
*** cristiana <cristiana!c0c6972c@gateway/web/freenode/ip.> has joined #yocto15:59
*** tomz <tomz!~trz@c-98-206-136-16.hsd1.il.comcast.net> has joined #yocto15:59
zeddiiBruce on as well15:59
tomzYPTM: Tom Z on15:59
*** tomz is now known as Guest8425115:59
vmesonYPTM: Randy joined.15:59
PiziwateDoes somebody know how to modify kernel configuration with a recipe for meta-ti (kernel 3.12.10 - linux-ti-staging) ? the .config is created during the do_configure (based on a defconfig)... In don't want to edit the .config between the configuration and the build... I'm really blocked with that... your help will be apprecied !15:59
cristianaYPTM: Cristiana on the  call15:59
*** belen1 <belen1!~Adium@> has joined #yocto16:00
*** belen <belen!Adium@nat/intel/x-sfxdewzwuanhltgf> has quit IRC16:00
belen1YPTM: Belén on the call16:01
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has quit IRC16:01
RPYPTM: Richard is on the call16:01
BSDCatYPTM: Matthew is on the call16:01
*** bluelightning_ <bluelightning_!~paul@> has joined #yocto16:01
*** bluelightning_ <bluelightning_!~paul@> has quit IRC16:01
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto16:01
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC16:01
*** bluelightning_ is now known as bluelightning16:01
JefroYPTM Jefro is on the call16:01
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has joined #yocto16:02
cristianiorgaYPTM: cristian.iorga joined16:02
jmpdelosYPTM: Jeff Polk is on16:02
vmesonPiziwate:  I haven't done it but: git://git.yoctoproject.org/meta-fsl-ppc has ~ 28 examples.16:02
bluelightningYPTM: Paul Eggleton is on16:02
vmesonaccording to grep defconfig * | wc -l16:03
*** nitink <nitink!~nitink@> has joined #yocto16:03
* nitink YPTM nitin on the call16:04
sgw_YPTM: Saul is on16:04
Crofton|workPiziwate, use a bbappend to change the defconfig16:04
denixPiziwate: there's a defconfig file for that16:05
Crofton|workor branch the layer and updatedefconfig16:05
Piziwateyes I created a linux-ti-staging_3.1.2.bbappend, but the defconfig is not in the git repo, but in the meta-ti recipe, so I can not apply the patch16:06
PiziwateCrofton: ? or branch the layer and updatedefconfig ?16:07
PiziwateThe defconfig is in meta-ti/recipes-kernel/linux/linux-ti-staging and I didn't find the way to patch it during the build16:08
*** SorenHolm <SorenHolm!~quassel@5634f347.rev.stofanet.dk> has joined #yocto16:08
*** Fred_ <Fred_!c0373729@gateway/web/freenode/ip.> has joined #yocto16:11
*** Squix <Squix!~Squix__@p021.net112139202.tokai.or.jp> has quit IRC16:12
*** Fred_ is now known as Guest7755916:12
Piziwatedenix : Yes but the defconfig is not on the git directory... so I don't know how I can patch if with SRC_URI and FILESEXTRAPATHS_prepend !16:13
*** pidge_ <pidge_!pidge@nat/intel/x-qmoqplfiqrhrhlfa> has joined #yocto16:13
vmesonTo the speaker... the layers.openembedded.org site is really appreciated.16:13
RPhalstead: thanks!16:14
halsteadThank you RP.16:14
LetoThe2ndbluelightning: for the protocol: subprocess.Call needs exectuable="bin/bash" set explicitly16:14
bluelightningLetoThe2nd: what is your default shell16:14
* fray is happy with a warning..16:15
LetoThe2ndbluelightning: it is bash, but bash shows a different behaviour when called as "/bin/sh", which is what the subprocess module does by default16:16
pidge_YPTM: Beth joining late16:17
bluelightningLetoThe2nd: oh, I've figured it out - "." for sourcing is bash-specific syntax16:17
bluelightningLetoThe2nd: you could use "source" instead with /bin/sh16:17
PiziwateMy goal is to create two patch (one for CONFIG_PPP... and one for SPIDEV). The defconfig from meta-ti uses use-kernel-config=omap2plus_defconfig, so I created a git patch for PPP to modify the omap2plus_defconfig.16:17
LetoThe2ndbluelightning: yeah but "source" confuses the calling mechanism somewhere else (not worked out so far)16:18
Crofton|workyou YPTM eople, do not forget: http://openembedded.org/wiki/OEDAM16:18
sjolleyYPTM has ended16:18
*** Guest84251 <Guest84251!~trz@c-98-206-136-16.hsd1.il.comcast.net> has left #yocto16:19
* zeddii reads16:19
*** Guest77559 <Guest77559!c0373729@gateway/web/freenode/ip.> has quit IRC16:19
*** vali_enea <vali_enea!bc1b56bf@gateway/web/freenode/ip.> has quit IRC16:21
denixPiziwate: just put your own defconfig in there16:21
Piziwatedenix : is it possible to append lines to a file containing : use-kernel-config=omap2plus_defconfig16:22
Piziwatebut I want to keep the original omap2plus_defconfig file...16:23
*** sjolley <sjolley!sjolley@nat/intel/x-pgdaozdlxfdeezzk> has quit IRC16:23
*** reallife <reallife!~reallife@ool-4b7ff55a.static.optonline.net> has quit IRC16:24
*** OlivierG <OlivierG!oguiter@nat/intel/x-kuafkbkyykejcooc> has left #yocto16:24
*** reallife <reallife!~reallife@ool-4b7ff55a.static.optonline.net> has joined #yocto16:24
denixPiziwate: just copy it to your defconfig then and then modify16:24
*** aragua <aragua!~aragua@232-28-190-109.dsl.ovh.fr> has quit IRC16:25
Piziwatedenix : ok, but if the meta-ti team changes something on it, I'll pass over the changes... is there not a way to include a defconfig in an other defconfig who adds some config lines ?16:25
denixPiziwate: not by default in the kernel. you can keep patching omap2plus_defconfig in the kernel - we do that sometimes. linux-yocto supports config snippets, but we don't use that yet...16:29
Piziwatedenix : ok thanks... but I'm wondering if there is a way to create a patch who is not dependant of the destination... a patch who just add some lines (I tried with diff, but I got an error...) Is it mandatory to use a git patch ?16:31
*** vmeson <vmeson!~quassel@> has quit IRC16:33
denixdestination? you can play with patchlevel, I guess16:33
*** ant_work <ant_work!~ant__@host54-128-static.10-188-b.business.telecomitalia.it> has quit IRC16:38
Piziwateit doesn't work if I create this patch :16:39
Piziwate++ arch/arm/configs/omap2plus_defconfig2014-02-14 16:48:40.325397902 +010016:39
*** jwhitmore_ <jwhitmore_!~jwhitmore@> has quit IRC16:41
denixthat's not a valid patch of course...16:42
*** vmeson <vmeson!~quassel@> has joined #yocto16:42
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has quit IRC16:42
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has joined #yocto16:45
Piziwatedenix : is it mandatory to use git diff or is it possible to use diff ?16:49
*** wmat <wmat!wmat@wallace.mixdown.ca> has joined #yocto16:49
*** SorenHolm <SorenHolm!~quassel@5634f347.rev.stofanet.dk> has quit IRC16:49
denixPiziwate: I believe it can be plain diff, but of the right context format.16:53
*** belen1 <belen1!~Adium@> has quit IRC16:59
*** Ratheesh <Ratheesh!48a3d966@gateway/web/freenode/ip.> has quit IRC16:59
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has quit IRC17:00
*** belen <belen!Adium@nat/intel/x-dcjjqapybairoxxn> has joined #yocto17:01
*** mckoan is now known as mckoan|away17:01
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto17:02
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC17:02
*** bluelightning_ is now known as bluelightning17:02
*** SorenHolm <SorenHolm!~quassel@5634f347.rev.stofanet.dk> has joined #yocto17:02
Piziwatedenix : arf... diff patch doesn't work, I got a "patch: **** Only garbage was found in the patch input."17:03
Piziwatedenix : I do it with diff -Nurp ./arch/arm/configs/omap2plus_defconfig.old ./arch/arm/configs/omap2plus_defconfig | sed -n "s/^\+//p" > mypatch.patch17:03
Piziwate(like in the Yocto documentation)17:04
denixwhy the sed?17:04
*** JDuke128 <JDuke128!~textual@> has joined #yocto17:04
PiziwateI saw it on the yocto book... Let's try without !17:04
*** reallife <reallife!~reallife@ool-4b7ff55a.static.optonline.net> has quit IRC17:06
*** reallife <reallife!~reallife@ool-4b7ff55a.static.optonline.net> has joined #yocto17:06
*** sjolley <sjolley!~sjolley@> has joined #yocto17:06
*** jwhitmore_ <jwhitmore_!~jwhitmore@> has joined #yocto17:08
*** cristiana <cristiana!c0c6972c@gateway/web/freenode/ip.> has quit IRC17:09
denixPiziwate: here's one of the raw diff patches in oe-core: http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-multimedia/gstreamer/gst-ffmpeg-0.10.13/lower-rank.diff17:11
*** maxin <maxin!~maxin@c83-251-182-100.bredband.comhem.se> has quit IRC17:12
*** eballetbo <eballetbo!~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net> has quit IRC17:12
*** mihai <mihai!~mihai@> has quit IRC17:12
denixPiziwate: as long as you have proper "--- blah", "+++ blah" and "@@ blah @@" lines to be identified as valid diff file, it should work17:12
Piziwatedenix: do you kown the command they used... ? In my patch I've  --- ./arch/arm/configs/omap2plus_defconfig.old and +++ ./arch/arm/configs/omap2plus_defconfig17:13
Piziwateand do_compile don't like it !17:13
denixit would be do_patch that doesn't like it17:14
Piziwateyes... sorry17:14
denixbut the command is standard - diff -uNr old new17:14
denixso, your command above is good, not sure about sed though17:15
Piziwatearf... : Hunk #1 FAILED at 400. 1 out of 1 hunk FAILED -- rejects in file arch/arm/configs/omap2plus_defconfig17:17
denixat least it recognized it as a valid patch now :)17:18
Piziwatedenix : ;-)17:19
*** hasselmm <hasselmm!~mathias@> has quit IRC17:19
*** zeeblex <zeeblex!~apalalax@> has left #yocto17:22
Piziwatedenix : I think, there is other meta-ti patch who modifies the same file !17:22
denixPiziwate: http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-kernel/linux/linux-ti-staging/0001-Not-for-merge-ARM-config-omap-Disable-SMP-for-AM335x.patch17:23
Piziwatedenix: So the best way to create my patch is to make a patch after the meta-ti patches ?17:24
denixPiziwate: yes, patch dependencies are important. but unless you are modifying the area that is tight next to the other patch, that changes the context, it shouldn't really affect much...17:26
*** pidge <pidge!~eflanagan@c-24-21-207-18.hsd1.or.comcast.net> has quit IRC17:27
*** shoragan <shoragan!~shoragan@debian/developer/shoragan> has quit IRC17:27
*** pocek_ <pocek_!pock@77-254-122-244.adsl.inetia.pl> has quit IRC17:29
Piziwatedenix : ok... I think now I've everything to solve my problem.17:29
*** belen1 <belen1!Adium@nat/intel/x-pajajwmpmemkxxig> has joined #yocto17:31
*** pocek <pocek!pock@77-254-121-84.adsl.inetia.pl> has joined #yocto17:31
*** belen <belen!Adium@nat/intel/x-dcjjqapybairoxxn> has quit IRC17:33
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has joined #yocto17:34
*** diego_r <diego_r!~diego@host65-246-static.10-188-b.business.telecomitalia.it> has quit IRC17:34
*** maxin <maxin!~maxin@c83-251-182-100.bredband.comhem.se> has joined #yocto17:36
*** beaver_545 <beaver_545!~stuart@> has quit IRC17:39
*** SorenHolm <SorenHolm!~quassel@5634f347.rev.stofanet.dk> has quit IRC17:39
*** Piziwate <Piziwate!3e02bf43@gateway/web/freenode/ip.> has quit IRC17:41
*** Squt <Squt!~sputnick@quassel/developer/sput> has joined #yocto17:45
*** Sput <Sput!~sputnick@quassel/developer/sput> has quit IRC17:45
*** e8johan <e8johan!~quassel@> has joined #yocto17:48
*** seebs <seebs!~seebs@home.seebs.net> has quit IRC17:49
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has quit IRC17:50
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has joined #yocto17:50
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has joined #yocto17:51
*** seebs <seebs!~seebs@home.seebs.net> has joined #yocto17:52
*** belen1 <belen1!Adium@nat/intel/x-pajajwmpmemkxxig> has quit IRC17:58
*** belen <belen!~Adium@> has joined #yocto18:00
*** sameo <sameo!~samuel@> has quit IRC18:08
*** maxin <maxin!~maxin@c83-251-182-100.bredband.comhem.se> has quit IRC18:28
*** belen <belen!~Adium@> has quit IRC18:30
*** belen <belen!Adium@nat/intel/x-wfgmnzavfnvtxacw> has joined #yocto18:34
*** e8johan <e8johan!~quassel@> has quit IRC18:41
*** belen <belen!Adium@nat/intel/x-wfgmnzavfnvtxacw> has quit IRC18:44
*** andhe_ <andhe_!~ah@c-958ae155.447-1-64736c11.cust.bredbandsbolaget.se> has quit IRC18:46
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC19:03
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC19:04
*** b1gtuna <b1gtuna!~adam@> has joined #yocto19:05
*** jkridner <jkridner!~jkridner@c-98-250-189-79.hsd1.mi.comcast.net> has joined #yocto19:05
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto19:05
b1gtunagood morning! is there a way to list tasks in order of execution?19:05
-YoctoAutoBuilder- build #70 of nightly-x86-64-lsb is complete: Failure [failed Publishing Artifacts] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86-64-lsb/builds/7019:21
*** joeythesaint <joeythesaint!~jjm@> has quit IRC19:26
*** meph1s <meph1s!~eric@e180072069.adsl.alicedsl.de> has joined #yocto19:27
*** smartin_ <smartin_!~smartin@ivr94-4-82-229-165-48.fbx.proxad.net> has joined #yocto19:28
*** Jin^eLD is now known as Jin|away19:39
-YoctoAutoBuilder- build #71 of nightly-mips is complete: Failure [failed Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-mips/builds/7120:03
kergothb1gtuna: the order of execution isn't linear, its a graph traversal, so a certain amount of variance from run to run will occur20:06
kergoththat said, its possible to produce a linearization. you can use --dry-run, or you can dump the graph with -g and flatten that20:07
kergothif all you want is the order of *recipe* execution, pn-buildlist from -g will give you that20:07
kergothreally depends on your goals20:07
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:5e51:4fff:febb:401d> has joined #yocto20:13
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:5e51:4fff:febb:401d> has quit IRC20:13
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto20:13
*** SwedeMike <SwedeMike!swmike@ipv6.swm.pp.se> has quit IRC20:14
*** SwedeMike <SwedeMike!swmike@ipv6.swm.pp.se> has joined #yocto20:14
*** SwedeMike <SwedeMike!swmike@ipv6.swm.pp.se> has quit IRC20:21
*** SwedeMike <SwedeMike!swmike@ipv6.swm.pp.se> has joined #yocto20:22
*** pocek_ <pocek_!pock@> has joined #yocto20:24
*** pocek <pocek!pock@77-254-121-84.adsl.inetia.pl> has quit IRC20:26
*** SwedeMike <SwedeMike!swmike@ipv6.swm.pp.se> has quit IRC20:30
-YoctoAutoBuilder- build #72 of nightly-ppc is complete: Failure [failed Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-ppc/builds/7220:31
*** pocek <pocek!pock@> has joined #yocto20:32
*** pocek_ <pocek_!pock@> has quit IRC20:35
*** SwedeMike <SwedeMike!swmike@ipv6.swm.pp.se> has joined #yocto20:36
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC20:39
*** sameo <sameo!~samuel@> has joined #yocto20:40
*** SwedeMike <SwedeMike!swmike@ipv6.swm.pp.se> has quit IRC20:41
*** SwedeMike <SwedeMike!swmike@ipv6.swm.pp.se> has joined #yocto20:43
*** ant_home <ant_home!~ant__@host63-12-dynamic.21-79-r.retail.telecomitalia.it> has joined #yocto21:02
*** rhn <rhn!~rhn@unaffiliated/rhn> has quit IRC21:17
*** seezer <seezer!Moscherkob@quassel/developer/seezer> has joined #yocto21:19
b1gtunakergoth: thanks! I think that's all I was looking for. I will try out those commands once my build finishes. Thanks agian.21:21
b1gtunakergoth: (btw I was looking for *recipe* execution order, so what you answer was perfect)21:22
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has quit IRC21:23
kergothcool, sounds like pn-buildlist might be ideal, indeed21:24
kergothi've used that to rebuild everything one recipe at a time to do leaky deps testing and the like21:24
kergothquite useful information21:24
b1gtunakergoth: ya this time I am just trying to do a dirty hack in the kernel. I mod'd the source, but I don't know how to build and package the kernel modules21:36
b1gtunaso I had to find out the order of task execution21:37
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto21:38
*** maxin <maxin!~maxin@c83-251-182-100.bredband.comhem.se> has joined #yocto21:47
*** e8johan <e8johan!~quassel@> has joined #yocto21:50
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has joined #yocto21:51
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has quit IRC21:51
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto21:51
sgw_Gah, just finished writing a nice little patch, then decide to search for it on the upstream list: bug#16929: [PATCH] ui: switch to new-style readline typedef     Date:   Mon,  3 Mar 2014 10:40:08 -030021:52
yoctiBug https://bugzilla.yoctoproject.org/show_bug.cgi?id=16929 was not found.21:52
* sgw_ sez -> timing is!21:52
*** maxin <maxin!~maxin@c83-251-182-100.bredband.comhem.se> has quit IRC22:03
*** SwedeMike <SwedeMike!swmike@ipv6.swm.pp.se> has quit IRC22:04
*** SwedeMike <SwedeMike!swmike@ipv6.swm.pp.se> has joined #yocto22:06
kergoththere we go, did a little python class to use bb.data to parse bblayers.conf, and can use the variable history tracking to obtain line ranges and modify lines and write it back out. now to add args to add/remove/reorder layers to the current bblayers.conf..22:08
*** meph1s <meph1s!~eric@e180072069.adsl.alicedsl.de> has quit IRC22:19
*** mulhern <mulhern!~mulhern@> has joined #yocto22:20
*** agust <agust!~agust@p4FC4663E.dip0.t-ipconnect.de> has quit IRC22:22
*** regorianer <regorianer!~rego@p54BACF3E.dip0.t-ipconnect.de> has quit IRC22:28
*** sjolley <sjolley!~sjolley@> has quit IRC22:29
*** regorianer <regorianer!~rego@p54BAB868.dip0.t-ipconnect.de> has joined #yocto22:31
*** sjolley <sjolley!~sjolley@> has joined #yocto22:31
*** hasselmm <hasselmm!~mathias@p57A9EF32.dip0.t-ipconnect.de> has joined #yocto22:35
*** sjolley <sjolley!~sjolley@> has quit IRC22:37
*** e8johan <e8johan!~quassel@> has quit IRC22:41
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC22:55
*** BSDCat <BSDCat!~unique@calvin.idempot.net> has left #yocto22:56
*** dv_ <dv_!~quassel@chello080108088242.14.11.vie.surfer.at> has quit IRC22:58
*** swex <swex!~swex@> has joined #yocto22:59
*** dv_ <dv_!~quassel@chello080108088242.14.11.vie.surfer.at> has joined #yocto23:00
*** SorenHolm <SorenHolm!~quassel@5634f347.rev.stofanet.dk> has joined #yocto23:00
*** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC23:01
*** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto23:01
*** e8johan <e8johan!~quassel@> has joined #yocto23:04
*** jwhitmore_ <jwhitmore_!~jwhitmore@> has quit IRC23:14
*** sjolley <sjolley!sjolley@nat/intel/x-bfrmxwvfdniduatm> has joined #yocto23:23
*** SorenHolm <SorenHolm!~quassel@5634f347.rev.stofanet.dk> has quit IRC23:37
*** e8johan <e8johan!~quassel@> has quit IRC23:40
*** smartin_ <smartin_!~smartin@ivr94-4-82-229-165-48.fbx.proxad.net> has quit IRC23:41
-YoctoAutoBuilder- build #95 of nightly is complete: Failure [failed BuildImages_1 BuildImages_2 BuildImages_3 BuildImages_4 BuildImages_5 BuildImages_6 BuildImages_7 BuildImages_8 BuildImages_9 BuildImages_10 BuildImages_11 BuildImages_12] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly/builds/9523:48
*** Jefro <Jefro!~jefro@pool-114-87.mcoe.us> has joined #yocto23:50
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has quit IRC23:56
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has joined #yocto23:56

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!