Monday, 2015-11-16

sayguhI'm going to be afk, I'll check back in a while if there are any suggestions, thanks for any support :-)00:18
*** IvanSB <IvanSB!~IvanSB@host81-144-dynamic.8-87-r.retail.telecomitalia.it> has quit IRC00:26
*** robher <robher!sid20343@gateway/web/irccloud.com/x-atqoqvfubempnhiw> has quit IRC01:32
*** rdenis <rdenis!sid16562@gateway/web/irccloud.com/x-dgryiaieiglmshol> has quit IRC01:32
*** khem` is now known as onoffon01:33
*** radhus <radhus!~radhus@sevh.radhuset.org> has quit IRC01:33
*** onoffon <onoffon!~khem@unaffiliated/khem> has quit IRC01:33
*** sandsmark <sandsmark!~sandsmark@kde/sandsmark> has quit IRC01:33
*** Cardoe <Cardoe!~Cardoe@gentoo/developer/Cardoe> has quit IRC01:34
*** halfhalo <halfhalo!halfhalo@nasadmin/webteam/halfhalo> has quit IRC01:34
*** jcreekmore <jcreekmore!~jcreekmor@2601:7c0:c300:dad6:21d:92ff:fef3:50e> has quit IRC01:34
*** Guest41169 <Guest41169!ka6sox@nasadmin/ka6sox> has quit IRC01:34
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto01:34
*** captainigloo <captainigloo!~captainig@2001:41d0:8:114b::1> has quit IRC01:35
*** sandsmark <sandsmark!~sandsmark@kde/sandsmark> has joined #yocto01:37
*** rdenis <rdenis!sid16562@gateway/web/irccloud.com/x-qivundjehlgyyiyh> has joined #yocto01:37
*** Cardoe <Cardoe!~Cardoe@gentoo/developer/Cardoe> has joined #yocto01:38
*** radhus <radhus!~radhus@sevh.radhuset.org> has joined #yocto01:38
*** jcreekmore <jcreekmore!~jcreekmor@2601:7c0:c300:dad6:21d:92ff:fef3:50e> has joined #yocto01:38
*** captainigloo <captainigloo!~captainig@2001:41d0:8:114b::1> has joined #yocto01:38
*** robher <robher!sid20343@gateway/web/irccloud.com/x-yljmxrnglyiagqdv> has joined #yocto01:40
*** halfhalo <halfhalo!halfhalo@nasadmin/webteam/halfhalo> has joined #yocto01:41
*** khem` is now known as onoffon01:42
*** Guest16537 <Guest16537!ka6sox@cryptkcoding.com> has joined #yocto01:43
*** onoffon is now known as khem`01:45
*** nighty-_ <nighty-_!~nighty@s1015222.xgsspn.imtp.tachikawa.spmode.ne.jp> has quit IRC01:47
*** captainigloo <captainigloo!~captainig@2001:41d0:8:114b::1> has quit IRC02:05
*** captainigloo <captainigloo!~captainig@2001:41d0:8:114b::1> has joined #yocto02:09
-YoctoAutoBuilder- build #188 of ptest-x86 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/ptest-x86/builds/18802:42
*** sayguh <sayguh!ad4f3520@gateway/web/freenode/ip.173.79.53.32> has quit IRC02:47
*** khem` is now known as onoffon02:54
*** onoffon is now known as khem`02:54
*** sameo <sameo!~samuel@134.134.139.72> has quit IRC03:05
*** khem` is now known as onoffon03:39
*** onoffon is now known as khem`03:41
*** bananadev <bananadev!~bananadev@117.6.99.240> has joined #yocto03:53
*** halstead_ is now known as halstead04:23
*** halstead <halstead!~halstead@drupal.org/user/301087/view> has joined #yocto04:24
*** edtyler <edtyler!~edt@ip68-4-156-81.oc.oc.cox.net> has joined #yocto04:40
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC04:55
*** khem` is now known as onoffon04:57
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto04:57
*** onoffon <onoffon!~khem@unaffiliated/khem> has quit IRC05:15
-YoctoAutoBuilder- build #530 of nightly-x32 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/53005:16
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC05:25
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto05:26
*** hamis_lt_u <hamis_lt_u!~irfan@110.93.212.98> has joined #yocto05:52
-YoctoAutoBuilder- build #185 of nightly-arm64 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm64/builds/18506:31
abelalmorning all06:43
-YoctoAutoBuilder- build #543 of nightly-ppc is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds/54306:47
*** ][Sno][ <][Sno][!~sno@p578b540c.dip0.t-ipconnect.de> has quit IRC06:47
*** pohly <pohly!~pohly@p5DE8F322.dip0.t-ipconnect.de> has joined #yocto06:49
*** yann|work <yann|work!~yann@nan92-1-81-57-214-146.fbx.proxad.net> has joined #yocto06:53
*** marek_ <marek_!~marek@81.89.61.168.host.vnet.sk> has joined #yocto06:57
*** yann|work <yann|work!~yann@nan92-1-81-57-214-146.fbx.proxad.net> has quit IRC06:58
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto06:59
*** bfederau_ <bfederau_!~quassel@service.basyskom.com> has joined #yocto07:10
*** rperier_ <rperier_!~quassel@2001:41d0:52:100::44a> has joined #yocto07:10
*** onoffon <onoffon!~khem@unaffiliated/khem> has joined #yocto07:11
*** abelloni_ <abelloni_!~abelloni@88.191.26.124> has joined #yocto07:11
*** nrossi_ <nrossi_!~nrossi@43.252.111.142> has joined #yocto07:11
*** tobiash <tobiash!~quassel@mail.bmw-carit.de> has joined #yocto07:12
*** rdenis_ <rdenis_!sid16562@gateway/web/irccloud.com/x-lokfdrtnejepjfaj> has joined #yocto07:13
*** thaytan_ <thaytan_!~thaytan@199.7.70.115.static.exetel.com.au> has joined #yocto07:14
*** Rootert_ <Rootert_!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto07:14
*** RagBal_ <RagBal_!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto07:15
*** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC07:15
*** tobiash_ <tobiash_!~quassel@mail.bmw-carit.de> has quit IRC07:15
*** nrossi <nrossi!~nrossi@43.252.111.142> has quit IRC07:15
*** rperier <rperier!~quassel@2001:41d0:52:100::44a> has quit IRC07:15
*** abelloni <abelloni!~abelloni@88.191.26.124> has quit IRC07:15
*** rdenis <rdenis!sid16562@gateway/web/irccloud.com/x-qivundjehlgyyiyh> has quit IRC07:15
*** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC07:15
*** khem <khem!~khem@unaffiliated/khem> has quit IRC07:15
*** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC07:15
*** thaytan <thaytan!~thaytan@199.7.70.115.static.exetel.com.au> has quit IRC07:15
*** Rootert_ is now known as Rootert07:15
*** rdenis_ is now known as rdenis07:17
*** grma <grma!~gruberm@chello213047201250.tirol.surfer.at> has quit IRC07:24
*** frsc <frsc!~frsc@80.149.173.68> has joined #yocto07:26
*** egavinc <egavinc!~egavinc@4.Red-83-34-185.dynamicIP.rima-tde.net> has joined #yocto07:32
*** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has joined #yocto07:37
*** belen <belen!Adium@nat/intel/x-mtpsvzkfutrdgdds> has joined #yocto07:45
-YoctoAutoBuilder- build #194 of nightly-deb-non-deb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-deb-non-deb/builds/19407:46
*** sgw_ <sgw_!~sgw_@134.134.139.78> has quit IRC07:47
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-bydodmtqvuanqpgh> has joined #yocto07:51
*** jbrianceau_away is now known as jbrianceau07:51
*** csanchezdll <csanchezdll!~user@galileo.kdpof.com> has joined #yocto07:53
*** rperier_ is now known as rperier07:57
*** rperier <rperier!~quassel@ubuntu/member/rperier> has joined #yocto07:57
*** townxelliot <townxelliot!~ell@176.251.36.115> has joined #yocto07:57
*** TuTizz <TuTizz!~TuTizz@46.18.96.158> has joined #yocto08:03
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has joined #yocto08:03
*** Biliogadafr <Biliogadafr!~User@nat2-minsk-pool-46-53-195-225.telecom.by> has joined #yocto08:05
*** townxelliot <townxelliot!~ell@176.251.36.115> has quit IRC08:05
*** RagBal_ is now known as RagBal08:10
*** maxin <maxin!~maxin@2001:998:22:0:3155:467f:b986:199b> has joined #yocto08:13
*** smartin__ is now known as smartin_08:14
*** aragua <aragua!~flahouder@212.194.216.83> has joined #yocto08:14
*** townxelliot <townxelliot!~ell@94.13.69.111> has joined #yocto08:19
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto08:20
*** fl0v0 <fl0v0!~fvo@p5DDC639A.dip0.t-ipconnect.de> has joined #yocto08:26
*** aime-Pierre <aime-Pierre!~Thunderbi@bob75-2-81-56-46-209.fbx.proxad.net> has joined #yocto08:35
*** sameo <sameo!samuel@nat/intel/x-nijypebmeixsfotq> has joined #yocto08:37
*** LocutusOfBorg1 <LocutusOfBorg1!~LocutusOf@93.51.30.27> has joined #yocto08:39
*** roccof <roccof!~roccof@93-51-177-218.ip268.fastwebnet.it> has joined #yocto08:45
-YoctoAutoBuilder- build #256 of nightly-world-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-world-lsb/builds/25608:47
*** Saur1 <Saur1!pkj@nat/axis/x-gvojeqyvkuxaduyj> has quit IRC08:48
*** Saur <Saur!pkj@nat/axis/x-xgpefesmlmehzwuu> has joined #yocto08:48
*** ftonello <ftonello!~quassel@81.145.202.106> has joined #yocto08:51
*** yann|work <yann|work!~yann@LFbn-1-1026-146.w86-247.abo.wanadoo.fr> has joined #yocto08:54
*** tasslehoff <tasslehoff!~Tasslehof@77.40.182.98> has joined #yocto08:55
*** psnsilva <psnsilva!~psnsilva@193-126-29-154.net.novis.pt> has joined #yocto08:56
*** nighty-_ <nighty-_!~nighty@ag136174.dynamic.ppp.asahi-net.or.jp> has joined #yocto08:58
*** sameo <sameo!samuel@nat/intel/x-nijypebmeixsfotq> has quit IRC08:59
*** sameo <sameo!samuel@nat/intel/x-tribcnrurlythrou> has joined #yocto08:59
*** ][Sno][ <][Sno][!~sno@rademacherexchange.de> has joined #yocto09:01
*** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has quit IRC09:01
*** sujith_h <sujith_h!~toaster@139.181.35.34> has joined #yocto09:03
*** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has joined #yocto09:03
*** jonathanmaw <jonathanmaw!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has joined #yocto09:05
*** nrossi_ is now known as nrossi09:06
*** roxell_ <roxell_!~roxell@c-aa3470d5.07-21-73746f28.cust.bredbandsbolaget.se> has quit IRC09:11
*** roxell <roxell!~roxell@linaro/roxell> has joined #yocto09:11
*** Guest83_ <Guest83_!~textual@83.233.227.60> has joined #yocto09:14
*** Guest83_ is now known as ionte09:14
*** t0mmy_ <t0mmy_!~tprrt@217.114.201.133> has joined #yocto09:16
*** dreyna4529 <dreyna4529!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto09:22
*** jonathanmaw_ <jonathanmaw_!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has joined #yocto09:25
*** DatGizmo_ <DatGizmo_!~mogwai@ipbcc242a9.dynamic.kabel-deutschland.de> has quit IRC09:25
*** jonathanmaw <jonathanmaw!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has quit IRC09:29
-YoctoAutoBuilder- build #546 of nightly-arm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/54609:31
*** dreyna4529 <dreyna4529!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC09:39
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-mfksdaopewaccogt> has joined #yocto09:45
*** frsc <frsc!~frsc@80.149.173.68> has quit IRC09:46
*** tasslehoff <tasslehoff!~Tasslehof@77.40.182.98> has quit IRC09:46
*** diego_r <diego_r!~diego@host65-246-static.10-188-b.business.telecomitalia.it> has joined #yocto09:55
*** dolphin` is now known as dolphin10:00
*** dolphin <dolphin!dolphin@unaffiliated/dolphin> has joined #yocto10:01
*** hamis_lt_u <hamis_lt_u!~irfan@110.93.212.98> has quit IRC10:01
*** frsc <frsc!~frsc@80.149.173.68> has joined #yocto10:02
*** Guest83585 <Guest83585!~vivek@78.32.176.249> has joined #yocto10:04
*** hamis_lt_u <hamis_lt_u!~irfan@110.93.212.98> has joined #yocto10:04
*** hamis_lt_u <hamis_lt_u!~irfan@110.93.212.98> has quit IRC10:05
*** hamis_lt_u <hamis_lt_u!~irfan@110.93.212.98> has joined #yocto10:06
*** rburton <rburton!~Adium@35.106.2.81.in-addr.arpa> has joined #yocto10:07
*** tasslehoff <tasslehoff!~Tasslehof@77.40.182.98> has joined #yocto10:11
*** frsc <frsc!~frsc@80.149.173.68> has quit IRC10:11
*** DatGizmo <DatGizmo!~mogwai@ipbcc242a9.dynamic.kabel-deutschland.de> has joined #yocto10:11
*** hamis_lt_u <hamis_lt_u!~irfan@110.93.212.98> has quit IRC10:12
*** jonathanmaw_ <jonathanmaw_!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has quit IRC10:12
*** frsc <frsc!~frsc@80.149.173.68> has joined #yocto10:13
*** frsc <frsc!~frsc@80.149.173.68> has quit IRC10:14
*** rrva <rrva!unknown@y.mima.x.se> has quit IRC10:16
*** matteo <matteo!~matteo@openwrt/developer/matteo> has joined #yocto10:17
*** c10ud <c10ud!~c10ud@emesene/dictator/c10ud> has joined #yocto10:23
*** jonathanmaw_ <jonathanmaw_!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has joined #yocto10:25
-YoctoAutoBuilder- build #186 of nightly-mips64 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips64/builds/18610:42
*** _jmleo <_jmleo!~jmleo@105-197-190-109.dsl.ovh.fr> has joined #yocto10:49
*** frsc <frsc!~frsc@80.149.173.68> has joined #yocto10:50
*** jmleo <jmleo!~jmleo@105-197-190-109.dsl.ovh.fr> has quit IRC10:52
*** thaytan_ is now known as thaytan10:52
*** jku <jku!jku@nat/intel/x-wsmdkxvakbhgdoqe> has joined #yocto10:55
*** jku <jku!jku@nat/intel/x-wsmdkxvakbhgdoqe> has quit IRC10:57
*** jku <jku!jku@nat/intel/x-zvdlinpvzquhtzpq> has joined #yocto10:57
*** hamis_lt_u <hamis_lt_u!~irfan@110.93.212.98> has joined #yocto11:00
*** _4urele_ <_4urele_!~aurele@srvmail.castel.fr> has quit IRC11:02
*** hamis_lt_u <hamis_lt_u!~irfan@110.93.212.98> has quit IRC11:05
*** hamis_lt_u <hamis_lt_u!~irfan@110.93.212.98> has joined #yocto11:10
uenihallo, i have a trouble with populating a sdk. the command i use is "bitbake <myimage> -C populate_sdk" the error i receive is from binutils "configure.ac:34: error: Please use exactly Autoconf 2.64 instead of 2.69.". wich is the right way to solve the problem? just write a patch for configure.ac isn't the right thing to do, i think.11:12
*** dolphin <dolphin!dolphin@unaffiliated/dolphin> has left #yocto11:15
*** jonathanmaw_ is now known as jonathanmaw11:20
*** frsc <frsc!~frsc@80.149.173.68> has quit IRC11:20
*** frsc <frsc!~frsc@80.149.173.68> has joined #yocto11:22
*** hamis_lt_u <hamis_lt_u!~irfan@110.93.212.98> has quit IRC11:24
*** hamis_lt_u <hamis_lt_u!~irfan@110.93.212.98> has joined #yocto11:25
*** bananadev <bananadev!~bananadev@117.6.99.240> has quit IRC11:27
fmeerkoetterthe configure step of a software i am packaging fails with11:33
fmeerkoetterERROR: This autoconf log indicates errors, it looked at host include and/or library paths while determining system capabilities.11:33
fmeerkoetterlooking through the configure.ac i see a lot of hardcoded references to /usr/local, /opt/local, etc...11:34
fmeerkoetterhow can I prefix these so that they reference the yocto sysroot?11:34
fmeerkoetteror rather should I?11:35
*** aime-Pierre <aime-Pierre!~Thunderbi@bob75-2-81-56-46-209.fbx.proxad.net> has quit IRC11:35
*** aime-Pierre <aime-Pierre!~Thunderbi@193.56.60.161> has joined #yocto11:36
*** hamis_lt_u <hamis_lt_u!~irfan@110.93.212.98> has quit IRC11:39
*** frsc <frsc!~frsc@80.149.173.68> has quit IRC11:40
*** frsc <frsc!~frsc@80.149.173.68> has joined #yocto11:41
*** Guest83585 <Guest83585!~vivek@78.32.176.249> has quit IRC11:44
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:37f8:f279:59ff:fe64:3a8> has joined #yocto11:46
*** hanthings <hanthings!~nandor@194.9.252.237> has joined #yocto11:47
*** anselmolsm <anselmolsm!anselmolsm@nat/intel/x-sjszfdopthppoyhu> has joined #yocto11:47
*** hamis_lt_u <hamis_lt_u!~irfan@110.93.212.98> has joined #yocto11:52
*** Guest83585 <Guest83585!~vivek@pakora.collabora.co.uk> has joined #yocto11:53
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:37f8:f279:59ff:fe64:3a8> has quit IRC11:54
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:37f8:f279:59ff:fe64:3a8> has joined #yocto11:54
marek_hi12:02
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:37f8:f279:59ff:fe64:3a8> has quit IRC12:02
marek_it is possible to have in one layer 2 bbappends for one recipe but for different machines only (I've added COMPATIBLE_MACHINE for bot but it's not working)12:03
*** frsc <frsc!~frsc@80.149.173.68> has quit IRC12:05
*** frsc <frsc!~frsc@80.149.173.68> has joined #yocto12:05
*** drou <drou!c32a382b@gateway/web/freenode/ip.195.42.56.43> has joined #yocto12:13
*** jku <jku!jku@nat/intel/x-zvdlinpvzquhtzpq> has quit IRC12:14
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:37f8:f279:59ff:fe64:3a8> has joined #yocto12:14
drouhi all12:14
Ulfalize1how could i force all tasks starting from do_configure to run for a package?12:15
Ulfalize1(while trying to debug an issue by directly modifying the fetched source code.)12:15
Ulfalize1oh... bitbake <pkg> -c configure -f  followed by  bitbake <pkg>  might be sufficient12:17
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:37f8:f279:59ff:fe64:3a8> has quit IRC12:21
rburtonUlfalize1: -C12:23
*** egavinc <egavinc!~egavinc@4.Red-83-34-185.dynamicIP.rima-tde.net> has quit IRC12:23
rburton-C is "invalidate the stamp for a specific task and then run do_build"12:24
*** blueness_ <blueness_!~blueness@cpe-74-77-145-97.buffalo.res.rr.com> has quit IRC12:24
rburtonso bitbake foo -C configure will re-run configure and everything after it12:24
*** jku <jku!jku@nat/intel/x-lkvzctuipnqvketl> has joined #yocto12:25
*** drou <drou!c32a382b@gateway/web/freenode/ip.195.42.56.43> has quit IRC12:25
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:37f8:f279:59ff:fe64:3a8> has joined #yocto12:25
*** c10ud <c10ud!~c10ud@emesene/dictator/c10ud> has quit IRC12:31
*** drou <drou!c32a382b@gateway/web/freenode/ip.195.42.56.43> has joined #yocto12:37
-YoctoAutoBuilder- build #538 of nightly-mips is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/53812:37
*** psadro <psadro!~Thunderbi@2620:0:ed0:800a:72f3:95ff:fe1d:9866> has joined #yocto12:46
marek_anyways it's possible to 2 bbappends for one recipe?12:51
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:37f8:f279:59ff:fe64:3a8> has quit IRC12:52
*** belen <belen!Adium@nat/intel/x-sncxpdpmcjhxpwyq> has joined #yocto13:01
*** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has quit IRC13:04
*** dshwang <dshwang!~dshwang@134.134.139.77> has joined #yocto13:15
-YoctoAutoBuilder- build #521 of nightly-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm-lsb/builds/52113:19
*** challinan_ <challinan_!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has quit IRC13:21
*** challinan <challinan!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has joined #yocto13:24
*** tsramos <tsramos!~tsramos@134.134.139.70> has joined #yocto13:31
*** blueness_ <blueness_!~blueness@cpe-74-77-145-97.buffalo.res.rr.com> has joined #yocto13:32
droumarek_: yes13:33
marek_drou: can I use also different COMPATIBLE_MCHINE for both of them?13:34
marek_drou: because it seems it's doing problems13:35
*** tasslehoff <tasslehoff!~Tasslehof@77.40.182.98> has quit IRC13:35
*** zeddii <zeddii!~bruce@128.224.252.2> has joined #yocto13:44
*** sujith_h_ <sujith_h_!~toaster@139.181.35.34> has joined #yocto13:44
*** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has quit IRC13:45
*** sujith_h_ is now known as sujith_h13:45
*** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has joined #yocto13:46
*** ftonello <ftonello!~quassel@81.145.202.106> has quit IRC13:46
*** georgem_ is now known as georgem13:50
*** smurray <smurray!sid98062@gateway/web/irccloud.com/x-gjxinfygxjluuzvw> has quit IRC13:52
*** smurray <smurray!sid98062@gateway/web/irccloud.com/x-ycifgnjqpbjubbfq> has joined #yocto13:52
*** aoibhinnditori <aoibhinnditori!sid95825@gateway/web/irccloud.com/x-qsbybmtkcmltmhyt> has quit IRC13:53
*** vmeson <vmeson!~rmacleod@128.224.252.2> has joined #yocto13:56
*** aoibhinnditori <aoibhinnditori!sid95825@gateway/web/irccloud.com/x-fgpfsguvawckzdwu> has joined #yocto13:58
*** psadro <psadro!~Thunderbi@2620:0:ed0:800a:72f3:95ff:fe1d:9866> has quit IRC14:01
*** psadro <psadro!~Thunderbi@2620:0:ed0:800a:72f3:95ff:fe1d:9866> has joined #yocto14:03
*** blueness_ <blueness_!~blueness@cpe-74-77-145-97.buffalo.res.rr.com> has quit IRC14:10
*** drou <drou!c32a382b@gateway/web/freenode/ip.195.42.56.43> has quit IRC14:17
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:37f8:f279:59ff:fe64:3a8> has joined #yocto14:34
*** Ulfalize1 <Ulfalize1!~ulf@217.89.178.116> has quit IRC14:34
*** nighty-_ <nighty-_!~nighty@ag136174.dynamic.ppp.asahi-net.or.jp> has quit IRC14:35
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:37f8:f279:59ff:fe64:3a8> has quit IRC14:45
LocutusOfBorg1hi guys, quick question: I have ofono on my target image, and I don't know why14:45
LocutusOfBorg11) how can I easily know who is adding it to the image?14:46
LocutusOfBorg12) how can I remove packages from the image?14:46
LocutusOfBorg1some blacklisting or similar14:46
*** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has quit IRC14:46
LocutusOfBorg1without avoiding the "inherit core-image"14:46
*** nighty-_ <nighty-_!~nighty@s1439095.xgsspn.imtp.tachikawa.spmode.ne.jp> has joined #yocto14:48
*** kscherer <kscherer!~kscherer@128.224.252.2> has joined #yocto14:48
*** blueness_ <blueness_!~blueness@cpe-74-77-145-97.buffalo.res.rr.com> has joined #yocto14:49
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:38dd:f279:59ff:fe64:3a8> has joined #yocto14:57
*** hamis_lt_u <hamis_lt_u!~irfan@110.93.212.98> has quit IRC14:57
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC15:03
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:38dd:f279:59ff:fe64:3a8> has quit IRC15:06
*** sgw_ <sgw_!~sgw_@c-73-164-210-189.hsd1.or.comcast.net> has joined #yocto15:10
*** jku <jku!jku@nat/intel/x-lkvzctuipnqvketl> has quit IRC15:11
*** madisox <madisox!~madison@12.30.244.5> has joined #yocto15:12
*** SoleSoul <SoleSoul!86bfe847@gateway/web/freenode/ip.134.191.232.71> has joined #yocto15:16
*** ntl <ntl!~ntl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has joined #yocto15:16
*** sjolley <sjolley!~sjolley@134.134.139.72> has quit IRC15:16
SoleSoulHi. I'm an Archlinux user and I have to bring a software project to Yocto. I've heard that15:17
SoleSoulHi. I'm an Archlinux user and I have to bring a software project to Yocto. I've heard that Yocto is different from other distros but I didn't find what the differences are exactly.15:18
SoleSoulIs there a list of major differences?15:18
SoleSoulIs the package management different?15:18
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:38dd:f279:59ff:fe64:3a8> has joined #yocto15:18
*** aime-Pierre <aime-Pierre!~Thunderbi@193.56.60.161> has quit IRC15:19
SoleSoulI know that Yocto is easier to be built small and optimized for certain devices but assuming I include this 'smart' package manager, is there any real different between the image I built and any other distibution?15:20
*** marek_ <marek_!~marek@81.89.61.168.host.vnet.sk> has quit IRC15:21
*** gabrbedd <gabrbedd!~beddingfi@li680-65.members.linode.com> has quit IRC15:23
*** gabrbedd <gabrbedd!~beddingfi@li680-65.members.linode.com> has joined #yocto15:25
*** aime-Pierre <aime-Pierre!~Thunderbi@193.56.60.161> has joined #yocto15:25
*** blueness_ <blueness_!~blueness@cpe-74-77-145-97.buffalo.res.rr.com> has quit IRC15:26
*** adelcast <adelcast!~adelcast@130.164.62.224> has left #yocto15:27
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC15:29
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:38dd:f279:59ff:fe64:3a8> has quit IRC15:29
gabrbeddSoleSoul: The smart package manager is a front-end for rpm. It's kind of like yum, zypper, apt, up2date, etc.15:29
gabrbeddSoleSoul: when you enable package management, the default is rpm... but you can also select deb,, ipk, or even tarballs (I think).15:30
*** CromFr <CromFr!~CromFr@146.185.162.164> has joined #yocto15:30
*** aime-Pierre <aime-Pierre!~Thunderbi@193.56.60.161> has quit IRC15:30
*** adelcast <adelcast!~adelcast@130.164.62.82> has joined #yocto15:30
gabrbeddSoleSoul: IMHO, Yocto's strong suit is in generating complete OS images. While the package management systems work well, I don't think they're up to par with big distros like Fedora, Ubuntu, and Debian.15:32
gabrbeddAnd by "work well" I mean "always leave the system in a good and repeatable state."15:32
SoleSoulgabrbedd: Thanks. So it's basically a normal distro, but it's easier to create images from.15:33
SoleSoulyour last comment about leaving the system in a good state is important. So it's not meant for a day to day use15:33
*** CromFr <CromFr!~CromFr@146.185.162.164> has quit IRC15:34
*** CromFr <CromFr!~CromFr@146.185.162.164> has joined #yocto15:34
rburtoni see the value as something in which you're in control.  you don't take debian or redhat or whatever and customise it, at the whim of their control15:34
SoleSoulgabrbedd: Do I have multiple package repositories to choose from or is there a main one (or only one)?15:35
*** dreyna4529 <dreyna4529!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto15:35
rburtonSoleSoul: that's up to you, as you'll be building the repos15:35
gabrbeddI can't tell you what the upstream folks /indend/ for package mgmt, but _I_ wouldn't try to use Yocto like I use Debian: with binary package updates to my system.15:35
*** CromFr <CromFr!~CromFr@146.185.162.164> has left #yocto15:35
gabrbeddSoleSoul: I would say "So it's basically a normal distro, but it's easier to create CROSS-COMPILED images from."15:36
SoleSoulrburton: Is there a main repo?15:36
SoleSoulthat someone has already built?15:36
gabrbeddSoleSoul: not really.15:36
rburtonSoleSoul: angstrom has one, but thats only if you want to run the angstrom distribution15:36
SoleSoulgabrbedd: what if I need a newer gcc (which I already do)?15:36
rburtonthe entire point is *you* build the distro you want15:37
rburtonSoleSoul: the 2.0 release has gcc 5.2, is that new enough?15:37
SoleSoulas you can see, I'm still trying to understand the concept. Thanks for your patience.15:37
SoleSoulrburton: yes it is15:37
SoleSoulI have 4.9 here15:37
rburton"it's not a linux distribution, it lets you build your own linux distribution"15:38
SoleSoulrburton: yeah I got that part but I thought that if I take an already built image I could roll with it just as I do with other distros15:38
gabrbeddSoleSoul: The canonical Yocto repositories all have "bitbake recipes" -- these are like Gentoo ebuild descriptions.15:39
SoleSoulgabrbedd: This concept I do know. I've used Gentoo before.15:39
gabrbeddSoleSoul: as a matter of breaking up the problem and re-using previous compiles, it also will use some packaging tools (RPM, DEB, IPK) to generate the emages.15:39
*** dreyna4529 <dreyna4529!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC15:39
rburtonSoleSoul: sure, start from poky or angstrom or something, but building an image is sufficiently fast that you might as well start from scratch15:39
rburton(scratch being from sources, and not from an existing image)15:40
SoleSoulrburton: maybe I should try building a new image to understand what's going on even if I'm not going to use it.15:40
rburtonyes15:40
*** nighty-_ <nighty-_!~nighty@s1439095.xgsspn.imtp.tachikawa.spmode.ne.jp> has quit IRC15:40
gabrbeddSoleSoul: I've worked on an OpenEmbedded-based system where we used IPK's for updates. We created our own package repositories.15:40
rburtonSoleSoul: the poky quickstart is a good introduction - gets you building an image for the poky distro (the reference distro for QA purposes) nice and quickly.  then you can take that wherever you want.15:41
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:38dd:f279:59ff:fe64:3a8> has joined #yocto15:41
SoleSoulgabrbedd: the only 'embedded' linux I used was OpenWRT and it does have compiled packages so this is new to me.15:41
gabrbeddSoleSoul: it generally worked OK when we upgraded things... but pre-install and post-install scripts became problematic for us since we needed a high-reliability upgrade.15:41
rburtonyeah for reliability you don't want packages, you want whole-image updates, secondary images, and rollback15:42
fraygabrbedd, this is why both RPM and IPK (and deb) are supported..15:42
*** anselmolsm <anselmolsm!anselmolsm@nat/intel/x-sjszfdopthppoyhu> has quit IRC15:42
rburtonnot quite trivial15:42
frayrburton you can do high reliability with packages -- but -- you need to be smart about it and control how the upgrade happens..15:42
fraysecondary images (or at least a maintenance image) is often used to facilitate that..15:43
SoleSoulwhy isn't there a central binary repository? Is it against Yocto's purpose?15:43
rburtonSoleSoul: yes15:43
SoleSoulwhy wouldn't I want that?15:43
fraythe problem is that you need to weigh the download of the update against the reliability factor and make smart decisions.. if the image is 1 MB, easy do an image.. but if the image is 1 GB.. then packages are much better..15:43
rburtonSoleSoul: because who is to say that your systemd package has the same options as mine?15:43
fraySoleSoul, this is where the 'custom distribution' part fits in..15:43
LetoThe2ndSoleSoul: it becomes pointless once you do not use pre-defined machines or architectures.15:44
gabrbeddSoleSoul: think about Gentoo's USE flags. Bitbake uses something like them -- and it makes the binary packages slightly incompatible.15:44
frayThe example configuration for the YP's systemd, bash, coreutils, etc may be different then your needs..15:44
LetoThe2ndSoleSoul: which in turn is exactly what most OE/YP users actively want15:44
frayso there is no one way to do things15:44
LetoThe2ndSoleSoul: sounds like you actually want angstrom or such.15:44
SoleSoulThank you all for the answer :)15:45
SoleSoulLetoThe2nd: Not necessarily, I'm just trying to understand the concept15:45
LetoThe2ndSoleSoul: just think about - "what binaries do you want to provide if you have to assume that every single user has a different architecture".15:45
SoleSoulLetoThe2nd: Yeah I think I get it.15:46
LetoThe2nd:-)15:46
SoleSoulI have a client who has a built of Yocto which he builds himself. Before sending him my sources I want to make sure that my application works on Yocto. I got an image of Yocto that my coworker built and it misses some things I need. That's where my questions came from.15:46
LetoThe2ndSoleSoul: the problems all come from the mindset "image of yocto"15:47
SoleSoulwhat's wrong about it? :)15:47
LetoThe2ndSoleSoul: that it doesn't exist.15:47
SoleSoulit's for a specific hardware build which we both use.15:47
*** anselmolsm <anselmolsm!~anselmols@192.55.55.37> has joined #yocto15:48
SoleSoulme and my coworker15:48
SoleSoulthe client will get sources15:48
LetoThe2ndSoleSoul: your problem is more like this. "my customer has a linux image, and my coworker has a linux image. they are different."15:48
LetoThe2ndthey just used a similar mechanism to build it.15:48
kergothdistro, machine, and image are orthogonal concepts in these build tools. what packages go into the image is largely independent of what the target board happens to be. much as multiple desktops can run ubuntu but have entirely different packages installed, only more so, since build configuration is more of a factor15:49
* kergoth yawns15:49
frayhardware only affects the kernel configuration and the format of the resulting ELF binaries..15:49
fraybut it doesn't explain how things were configured and the overall system design issues you may have selected..15:49
frayas kergot said, these are all orthogonal concepts...15:49
LetoThe2ndSoleSoul: just like "see, i've got this 18-wheeler, and my friend has this sports car. why don't my tyres fit there? they both have an engine, so its both suposed to be a car!"15:49
SoleSoulLetoThe2nd: Actually, the customer knows more about Yocto than I do. He'll be fine. I'm trying to understand how to make a testing/development machine for myself15:49
frayYou need to establish a configuration.. one that specifies the BSP and distribution settings you and your customer agree on..15:50
rburtonSoleSoul: ask him for a copy of the image, or access to his layers and configuration so you can repeat his build15:50
LetoThe2ndSoleSoul: then ask your customer to provide you with the sdk that he wants you to use.15:50
fraythen you select one or more image recipes that have the filesystem confgiuration..15:50
fraythen you'll both be on the same page15:50
*** frsc <frsc!~frsc@80.149.173.68> has quit IRC15:50
*** berton <berton!~fabio@177.220.212.62> has joined #yocto15:50
SoleSoulSounds logical. Thanks15:51
*** tsramos_ <tsramos_!~tsramos@134.134.139.70> has joined #yocto15:52
*** sjolley <sjolley!~sjolley@134.134.139.78> has joined #yocto15:52
SoleSoulIt's so nice to have an irc channel on a topic I'm interested in.15:53
SoleSoulI'll be going now. I really appreciate your help you'all :)15:53
* armpit work build ate my disk.. again15:54
*** jku <jku!~jku@d-lltyxzqsj--98wl3k-3.rev.dnainternet.fi> has joined #yocto15:54
SoleSoulTime to do some homework on the topic15:54
*** tsramos <tsramos!~tsramos@134.134.139.70> has quit IRC15:54
*** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has joined #yocto15:55
*** abelal <abelal!~quassel@110.93.212.98> has quit IRC15:56
*** abelal <abelal!~quassel@110.93.212.98> has joined #yocto15:57
*** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has quit IRC15:58
rburtonquick poll15:59
rburtonthere's a series on the list to fix five CVEs in libav15:59
rburtonone patch per cve15:59
rburtonas in each cve fix is a patch to the recipe, and each patch is added in an independent commit to the recipe15:59
*** radzy <radzy!~radzy@unknown-216-78.windriver.com> has quit IRC15:59
rburtonshould these be squashed so one commit to the recipe adds all five fixes (in separate files)16:00
fray(I'd be fine with one commit -- but one patch per CVE is the best way to handle this in my experience)16:00
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:38dd:f279:59ff:fe64:3a8> has quit IRC16:00
kergothYeah, I'd think one commit but one patch per CVE in the layer16:00
fraythe commit is and should be considered the logical change.  5 CVEs can be one logical change16:00
rburtonfray: for reference its poky-contrib/jhuang0/d_libav-cve_151113-116:00
rburtonpersonally i'd squash it so there's a single commit in oe-core which adds five files16:01
rburton*definitely* a patch per cve for analysis16:01
frayif there is a reason to take these patches individually (bisect or otherwise) then multiple commits.. otherwise I'd be fine squashing -- OR -- keeping them individual.. doesn't really matter as long as the system works with one or all16:01
frayif 'all' is required, then they should be squashed16:01
rburtonhm the upstream-status is wrong too16:01
*** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has joined #yocto16:02
rburtonhuh16:03
rburtona libav cve, fixed with a patch from ffmpeg16:03
*** aragua <aragua!~flahouder@212.194.216.83> has quit IRC16:03
rburtonnot sure we have a upstream-status for that16:03
rburtonUpstream-Status: Disaster16:03
*** SoleSoul <SoleSoul!86bfe847@gateway/web/freenode/ip.134.191.232.71> has quit IRC16:04
*** figiel <figiel!~pf@95.143.242.242> has quit IRC16:04
Guest83585I wouldn't squash them.16:04
*** Guest83585 is now known as flahouder16:05
*** flahouder is now known as fledermaus16:05
fledermausthe fixes for one CVE might evolve or change or turn out to be wrong.16:05
*** radzy_lunch <radzy_lunch!~radzy@unknown-216-78.windriver.com> has joined #yocto16:05
fledermausthey might get fixed upstream at different times.16:05
*** radzy_lunch is now known as radzy16:05
fledermausif you squash them you'll have to unpick the patch if any of that happens.16:05
rburtonfledermaus: the cve fixes themselves would still be separate files16:05
fledermausoh right.16:06
rburtonjust the commit to oe-core would add five patches, instead of five commits with a patch each16:06
fledermausfine whatever then :)16:06
rburtonyeah hard to have a strong opinion16:06
rburtonmy main argument for squashing is length of commit log :)16:06
*** cbzx <cbzx!~cbzx@CPE0015f275ecd5-CM00195edd810c.cpe.net.cable.rogers.com> has joined #yocto16:08
*** cbzx <cbzx!~cbzx@CPE0015f275ecd5-CM00195edd810c.cpe.net.cable.rogers.com> has joined #yocto16:08
rburtonspeaking of which16:08
rburtonlibav vs ffmpeg16:08
rburtonFIGHT!16:08
fledermauswhoever wins, we lose?16:09
*** ionte <ionte!~textual@83.233.227.60> has quit IRC16:10
armpithaving a commit per cve allows users to cherry pick what they want16:11
armpitnot all issues are equal16:12
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:38dd:f279:59ff:fe64:3a8> has joined #yocto16:12
fledermausmeh, they can tweak the bb file to drop a patch just as easily.16:12
kergotharmpit: that's a fair point. i would expect folks who want updates to stable branches would likely want all security fixes, but it depends on how risk averse they are and which form of risk is most concerning to them, security or potential breakage :)16:14
kergothmeh16:14
armpitits more of an issue once our customer deply. they only want the high and critical changes only.. but that is more of my problem.. just trying to save me time16:16
* kergoth nods16:19
kergothmakes sense16:19
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:38dd:f279:59ff:fe64:3a8> has quit IRC16:20
*** bluelightning <bluelightning!~paul@125-239-194-188.jetstream.xtra.co.nz> has joined #yocto16:20
*** bluelightning <bluelightning!~paul@125-239-194-188.jetstream.xtra.co.nz> has quit IRC16:20
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto16:20
* kergoth thinks devtool's oe-local-files should really just be source controlled in the repo alongside our patches, then changes to them could be tracked when using e.g. devtool sync16:23
kergoths/patches/changes from our patches/16:23
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto16:25
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC16:26
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:38dd:f279:59ff:fe64:3a8> has joined #yocto16:32
*** scottrif <scottrif!~scottrif@68-186-122-205.dhcp.knwc.wa.charter.com> has joined #yocto16:35
*** blueness_ <blueness_!~blueness@cpe-74-77-145-97.buffalo.res.rr.com> has joined #yocto16:36
*** focus <focus!~Doug@164.39.177.154> has quit IRC16:39
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC16:41
*** belen <belen!Adium@nat/intel/x-sncxpdpmcjhxpwyq> has quit IRC16:44
*** belen <belen!Adium@nat/intel/x-uqmdblwhpeaicngj> has joined #yocto16:44
*** blueness_ <blueness_!~blueness@cpe-74-77-145-97.buffalo.res.rr.com> has quit IRC16:45
*** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has joined #yocto16:47
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto16:47
Cardoeis there an environment variable I can use to make ${PN}-cross-${MYARCH} or is there a variable that will be MYARCH?16:47
CardoeI'm trying to avoid hardcoding x86_64 in my layer because I know that's not correct16:48
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto16:48
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC16:49
*** blueness_ <blueness_!~blueness@cpe-74-77-145-97.buffalo.res.rr.com> has joined #yocto16:50
*** cbzx <cbzx!~cbzx@CPE0015f275ecd5-CM00195edd810c.cpe.net.cable.rogers.com> has quit IRC16:51
kergothlook at one of the existing recipes. there's a PN .= line in all the cross reicpes that append an architecture16:52
Cardoekergoth: thanks.16:52
CardoeAnother stupid question... what's really the need of the cross packages?16:53
CardoeI'm wondering if this layer is totally screwed up16:53
CardoeIt's building the Rust language and it builds rust-native, rust-cross-x86_64 and rust16:53
kergothA cross recipe is built to run on the host but target the target architecture. It's how you build a crosscompiler toolchain that runs on teh build machine but emits binaries for the target16:53
Cardoealright16:54
CardoeSo I probably want rust-native and rust-cross to build but not rust for a package.16:54
CardoeThe compiler isn't necessary to execute packages on the target.16:54
kergothif you never want to support on target development with rust, sure16:54
CardoeWell if I write a program in Rust, it shouldn't depend on rust the package. Just rust-cross16:56
CardoeSince it gets compiled to native code.16:56
CardoeAssuming my logic is correct here.16:56
kergoththat sounds accurate, indeed16:56
CardoeLast question16:56
CardoeSECURITY_CFLAGS-pn_rust-cross-x86_64 = "" would be correct?16:56
Cardoeto clear out SECURITY_CFLAGS for rust-cross.16:57
*** blueness_ <blueness_!~blueness@cpe-74-77-145-97.buffalo.res.rr.com> has quit IRC17:00
kergothit's _pn-, not -pn_17:01
kergoththe syntax is generic for anything in OVERRIDES. <variable>_<override>. in this case the override is pn-${PN}17:01
kergothso yes, SECURITY_FLAGS_pn-rust-cross-whatever would likely do the job17:01
Cardoeer sorry I typoed that17:01
kergothbut use bitbake -e yourrecipe to examine the final value to make sure it's set to what oyu want17:02
CardoeWould I use "rust-cross-x86_64" for yourreceipe or just "rust"?17:02
*** jonathanmaw <jonathanmaw!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has quit IRC17:02
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:38dd:f279:59ff:fe64:3a8> has quit IRC17:03
kergothas i just said, it' sthe recipe's PN variable17:06
kergothwhich would include the arch, since it's appended to PN17:06
Cardoekergoth: Ok. thank you. I appreciate your help.17:07
kergothnp17:08
*** jbrianceau is now known as jbrianceau_away17:10
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:38dd:f279:59ff:fe64:3a8> has joined #yocto17:11
*** aime-Pierre <aime-Pierre!~Thunderbi@bob75-2-81-56-46-209.fbx.proxad.net> has joined #yocto17:13
*** bluelightning_ <bluelightning_!~paul@125-239-194-188.jetstream.xtra.co.nz> has joined #yocto17:19
*** bluelightning_ <bluelightning_!~paul@125-239-194-188.jetstream.xtra.co.nz> has quit IRC17:19
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto17:19
*** townxelliot <townxelliot!~ell@94.13.69.111> has quit IRC17:20
*** blueness_ <blueness_!~blueness@cpe-74-77-145-97.buffalo.res.rr.com> has joined #yocto17:21
*** aime-Pierre <aime-Pierre!~Thunderbi@bob75-2-81-56-46-209.fbx.proxad.net> has quit IRC17:25
*** scottrif <scottrif!~scottrif@68-186-122-205.dhcp.knwc.wa.charter.com> has left #yocto17:26
*** clsulliv1 <clsulliv1!clsulliv@nat/intel/x-dhhpkebhhhqgiwmu> has left #yocto17:28
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:38dd:f279:59ff:fe64:3a8> has quit IRC17:30
*** _jmleo is now known as jmleo17:31
*** roccof <roccof!~roccof@93-51-177-218.ip268.fastwebnet.it> has quit IRC17:31
*** townxelliot <townxelliot!~ell@94.13.69.111> has joined #yocto17:37
*** paulg <paulg!~paulg@72.1.195.9> has joined #yocto17:38
*** maxin <maxin!~maxin@2001:998:22:0:3155:467f:b986:199b> has quit IRC17:39
*** blueness_ <blueness_!~blueness@cpe-74-77-145-97.buffalo.res.rr.com> has quit IRC17:39
*** c10ud <c10ud!~c10ud@emesene/dictator/c10ud> has joined #yocto17:42
*** t0mmy_ <t0mmy_!~tprrt@217.114.201.133> has quit IRC17:43
*** fl0v0 <fl0v0!~fvo@p5DDC639A.dip0.t-ipconnect.de> has quit IRC17:47
*** sameo <sameo!samuel@nat/intel/x-tribcnrurlythrou> has quit IRC17:52
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-mfksdaopewaccogt> has left #yocto17:55
*** jku <jku!~jku@d-lltyxzqsj--98wl3k-3.rev.dnainternet.fi> has quit IRC17:56
*** IvanSB <IvanSB!~IvanSB@host81-144-dynamic.8-87-r.retail.telecomitalia.it> has joined #yocto17:58
*** clopez_ is now known as clopez17:58
*** yann|work <yann|work!~yann@LFbn-1-1026-146.w86-247.abo.wanadoo.fr> has quit IRC17:59
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC18:00
*** bluelightning_ <bluelightning_!~paul@125-239-194-188.jetstream.xtra.co.nz> has joined #yocto18:00
*** bluelightning_ <bluelightning_!~paul@125-239-194-188.jetstream.xtra.co.nz> has quit IRC18:00
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto18:00
*** dreyna4529 <dreyna4529!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto18:04
*** blueness_ <blueness_!~blueness@cpe-74-77-145-97.buffalo.res.rr.com> has joined #yocto18:06
*** Biliogadafr <Biliogadafr!~User@nat2-minsk-pool-46-53-195-225.telecom.by> has quit IRC18:13
*** Biliogadafr <Biliogadafr!~User@nat2-minsk-pool-46-53-195-225.telecom.by> has joined #yocto18:15
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC18:15
*** stwcx <stwcx!~stwcx@32.97.110.52> has joined #yocto18:17
*** bluelightning1 <bluelightning1!~paul@125-239-194-188.jetstream.xtra.co.nz> has joined #yocto18:18
*** Biliogadafr <Biliogadafr!~User@nat2-minsk-pool-46-53-195-225.telecom.by> has quit IRC18:19
*** nrossi <nrossi!~nrossi@43.252.111.142> has quit IRC18:21
*** nrossi <nrossi!~nrossi@103.26.61.194> has joined #yocto18:23
*** ulf`_ <ulf`_!~ulf@134.134.137.71> has quit IRC18:27
*** blueness_ <blueness_!~blueness@cpe-74-77-145-97.buffalo.res.rr.com> has quit IRC18:30
-YoctoAutoBuilder- build #531 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/53118:30
*** bluelightning1 <bluelightning1!~paul@125-239-194-188.jetstream.xtra.co.nz> has quit IRC18:32
*** matteo <matteo!~matteo@openwrt/developer/matteo> has quit IRC18:41
-YoctoAutoBuilder- build #530 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/53018:50
-YoctoAutoBuilder- build #526 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/52618:50
*** blueness_ <blueness_!~blueness@cpe-74-77-145-97.buffalo.res.rr.com> has joined #yocto18:54
-YoctoAutoBuilder- build #539 of nightly-fsl-ppc-lsb is complete: Failure [failed BuildImages] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc-lsb/builds/53918:55
-YoctoAutoBuilder- build #527 of build-appliance is complete: Failure [failed BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/52718:56
*** IvanSB <IvanSB!~IvanSB@host81-144-dynamic.8-87-r.retail.telecomitalia.it> has quit IRC18:58
*** tsramos <tsramos!tsramos@nat/intel/x-qwhxtemoebscjdan> has joined #yocto19:02
*** ulf` <ulf`!ulf@nat/intel/x-ndwjiafoidzgkzbu> has joined #yocto19:02
*** tsramos_ <tsramos_!~tsramos@134.134.139.70> has quit IRC19:04
*** blueness_ <blueness_!~blueness@cpe-74-77-145-97.buffalo.res.rr.com> has quit IRC19:06
*** dvhart <dvhart!~dvhart@134.134.137.73> has joined #yocto19:10
*** townxelliot <townxelliot!~ell@94.13.69.111> has quit IRC19:13
*** ylouise1 <ylouise1!~yalouise@134.134.139.78> has left #yocto19:14
*** blueness_ <blueness_!~blueness@cpe-74-77-145-97.buffalo.res.rr.com> has joined #yocto19:16
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-bydodmtqvuanqpgh> has quit IRC19:20
*** vmrod25 <vmrod25!~vrodri3@134.134.139.78> has joined #yocto19:23
vmrod25hi team question is there any standard solution to create an IoT newtwork ? from the comunication to the app and analitics point of view ? ( I have just found zatar : http://www.zatar.com/ )19:24
*** fledermaus <fledermaus!~vivek@pakora.collabora.co.uk> has quit IRC19:26
*** belen <belen!Adium@nat/intel/x-uqmdblwhpeaicngj> has quit IRC19:27
*** gunnarx <gunnarx!~gan@unaffiliated/gan> has joined #yocto19:29
*** t0mmy_ <t0mmy_!~tprrt@ram31-2-82-228-88-46.fbx.proxad.net> has joined #yocto19:29
fraythere are a number fo commercial products that assist with this..19:30
fray(and lots of OSS components to build your own)19:30
vmrod25agree19:31
vmrod25I was just wondering if somethin yocto was involved in19:31
*** AndersD <AndersD!~anders@37.250.11.3.bredband.tre.se> has joined #yocto19:32
fraynot that I am aware of19:33
gunnarxhmm... does do_patch commit each patch to the git tree?19:33
*** madisox <madisox!~madison@12.30.244.5> has quit IRC19:34
gunnarxor why I got a user.name and user.email not set error during do_patch (they are not set using git config --global)19:34
-YoctoAutoBuilder- build #531 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/53119:37
gunnarxapparently it does git-am19:39
-YoctoAutoBuilder- build #547 of nightly-x86-64 is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Running SDK Sanity Tests Building Toolchain Images_1 Running SDK Sanity Tests_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-64/builds/54719:39
-YoctoAutoBuilder- build #187 of nightly-mips64 is complete: Failure [failed BuildImages Running Sanity Tests Building Toolchain Images Running SDK Sanity Tests Building Toolchain Images_1 Running SDK Sanity Tests_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips64/builds/18719:40
kergothgunnarx: depends on what PATCHTOOL is set to, generally19:40
*** maxin <maxin!~maxin@dsl-espbrasgw1-54fa70-49.dhcp.inet.fi> has joined #yocto19:41
gunnarxah, ok.  Well git-am requires user.name to be set so I'm guessing that's what is happening19:42
-YoctoAutoBuilder- build #86 of nightly-wic is complete: Failure [failed BuildImages_1 CreateWicImages CreateWicImages_1 BuildImages_3 CreateWicImages_2 CreateWicImages_3] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-wic/builds/8619:44
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:38dd:f279:59ff:fe64:3a8> has joined #yocto19:45
gunnarxHow does PATCHTOOL play in?   meta/lib/oe/patch.py suggests to me git-am is involved anyway19:46
*** AndersD <AndersD!~anders@37.250.11.3.bredband.tre.se> has quit IRC19:47
gunnarxI wonder how often this just ends up using whatever is set in git config --global?  Should bitbake provide something so the operation doesn't simply fail on a bare machine?19:48
*** slidercrank <slidercrank!~slidercra@unaffiliated/slidercrank> has quit IRC19:48
kergoth?19:48
kergothpatch.py has multiple classes that apply patches19:48
kergoththe git class is just one19:48
kergothand is only used when PATCHTOOL is set to git19:48
kergothbut yes, it should probably add a sane fallback the way buildhistory does (see http://git.openembedded.org/openembedded-core/commit/?id=f62255bfa6c5a322c867b7c4ea5686ea7bfab3fe)19:49
gunnarxok, fair enough.  the failing do_patch is on a git repo anyway19:49
gunnarxyes, looks like same issue19:49
kergothjust because it's a git repo dioesn't mean git would be use dto apply the patches, unless PATCHTOOL is set to git19:49
kergothi'd suggest opening a bug in the yocto bugzilla19:50
gunnarxkergoth:  The amount of configuration is amazing.  It would be the default to use git as PATCHTOOL for a git repo at least? :)19:51
kergothi doubt that would be a very good idea19:51
kergothgit apply (and therefore, git am) is much picker about applying patches than patch is19:51
kergothpatch handles fuzz better19:51
* zeddii nods19:51
kergothswitching to git application by default for git repositoiries would cause us patch application failures19:51
-YoctoAutoBuilder- build #532 of nightly-qa-pam is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-pam/builds/53219:51
kergothone might argue that its a net gain to not keep around fuzz in our patches, but that'd have to be a conscious choice19:52
paulgdo-able for kernel ; not sure about a wider net than that...19:52
zeddiiand a flag day sort of thing.19:52
zeddiiwe already took that hit for linux-yocto kernels, but that's a relatively small scope compared to the horrors of userspace and all the layers.19:53
paulgagreed.19:53
-YoctoAutoBuilder- build #547 of nightly-arm is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Running SDK Sanity Tests Building Toolchain Images_1 Running SDK Sanity Tests_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/54719:54
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:38dd:f279:59ff:fe64:3a8> has quit IRC19:55
paulgISTR that you could "tune" git-am to allow the same level of fast-n-loose fuzz that patch allows by default...19:55
paulgOTOH, I think I'd rather just see git-am fail and then manually intervene to check things out vs. having crap mis-applied in a section that has nothing but whitespace and curly braces19:56
paulgthat is typically where I've seen patch fuzz in crap incorrectly ; where the context is vague.19:56
*** sno <sno!~sno@rademacherexchange.de> has joined #yocto19:56
kergothagreed19:56
kergothI've often seen duplicated sections or entire functions when the only context is a closing } in a previous block or something19:57
paulgyep, seen that too.19:57
-YoctoAutoBuilder- build #539 of nightly-mips is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Running SDK Sanity Tests Building Toolchain Images_1 Running SDK Sanity Tests_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/53919:57
paulgfortunately gcc gets pretty angry about that, even if the meatware at the keyboard missed spotting it.19:57
*** wenzong <wenzong!~wfan@106.120.101.38> has quit IRC19:57
*** wenzong <wenzong!~wfan@106.120.101.38> has joined #yocto19:58
*** vmrod25 <vmrod25!~vrodri3@134.134.139.78> has left #yocto19:58
kergothoften things like that seem to come up if folks bump versions and blindly test patch application for failures rather than actually checking to see if the underlying issues fixed by the patches were addressed upstream19:59
*** ][Sno][ <][Sno][!~sno@rademacherexchange.de> has quit IRC19:59
*** t0mmy_ <t0mmy_!~tprrt@ram31-2-82-228-88-46.fbx.proxad.net> has quit IRC20:00
gunnarxkergoth, paulg :  sorry, was off looking at bugzilla.  makes sense what you are saying.  I'll try to figure out then why this project is (maybe) using git-am, at least that's my theory wrt the error20:01
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC20:04
*** blueness_ <blueness_!~blueness@cpe-74-77-145-97.buffalo.res.rr.com> has quit IRC20:06
gunnarxoffending recipe sets PATCHTOOL to git seemingly to get support for binary patches.  Thanks for leading me to the solution guys.20:07
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:38dd:f279:59ff:fe64:3a8> has joined #yocto20:08
*** fledermaus <fledermaus!~vivek@78.32.176.249> has joined #yocto20:08
paulgwhee.  binary patches.   :-/20:09
gunnarxyay20:09
gunnarxyeah some png file. Ought to be fetched but you know, lazy recipe writers.20:11
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:38dd:f279:59ff:fe64:3a8> has quit IRC20:13
paulgI was going to guess some hideous firmware blob.20:14
-YoctoAutoBuilder- build #547 of nightly-x86 is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Running SDK Sanity Tests Building Toolchain Images_1 Running SDK Sanity Tests_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86/builds/54720:14
-YoctoAutoBuilder- build #526 of nightly-ipk is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ipk/builds/52620:15
*** rci <rci!~rci@70-90-78-101-BusName-mn.hfc.comcastbusiness.net> has joined #yocto20:18
-YoctoAutoBuilder- build #195 of nightly-deb-non-deb is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-deb-non-deb/builds/19520:21
-YoctoAutoBuilder- build #551 of nightly-x86-64-lsb is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb/builds/55120:21
*** yann|work <yann|work!~yann@nan92-1-81-57-214-146.fbx.proxad.net> has joined #yocto20:25
*** ryansturmer <ryansturmer!~ryansturm@cpe-75-189-150-192.nc.res.rr.com> has joined #yocto20:30
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:38dd:f279:59ff:fe64:3a8> has joined #yocto20:31
ryansturmerQuestion: When I do my yocto build, where is the version of the kernel to use defined?20:31
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto20:32
paulgin your local layer conf or your distro conf, look for...20:33
paulgPREFERRED_VERSION_linux-yocto ?=  <...>20:33
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC20:34
*** sno <sno!~sno@rademacherexchange.de> has quit IRC20:34
-YoctoAutoBuilder- build #526 of nightly-fsl-ppc is complete: Failure [failed BuildImages Building Toolchain Images Building Toolchain Images_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc/builds/52620:34
Cardoekergoth: another potential silly question for Rust.20:34
CardoeThe native can be built with as many targets as necessary. Is there an advantage to building rust-native and rust-cross-${TARGET_ARCH}?20:35
Cardoeor just building all those targets into the native?20:35
Cardoerust-native isn't even used to build rust-cross-${TARGET_ARCH}20:36
kergothif a single build can target any number of archs, i'd think it could do the job and avoid the need for the cross incarnations, but i dont' really know much about rust20:36
frayQEMU is setup similarly, in that we generally build QEMU to support all of the available targets we care about20:37
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:38dd:f279:59ff:fe64:3a8> has quit IRC20:38
kergothi think go and clang/llvm are along similar lines20:39
-YoctoAutoBuilder- build #522 of nightly-rpm is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-rpm/builds/52220:41
*** drou <drou!52e867a5@gateway/web/freenode/ip.82.232.103.165> has joined #yocto20:44
drouhi guys20:44
ryansturmerthanks @paulg20:45
-YoctoAutoBuilder- build #186 of nightly-arm64 is complete: Failure [failed BuildImages Running Sanity Tests Building Toolchain Images Running SDK Sanity Tests Building Toolchain Images_1 Running SDK Sanity Tests_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm64/builds/18620:45
Cardoekergoth: Rust is on top of llvm similarly to clang20:45
CardoeI'll check out how clang is built.20:45
*** blueness_ <blueness_!~blueness@cpe-74-77-145-97.buffalo.res.rr.com> has joined #yocto20:46
-YoctoAutoBuilder- build #544 of nightly-ppc is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Running SDK Sanity Tests Building Toolchain Images_1 Running SDK Sanity Tests_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds/54420:49
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:38dd:f279:59ff:fe64:3a8> has joined #yocto20:51
*** paulg <paulg!~paulg@72.1.195.9> has quit IRC20:51
jcreekmoreSo, say you wanted to include the output of one image into another. How would you go about that? Say I have one image that is a PXE server and another image that is an initramfs that I want to embed into the PXE server image. Any advice on how I could go about doing that?20:52
rburtonjcreekmore: one image depends on the other, the hddimg formats all do this as they embed a initramfs20:53
jcreekmoreBut where would it put that? Would I need to write a custom rule to get it installed into a particular place?20:53
*** blueness_ <blueness_!~blueness@cpe-74-77-145-97.buffalo.res.rr.com> has quit IRC20:54
*** blueness_ <blueness_!~blueness@gentoo/developer/blueness> has joined #yocto20:54
-YoctoAutoBuilder- build #514 of nightly-deb is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/51420:55
Cardoerburton: would it be a RDEPENDS or DEPENDS?20:55
-YoctoAutoBuilder- build #529 of nightly-ppc-lsb is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/builds/52920:55
Cardoefor jcreekmore's issue20:55
drouhas anyone experience this kind of perl issue: SSL connect attempt failed error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed? i'm not sure about my configuration, i added libio-socket-ssl-perl & libnet-ssleay-perl20:57
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:38dd:f279:59ff:fe64:3a8> has quit IRC20:57
rburtonCardoe: depends, rdepends are specific to packages20:58
*** gunnarx <gunnarx!~gan@unaffiliated/gan> has quit IRC20:58
rburtonjcreekmore: to be honest, assuming your pxe image is just a tarball or directory, that's already supported20:58
rburtonotavio: https://autobuilder.yoctoproject.org/main/builders/nightly-rpm/builds/522/steps/BuildImages/logs/stdio <— you broke lttng's ptest21:02
rburton(clearly i failed to test build that)21:02
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto21:03
-YoctoAutoBuilder- build #188 of ptest-x86-64 is complete: Failure [failed BuildImages] Build details are at http://autobuilder.yoctoproject.org/main/builders/ptest-x86-64/builds/18821:04
-YoctoAutoBuilder- build #522 of nightly-arm-lsb is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm-lsb/builds/52221:06
*** yann|work <yann|work!~yann@nan92-1-81-57-214-146.fbx.proxad.net> has quit IRC21:07
drouit seems that im missing something to verify the certificates on my target21:07
-YoctoAutoBuilder- build #539 of nightly-multilib is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Running Sanity Tests_1 BuildImages_2 Running Sanity Tests_2 BuildImages_3 Running Sanity Tests_3 BuildImages_4] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/53921:10
*** ant_home <ant_home!~ant__@host207-253-dynamic.44-79-r.retail.telecomitalia.it> has joined #yocto21:16
-YoctoAutoBuilder- build #526 of nightly-mips-lsb is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/52621:20
fishey1Is there a package or option I could include or use to cause the -dbg packages for all packages in my image to also be installed?21:20
*** paulg <paulg!~paulg@184-94-55-234.dedicated.allstream.net> has joined #yocto21:21
*** WarheadsSE <WarheadsSE!~WarheadsS@c-174-54-190-115.hsd1.pa.comcast.net> has joined #yocto21:22
WarheadsSEWould anyone happen to be aware of an existing recipe for linux kernel, drm-intel-nightly branch?21:22
WarheadsSEIf not, has anyone ever seen this one pop up? "Failure expanding variable WORKDIR, expression was ${BASE_WORKDIR}/${MULTIMACH_TARGET_SYS}/${PN}/${EXTENDPE}${PV}-${PR} which triggered exception RuntimeError: maximum recursion depth exceeded while calling a Python object"21:23
jcreekmorerburton: thanks, that helped me figure it out.21:25
*** tsramos <tsramos!tsramos@nat/intel/x-qwhxtemoebscjdan> has quit IRC21:25
frayWarheadsSE the message says that something in the way 'WORKDIR' is defined failed, because it somehow become recursively defined..21:26
frayyou should be able to use 'bitbake -e' and look how it is defined.. (as well as bitbake -e <recipe>) and compare.. it might help you spot the recusion21:26
rburtonfishey1: dbg-pkgs IMAGE_FEATURE21:28
*** drou <drou!52e867a5@gateway/web/freenode/ip.82.232.103.165> has quit IRC21:28
WarheadsSEfray: understood, going spelunking.21:29
*** vmeson <vmeson!~rmacleod@128.224.252.2> has quit IRC21:29
WarheadsSEwell, -e <package> results in only that warning.21:31
WarheadsSEand nothing seems to jump at be about recursion, looking at the set values.21:36
*** pohly <pohly!~pohly@p5DE8F322.dip0.t-ipconnect.de> has quit IRC21:38
*** c10ud <c10ud!~c10ud@emesene/dictator/c10ud> has quit IRC21:42
* WarheadsSE smh, moved PR= below an inc.21:43
* WarheadsSE viola *jazzhands*21:44
*** maxin <maxin!~maxin@dsl-espbrasgw1-54fa70-49.dhcp.inet.fi> has quit IRC21:44
fishey1rburton: thanks21:45
*** cbzx <cbzx!~cbzx@CPE0015f275ecd5-CM00195edd810c.cpe.net.cable.rogers.com> has joined #yocto21:51
-YoctoAutoBuilder- build #189 of ptest-x86 is complete: Failure [failed BuildImages] Build details are at http://autobuilder.yoctoproject.org/main/builders/ptest-x86/builds/18921:55
*** roccof <roccof!~rocco@95.232.137.133> has joined #yocto21:56
-YoctoAutoBuilder- build #192 of nightly-rpm-non-rpm is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-rpm-non-rpm/builds/19221:59
*** [Sno] <[Sno]!~sno@p578b540c.dip0.t-ipconnect.de> has joined #yocto22:02
*** WarheadsSE <WarheadsSE!~WarheadsS@c-174-54-190-115.hsd1.pa.comcast.net> has left #yocto22:16
*** sjolley <sjolley!~sjolley@134.134.139.78> has quit IRC22:22
*** paulg <paulg!~paulg@184-94-55-234.dedicated.allstream.net> has quit IRC22:26
*** paulg <paulg!~paulg@184-94-55-234.dedicated.allstream.net> has joined #yocto22:28
*** Vardon3 <Vardon3!~var@mav44-1-78-229-65-140.fbx.proxad.net> has joined #yocto22:36
*** Vardon3 <Vardon3!~var@mav44-1-78-229-65-140.fbx.proxad.net> has joined #yocto22:41
*** berton <berton!~fabio@177.220.212.62> has quit IRC22:42
*** Vardon3 <Vardon3!~var@mav44-1-78-229-65-140.fbx.proxad.net> has quit IRC22:45
*** Vardon3 <Vardon3!~var@mav44-1-78-229-65-140.fbx.proxad.net> has joined #yocto22:45
*** Vardon3 <Vardon3!~var@mav44-1-78-229-65-140.fbx.proxad.net> has quit IRC22:45
*** Vardon3 <Vardon3!~var@mav44-1-78-229-65-140.fbx.proxad.net> has joined #yocto22:48
-YoctoAutoBuilder- build #537 of nightly-x86-lsb is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-lsb/builds/53722:50
*** wolfywolf <wolfywolf!ad0aec75@gateway/web/freenode/ip.173.10.236.117> has joined #yocto22:50
wolfywolfG'day all22:50
wolfywolfDoes anyone know why the meta-intel BSP is missing for the Jethro release?22:51
frayJethro was released on Tuesday of last week.  I'd guess meta-intel isn't ready yet22:52
*** smo <smo!canuck@me.wantsmo.com> has quit IRC22:52
*** smo <smo!canuck@me.wantsmo.com> has joined #yocto22:52
wolfywolfI was thinking that might be the case but seems strange they would put broken links on the YP page (https://www.yoctoproject.org/downloads/bsps)22:52
*** rburton1 <rburton1!~Adium@35.106.2.81.in-addr.arpa> has joined #yocto22:53
*** binhnk <binhnk!~binhnk@117.6.99.240> has quit IRC22:53
*** ersatzma` <ersatzma`!~vivek@78.32.176.249> has joined #yocto22:54
*** dreyna4529 <dreyna4529!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC22:54
*** kscherer <kscherer!~kscherer@128.224.252.2> has quit IRC22:54
*** rburton <rburton!~Adium@35.106.2.81.in-addr.arpa> has quit IRC22:54
*** Rallis <Rallis!~chris@208-53-195-38.static.ravenind.com> has quit IRC22:54
*** Calchan <Calchan!~calchan@gentoo/developer/calchan> has quit IRC22:54
*** bboozzoo <bboozzoo!~Maciej_Bo@staticline-31-182-60-238.toya.net.pl> has quit IRC22:54
*** geheimnis` <geheimnis`!~geheimnis@23.226.237.192> has quit IRC22:54
*** Vardon3 <Vardon3!~var@mav44-1-78-229-65-140.fbx.proxad.net> has quit IRC22:54
*** blueness_ <blueness_!~blueness@gentoo/developer/blueness> has quit IRC22:54
*** fledermaus <fledermaus!~vivek@78.32.176.249> has quit IRC22:54
*** csanchezdll <csanchezdll!~user@galileo.kdpof.com> has quit IRC22:54
*** RP <RP!~richard@5751f4a1.skybroadband.com> has quit IRC22:54
*** csmart <csmart!~quassel@45.55.219.131> has quit IRC22:54
*** geheimnis` <geheimnis`!~geheimnis@23.226.237.192> has joined #yocto22:55
*** csmart <csmart!~quassel@45.55.219.131> has joined #yocto22:55
*** Calchan <Calchan!~calchan@gentoo/developer/calchan> has joined #yocto22:56
*** sjolley <sjolley!~sjolley@134.134.139.78> has joined #yocto22:59
*** challinan_ <challinan_!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has joined #yocto22:59
*** marquiz <marquiz!~marquiz@134.134.139.70> has joined #yocto22:59
*** igor3 <igor3!~Igor_Stop@134.134.139.77> has joined #yocto22:59
*** loggerbox <loggerbox!~todor@134.134.139.77> has joined #yocto22:59
*** cesdv <cesdv!~cesdv@client-188-168-43-165.spb-teleport.ru> has joined #yocto23:00
*** Jackie <Jackie!~quassel@106.120.101.38> has joined #yocto23:00
*** tf_ <tf_!~tomas@r-finger.com> has joined #yocto23:00
*** tripzero <tripzero!tripzero@nat/intel/x-rjhbzyyyfbrfrhpb> has joined #yocto23:00
*** sjolley <sjolley!~sjolley@134.134.139.78> has quit IRC23:00
*** Jackie is now known as Guest5432423:00
*** fmeerkoetter <fmeerkoetter!~quassel@service.basyskom.com> has quit IRC23:01
*** bfederau_ <bfederau_!~quassel@service.basyskom.com> has quit IRC23:01
*** fmeerkoetter <fmeerkoetter!~quassel@service.basyskom.com> has joined #yocto23:01
*** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto23:01
*** challinan <challinan!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has quit IRC23:06
*** psnsilva <psnsilva!~psnsilva@193-126-29-154.net.novis.pt> has quit IRC23:06
*** Crofton|work <Crofton|work!~balister@pool-71-171-14-127.ronkva.east.verizon.net> has quit IRC23:06
*** Guest87614 <Guest87614!~quassel@106.120.101.38> has quit IRC23:06
*** tripzero_ <tripzero_!~tripzero@134.134.139.70> has quit IRC23:06
*** cesdv_ <cesdv_!~cesdv@client-188-168-43-165.spb-teleport.ru> has quit IRC23:06
*** vquicksilver <vquicksilver!~nobody@gentoo/contributor/vquicksilver> has quit IRC23:06
*** joseppc <joseppc!~Josep@sestofw01.enea.se> has quit IRC23:06
*** marquiz_ <marquiz_!marquiz@nat/intel/x-pseqaxnyjsmldmkr> has quit IRC23:06
*** igor <igor!~Igor_Stop@134.134.139.77> has quit IRC23:06
*** tf <tf!~tomas@r-finger.com> has quit IRC23:06
*** loggerbo1 <loggerbo1!~todor@134.134.139.77> has quit IRC23:06
*** rodgort <rodgort!~rodgort@105.ip-167-114-152.net> has quit IRC23:06
*** blueness_ <blueness_!~blueness@cpe-74-77-145-97.buffalo.res.rr.com> has joined #yocto23:07
*** binhnk <binhnk!~binhnk@117.6.99.240> has joined #yocto23:08
*** bboozzoo <bboozzoo!~Maciej_Bo@staticline-31-182-60-238.toya.net.pl> has joined #yocto23:08
*** rodgort <rodgort!~rodgort@2607:5300:100:200::160d> has joined #yocto23:08
*** dvhart <dvhart!~dvhart@134.134.137.73> has quit IRC23:09
*** RP <RP!~richard@5751f4a1.skybroadband.com> has joined #yocto23:11
*** joseppc <joseppc!~Josep@sestofw01.enea.se> has joined #yocto23:13
*** Crofton|work <Crofton|work!~balister@pool-71-171-14-127.ronkva.east.verizon.net> has joined #yocto23:13
*** psnsilva <psnsilva!~psnsilva@193-126-29-154.net.novis.pt> has joined #yocto23:13
*** roccof <roccof!~rocco@95.232.137.133> has quit IRC23:15
*** vquicksilver <vquicksilver!~nobody@gentoo/contributor/vquicksilver> has joined #yocto23:15
*** ersatzma` is now known as fledermaus23:21
*** sjolley <sjolley!~sjolley@134.134.139.78> has joined #yocto23:22
*** sjolley <sjolley!~sjolley@134.134.139.78> has quit IRC23:24
*** madisox <madisox!~madison@216-75-232-11.static.wiline.com> has joined #yocto23:44
*** Guest54324 <Guest54324!~quassel@106.120.101.38> has quit IRC23:45
*** Jackie <Jackie!~quassel@106.120.101.38> has joined #yocto23:46
*** Jackie is now known as Guest593123:47
*** stwcx <stwcx!~stwcx@32.97.110.52> has quit IRC23:49
*** dreyna4529 <dreyna4529!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto23:50
*** roccof <roccof!~rocco@95.232.137.133> has joined #yocto23:52

Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!