Monday, 2015-04-27

-YoctoAutoBuilder- build #267 of build-appliance is complete: Failure [failed BuildImages BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/26700:05
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC00:19
-YoctoAutoBuilder- build #273 of nightly-non-gpl3 is complete: Failure [failed BuildImages] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-non-gpl3/builds/27300:41
*** nicktick <nicktick!~john@unaffiliated/nicktick> has joined #yocto00:42
*** seebs_ <seebs_!~seebs@home.seebs.net> has quit IRC00:44
*** seebs <seebs!~seebs@home.seebs.net> has joined #yocto00:44
-YoctoAutoBuilder- build #270 of nightly-x32 is complete: Failure [failed BuildImages Running Sanity Tests Running Sanity Tests_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/27000:57
-YoctoAutoBuilder- build #271 of nightly-qa-skeleton is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-skeleton/builds/27101:01
*** paulg_ <paulg_!~paulg@71-19-175-186.dedicated.allstream.net> has quit IRC01:01
*** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC01:05
*** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto01:06
-YoctoAutoBuilder- build #271 of nightly-qa-logrotate is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-logrotate/builds/27101:08
*** dzoe_ <dzoe_!joe@joe.cz> has quit IRC01:15
*** angolini <angolini!uid62003@gateway/web/irccloud.com/x-cyxgesqynejsrvbm> has quit IRC01:19
*** angolini <angolini!uid62003@gateway/web/irccloud.com/x-vnaygreuatdhgnrw> has joined #yocto01:20
*** dzoe <dzoe!joe@joe.cz> has joined #yocto01:22
*** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has joined #yocto01:30
-YoctoAutoBuilder- build #269 of nightly-qa-extras is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Running Sanity Tests_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-extras/builds/26901:35
*** Jackie_huang <Jackie_huang!~quassel@106.120.101.38> has joined #yocto02:07
-YoctoAutoBuilder- build #267 of nightly-ipk is complete: Failure [failed BuildImages Running Sanity Tests Running Sanity Tests_1 Running Sanity Tests_2] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ipk/builds/26702:12
-YoctoAutoBuilder- build #263 of nightly-deb is complete: Failure [failed BuildImages Running Sanity Tests Running Sanity Tests_1 Running Sanity Tests_2] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/26302:41
*** hsychla__ <hsychla__!~hsychla@pd95c9392.dip0.t-ipconnect.de> has joined #yocto03:00
*** hsychla_ <hsychla_!~hsychla@pd95c9392.dip0.t-ipconnect.de> has quit IRC03:05
-YoctoAutoBuilder- build #265 of nightly-rpm is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-rpm/builds/26503:12
*** RalphJr4_ <RalphJr4_!~RalphJr45@host86-184-120-107.range86-184.btcentralplus.com> has joined #yocto03:18
-YoctoAutoBuilder- build #270 of nightly-qa-systemd is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Running Sanity Tests_1 BuildImages_2 Running Sanity Tests_2] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/27003:18
-YoctoAutoBuilder- build #275 of nightly-mips is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Building Toolchain Images_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/27503:19
*** RalphJr4_ <RalphJr4_!~RalphJr45@host86-184-120-107.range86-184.btcentralplus.com> has quit IRC03:20
-YoctoAutoBuilder- build #274 of nightly-x86-64 is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Building Toolchain Images_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-64/builds/27403:25
-YoctoAutoBuilder- build #272 of nightly-arm is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Building Toolchain Images_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/27203:29
*** Crofton <Crofton!~balister@pool-108-44-109-21.ronkva.east.verizon.net> has quit IRC03:39
*** Crofton|work <Crofton|work!~balister@pool-108-44-109-21.ronkva.east.verizon.net> has quit IRC03:39
-YoctoAutoBuilder- build #272 of nightly-x86-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-lsb/builds/27203:50
*** Crofton|work <Crofton|work!~balister@pool-108-44-118-217.ronkva.east.verizon.net> has joined #yocto03:53
*** Crofton <Crofton!~balister@pool-108-44-118-217.ronkva.east.verizon.net> has joined #yocto03:53
*** AndersD <AndersD!~anders@c-89-160-69-55.cust.bredband2.com> has joined #yocto04:09
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto04:10
*** agust <agust!~agust@pD9E2F1A5.dip0.t-ipconnect.de> has joined #yocto04:23
*** e8johan <e8johan!~quassel@83.218.80.242> has joined #yocto04:44
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC04:44
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto04:45
-YoctoAutoBuilder- build #273 of nightly-ppc is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Building Toolchain Images_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds/27304:45
-YoctoAutoBuilder- build #273 of nightly-x86 is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Building Toolchain Images_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86/builds/27304:48
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC04:58
-YoctoAutoBuilder- build #269 of nightly-ppc-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/builds/26904:58
-YoctoAutoBuilder- build #267 of nightly-mips-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/26704:59
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto05:16
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@host78-171-dynamic.14-87-r.retail.telecomitalia.it> has quit IRC05:22
*** sarahsharp <sarahsharp!sarah@nat/intel/x-dncjdfhspqvwccyq> has joined #yocto05:35
*** neur0Fuzzy <neur0Fuzzy!~neur0Fuzz@p239.net182021249.tokai.or.jp> has joined #yocto05:37
*** grma <grma!~gruberm@chello213047201250.tirol.surfer.at> has quit IRC05:40
*** sarahsharp <sarahsharp!sarah@nat/intel/x-dncjdfhspqvwccyq> has quit IRC05:40
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@adsl-ull-177-162.46-151.net24.it> has joined #yocto05:53
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC05:54
*** frsc <frsc!~frsc@80.149.173.68> has joined #yocto06:00
*** todor <todor!todor@nat/intel/x-rgvspybrsetgteow> has quit IRC06:04
*** nbhat_DT <nbhat_DT!~nareshbha@111.93.218.67> has quit IRC06:04
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@adsl-ull-177-162.46-151.net24.it> has quit IRC06:06
*** freanux <freanux!~freanux@unaffiliated/freanux> has quit IRC06:15
*** freanux <freanux!~freanux@unaffiliated/freanux> has joined #yocto06:16
*** frsc <frsc!~frsc@80.149.173.68> has quit IRC06:21
*** volker_123456 <volker_123456!~quassel@host-80-81-19-29.customer.m-online.net> has joined #yocto06:22
*** frsc <frsc!~frsc@80.149.173.68> has joined #yocto06:29
*** SorenHolm <SorenHolm!~quassel@93.165.148.186> has joined #yocto06:32
*** mago|weekend is now known as mago_06:34
*** dshwang <dshwang!~dshwang@192.55.55.41> has joined #yocto06:35
*** volker- <volker-!~volker@unaffiliated/volker-> has quit IRC06:36
-YoctoAutoBuilder- build #275 of nightly-x86-64-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb/builds/27506:39
*** soderstrom <soderstrom!~soderstro@81.216.59.226> has joined #yocto06:42
*** wv <wv!~wv@ip2.televic.com> has joined #yocto06:42
*** volker- <volker-!~volker@unaffiliated/volker-> has joined #yocto06:44
*** hamis <hamis!~irfan@110.93.212.98> has joined #yocto06:46
wvcan somebody have a look to this output?06:47
wvhttp://pastebin.com/JD1Mu19V06:47
wvIt changes gstreamer versions from 0.10 to 1.0 and back06:47
-YoctoAutoBuilder- build #264 of nightly-arm-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm-lsb/builds/26406:47
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-efedlwabhdolrlxe> has joined #yocto06:48
*** melonipoika <melonipoika!~quassel@91-158-69-143.elisa-laajakaista.fi> has joined #yocto06:48
*** nbhat_DT <nbhat_DT!~nareshbha@111.93.218.67> has joined #yocto06:49
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@93.51.28.96> has joined #yocto06:55
*** blitz00__ <blitz00__!stefans@nat/intel/x-txnhdxpptiuuqnjq> has quit IRC06:57
*** jbrianceau_away is now known as jbrianceau07:00
*** Shanx_ <Shanx_!c3dc2512@gateway/web/freenode/ip.195.220.37.18> has joined #yocto07:01
Shanx_Hello07:01
*** wadim_ <wadim_!~egorov@mail.rapiddevelopmentkit.de> has joined #yocto07:06
*** frsc is now known as frsc_07:07
*** frsc_ is now known as frsc07:07
*** egavin <egavin!~egavin@43.Red-2-139-180.staticIP.rima-tde.net> has joined #yocto07:08
*** frsc <frsc!~frsc@80.149.173.68> has quit IRC07:09
*** mckoan|away is now known as mckoan07:09
*** frsc <frsc!~frsc@80.149.173.68> has joined #yocto07:09
*** tf <tf!~tomas@r-finger.com> has joined #yocto07:09
*** tf_ <tf_!~tomas@r-finger.com> has quit IRC07:09
*** frsc <frsc!~frsc@80.149.173.68> has quit IRC07:09
*** frsc <frsc!~frsc@80.149.173.68> has joined #yocto07:10
*** frsc_ <frsc_!~frsc@80.149.173.68> has joined #yocto07:12
*** jku <jku!jku@nat/intel/x-oimdriisfbwldwqc> has joined #yocto07:13
*** frsc <frsc!~frsc@80.149.173.68> has quit IRC07:13
*** frsc_ <frsc_!~frsc@80.149.173.68> has quit IRC07:13
*** frsc <frsc!~frsc@80.149.173.68> has joined #yocto07:13
*** melonipoika <melonipoika!~quassel@91-158-69-143.elisa-laajakaista.fi> has quit IRC07:15
mckoangood morning07:16
*** TobSnyder <TobSnyder!~schneider@ip92341b76.dynamic.kabel-deutschland.de> has joined #yocto07:16
*** DatGizmo <DatGizmo!~mogwai@ip1886d814.dynamic.kabel-deutschland.de> has joined #yocto07:17
*** patrickz <patrickz!~Thunderbi@212.118.209.82> has joined #yocto07:19
*** frsc <frsc!~frsc@80.149.173.68> has quit IRC07:20
*** frsc <frsc!~frsc@80.149.173.68> has joined #yocto07:22
*** patrickz <patrickz!~Thunderbi@212.118.209.82> has quit IRC07:23
-YoctoAutoBuilder- build #49 of eclipse-plugin-luna is complete: Failure [failed Building Eclipse Plugin Publishing Artifacts] Build details are at http://autobuilder.yoctoproject.org/main/builders/eclipse-plugin-luna/builds/4907:24
*** patrickz <patrickz!~Thunderbi@212.118.209.82> has joined #yocto07:25
*** ant_work <ant_work!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has joined #yocto07:27
-YoctoAutoBuilder- build #268 of nightly-intel-gpl is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-intel-gpl/builds/26807:28
-YoctoAutoBuilder- build #278 of poky-tiny is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/poky-tiny/builds/27807:40
*** Jackie_huang <Jackie_huang!~quassel@106.120.101.38> has quit IRC07:45
*** Jackie_huang <Jackie_huang!~quassel@106.120.101.38> has joined #yocto07:45
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:48
*** florian_kc is now known as florian07:54
*** darkspike <darkspike!~darkspike@217.110.68.82> has joined #yocto07:55
-YoctoAutoBuilder- build #270 of nightly-qa-extras is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-extras/builds/27007:56
*** rperier <rperier!~quassel@2001:41d0:52:100::44a> has quit IRC07:57
*** rperier <rperier!~quassel@ubuntu/member/rperier> has joined #yocto07:57
-YoctoAutoBuilder- build #272 of nightly-qa-logrotate is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-logrotate/builds/27208:00
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has joined #yocto08:00
-YoctoAutoBuilder- build #274 of nightly-non-gpl3 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-non-gpl3/builds/27408:08
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto08:10
bluelightningmorning all08:11
*** cristianiorga <cristianiorga!~cristiani@134.134.139.76> has quit IRC08:15
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@93.51.28.96> has quit IRC08:21
*** todor <todor!todor.minc@nat/intel/x-umkzugoqwdudsyaa> has joined #yocto08:22
-YoctoAutoBuilder- build #272 of nightly-qa-pam is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-pam/builds/27208:27
-YoctoAutoBuilder- build #272 of nightly-qa-skeleton is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-skeleton/builds/27208:32
-YoctoAutoBuilder- build #271 of nightly-x32 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/27108:43
*** ddom <ddom!~ddom@p4FFDBBE8.dip0.t-ipconnect.de> has joined #yocto08:44
wvwhen I want to upload data to my device, I get a "/usr/lib/openssh/sftp-server: not found"08:46
wvso sftp-server is not available on it08:46
wvwhich package is providing this?08:46
bluelightningwv: openssh-sftp-server08:47
wvthanks08:48
wvrecompile :)08:48
*** smustafa <smustafa!~mustafa@110.93.212.98> has joined #yocto08:50
*** frsc <frsc!~frsc@80.149.173.68> has quit IRC08:53
*** frsc <frsc!~frsc@80.149.173.68> has joined #yocto08:58
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has joined #yocto09:00
*** belen <belen!Adium@nat/intel/x-oyemprilfkekpdpx> has joined #yocto09:00
-YoctoAutoBuilder- build #268 of build-appliance is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/26809:05
*** frsc <frsc!~frsc@80.149.173.68> has quit IRC09:06
*** frsc <frsc!~frsc@80.149.173.68> has joined #yocto09:06
*** siri_ <siri_!55eb01a5@gateway/web/freenode/ip.85.235.1.165> has left #yocto09:12
*** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has joined #yocto09:14
*** tmpsantos <tmpsantos!~tmpsantos@a88-112-127-122.elisa-laajakaista.fi> has joined #yocto09:14
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto09:20
lpappbluelightning: is it so that it is not really recommended to carry on old kernel versions from earlier Yocto releases to new?09:20
lpappI think the userspace generated by Yocto could break using some old kernel version as well as the buildsystem, etc.09:21
*** nicktick <nicktick!~john@unaffiliated/nicktick> has quit IRC09:21
lpappI am trying to asses whether it is worth for us to update Yocto at this point as I really cannot figure out why the kernel would not boot with Daisy :(09:21
lpappI guess updating Yocto means having guys taking care of the kernel for the BSP.09:22
*** frsc <frsc!~frsc@80.149.173.68> has quit IRC09:22
lpappand that is not a minor project.09:22
lpappand we do not have it currently, sadly, and when things fall apart like this, we cannot do much.09:23
lpappwe could try integrating a precompiled kernel version, but that could still be problematic with new userspace and of course, that kind of defeats Yocto's goal to generate an image from scratch.09:23
*** belen1 <belen1!Adium@nat/intel/x-qlzhmgwxyscdbvxv> has joined #yocto09:24
*** jimBaxter <jimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto09:24
*** belen <belen!Adium@nat/intel/x-oyemprilfkekpdpx> has quit IRC09:24
bluelightninglpapp: is this perhaps a compiler issue? I recall in the 4.8.x timeframe there were kernel boot breaking issues requiring patches to the kernel and gcc09:25
lpappeither compiler or bitbake, yeah09:26
lpappbut we established that bitbake changes have not been done like this, so my old recipe still ought to work.09:26
bluelightningI'm not following...09:27
lpappI pretty much carry my recipe over from the denzil era ...09:27
lpappI fixed some issues about it at the migration to dylan.09:27
lpappbut from dylan to daisy, the recipe does not require any change, right?09:27
lpappwe are disregarding the kernel recipes coming with Yocto09:27
lpappfor the reason that we inherited a huge custom patch set that is never going to be upstreamed because they have so many design flaws09:27
lpappand so, we just carry the whole stuff ahead.09:28
bluelightningsure, and many others do that as well... not ideal, but common09:28
lpappof course, this cannot really be done for a long time.09:28
lpappas things will fall apart at some point in userspace, the latest.09:28
lpappbut as for dylan to daisy, I think it is the toolchain... What else could it be? It is just a guess obviously, but yeah, I do not know how even that could cause it. What changes were you referring to above?09:29
lpappwas it done in the gcc project, linux kernel and/or Yocto?09:29
lpappwith gcc 4.8, that is.09:29
*** belen1 <belen1!Adium@nat/intel/x-qlzhmgwxyscdbvxv> has quit IRC09:29
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@adsl-ull-110-86.44-151.net24.it> has joined #yocto09:31
*** belen <belen!Adium@nat/intel/x-hkskuulyflekcwpk> has joined #yocto09:32
bluelightninglpapp: both gcc and the kernel09:33
bluelightningI don't have the details to hand I'm sorry09:33
bluelightningbut there was at least one issue that meant that the kernel itself needed a patch, maybe that's the thing you're missing09:33
lpappquite possibly09:33
lpapphow to look for it? Did Yocto integrate that change as a patch in files/ or so?09:34
bluelightningI believe we would have; you might also try looking at other BSPs09:34
bluelightningyou would have to pick one with a similarly old kernel though or I'd assume they'd just have automatically got the patch from upstream09:35
bluelightning(maybe you could just look upstream?)09:35
-YoctoAutoBuilder- build #268 of nightly-ipk is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ipk/builds/26809:36
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@adsl-ull-110-86.44-151.net24.it> has quit IRC09:36
lpappare you aware of any public layer with such an old kernel version? Also, I would not know how to look for it in upstream as I do not know where exactly the issue is and so the linux kernel source code is quite huge to check the history for.09:36
lpappI could not nail it down myself to a particular code path.09:37
bluelightningI don't know, I don't even know what kernel version you are in fact using09:37
bluelightningas for upstream, surely a keyword search on "gcc" would at least narrow it down...09:38
ant_workbluelightning: about old kernels version...ehm...can you please flush that old meta-hh stuff?09:40
*** tasslehoff <tasslehoff!~Tasslehof@82.147.55.166> has joined #yocto09:41
bluelightningant_work: sorry been a bit busy, I'll try to get to it this evening09:42
ant_worknp, nobody asked for support for 2.6x yet but we never know :p09:43
AndersDlpapp, how old kernel, and what platform?09:44
*** nighty-_ <nighty-_!~nighty@hokuriku.rural-networks.com> has joined #yocto09:44
lpappAndersD: arm, 3.209:44
lpappI think it was the newest in denzil09:45
lpappwhen we moved to Yocto09:45
lpappbut I could be wrong.09:45
AndersDOk, last winter I migrated a 2.6.35 kernel to dora... One of the gcc changes that caused us trouble was related to unaligned accesses.09:45
lpappas it may give a bit more hint, this is the backtrace with jtag: https://paste.kde.org/pzn4owmmn09:45
lpappthis is where it gets stuck: #0  0xc0016f40 in davinci_psc_config ()09:46
AndersDIn particular, we had to patch both u-boot and the kernel builds for this.09:46
lpappthis is called during the board initialisation.09:46
*** belen <belen!Adium@nat/intel/x-hkskuulyflekcwpk> has quit IRC09:46
AndersDOk, if you get that far, it should be that issue at least.09:46
lpappAndersD: is this backtrace familiar to you?09:47
AndersDUnfortunately not...09:47
lpappbugger09:47
*** belen <belen!Adium@nat/intel/x-hamgfvtkrowszexn> has joined #yocto09:47
lpappor what the right word is in English :)09:47
lpappunfortunate09:48
lpapp:)09:48
lpappAndersD: do you think 3.2 is also affected by that unaligned access issue?09:48
AndersDNo, I think it was fixed earlier, and besides, that should have caused the kernel to get stuck a lot earlier09:50
lpappit gets stuck at Uncompressing Linux... done, booting the kernel. in my case.09:50
*** belen <belen!Adium@nat/intel/x-hamgfvtkrowszexn> has quit IRC09:50
*** belen <belen!Adium@nat/intel/x-qkegyylehjimasqh> has joined #yocto09:52
AndersDHm, well, it could be worth a try... Depending on which gcc version were using successfully earlier. I thinkg we migrated from danny -> dora when we incountered this. I.e. in our case gcc went from 4.5.x to >= 4.6.09:56
*** AndersD <AndersD!~anders@c-89-160-69-55.cust.bredband2.com> has left #yocto09:56
*** AndersD <AndersD!~anders@c-89-160-69-55.cust.bredband2.com> has joined #yocto09:56
lpappdylan to daise, so it is 4.7 to 4.809:56
lpappdaisy*09:56
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@net-93-146-202-56.cust.vodafonedsl.it> has joined #yocto09:57
AndersDThen I'm pretty sure that your builds already takes care of. (Our solution was to add KERNEL_CC_append = " -mno-unaligned-access" to the kernel build)09:57
AndersDBut I think the change that required this was introduced in gcc 4.6...09:58
lpapphmm, thanks, let met check the build log09:58
lpappAndersD: hmm, no, NOTE: make -j 8 uImage CC=arm-foo-linux-gnueabi-gcc  -mno-thumb-interwork -marm LD=arm-foo-linux-gnueabi-ld.bfd10:00
lpappdoes not look like it10:00
lpappunless that option is implicit with these options.10:01
lpappI would not know without reading.10:01
lpappgrep -rn "no-unaligned-access" ../meta* gives no results10:01
lpappso is it implicit then or shall it be explicite? Well, it is worth a try I guess?10:02
AndersDOn more recent kernels it should be fixed. I think it's this commit http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8428e84d42179c2a00f5f6450866e70d802d1d0510:03
AndersDSo, I'd guess that you're 3.2 kernel should be fine.10:04
AndersDThough I haven't double checked it ;)10:04
lpapp3.2 was released in July, 2012, so possibly, yes.10:04
lpapplet me check the git history just in case.10:05
lpappinteresting, git log | grep -rn "Allow kernel unaligned accesses on ARMv6+ processors" returns nothing10:05
AndersDHm, it was at least part of the stable 3.2 series. It could of course have been back-ported...10:06
lpappyes, we sadly use 3.2.110:07
AndersDThen you could always try to either cherry-pick it, or add the KERNEL_CC line from above and rebuild te kernel.10:07
lpappok, we have this line in the code,  #if defined(CONFIG_ALIGNMENT_TRAP) && __LINUX_ARM_ARCH__ < 610:07
lpappso this is fixed in 3.2.110:07
lpappmaybe with a different commit message, but it is.10:07
lpappok, git blame leads me to the same commit10:08
lpappso this is integrated, indeed.10:08
lpappwould have been surprised if not as that would mean a fundamentally broken workflow.10:08
lpappthen I am not sure what else.10:08
AndersDFor the moment, me neither10:09
*** frsc <frsc!~frsc@80.149.173.68> has joined #yocto10:11
lpappAndersD: my idea is to go through the LTS branch10:13
lpappand read the commit messages from 3.2.1 up to 3.2.6810:13
lpapplooking for "stuck", "hang", "gcc", etc, in the commit message10:13
lpappI really do not want to upgrade from 3.2.1. to 3.2.68. Even though they are bugfixes, I do not trust them completely :)10:13
lpappbut backport a fix from that LTS might be a good idea if there is one.10:14
lpappbackporting*10:14
lpappmy other idea is to use a precompiled kernel version for now.10:14
lpappyet another idea is do not touch dylan.10:14
-YoctoAutoBuilder- build #275 of nightly-x86-64 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-64/builds/27510:17
-YoctoAutoBuilder- build #264 of nightly-deb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/26410:18
*** frsc <frsc!~frsc@80.149.173.68> has joined #yocto10:19
*** acooks <acooks!~andrew@ppp121-45-237-216.lns20.per1.internode.on.net> has quit IRC10:22
ant_worklpapp: diving in the commits will take long time. Have you tried to apply your patchset to a more recent LTS linux version?10:24
lpappnot yet, I assume that would be a huge change10:25
*** jbrianceau is now known as jbrianceau_lunch10:25
lpappwell, git log has the -S option for searching, doesn't it?10:25
ant_workif you don't have any idea about the culprit you should properly bisect and yea, that's painful :/10:26
*** rich_b <rich_b!~rich@212.183.140.92> has joined #yocto10:27
lpapphaving said that, a quick ought to be easy by just updating the SRCREV in the recipe?10:27
lpappquick check*10:27
-YoctoAutoBuilder- build #274 of nightly-fsl-ppc-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc-lsb/builds/27410:28
ant_worklpapp: you should have the kernel spit more verbose logs (I'm not expert in that realm but the log you posted doesn't help much)10:32
-YoctoAutoBuilder- build #269 of nightly-fsl-ppc is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc/builds/26910:33
*** acooks <acooks!~andrew@ppp121-45-227-62.lns20.per1.internode.on.net> has joined #yocto10:33
lpappant_work: that is just backtrace, not log.10:33
lpappand I could not get early_printk working for one reason or another.10:34
*** volker_123456 <volker_123456!~quassel@host-80-81-19-29.customer.m-online.net> has quit IRC10:41
*** nicktick <nicktick!~john@119.39.101.117> has joined #yocto10:48
*** nicktick <nicktick!~john@unaffiliated/nicktick> has joined #yocto10:48
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC10:51
-YoctoAutoBuilder- build #266 of nightly-rpm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-rpm/builds/26610:52
*** nicktick <nicktick!~john@unaffiliated/nicktick> has quit IRC10:53
*** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has joined #yocto11:05
*** frsc <frsc!~frsc@80.149.173.68> has quit IRC11:07
*** todor <todor!todor.minc@nat/intel/x-umkzugoqwdudsyaa> has quit IRC11:10
*** hitlin37 <hitlin37!uid16371@gateway/web/irccloud.com/x-axgoftexhpuavbhn> has joined #yocto11:10
lpappant_work: problem is that if I change SRCREV, it takes ages to fetch the Linux kernel from that revision as that is not sstate-cached?11:17
*** jbrianceau_lunch is now known as jbrianceau11:23
*** todor <todor!todor.minc@nat/intel/x-ztdxsihiogoauspc> has joined #yocto11:23
Shanx_is there anyone who knows where are the source of u-boot ?11:28
Shanx_I'd like to modify the u-boot generated when creating an image with Yocto.11:29
ant_worklpapp: you should pull the latest git then go backwards11:30
lpappant_work: unfortunately, our patches do not apply against 3.2.6811:35
lpappShanx_: just fetch it, and use .bbappend with your custom patches if it is a simple case.11:35
Shanx_lpapp: I just want o modify the default boot using a custom command : fatload mmc 2:1 0x12000000 zImage ; fatload mmc 2:1 0x18000000 imx6q-sabresd-ldo.dtb ; setenv bootargs console=ttymxc0,115200 root=/dev/mmcblk3p2 ; bootz 0x12000000 - 0x1800000011:36
Shanx_But I don't know how to patch it and generate for the board.11:37
lpappShanx_: OK, I am doing that myself, too, so I can probably give some guidance.11:39
lpappbut not now ... as I am busy with the kernel stuff.11:39
Shanx_I'd like that. :)11:39
Shanx_Can you tell me when you are free to help ?11:39
lpappso in your own layer, you create recipes-bsp/u-boot11:41
lpappthen we create a patch file in there in a directory called files/11:41
lpappand then we use our custom recipe11:41
lpappthis is not recommended11:41
lpappinstead, I would suggest to do what we do with busybox11:41
lpappwe have a .bbappend file11:42
*** ant_work <ant_work!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has quit IRC11:42
lpappyou could put this into the .bbappend file: FILESEXTRAPATHS_prepend := "${THISDIR}/${P}:"11:42
lpappand then put the patch into a directory next to it, called: u-boot-myversion11:43
lpappreplace myversion with the version that you are trying to patch11:43
Shanx_What is the name of the .bbappend ? u-boot.bbappend ?11:43
lpappand I think this ought to work11:43
lpappthe same name as in meta/recipces-bsp/u-boot, but you use .bbappend instead of .bb11:44
-YoctoAutoBuilder- build #268 of nightly-mips-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/26811:45
lpappif you want to use a custom version not shipped by your picked-up Yocto release, do what we do.11:45
*** ant_work <ant_work!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has joined #yocto11:46
ericbuttershey, there is some machanism that boosts building time right? so lets say i have different machines, each builds an image. all of them need *-native packages. so there is a server holding these *-native packages.. how does that work?11:48
ericbuttersand one other thing: how to disable *-native packages?11:49
lpappare you looking for sstate cache?11:49
*** neur0Fuzzy <neur0Fuzzy!~neur0Fuzz@p239.net182021249.tokai.or.jp> has quit IRC11:51
ericbutterslpapp: yes, thanks.. i think it is SSTATE_MIRRORS11:51
-YoctoAutoBuilder- build #273 of nightly-x86-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-lsb/builds/27311:52
*** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has quit IRC11:53
lpappyep11:53
_4urele_hi all11:56
_4urele_is there a way to get which recipe is used for a package?11:56
_4urele_u-boot for example11:56
*** zaman <zaman!~zaman@192.198.151.43> has quit IRC12:02
*** Cubi_ <Cubi_!~cubi@b2b-94-79-174-114.unitymedia.biz> has joined #yocto12:03
-YoctoAutoBuilder- build #274 of nightly-ppc is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds/27412:03
*** grma <grma!~gruberm@HSI-KBW-46-237-193-133.hsi.kabel-badenwuerttemberg.de> has joined #yocto12:04
*** frsc <frsc!~frsc@80.149.173.68> has joined #yocto12:04
*** hamis_lt_u <hamis_lt_u!~irfan@110.93.212.98> has joined #yocto12:08
*** hamis <hamis!~irfan@110.93.212.98> has quit IRC12:08
*** challinan <challinan!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has joined #yocto12:09
bluelightning_4urele_: the Toaster web UI, or in recent master oe-pkgdata-util12:10
_4urele_bluelightning thanks12:10
bluelightningwell, recent master or 1.8 (fido)12:10
*** boucman <boucman!c32a382c@wesnoth/developer/boucman> has joined #yocto12:18
*** Cedrou <Cedrou!c32a382b@gateway/web/freenode/ip.195.42.56.43> has joined #yocto12:18
Cedrouhi12:19
boucmanHello everybody12:19
boucmanWe are trying to build a family of packages based on the same source, but different defconfig (they are kconfig based)12:19
boucmanThe idea is have multiple packages named bb-<defconfig>.rpm12:20
boucmanwe tried first using BBCLASSEXTENDS and then by having each recipe including a common file12:21
bluelightningboucman: multiple recipes including a common file would be my recommendation12:21
boucmanbluelightning: we tried that, next, but in both cases bitbake complains that some files in the second package built are already provided by the first12:22
boucmanRCONFLICTS doesn'ts seem to fix it either...12:22
boucmanwe tried using virtual/bb to see if it helps, but it doesn't seem to12:23
bluelightningboucman: that won't help, no12:23
boucmanok, doc is not very clear on what a virtual package is, and how to use it, so we tried :P12:23
bluelightningboucman: you can whitelist to avoid that warning; however if anything links to a binary in one of those packages then you'll probably be in trouble12:23
boucmanyeah, two versions of these packages should never be installed on the same machine12:24
bluelightningsure, but that's not what I meant12:24
bluelightningthe warning is about files going into the sysroot12:24
boucmanbut i'd like to understand exactly where the conflict comes from...12:24
boucmanI thought each package had a clean sysroot... am I wrong on that assumption ?12:25
bluelightningno, there is a shared sysroot per machine12:25
bluelightningfiles go into the sysroot so that other recipes can find them when building, and know which packages to depend upon when packaging12:25
boucmanah, ok, I understand better what's going on then12:25
boucmannot sure how to solve my use-case then though... we should be safe since the conflicting libs are only used by the application itself and no external app, but that's not very clean... hmmm12:27
lpappant_work: AndersD: git show v3.2.1..v3.2.68 | grep "4\.8" gives many results :P12:28
*** diego_r <diego_r!~diego@host65-246-static.10-188-b.business.telecomitalia.it> has joined #yocto12:29
*** tsramos <tsramos!~tsramos@134.134.139.70> has joined #yocto12:30
AndersDlpapp, oh, yep. And quite a few of them seems to actually refer to gcc 4.8. You might be able to find something there!12:30
lpapp8 changes mention gcc out of those, yeah12:30
*** nicktick <nicktick!~john@unaffiliated/nicktick> has joined #yocto12:31
-YoctoAutoBuilder- build #273 of nightly-arm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/27312:31
*** nicktick1 <nicktick1!~john@119.39.101.117> has joined #yocto12:32
lpappAndersD: might not be related, but it is an interesting commit, https://paste.kde.org/pn5g4lbhg12:33
*** nicktick <nicktick!~john@unaffiliated/nicktick> has quit IRC12:36
*** anselmolsm <anselmolsm!anselmolsm@nat/intel/x-ewiliysrqiikmkrp> has joined #yocto12:36
lpappok, this is most likely unrelated, but it is funny: https://paste.kde.org/pt74t76am12:37
-YoctoAutoBuilder- build #270 of nightly-ppc-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/builds/27012:39
*** varibull <varibull!~varibull@ta.tainstruments.com> has joined #yocto12:43
lpappcan I specify a different compiler file path for building a package from a recipe?12:46
lpappI would like to try using a bit older gcc (4.7) for building the kernel with daisy. It is just for testing as of now.12:46
*** varibull <varibull!~varibull@ta.tainstruments.com> has quit IRC12:47
*** varibull <varibull!~varibull@ta.tainstruments.com> has joined #yocto12:47
-YoctoAutoBuilder- build #276 of nightly-x86-64-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb/builds/27612:49
-YoctoAutoBuilder- build #265 of nightly-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm-lsb/builds/26512:50
*** varibull <varibull!~varibull@ta.tainstruments.com> has quit IRC12:50
*** varibull <varibull!~varibull@ta.tainstruments.com> has joined #yocto12:50
lpappericbutters: btw, you may also wish to look into icecc to speed up the build.12:51
*** scot <scot!~scot@130.164.62.160> has joined #yocto12:51
ericbutterslpapp: thanks13:01
ericbuttershow to checkout only one file from svn with bitbakeP13:01
*** lamego <lamego!~jalamego@134.134.139.76> has joined #yocto13:02
*** timsche <timsche!~quassel@port-92-192-70-232.dynamic.qsc.de> has joined #yocto13:06
*** hamis_lt_u_ <hamis_lt_u_!~irfan@110.93.212.98> has joined #yocto13:10
*** acidfu_ <acidfu_!~nib@24.37.17.210> has quit IRC13:12
*** acidfu_ <acidfu_!~nib@unaffiliated/acidmen> has joined #yocto13:12
*** hamis_lt_u <hamis_lt_u!~irfan@110.93.212.98> has quit IRC13:13
*** zaman <zaman!zaman@nat/intel/x-tybkfziyrcwcbivw> has joined #yocto13:21
*** tsramos_ <tsramos_!~tsramos@134.134.139.70> has joined #yocto13:26
*** tsramos <tsramos!~tsramos@134.134.139.70> has quit IRC13:28
AndersDericbutters, completely untested, but what happens when you set SRC_URI to point to just that file?13:37
AndersDIt might very well break for all I know13:37
*** Cedrou <Cedrou!c32a382b@gateway/web/freenode/ip.195.42.56.43> has quit IRC13:40
*** vmeson <vmeson!~rmacleod@128.224.252.2> has joined #yocto13:41
*** joshuagl_ is now known as joshuagl13:41
*** gabrbedd <gabrbedd!~beddingfi@li680-65.members.linode.com> has joined #yocto13:42
*** jku <jku!jku@nat/intel/x-oimdriisfbwldwqc> has quit IRC13:42
*** postman| <postman|!d0b90c34@gateway/web/freenode/ip.208.185.12.52> has quit IRC13:42
*** gabrbedd <gabrbedd!~beddingfi@li680-65.members.linode.com> has quit IRC13:42
*** cbzx <cbzx!~cbzx@CPE0015f275ebd6-CM00195edd810c.cpe.net.cable.rogers.com> has joined #yocto13:43
*** slips <slips!~slips@240.150.34.95.customer.cdi.no> has quit IRC13:44
*** slips <slips!~slips@240.150.34.95.customer.cdi.no> has joined #yocto13:47
*** gabrbedd <gabrbedd!~beddingfi@li680-65.members.linode.com> has joined #yocto13:49
*** warthog19 <warthog19!~warthog9@149.20.54.19> has joined #yocto13:52
*** warthog9 <warthog9!~warthog9@149.20.54.19> has quit IRC13:52
*** warthog19 is now known as warthog913:55
*** nicktick1 <nicktick1!~john@119.39.101.117> has quit IRC13:55
lpappbluelightning: I do not understand this paragraph. Can you explain it? http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html#bsp-filelayout-binary14:02
lpapp1) What is the use case?14:03
lpapp2) How do you refer to those "bootable images"?14:03
*** Aethenelle <Aethenelle!~Aethenell@199.15.128.78> has joined #yocto14:04
*** SorenHolm <SorenHolm!~quassel@93.165.148.186> has quit IRC14:08
-YoctoAutoBuilder- build #276 of nightly-mips is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/27614:08
*** SorenHolm <SorenHolm!~quassel@93.165.148.186> has joined #yocto14:08
*** smustafa <smustafa!~mustafa@110.93.212.98> has quit IRC14:09
*** SorenHolm <SorenHolm!~quassel@93.165.148.186> has quit IRC14:13
bluelightninglpapp: I didn't have any input to that document14:14
lpapphmm, whom to ask? It is unclear to me what it is trying to write about.14:17
*** adelcast <adelcast!~adelcast@130.164.62.224> has left #yocto14:17
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC14:18
bluelightningif I understand correctly it might refer to people distributing pre-built binaries (images, bootloaders, etc.) with their BSPs, which used to be something that people talked about doing14:19
lpapphmm14:20
*** benjamirc <benjamirc!~besquive@134.134.139.70> has joined #yocto14:22
*** madisox <madisox!~madison@64-71-1-115.static.wiline.com> has joined #yocto14:23
*** ddalex <ddalex!~ddalex@83.217.123.106> has joined #yocto14:29
*** kalyank <kalyank!~kalyank@c-71-63-130-68.hsd1.or.comcast.net> has joined #yocto14:31
*** frsc <frsc!~frsc@80.149.173.68> has quit IRC14:31
*** zenx <zenx!~quassel@bl17-242-26.dsl.telepac.pt> has joined #yocto14:31
*** leonardosandoval <leonardosandoval!~leonardo@134.134.139.76> has joined #yocto14:31
*** cbzx <cbzx!~cbzx@CPE0015f275ebd6-CM00195edd810c.cpe.net.cable.rogers.com> has quit IRC14:35
-YoctoAutoBuilder- build #274 of nightly-x86 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86/builds/27414:36
*** michael_ <michael_!~michael@thos.me.uk> has joined #yocto14:37
*** jku <jku!~jku@212-149-207-214.bb.dnainternet.fi> has joined #yocto14:41
*** rburton <rburton!~Adium@35.106.2.81.in-addr.arpa> has joined #yocto14:43
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto14:46
*** TobSnyder <TobSnyder!~schneider@ip92341b76.dynamic.kabel-deutschland.de> has quit IRC14:46
*** adelcast1 <adelcast1!~adelcast@130.164.62.82> has joined #yocto14:47
*** sarahsharp <sarahsharp!~sarah@192.55.54.36> has joined #yocto14:52
*** tasslehoff <tasslehoff!~Tasslehof@82.147.55.166> has quit IRC14:57
*** cristianiorga <cristianiorga!~cristiani@134.134.139.76> has joined #yocto15:01
*** dmoseley <dmoseley!~dmoseley@cpe-174-96-222-251.carolina.res.rr.com> has joined #yocto15:01
*** belen2 <belen2!Adium@nat/intel/x-vvgffjkplamokkvc> has joined #yocto15:02
*** bluelightning_ <bluelightning_!~paul@83.217.123.106> has joined #yocto15:02
*** bluelightning_ <bluelightning_!~paul@83.217.123.106> has quit IRC15:02
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto15:02
*** belen <belen!Adium@nat/intel/x-qkegyylehjimasqh> has quit IRC15:03
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC15:03
*** bluelightning_ is now known as bluelightning15:03
*** hamis_lt_u_ <hamis_lt_u_!~irfan@110.93.212.98> has quit IRC15:07
*** belen2 <belen2!Adium@nat/intel/x-vvgffjkplamokkvc> has quit IRC15:19
*** Shanx_ <Shanx_!c3dc2512@gateway/web/freenode/ip.195.220.37.18> has quit IRC15:20
*** belen <belen!Adium@nat/intel/x-qroaaijnsgybyumq> has joined #yocto15:20
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC15:20
ericbuttershi.. using SSTATE_MIRROR will not modify/change the mirror content itself right?!15:24
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto15:25
ericbuttershi.. using SSTATE_MIRROR will not modify/change the mirror content itself right?!15:25
rburtonright, just read it15:26
ericbuttersnice15:28
*** timsche <timsche!~quassel@port-92-192-70-232.dynamic.qsc.de> has quit IRC15:29
*** e8johan <e8johan!~quassel@83.218.80.242> has quit IRC15:29
*** Cubi_ <Cubi_!~cubi@b2b-94-79-174-114.unitymedia.biz> has quit IRC15:29
*** benjamirc <benjamirc!~besquive@134.134.139.70> has quit IRC15:29
*** belen <belen!Adium@nat/intel/x-qroaaijnsgybyumq> has quit IRC15:30
*** zenx <zenx!~quassel@bl17-242-26.dsl.telepac.pt> has quit IRC15:30
*** wadim_ <wadim_!~egorov@mail.rapiddevelopmentkit.de> has quit IRC15:31
*** wv <wv!~wv@ip2.televic.com> has quit IRC15:32
*** grma <grma!~gruberm@HSI-KBW-46-237-193-133.hsi.kabel-badenwuerttemberg.de> has quit IRC15:33
*** belen <belen!Adium@nat/intel/x-hrwvomvxyntqfkrr> has joined #yocto15:33
*** jbrianceau is now known as jbrianceau_away15:37
*** benjamirc <benjamirc!~besquive@134.134.139.76> has joined #yocto15:46
*** ant_work <ant_work!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has quit IRC15:47
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC15:47
*** sjolley <sjolley!~sjolley@134.134.139.74> has quit IRC15:47
*** DS_ <DS_!bb6a2d78@gateway/web/freenode/ip.187.106.45.120> has joined #yocto15:53
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto15:54
DS_Hi! I'm using the dizzy branch in yocto, but need the python 2.7.9 recipe (currently dizzy only has 2.7.3). What is the best approach to updating it? I'd prefer not to change things in the meta layer. I've tried getting the python recipe from the master branch and putting it in another layer (recipe with the same name), but bitbake still selects the 2.7.3 recipe.15:56
*** Aethenelle <Aethenelle!~Aethenell@199.15.128.78> has quit IRC15:56
*** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has quit IRC15:58
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto15:58
kergothexplicitly set PREFERRED_VERSION_python = "2.7.9" or up the priority of your layer (BBFILE_PRIORITY)15:59
kergothalso python-native, obviously — they need to match up for the crosscompilation to work15:59
*** jku <jku!~jku@212-149-207-214.bb.dnainternet.fi> has quit IRC16:00
*** jku <jku!~jku@212-149-207-214.bb.dnainternet.fi> has joined #yocto16:01
DS_kergoth thanks, I will try that16:01
*** belen <belen!Adium@nat/intel/x-hrwvomvxyntqfkrr> has quit IRC16:10
*** limbrik <limbrik!~textual@64.197.89.235> has joined #yocto16:12
lpappbluelightning: one Yocto's sanity checker goes crazy, I cannot get bitbake back to working16:12
lpappnever seen this with dylan, only now with daisy.16:12
*** belen <belen!Adium@nat/intel/x-zltabwvazbfdsemj> has joined #yocto16:14
*** sjolley <sjolley!~sjolley@134.134.139.76> has joined #yocto16:15
lpappbluelightning: https://paste.kde.org/pluw8d8nz16:15
*** mckoan is now known as mckoan|away16:16
*** diego_r <diego_r!~diego@host65-246-static.10-188-b.business.telecomitalia.it> has quit IRC16:17
kergothlpapp: sounds like a bitbake version / metadata version mismatch. bb.which was moved to bb.utils.which quite some time ago16:18
kergothhmm16:18
bluelightningyes, it looks like it16:19
lpappso what is the right fix?16:20
bluelightninglpapp: maybe there is some confusion between multiple versions of bitbake / the metadata?16:20
lpappwhy did it come up all of a sudden?16:20
bluelightningdon't know16:20
kergothrun 'which bitbake', make sure it's the one you think it is?16:20
* kergoth shrugs16:20
lpappI was overriding meta scripts bitbake and .template...16:20
lpappI will run that in an hour16:20
lpappI started a fresh clean build16:20
bluelightningsigh16:23
lpappalways the first reaction after something goes horribly wrong :-)16:28
lpappI rather spend one time on the full rebuild than debugging weird stray file and other issues for hours or days16:29
bluelightningthere's basically no chance of debugging it now though until the next time it comes up16:33
lpappthat is fine, I do not have time debugging it.16:34
lpappbut it comes up quite often to be honest16:34
lpappI think we even discussed it at least twice already16:34
*** benjamirc <benjamirc!~besquive@134.134.139.76> has quit IRC16:35
*** benjamirc <benjamirc!besquive@nat/intel/x-jfmztikhmddyndgj> has joined #yocto16:36
bluelightningright, but I don't have any more information now than when you mentioned it before16:36
bluelightningand if you blew away your build dir you have no means of providing it16:36
bluelightningso there's not much I can do here...16:36
lpappyeah, unfortunately I am also pushed with deadlines and all that16:38
lpappand people cannot guarantee response time in here, so I cannot really wait...16:38
lpappyou may not reply for hours.16:38
lpappand that is fine16:38
*** kalyank <kalyank!~kalyank@c-71-63-130-68.hsd1.or.comcast.net> has quit IRC16:40
*** kalyank <kalyank!~kalyank@c-71-63-130-68.hsd1.or.comcast.net> has joined #yocto16:41
*** abelloni_ <abelloni_!~abelloni@128-79-216-6.hfc.dyn.abo.bbox.fr> has quit IRC16:44
*** abelloni <abelloni!~abelloni@128-79-216-6.hfc.dyn.abo.bbox.fr> has joined #yocto16:45
*** khem` is now known as khem[away]16:47
*** khem[away] is now known as khem`16:48
*** khem` is now known as khem[away]16:49
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@net-93-146-202-56.cust.vodafonedsl.it> has quit IRC16:50
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has quit IRC16:54
*** khem[away] is now known as khem`16:55
*** khem` is now known as khem[away]16:56
*** khem[away] is now known as khem`16:56
*** khem` is now known as khem[away]16:56
*** khem[away] is now known as khem`16:56
*** khem` is now known as khem[away]16:57
*** khem[away] is now known as khem`16:57
*** khem` is now known as khem[away]16:57
*** khem[away] is now known as khem`16:57
*** khem` is now known as khem[away]16:58
*** khem[away] is now known as khem`16:58
*** khem` is now known as khem[away]16:58
*** khem[away] is now known as khem`16:58
*** khem` is now known as khem[away]16:59
*** khem[away] is now known as khem`17:00
*** khem` is now known as khem[away]17:00
*** armpit <armpit!~akuster@2601:c:a700:3ba7:c4df:818e:9ec:b53a> has joined #yocto17:00
*** khem[away] is now known as khem`17:00
*** benjamirc1 <benjamirc1!~besquive@134.134.139.76> has joined #yocto17:01
*** khem` is now known as khem[away]17:01
*** khem[away] is now known as khem`17:01
*** benjamirc <benjamirc!besquive@nat/intel/x-jfmztikhmddyndgj> has quit IRC17:03
*** paulg_ <paulg_!~paulg@72.1.195.9> has joined #yocto17:05
*** zenx <zenx!~quassel@bl17-242-26.dsl.telepac.pt> has joined #yocto17:06
*** zenx is now known as Guest4868617:06
*** ddom <ddom!~ddom@p4FFDBBE8.dip0.t-ipconnect.de> has quit IRC17:08
*** Aethenelle <Aethenelle!~Aethenell@166.170.40.121> has joined #yocto17:09
*** Aethenelle <Aethenelle!~Aethenell@166.170.40.121> has quit IRC17:16
*** pumpernickel <pumpernickel!~pumpernic@41333086.cst.lightpath.net> has joined #yocto17:16
* darknighte thinks that khem` is doing the IRC hokey-pokey17:17
khem`hrmm17:18
khem`smart IRC clients17:18
khem`they know when I am away and when not17:18
*** btooth <btooth!~daniel@HSI-KBW-134-3-88-164.hsi14.kabel-badenwuerttemberg.de> has joined #yocto17:18
* armpit IRC big brother17:19
*** egavin <egavin!~egavin@43.Red-2-139-180.staticIP.rima-tde.net> has quit IRC17:19
*** btooth <btooth!~daniel@HSI-KBW-134-3-88-164.hsi14.kabel-badenwuerttemberg.de> has quit IRC17:20
*** tsramos <tsramos!~tsramos@134.134.139.74> has joined #yocto17:26
*** tsramos <tsramos!~tsramos@134.134.139.74> has quit IRC17:27
*** tsramos <tsramos!~tsramos@192.55.54.40> has joined #yocto17:27
*** tsramos_ <tsramos_!~tsramos@134.134.139.70> has quit IRC17:29
*** ddalex <ddalex!~ddalex@83.217.123.106> has quit IRC17:33
*** benjamirc1 <benjamirc1!~besquive@134.134.139.76> has quit IRC17:38
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-efedlwabhdolrlxe> has quit IRC17:38
*** varibull <varibull!~varibull@ta.tainstruments.com> has joined #yocto17:43
*** varibull <varibull!~varibull@ta.tainstruments.com> has joined #yocto17:44
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@bo-18-154-218.service.infuturo.it> has joined #yocto17:50
*** kw01f <kw01f!~kw01f@x4d047369.dyn.telefonica.de> has joined #yocto18:01
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@bo-18-154-218.service.infuturo.it> has quit IRC18:02
*** varibull <varibull!~varibull@ta.tainstruments.com> has quit IRC18:03
*** varibull <varibull!~varibull@ta.tainstruments.com> has joined #yocto18:03
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@bo-18-154-218.service.infuturo.it> has joined #yocto18:03
*** AndersD <AndersD!~anders@c-89-160-69-55.cust.bredband2.com> has quit IRC18:11
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC18:14
*** jimBaxter <jimBaxter!~jbaxter@jimbax.plus.com> has quit IRC18:14
*** belen <belen!Adium@nat/intel/x-zltabwvazbfdsemj> has quit IRC18:18
*** adelcast1 <adelcast1!~adelcast@130.164.62.82> has left #yocto18:22
*** adelcast <adelcast!~adelcast@130.164.62.82> has joined #yocto18:29
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@bo-18-154-218.service.infuturo.it> has quit IRC18:42
*** ntl <ntl!~ntl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has quit IRC18:44
khem`hmm so I think I need to shed the debug info for getting sstate to get bulkier for chromium18:44
khem`life is all about compromises18:44
khem`10 years ago it was in Mbs now its in Gbs18:45
khem`same situation18:45
khem`units have changed18:45
khem`unstripped chomium binary is 2.1G18:45
khem`:)18:45
khem`thats where sstate kills it18:46
*** lamego <lamego!~jalamego@134.134.139.76> has quit IRC18:46
khem`if it was package feeds then only the needed will be penalized18:46
khem`but here everyone is18:46
*** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has quit IRC18:48
*** hitlin37 <hitlin37!uid16371@gateway/web/irccloud.com/x-axgoftexhpuavbhn> has quit IRC18:52
*** DS_ <DS_!bb6a2d78@gateway/web/freenode/ip.187.106.45.120> has quit IRC18:55
*** denix <denix!~denix@pool-108-28-31-169.washdc.fios.verizon.net> has joined #yocto19:05
*** varibull <varibull!~varibull@ta.tainstruments.com> has quit IRC19:06
*** varibull <varibull!~varibull@ta.tainstruments.com> has joined #yocto19:07
*** lamego <lamego!~jalamego@134.134.139.76> has joined #yocto19:07
*** benjamirc <benjamirc!besquive@nat/intel/x-cigeuakhmihvkbmu> has joined #yocto19:08
*** joshuagl <joshuagl!~joshuagl@81.156.165.173> has quit IRC19:13
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC19:13
*** joshuagl <joshuagl!~joshuagl@host109-157-99-174.range109-157.btcentralplus.com> has joined #yocto19:14
*** lamego1 <lamego1!~jalamego@134.134.139.76> has joined #yocto19:20
*** lamego <lamego!~jalamego@134.134.139.76> has quit IRC19:20
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC19:22
*** lamego1 <lamego1!~jalamego@134.134.139.76> has quit IRC19:22
*** lamego <lamego!~jalamego@134.134.139.76> has joined #yocto19:22
falstaffHi, my package ${PN} contain a library (/usr/lib/foo.so), packagesplit creates a ${PN}-dev. This leads to a QA Issue "dev-deps"... How can I avoid that OE splits the package?19:23
*** acooks <acooks!~andrew@ppp121-45-227-62.lns20.per1.internode.on.net> has quit IRC19:25
neverpanicis /usr/lib/foo.so a symlink?19:30
*** acooks <acooks!~andrew@ppp121-45-232-63.lns20.per1.internode.on.net> has joined #yocto19:37
*** tmpsantos <tmpsantos!~tmpsantos@a88-112-127-122.elisa-laajakaista.fi> has quit IRC19:44
-YoctoAutoBuilder- build #50 of eclipse-plugin-luna is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/eclipse-plugin-luna/builds/5019:47
*** ddalex1 <ddalex1!~ddalex@154.58.102.3> has joined #yocto19:47
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto19:51
*** leonardosandoval <leonardosandoval!~leonardo@134.134.139.76> has left #yocto19:58
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto20:04
*** vmeson <vmeson!~rmacleod@128.224.252.2> has quit IRC20:15
JYDawghullo, question I need to create a new package during build which should not be installed20:16
*** khem` is now known as khem[away]20:25
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC20:38
*** khem[away] is now known as khem`20:43
-YoctoAutoBuilder- build #269 of build-appliance is complete: Failure [failed BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/26920:45
kergothJYDawg: so create a recipe and build it. no package gets installed unless it's added to IMAGE_INSTALL in the recipe you're building, or is a dependency of one of those20:48
kergothhmm, the bitbake UI keeps exiting on me in the middle of a world build after a task fails even when using -k20:48
kergothkeep having to pkill the server process after that20:48
*** varibull <varibull!~varibull@ta.tainstruments.com> has quit IRC20:51
*** varibull <varibull!~varibull@ta.tainstruments.com> has joined #yocto20:51
*** jku <jku!~jku@212-149-207-214.bb.dnainternet.fi> has quit IRC20:53
*** trip0 <trip0!tripzero@nat/intel/x-gxensehahkoxabge> has joined #yocto20:54
*** lamego <lamego!~jalamego@134.134.139.76> has quit IRC20:57
kergothand it spontaneously exited again21:00
kergothsigh21:00
*** lamego <lamego!~jalamego@134.134.139.76> has joined #yocto21:02
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto21:02
*** jku <jku!~jku@212-149-207-214.bb.dnainternet.fi> has joined #yocto21:02
sri_hello21:03
*** lamego <lamego!~jalamego@134.134.139.76> has quit IRC21:03
*** ant_home <ant_home!~ant__@host22-222-dynamic.7-79-r.retail.telecomitalia.it> has joined #yocto21:03
*** lamego <lamego!~jalamego@134.134.139.76> has joined #yocto21:04
JYDawgkergoth: thanks, makes sense21:06
kergoths/added to IMAGE_INSTALL in the recipe/added to IMAGE_INSTALL in the image recipe/21:07
kergothnp21:07
JYDawgis there a way to detect package upgrades? I've got a "pkg_postinst_${PN}" script that should only run at first boot, not image creation or package upgrades21:10
kergothimage creation is handled via $D. if that env var is set, then you're running at image creation time, and that's the full path to the rootfs21:12
kergothi *think* there's a postinst argument passed in an upgrade case, but not sure offhand what it is21:12
*** kw01f <kw01f!~kw01f@x4d047369.dyn.telefonica.de> has quit IRC21:12
JYDawgI'm thinking a simple token file, but rather use something like rpms upgrade / post scriptlets21:13
kergothi'd add echo "$@" to it, and test an upgrade21:13
kergothalso not sure if that behavior is identical between package managers..21:13
JYDawgusing rpm21:13
*** jku <jku!~jku@212-149-207-214.bb.dnainternet.fi> has quit IRC21:13
kergotheither test what arguments are passed in what context, or read up on the package managers to see what they do21:15
kergothor check the yocto docs to see if it's mentioned there, not sure21:15
* kergoth doesn't know offhand21:15
JYDawgwas just thinking, can also seperate the bootstrapping targets to a specific package.21:17
JYDawgworx!21:21
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC21:25
*** rich_b <rich_b!~rich@212.183.140.92> has quit IRC21:28
*** tsramos_ <tsramos_!tsramos@nat/intel/x-ztlgsxutgpqsscwc> has joined #yocto21:46
*** sjolley <sjolley!~sjolley@134.134.139.76> has quit IRC21:47
*** tsramos <tsramos!~tsramos@192.55.54.40> has quit IRC21:49
*** tsramos_ <tsramos_!tsramos@nat/intel/x-ztlgsxutgpqsscwc> has quit IRC21:50
*** sjolley <sjolley!~sjolley@134.134.139.76> has joined #yocto21:51
*** lamego <lamego!~jalamego@134.134.139.76> has quit IRC21:52
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-rqgwlxtplthcfuwc> has joined #yocto21:56
*** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC22:01
*** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto22:01
*** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has joined #yocto22:07
*** sjolley <sjolley!~sjolley@134.134.139.76> has quit IRC22:07
*** sjolley <sjolley!~sjolley@134.134.137.75> has joined #yocto22:17
*** sjolley <sjolley!~sjolley@134.134.137.75> has quit IRC22:19
*** thaytan <thaytan!~thaytan@199.7.70.115.static.exetel.com.au> has quit IRC22:25
*** rburton <rburton!~Adium@35.106.2.81.in-addr.arpa> has quit IRC22:27
*** nicktick <nicktick!~john@unaffiliated/nicktick> has joined #yocto22:28
*** anselmolsm <anselmolsm!anselmolsm@nat/intel/x-ewiliysrqiikmkrp> has quit IRC22:29
*** thaytan <thaytan!~thaytan@199.7.70.115.static.exetel.com.au> has joined #yocto22:32
*** khem` is now known as khem[away]22:35
*** agust <agust!~agust@pD9E2F1A5.dip0.t-ipconnect.de> has quit IRC22:38
*** boucman <boucman!c32a382c@wesnoth/developer/boucman> has quit IRC22:40
*** benjamirc <benjamirc!besquive@nat/intel/x-cigeuakhmihvkbmu> has quit IRC22:40
*** sjolley <sjolley!~sjolley@134.134.139.76> has joined #yocto22:51
*** nighty-_ <nighty-_!~nighty@hokuriku.rural-networks.com> has quit IRC22:58
*** nicktick <nicktick!~john@unaffiliated/nicktick> has quit IRC23:10
*** paulg_ <paulg_!~paulg@72.1.195.9> has quit IRC23:11
*** khem[away] is now known as khem`23:15
*** kalyank <kalyank!~kalyank@c-71-63-130-68.hsd1.or.comcast.net> has quit IRC23:18
*** pumpernickel <pumpernickel!~pumpernic@41333086.cst.lightpath.net> has quit IRC23:20
*** sjolley <sjolley!~sjolley@134.134.139.76> has quit IRC23:24
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC23:29
*** kalyank <kalyank!~kalyank@c-71-63-130-68.hsd1.or.comcast.net> has joined #yocto23:31
*** ant_home <ant_home!~ant__@host22-222-dynamic.7-79-r.retail.telecomitalia.it> has quit IRC23:50
*** agherzan <agherzan!573f4d0e@gateway/web/freenode/ip.87.63.77.14> has joined #yocto23:54
agherzanhello guys23:54
agherzanI have a package with uses autotools23:54
agherzanit used to work just fine with dizzy, but now, after switching to fido i get this error:23:55
agherzanerror: cannot find install-sh,23:55
agherzan configure: error: cannot find install-sh, install.sh, or shtool in23:55
kergothtry inheriting autotools-brokensep instead of autotools23:55
agherzanAnd this is because configure was generated wrongly23:55
kergothit's possible that it's a non-automake recipe that can't handle the build and source directories being separate23:55
kergoths/recipe/project/23:55
agherzanfor ac_dir in "$srcdir" "$srcdir/.." "$srcdir/../.."; do23:55
agherzanit used to work as it is with duzzy23:56
agherzandizzy*23:56
kergothin fido, we default to using a separate build/object directory from the source23:56
kergoththis has changed from previous releases23:56
agherzani tried with brokensep and din't see any improvements23:57
-YoctoAutoBuilder- build #271 of nightly-ppc-lsb is complete: Failure [failed BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/builds/27123:57
*** pdp7 <pdp7!~pdp7@asciipr0n.com> has joined #yocto23:57
agherzanthe problem is the way configure was generated bu autoconf23:58
kergothcould also be they expect / are compatible with only certain versions of autoconf/automake,s o a version bump of one of those ccould have been problematic23:58
agherzanby*23:58
*** pdp7 is now known as Guest2499723:58
kergothyes, i know how autoconf works23:58
*** silviof <silviof!~silviof@unaffiliated/silviof> has quit IRC23:58
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-rqgwlxtplthcfuwc> has quit IRC23:58
agherzankergoth: that's what i suspect too23:59

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