Tuesday, 2015-02-24

*** ulf` <ulf`!~ulf@> has quit IRC00:01
*** sarahsharp <sarahsharp!~sarah@> has quit IRC00:03
*** alimon <alimon!alimon@nat/intel/x-ivmcljxwqjmcogda> has quit IRC00:03
*** benjamirc <benjamirc!besquive@nat/intel/x-vgazyisvyawtglmb> has quit IRC00:10
*** ulf` <ulf`!ulf@nat/intel/x-qwkqetycbkjzzesx> has joined #yocto00:17
*** Nitin <Nitin!~nakamble@> has joined #yocto00:17
*** rewitt <rewitt!~rewitt@> has quit IRC00:28
*** onoffon is now known as khem`00:51
*** melio_cc <melio_cc!~melio_cc@c-75-67-202-137.hsd1.ma.comcast.net> has joined #yocto01:09
*** sameo <sameo!samuel@nat/intel/x-nymylgsxdaprjmbf> has quit IRC01:15
*** khem` is now known as khem[away]01:16
*** khem[away] is now known as khem`01:19
*** khem` is now known as khem[away]01:19
*** khem[away] is now known as khem`01:20
*** khem` is now known as khem[away]01:20
*** khem[away] is now known as khem`01:20
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC01:25
*** khem` is now known as khem[away]01:46
*** khem[away] is now known as khem`01:53
*** khem` is now known as khem[away]01:54
*** khem[away] is now known as khem`01:54
*** nicktick <nicktick!~john@unaffiliated/nicktick> has joined #yocto01:55
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has quit IRC01:59
*** khem` is now known as khem[away]02:07
*** khem[away] is now known as khem`02:07
*** khem` is now known as khem[away]02:07
*** khem[away] is now known as khem`02:07
*** khem` is now known as khem[away]02:08
*** khem[away] is now known as khem`02:08
*** nicktick1 <nicktick1!~john@> has joined #yocto02:09
*** nicktick <nicktick!~john@unaffiliated/nicktick> has quit IRC02:09
*** khem` is now known as khem[away]02:16
*** khem[away] is now known as khem`02:16
*** evanp <evanp!~evan@> has joined #yocto02:18
*** khem` is now known as khem[away]02:20
*** khem[away] is now known as khem`02:20
*** evanp <evanp!~evan@> has quit IRC02:21
*** evanp <evanp!evan@nat/intel/x-xpayetfrxqucwdwg> has joined #yocto02:22
*** alimon <alimon!~alimon@187-176-43-14.dynamic.axtel.net> has joined #yocto02:23
*** khem` is now known as khem[away]02:24
*** khem[away] is now known as khem`02:24
*** khem` is now known as khem[away]02:28
*** khem[away] is now known as khem`02:28
*** aehs29 <aehs29!aehernan@nat/intel/x-qsrhtterksskwqma> has quit IRC02:34
*** alimon <alimon!~alimon@187-176-43-14.dynamic.axtel.net> has quit IRC02:34
*** varibull <varibull!~varibull@ta.tainstruments.com> has quit IRC02:36
*** alimon <alimon!~alimon@187-176-43-14.dynamic.axtel.net> has joined #yocto02:37
chankitwhere can i see the definition of do_patch?02:44
*** khem` is now known as khem[away]02:45
*** khem[away] is now known as khem`02:46
*** khem` is now known as khem[away]02:53
*** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC02:55
*** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto02:57
*** khem[away] is now known as khem`03:00
*** khem` is now known as khem[away]03:05
*** trj <trj!~trj@82-69-47-156.dsl.in-addr.zen.co.uk> has quit IRC03:12
*** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC03:18
*** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC03:19
*** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto03:21
*** trj <trj!~trj@82-69-47-156.dsl.in-addr.zen.co.uk> has joined #yocto03:21
*** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto03:23
*** Nilesh_ <Nilesh_!~minda@> has joined #yocto03:31
*** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC03:31
*** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto03:32
*** tismith <tismith!~toby@> has quit IRC03:38
*** tismith <tismith!~toby@> has joined #yocto03:45
*** hundeboll <hundeboll!~hundeboll@open-mesh.org/catwoman/hundeboll> has quit IRC03:45
*** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC03:46
*** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC03:47
*** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto03:52
*** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto03:53
*** melio_cc <melio_cc!~melio_cc@c-75-67-202-137.hsd1.ma.comcast.net> has quit IRC03:54
*** OutOfNoWhere <OutOfNoWhere!~rpb@> has quit IRC03:58
*** khem[away] is now known as khem`04:04
*** hundeboll <hundeboll!~hundeboll@open-mesh.org/catwoman/hundeboll> has joined #yocto04:11
*** khem` is now known as khem[away]04:12
*** nicktick1 <nicktick1!~john@> has quit IRC04:22
*** nicktick <nicktick!~john@unaffiliated/nicktick> has joined #yocto04:23
-YoctoAutoBuilder- build #207 of nightly-ppc-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/builds/20704:31
*** tismith <tismith!~toby@> has quit IRC04:31
*** khem[away] is now known as khem`04:32
*** tismith <tismith!~toby@> has joined #yocto04:43
*** fitzsim <fitzsim!~user@2001:420:284a:1300:21c:c4ff:fe73:2d74> has quit IRC04:45
*** behanw <behanw!~behanw@2001:470:b26c:0:ad3a:f60b:f9d4:e3dd> has quit IRC04:52
chankitwhere can i see the definition of do_patch04:56
nrossichankit: depends if you want the source or just want to see what its doing, if you want to see what its doing 'bitbake <foo> -e > temp', open temp and search for 'do_patch()'05:12
*** aehs29 <aehs29!aehernan@nat/intel/x-kkofsvgffyuwkfzp> has joined #yocto05:17
*** AndersD <AndersD!~anders@c-89-160-69-55.cust.bredband2.com> has joined #yocto05:21
*** aehs29 <aehs29!aehernan@nat/intel/x-kkofsvgffyuwkfzp> has left #yocto05:24
*** e8johan <e8johan!~quassel@> has joined #yocto05:35
*** Svendsen <Svendsen!~Thunderbi@0128800289.0.fullrate.dk> has quit IRC05:48
*** tomwoehlke <tomwoehlke!~tomwoehlk@pool-100-40-154-150.pghkny.fios.verizon.net> has quit IRC05:54
*** Crofton|road <Crofton|road!~balister@> has quit IRC05:58
*** alimon <alimon!~alimon@187-176-43-14.dynamic.axtel.net> has quit IRC06:06
*** Nilesh_ <Nilesh_!~minda@> has quit IRC06:12
*** behanw <behanw!~behanw@2001:470:b26c:0:3030:a2c6:1344:5d3b> has joined #yocto06:15
nerdboyisn't there a do_patch log?06:16
nrossinerdboy: i think there is also a run.do_patch, but i thought that was some python that calls into bitbake06:19
nerdboythere should be both logs and scripts06:20
khem`its python06:23
khem`so no logs06:23
khem`unless something goes wrong06:23
*** hamis <hamis!~irfan@> has joined #yocto06:24
*** kanupatar <kanupatar!79f4c042@gateway/web/freenode/ip.> has joined #yocto06:25
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto06:25
kanupatarMay I know, yocto build engine is supported by jenkins?06:25
*** Nilesh_ <Nilesh_!~minda@> has joined #yocto06:27
*** grma <grma!~gruberm@chello213047201250.tirol.surfer.at> has joined #yocto06:28
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC06:32
khem`kanupatar: it is in a way06:43
khem`its agnostic to autobuilders06:43
kanupatarkhem`:  means?06:45
khem`mean you can use buildbot jenkins, your own scripts06:45
khem`doesnt matter06:45
nerdboyi would use the bash script window in jenkins to start...06:47
nerdboyunless somebody made a plugin maybe06:47
*** pohly <pohly!~pohly@p5DE8ED5F.dip0.t-ipconnect.de> has joined #yocto07:15
*** Svendsen <Svendsen!~Thunderbi@> has joined #yocto07:18
*** SorenHolm <SorenHolm!~quassel@> has joined #yocto07:25
chankithow do I set yocto to run kernel 3.19 in http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-dev/ ? I tried setting PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-dev" in local.conf but it only checks out 3.1707:26
*** wadim_ <wadim_!~egorov@mail.phycard.de> has joined #yocto07:28
*** sujith_h <sujith_h!~sharidas@kde/developers/sujithh> has left #yocto07:30
*** TobSnyder <TobSnyder!~schneider@ip92341b76.dynamic.kabel-deutschland.de> has joined #yocto07:31
*** _4urele_ <_4urele_!~aurele@srvmail.castel.fr> has joined #yocto07:34
*** dmoseley <dmoseley!~dmoseley@cpe-174-096-222-251.carolina.res.rr.com> has quit IRC07:35
*** MDR_ <MDR_!~MRustad@static-50-43-14-17.bvtn.or.frontiernet.net> has joined #yocto07:40
*** dmoseley <dmoseley!~dmoseley@cpe-174-096-222-251.carolina.res.rr.com> has joined #yocto07:44
*** hitlin37 <hitlin37!uid16371@gateway/web/irccloud.com/x-yzqpgigqvhnxmrvh> has joined #yocto07:56
*** rburton <rburton!~Adium@> has joined #yocto08:00
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-hyzidqesrcrydejp> has joined #yocto08:03
*** jbrianceau_away is now known as jbrianceau08:03
*** MDR_ <MDR_!~MRustad@static-50-43-14-17.bvtn.or.frontiernet.net> has quit IRC08:07
chankithow do I set yocto to run kernel 3.19 in http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-dev/ ? I tried setting PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-dev" in local.conf but it only checks out 3.1708:09
*** e8johan <e8johan!~quassel@> has quit IRC08:10
*** e8johan <e8johan!~quassel@> has joined #yocto08:12
*** SorenHolm <SorenHolm!~quassel@> has quit IRC08:14
*** SorenHolm <SorenHolm!~quassel@> has joined #yocto08:16
*** tmpsantos <tmpsantos!tmpsantos@nat/intel/x-pfjmwzimwltenkol> has joined #yocto08:17
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto08:23
*** e8johan <e8johan!~quassel@> has quit IRC08:23
*** BlauskaerM <BlauskaerM!~Fever@h-142-6.a357.priv.bahnhof.se> has joined #yocto08:33
*** e8johan <e8johan!~quassel@> has joined #yocto08:33
BlauskaerMMorning gentlemen08:34
BlauskaerMIf someone has some time to spare, I have a question about how to add a custom driver to my yocto image08:34
*** sameo <sameo!~samuel@> has joined #yocto08:35
BlauskaerMI think I have figured out how to add a hello world program, using the yocto build flow (not 100% sure it is correct though) but it seems that it's a different approach when it comes to drivers.08:36
*** tecdroid <tecdroid!~icke@tmo-096-224.customers.d1-online.com> has joined #yocto08:37
*** mago_ <mago_!~mago@smtp.hms.se> has quit IRC08:37
BlauskaerMAnyone knows what steps I should take to accomplish this? Like good documents to read or available examples?08:38
*** mago_ <mago_!~mago@smtp.hms.se> has joined #yocto08:39
JEEBsvhmm, is EFI_PROVIDER more of an image or distro thing?08:41
*** e8johan <e8johan!~quassel@> has quit IRC08:43
nerdboyBlauskaerM: can i assume you mean kernel driver?08:53
BlauskaerMnerdboy: Yeah08:53
*** e8johan <e8johan!~quassel@> has joined #yocto08:53
*** patrickz <patrickz!~Thunderbi@> has quit IRC08:54
nerdboydocs are your friend, at least in the better open source projects08:54
nerdboyshocking, i know...08:54
BlauskaerMnerdboy: Looks good, can start with this and come back later :)08:55
ericbuttersnerdboy: but i think when it comes to scc and cfg files that won't work08:55
ericbutterswe saw yesterday some conversation here about that08:56
* nerdboy usually breaks the rules with kernel sources anyway08:56
nerdboycan't get in trouble pointing at the official docs...08:56
ericbuttersbetter to do some patch and include this to the recipe-kernel/linxu*08:57
nerdboythe linux-yocto kernel is the current "official" way to do it, but not the only way08:57
nerdboyolder model recipes are still there08:57
nerdboycan also go back to previous doc releases for those08:58
nerdboysometimes you hack your own fix08:58
*** e8johan <e8johan!~quassel@> has quit IRC08:58
nerdboymostly i deploy manual-built kernels right now, so i probably can't be much help unless it becomes my problem at some point08:59
nerdboywhat i need for project isn't available in yocto kernels right now unless i make my own09:00
nerdboywhich i eventually will for beaglebone09:00
JEEBsvinteresting, would have thought that getting "ConvertPages: failed to find range ..." from gummiboot is a fatal error, but after that it happily chugs along booting the kernel :D09:00
nerdboyericbutters: what is the machine in this case?09:01
nerdboyand you are always free to bbappend the kernel recipe for whatever...09:02
ericbuttersnerdboy: it was some kind of sierra wireless thing.. i only read it here, where the question was similar to what BlauskaerM asked.. It was not my problem.. it was reported by someone else09:03
ericbuttersbut anyway i think using a patch and scc/cfg files located in recipes-kernel/* is a good way09:04
nerdboycustom firmware maybe?09:04
*** e8johan <e8johan!~quassel@> has joined #yocto09:04
*** dvorkbjel <dvorkbjel!~viskestel@li607-220.members.linode.com> has quit IRC09:04
nerdboythe config thing is the documented way09:04
nerdboyolder maybe, but still works09:04
ericbutterssome simple patch that provides the kernel driver and scc/cfg that brings the kernel configuration09:05
*** kanupatar <kanupatar!79f4c042@gateway/web/freenode/ip.> has quit IRC09:05
*** Pierre_ <Pierre_!6dbe6fab@gateway/web/freenode/ip.> has quit IRC09:05
*** r23s <r23s!d0b90c36@gateway/web/freenode/ip.> has quit IRC09:05
nerdboythat's 1.3/1/4 but still valid09:06
chankithow do I set yocto to run kernel 3.19 in http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-dev/ ? I tried setting PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-dev" in local.conf but it only checks out 3.1709:06
nerdboyericbutters: it's in the lab09:06
nerdboychankit: did you also add preferred_version?09:07
chankitnerdboy: no. how do I add it?09:07
chankitis it something like PREFERRED_VERSION=3.19?09:08
*** tecdroid <tecdroid!~icke@tmo-096-224.customers.d1-online.com> has left #yocto09:09
nerdboythat should work, but PREFERRED_VERSION_linux-mainline = "3.19%" is better09:09
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC09:09
nerdboysorry, paste error09:10
nerdboylinux-yocto-dev in your case09:10
nerdboyand spaces count09:11
BlauskaerMnerdboy: Is the "%" symbol a wildcard?09:11
* nerdboy tired after 4 days conference and travel09:12
nerdboyif you want, you can check yocto crash course slides and see if they help09:13
nerdboywe didn't get a short course, just an hour talk09:13
chankitnerdboy: doesn't do good.. I got " preferred version 3.19% of linux-yocto-dev not available (for item virtual/kernel)"09:13
nerdboyit has to be there09:14
nerdboythe version needs to exist rather09:14
BlauskaerMnerdboy: Have looked through them but it didn't really give me any clarity unfortunately =/09:14
nerdboydo a find in recipe tree09:14
nerdboyBlauskaerM: that one09:15
*** belen <belen!Adium@nat/intel/x-leosaaeraaxsevdk> has joined #yocto09:15
*** memcpy <memcpy!~memcpy@unaffiliated/memcpy> has joined #yocto09:15
nerdboychankit: what is latest yocto-dev in poky master?09:16
* nerdboy flossing09:16
chankitnerdboy: not sure but according to http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-dev/ it has 3.1909:16
BlauskaerMnerdboy: Oh, haven't seen these before. Thanks :)09:16
BlauskaerMThought you meant the lab pdf09:17
*** SorenHolm <SorenHolm!~quassel@> has quit IRC09:17
nerdboythat summarizes/explains the lab a little bit09:17
nerdboyat least i hope it does...09:17
nerdboyplus other stuff09:18
nerdboychankit: what machine?09:19
nerdboyyou might need to help it a little09:20
chankitnerdboy: standard/common-pc-64/base09:21
nerdboygrep COMPATIBLE_MACHINE09:21
chankitfrom where should I grep that?09:22
nerdboymight only support qemu machines09:22
nerdboyyou could set COMPATIBLE_MACHINE = "your machine"09:22
nerdboymight need to set commit hash too09:22
nerdboyin poky dir grep -R09:23
chankitnerdboy: I got quite a lot of output ..what u looking for?09:26
nerdboyin order to bump the kernel your machine must be supported by 3.19 recipe09:27
nerdboyyou can override with the above setting09:27
nerdboyit's actually in the handout notes i just pointed at09:28
* nerdboy needs another ploy so he can finish flossing/brushing...09:29
chankitso I should set COMPATIBLE_MACHINE_linux-dev_yocto = "my machine" ?09:30
nerdboyno, actually  COMPATIBLE_MACHINE_machine = "machine"09:32
nerdboyi know, kinda weird but...09:32
nerdboyyou're overriding it09:32
nerdboyas in COMPATIBLE_MACHINE_beaglebone = "beaglebone"09:33
chankitnerdboy: so I put that in local.conf right?09:33
*** bluelightning <bluelightning!~paul@> has joined #yocto09:33
*** bluelightning <bluelightning!~paul@> has quit IRC09:33
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto09:33
nerdboyyup that shoudl work09:34
bluelightningmorning all09:34
nerdboyassuming you have a beaglebone or change it to your machine09:35
nerdboybluelightning: morning for you09:35
nerdboyi'm still trying to brush my teeth...09:35
nerdboytop-o-the-morning for you i hope?09:36
chankitnerdboy: sorry to ruin your morning but that approach is negative09:37
chankitnerdboy: I set my machine to genericx86-64 so there should be a 3.19 kernel available?09:37
chankitsorry..not an expert in navigating linux-dev-yocto page09:38
chankitand I set the compatible machine variable by COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"09:39
chankitso not sure if I'm doing it right09:39
chankitnerdboy: I'm heading off now so I will check with you again later if you don't mind09:42
nerdboywhatever your actual MACHINE is, use that09:43
nerdboyand you should set it in local.conf with =09:43
nerdboyi know this works because i just did it with beaglebone and linux-yocto09:44
nerdboytrust me...09:44
nerdboyon master in my case, but should also work on release branches09:45
*** jimBaxter <jimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto09:47
*** FrankSansC <FrankSansC!~frank@LVelizy-156-45-9-168.w80-11.abo.wanadoo.fr> has quit IRC09:50
*** memcpy <memcpy!~memcpy@unaffiliated/memcpy> has quit IRC09:53
*** e8johan <e8johan!~quassel@> has quit IRC10:00
*** kevin_t <kevin_t!~Thunderbi@> has quit IRC10:01
*** kevin_t <kevin_t!~Thunderbi@> has joined #yocto10:08
*** e8johan <e8johan!~quassel@> has joined #yocto10:33
*** kevin_t <kevin_t!~Thunderbi@> has quit IRC10:56
*** patrickz <patrickz!~Thunderbi@> has joined #yocto10:56
*** kevin_t <kevin_t!~Thunderbi@> has joined #yocto10:56
*** kevin_t <kevin_t!~Thunderbi@> has quit IRC11:03
*** kevin_t1 <kevin_t1!~Thunderbi@> has joined #yocto11:04
*** kevin_t1 <kevin_t1!~Thunderbi@> has quit IRC11:12
*** sighack <sighack!~kshitij@> has joined #yocto11:17
sighackHi, can anyone help me to enable /proc on my device??11:18
sighackI have enabled the proc filesystem through the kernel configuration, but when i do ifconfig i get an error : "Warning: cannot open /proc/net/dev (No such file or directory). Limited output."11:19
rburtonhave you mounted it?11:24
rburton(the default fstab mounts it)11:24
*** belen <belen!Adium@nat/intel/x-leosaaeraaxsevdk> has quit IRC11:30
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto11:54
*** ant_work <ant_work!~ant__@host54-128-static.10-188-b.business.telecomitalia.it> has joined #yocto11:55
*** varibull <varibull!~varibull@ta.tainstruments.com> has joined #yocto11:59
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC12:00
*** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has joined #yocto12:04
*** AndersD <AndersD!~anders@c-89-160-69-55.cust.bredband2.com> has quit IRC12:07
*** belen <belen!Adium@nat/intel/x-hefnunkfpfnxrpit> has joined #yocto12:07
*** warthog9 <warthog9!~warthog9@> has quit IRC12:18
*** Nilesh_ <Nilesh_!~minda@> has quit IRC12:19
*** chankit11 <chankit11!~oneam@> has joined #yocto12:29
*** memcpy <memcpy!~memcpy@unaffiliated/memcpy> has joined #yocto12:29
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto12:39
*** warthog9 <warthog9!~warthog9@> has joined #yocto12:39
*** memcpy <memcpy!~memcpy@unaffiliated/memcpy> has quit IRC12:43
*** ntl <ntl!~ntl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has quit IRC12:46
*** warthog9 <warthog9!~warthog9@> has quit IRC12:51
*** warthog9 <warthog9!~warthog9@> has joined #yocto12:55
*** ntl <ntl!~ntl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has joined #yocto12:59
*** warthog9 <warthog9!~warthog9@> has quit IRC13:01
*** belen <belen!Adium@nat/intel/x-hefnunkfpfnxrpit> has quit IRC13:02
*** warthog9 <warthog9!~warthog9@> has joined #yocto13:06
*** e8johan <e8johan!~quassel@> has quit IRC13:08
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC13:09
*** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has quit IRC13:12
BlauskaerMHmm.... Still can't get the module over to my image.13:13
BlauskaerMNot 100 percent sure that it's getting compiled however13:14
ericbuttersBlauskaerM: remove some ";" -- that sould throw an error while compiling13:15
BlauskaerMI followed the "instructions" from the manual (http://www.yoctoproject.org/docs/1.7.1/kernel-dev/kernel-dev.html#incorporating-out-of-tree-modules) but there is something that I'm missing13:15
BlauskaerMericbutters: Will try that13:15
ericbuttersBlauskaerM: does your module need a kernel confiuration (CONFIG_)?13:16
BlauskaerMericbutters: No I dont think so? Its just a simple module that should print some text when it is loaded13:17
BlauskaerMSo nothing complicated13:17
BlauskaerMI really need a better computer to build on -_-13:22
*** vmeson <vmeson!~rmacleod@> has joined #yocto13:30
*** marka <marka!~marka@> has joined #yocto13:30
*** sighack <sighack!~kshitij@> has quit IRC13:32
BlauskaerMHmm, that was good news (and also bad)13:37
BlauskaerMI removed some ; from the module source code but I didn't get any errors while running bitbake?13:37
rburtonbitbake doesn't know that you've changed the source and won't rebuild everything just in case13:37
rburtonbitbake myrecipe -C compile will force it to recompile the recipe13:38
BlauskaerMIs there a command that I can use to clean?13:38
BlauskaerM2 sec13:38
rburtonthen rebuild the image or install the packages or whatever you want13:39
BlauskaerMThere we go13:40
BlauskaerMGot the error13:40
BlauskaerMSo every time I change the code in the module, I need to recompile it with bitbake myrecipe -C compile?13:41
BlauskaerMAnd then rebuild the image?13:41
rburtonyeah, but you can just copy the package with the changes in to the image and install that - much shorter cycle13:41
BlauskaerMSo after I have compiled the module I can just copy the .ko file from the tmp dir to the image?13:42
*** e8johan <e8johan!~quassel@> has joined #yocto13:43
BlauskaerMWill try to fix the module file (reinsert the ;) and then compile it again so see if I can find any .ko file in the tmp dir13:45
BlauskaerMBecause that is where all end up right?13:45
rburtontmp/work/[machine]/[recipe]/deploy-* has the packages generated13:46
rburtonor packages-split has the packages before they were packaged up13:46
BlauskaerMWill check that. Waiting for bitbake to terminate :P13:47
BlauskaerMFound a directory for the module but it does not contain a deply dir?13:48
*** belen <belen!Adium@nat/intel/x-gclxzrwvhuzrpkqt> has joined #yocto13:49
*** rcw <rcw!~rwoolley@> has joined #yocto13:50
BlauskaerMMaybe that is because the compile failed?13:51
*** memcpy <memcpy!~memcpy@unaffiliated/memcpy> has joined #yocto13:53
*** e8johan <e8johan!~quassel@> has quit IRC13:58
*** belen <belen!Adium@nat/intel/x-gclxzrwvhuzrpkqt> has quit IRC14:00
*** T0mW <T0mW!~Tom@> has joined #yocto14:05
*** melio_cc <melio_cc!~melio_cc@static-194-113-26-69.axsne.net> has joined #yocto14:08
rburtonprobably, if the compile failed then it can't distribute anything14:17
*** tmpsantos <tmpsantos!tmpsantos@nat/intel/x-pfjmwzimwltenkol> has quit IRC14:26
*** cyclist <cyclist!~dan@24-207-238-91.dhcp.stls.mo.charter.com> has left #yocto14:29
BlauskaerMrburton: Sounds like it. I appeared after I fixed the source file and recompiled :)14:29
*** cyclist <cyclist!~dan@24-207-238-91.dhcp.stls.mo.charter.com> has joined #yocto14:30
dgm816hi guys.. while developing, should i clear out the tmp/cache dirs as i modify recipes in regards to making feeds? specifically, im wondering if the package-index recipe would hold multiple versions of a package for me, so i could install v1.0 of my package even if v1.1 was available..14:33
dgm816or another way.. how do i ensure that Package.gz index files contain all the packages available on the feed?14:34
bluelightningdgm816: bitbake package-index will update the feed immediately14:37
bluelightningdgm816: however, note that when a newer version of a recipe is built and packaged, the older package is deleted14:38
dgm816bluelightning, ah, ok.. so i would need 2 feeds say one for unstable/devel and the other feed stable.. to deploy for testing?14:38
bluelightningyes, you need to manage your own feeds to get that14:39
*** memcpy <memcpy!~memcpy@unaffiliated/memcpy> has quit IRC14:49
*** hamis <hamis!~irfan@> has quit IRC14:49
*** nicktick <nicktick!~john@unaffiliated/nicktick> has quit IRC14:49
*** melio_cc_ <melio_cc_!~melio_cc@static-194-113-26-69.axsne.net> has joined #yocto14:59
*** melio_cc <melio_cc!~melio_cc@static-194-113-26-69.axsne.net> has quit IRC15:02
*** Svendsen <Svendsen!~Thunderbi@> has quit IRC15:04
*** [Sno] <[Sno]!~Sno]@p578b540c.dip0.t-ipconnect.de> has quit IRC15:04
*** wadim_ <wadim_!~egorov@mail.phycard.de> has quit IRC15:10
*** fitzsim <fitzsim!~user@2001:420:284a:1300:21c:c4ff:fe73:2d74> has joined #yocto15:12
*** wadim_ <wadim_!~egorov@mail.rapiddevelopmentkit.de> has joined #yocto15:14
*** wadim_ <wadim_!~egorov@mail.rapiddevelopmentkit.de> has quit IRC15:16
*** chankit11 <chankit11!~oneam@> has quit IRC15:24
*** belen <belen!Adium@nat/intel/x-gotgykwqboybarle> has joined #yocto15:26
*** melio_cc_ <melio_cc_!~melio_cc@static-194-113-26-69.axsne.net> has quit IRC15:29
*** melio_cc <melio_cc!~melio_cc@static-194-113-26-69.axsne.net> has joined #yocto15:30
*** Crofton|road <Crofton|road!~balister@> has joined #yocto15:30
*** melio_cc <melio_cc!~melio_cc@static-194-113-26-69.axsne.net> has quit IRC15:34
*** melio_cc <melio_cc!~melio_cc@static-194-113-26-69.axsne.net> has joined #yocto15:37
*** mago_ <mago_!~mago@smtp.hms.se> has quit IRC15:43
*** melio_cc <melio_cc!~melio_cc@static-194-113-26-69.axsne.net> has quit IRC15:43
*** melio_cc <melio_cc!~melio_cc@static-194-113-26-69.axsne.net> has joined #yocto15:44
*** chankit11 <chankit11!~oneam@> has joined #yocto15:46
*** alimon <alimon!alimon@nat/intel/x-gaygrtlgmtiupmuf> has joined #yocto15:47
*** [Sno] <[Sno]!~Sno]@static-87-79-200-121.netcologne.de> has joined #yocto15:47
*** AlexVaduva <AlexVaduva!2ebd1cd2@gateway/web/freenode/ip.> has joined #yocto15:47
*** mago_ <mago_!~mago@smtp.hms.se> has joined #yocto15:48
*** jmd <jmd!~user@de.cellform.com> has joined #yocto15:51
*** Casper_ <Casper_!2eb6e353@gateway/web/freenode/ip.> has joined #yocto15:55
sjolleyYPTM:   Ready-Access Number: 8007302996/9139049836  Access Code:     2705751#15:58
sjolleyYPTM: Stephen Joined15:58
sgw_YPTM: Saul is on15:58
joeythesaintYPTM: Joe Mac here.15:59
frayYPTM: Mark here16:00
cristianiorgaYPTM: Cristian joined16:00
*** sameo <sameo!~samuel@> has quit IRC16:01
*** benjamirc <benjamirc!~besquive@> has joined #yocto16:01
AlexVaduvaYPTM: AlexVaduva here16:02
bluelightningYPTM: Paul Eggleton is on16:02
RPRichard joined16:02
*** sona <sona!4e52766f@gateway/web/freenode/ip.> has joined #yocto16:02
rburtonRoss joined16:03
*** onoffon <onoffon!~khem@unaffiliated/khem> has joined #yocto16:04
*** onoffon is now known as khem`16:06
bluelightningI'm assuming nobody heard me speaking...16:07
bluelightning(something went weird with the bridge, but since rejoining it seems fine)16:10
*** chankit11 <chankit11!~oneam@> has quit IRC16:10
rburtonbluelightning: the upgrade was stalling on a circular dependency in util-linux, i have a patch that drops the systemd dep from util-linux.  i'll verify it is mostly harmless and post if so16:11
bluelightningok, cool, thanks16:11
frayI looked them over quickly.. looks intersting16:12
rburtonkhem: you added distutils-tools.bbclass "for python3" but nothing seems to include it.  can it be deleted or am i being blind?16:13
khem`I need to jog my memory down the lane16:15
rburtonthanks :)16:15
rburtondoes anyone know distutils well?16:18
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC16:19
sjolleyYPTM is over.16:20
*** aehs29 <aehs29!aehernan@nat/intel/x-xndscjqsoucvsvmi> has joined #yocto16:21
*** aehs29 <aehs29!aehernan@nat/intel/x-xndscjqsoucvsvmi> has left #yocto16:21
khem`rburton: ok, it was a jnpr thing, there were tools packages which were slightly different16:30
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto16:30
khem`some of them internal but some were external16:30
*** AlexVaduva <AlexVaduva!2ebd1cd2@gateway/web/freenode/ip.> has quit IRC16:30
khem`I dont remeber which were all external16:30
*** benjamirc1 <benjamirc1!~besquive@> has joined #yocto16:31
khem`but I never got around to contribute them16:31
khem`as of now it looks dead code16:31
rburtonok,i'll blast it away16:31
rburtonthanks khem16:31
rburtonkhem: an opinion on http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=ross/distutils&id=4d15f590e8aeedf2e7c03cdaf02dd57ccbff5ef5 would be helpful too :)16:31
*** sona <sona!4e52766f@gateway/web/freenode/ip.> has quit IRC16:32
*** lpapp <lpapp!~lpapp@kde/lpapp> has left #yocto16:32
rburtonfor a basic package it appears to work…  just kicked a build of all of oe-core's python to see16:32
rburtonits a bit horrid in that you need to do "build —build-base install" to do an install16:32
*** benjamirc <benjamirc!~besquive@> has quit IRC16:32
*** acidfu <acidfu!~nib@> has quit IRC16:35
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has joined #yocto16:35
khem`rburton: looks ok16:35
khem`you got the order of build-base and install right16:35
rburtonok, needs to do a cd ${S} first16:35
khem`IIRC there were issues when they were interchanged on cmdline in order16:35
*** bobdog555 <bobdog555!~bobdog555@> has joined #yocto16:35
rburtonyeah build-base is an option for build16:36
rburtondiscovered that ten minutes ago :)16:36
khem`let m find that bug16:36
khem`here http://bugs.python.org/issue101111316:36
khem`are we carrying these patches ?16:37
khem`if not then I would suggest to backport them16:37
*** ant_work <ant_work!~ant__@host54-128-static.10-188-b.business.telecomitalia.it> has quit IRC16:48
*** ynezz <ynezz!ynezz@ibawizard.net> has quit IRC16:57
*** ynezz <ynezz!ynezz@ibawizard.net> has joined #yocto16:57
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has joined #yocto17:07
rburtonwell distutils —build-base is nonsense isnt it17:07
*** kevin_t <kevin_t!~Thunderbi@> has joined #yocto17:11
dgm816i have 2 packages being built.. how to i specify to opkg that only one ipk can be installed? either one is fine (personal preference, provide same functionality), but i need to be sure only one or the other is installed.. can i do this from my bitbake recipe? anyone know of an example to look at?17:11
bluelightningdgm816: RCONFLICTS_packagename1 = "packagename2"17:12
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto17:12
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has quit IRC17:12
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has quit IRC17:13
*** blitz00 <blitz00!stefans@nat/intel/x-xfexpfmkrzbpymzf> has joined #yocto17:14
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has joined #yocto17:14
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has joined #yocto17:14
realBigfootGuys, i am having trouble with Dependency Loop, after updating master repository. What is this ?17:15
bluelightningrealBigfoot: what is the dependency loop you are seeing exactly?17:16
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has quit IRC17:17
realBigfootfrom a recipe that i have changed for test proposal17:17
dgm816bluelightning, thank you again!17:17
realBigfootthe weird thing is that it was working quite fine17:17
bluelightningrealBigfoot: in general a dependency loop means that recipe A depends on recipe B depends on recipe A and therefore there is no way to satisfy the dependency relationship17:18
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has joined #yocto17:18
bluelightningrealBigfoot: without specifics I can't really advise further17:18
dgm816bluelightning, at runtime i would have to do "opkg remove package1; opkg install package2" to switch conflicting packages from one to another?17:19
realBigfootbluelightning, I see, this is enough :)17:19
bluelightningdgm816: yes17:19
dgm816thank you17:19
realBigfootbluelightning, do you know how to increase debug level to see more about where is the dependency loop ? I've tried with bitbake -D option but it was the same17:21
bluelightningwhen is the error coming up exactly?17:24
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has quit IRC17:25
realBigfootbluelightning, when compiling systemd17:25
bluelightningmore specifically? i.e. in the middle of a task? before the build even gets started?17:25
realBigfootbluelightning, before the build gets started17:27
rburtonhelps if you say what the loop is…17:27
realBigfootrburton, this is what i am trying to figure out... :(17:28
rburtonwell what is the output of bitbake?17:28
realBigfootrburton, ERROR: Unbuildable tasks were found.17:28
realBigfootThese are usually caused by circular dependencies and any circular dependency chains found will be printed below. Increase the debug level to see a list of unbuildable tasks.17:28
*** vignatti <vignatti!~vignatti@annarchy.freedesktop.org> has quit IRC17:29
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has joined #yocto17:29
bluelightninglooking at the code, it reports the dependency loop as far as I can tell...17:30
rburtoncan't be a dependency loop then i guess17:30
bluelightningrealBigfoot: does it say "Identifying dependency loops" after that ?17:31
realBigfootbluelightning, sorry the delay i was pasting it here we go:17:32
realBigfootDependency loop #1 found:17:33
realBigfoot  Task 452 (/media/project/yocto/poky/meta/recipes-core/systemd/systemd_218.bb, do_packagedata) (dependent Tasks ['systemd, do_package'])17:33
realBigfoot  Task 927 (/media/project/yocto/poky/meta/recipes-core/util-linux/util-linux_2.25.2.bb, do_package) (dependent Tasks ['pseudo, do_populate_sysroot', 'gcc-runtime, do_packagedata', 'rpm, do_populate_sysroot', 'glibc, do_packagedata', 'systemd, do_packagedata', 'util-linux, do_install', 'zlib, do_packagedata', 'file, do_populate_sysroot', 'libtool-cross, do_packagedata', 'opkg-utils, do_packagedata', 'ncurses, do_packagedata'])17:33
realBigfoot  Task 924 (/media/project/yocto/poky/meta/recipes-core/util-linux/util-linux_2.25.2.bb, do_packagedata) (dependent Tasks ['util-linux, do_package'])17:33
realBigfoot  Task 455 (/media/project/yocto/poky/meta/recipes-core/systemd/systemd_218.bb, do_package) (dependent Tasks ['pseudo, do_populate_sysroot', 'libcgroup, do_packagedata', 'libtool-cross, do_packagedata', 'util-linux, do_packagedata', 'libgcrypt, do_packagedata', 'glibc, do_packagedata', 'curl, do_packagedata', 'kmod, do_packagedata', 'opkg-utils, do_packagedata', 'systemd, do_install_ptest_base', 'systemd, do_install', 'initscripts, do_packagedata',17:33
realBigfoot'gcc-runtime, do_packagedata', 'libidn, do_packagedata', 'glib-2.0, do_packagedata', 'acl, do_packagedata', 'xz, do_packagedata', 'lz4, do_packagedata', 'rpm, do_populate_sysroot', 'readline, do_packagedata', 'file, do_populate_sysroot', 'dbus, do_packagedata', 'libcap, do_packagedata'])17:33
bluelightningrealBigfoot: please use pastebin next time17:33
*** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has quit IRC17:33
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto17:33
nerdboybluelightning: did you get all the donuts?17:34
bluelightningnerdboy: not even one :p17:35
nerdboythat's poopy17:35
realBigfootbluelightning, rburton do you know what could be the problem ? or any clue what it says ?17:35
bluelightningrealBigfoot: have you applied a systemd 218 upgrade? that's not in master...17:36
rburtonyeah, that's what i was going to say17:36
realBigfootbluelightning, i have changed... something like I said before.... but it was working, I would sent it to you after i have finished17:36
nerdboybluelightning: going to ELC maybe?17:37
bluelightningnerdboy: I think so yes17:37
rburtonrealBigfoot: you've managed to add a circular dependency betwen util-linux and systemd17:38
realBigfootrbuton that makes sense :)17:39
rburtonrealBigfoot: which is why khem's series upgrading to 218 splits util-linux in half, and why i'm just cleaning up another series that disables systemd support in util-linux17:39
nerdboybluelightning: good, me too17:39
nerdboybluelightning: old speckled hen at a place down the street17:39
* nerdboy hopes he's still there17:40
* nerdboy working towards elc slide deadline17:41
realBigfootrburton, thanks! It was the perfect tip.. it worked perfect17:42
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has quit IRC17:42
*** melio_cc_ <melio_cc_!~melio_cc@static-194-113-26-69.axsne.net> has joined #yocto17:42
nerdboypeople seemed to like yocto crash course talk at scale17:44
*** melio_cc <melio_cc!~melio_cc@static-194-113-26-69.axsne.net> has quit IRC17:46
* nerdboy frowns at the meeting alarm17:47
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has joined #yocto17:50
Casper_Hi! Potential Yocto newbie here. I want to learn how to cross compile SW packages for BeagleBone running Angstrom 2012.12 so that I could install .ipk packages which are not readily available through opkg. Yocto (Poky) and BitBake came up a lot when searching the web. But always as a build system for complete Linux distributions. I only need to build a specific package . Is Yocto Project the right way to go or would you recommend an a17:50
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has quit IRC17:51
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has joined #yocto17:51
*** melio_cc_ <melio_cc_!~melio_cc@static-194-113-26-69.axsne.net> has quit IRC17:54
*** melio_cc <melio_cc!~melio_cc@static-194-113-26-69.axsne.net> has joined #yocto17:54
*** TobSnyder <TobSnyder!~schneider@ip92341b76.dynamic.kabel-deutschland.de> has quit IRC17:55
*** melio_cc_ <melio_cc_!~melio_cc@static-194-113-26-69.axsne.net> has joined #yocto17:57
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has quit IRC17:58
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has joined #yocto17:59
*** melio_cc <melio_cc!~melio_cc@static-194-113-26-69.axsne.net> has quit IRC18:00
*** belen1 <belen1!Adium@nat/intel/x-ztvbbgfhemqrbnzh> has joined #yocto18:00
*** belen <belen!Adium@nat/intel/x-gotgykwqboybarle> has quit IRC18:01
*** Nitin <Nitin!~nakamble@> has quit IRC18:05
*** rewitt <rewitt!~rewitt@> has joined #yocto18:06
*** khem` is now known as khem[away]18:11
*** jmd <jmd!~user@de.cellform.com> has quit IRC18:11
*** jmd <jmd!~user@de.cellform.com> has joined #yocto18:11
*** khem[away] is now known as khem`18:12
neverpanicCasper_: your message was cut off after "would you recommand an a"18:13
*** belen <belen!Adium@nat/intel/x-nxmbwwbbpfqetvgh> has joined #yocto18:15
*** belen <belen!Adium@nat/intel/x-dihpwowkikagzhia> has joined #yocto18:16
Casper_neverpanic: Was it indeed? Strange. I can see the whole message. Thanks for letting me know. The message goes on like this: "would you recommend an alternative approach? Thanks."18:16
neverpanicCasper_: IRC has a maximum line length; the server truncates the message.18:16
*** jbrianceau is now known as jbrianceau_away18:16
neverpanicbitbake can build .ipks. I'm not sure how they'd do compatibility-wise to your existing system, but if you use the same version or use an SDK you should be able to build a working package18:17
*** xerent <xerent!xerent@compose.lokalen.org> has quit IRC18:18
* kergoth likes irc clients that break up long messages automatically :)18:18
*** belen1 <belen1!Adium@nat/intel/x-ztvbbgfhemqrbnzh> has quit IRC18:18
dgm816how would i list a recipe in a image recipe to be built, but not necessarily installed in the image? i can use DEPENDS (fake a build time depend) but that seems hacky18:20
bluelightningdgm816: EXTRA_IMAGEDEPENDS += "..."18:21
*** melio_cc_ <melio_cc_!~melio_cc@static-194-113-26-69.axsne.net> has quit IRC18:22
dgm816ok, i saw that.. i thought that was only for bootloaders and such..18:22
dgm816i guess that will make ipk's and just not install them within the image?18:23
*** melio_cc <melio_cc!~melio_cc@static-194-113-26-69.axsne.net> has joined #yocto18:23
bluelightningdgm816: what are you trying to do exactly?18:26
dgm816i want to build package1 and package2.. but only 1 should be installed.. however, i want to put them both up on the feeds.. so i can 'opkg remove packag1; opkg install package2' if that one is preferred..18:27
dgm816it relates to my earlier question really..18:27
dgm816correction, only one installed in the image at a time..18:27
*** xerent <xerent!xerent@compose.lokalen.org> has joined #yocto18:29
bluelightningok, well in that case I would have to assume it's not the only package you want to be available alongside the image18:29
bluelightningin which case, you should consider creating a meta recipe which depends on the other recipes you want packaged but not installed18:30
bluelightning(basically just create a recipe that contains "inherit meta" and DEPENDS on all of the things that should build when you build it)18:30
nerdboyneverpanic: you would want to build at least the metatoolchain target for the release on your beaglebone18:31
dgm816bluelightning, that sounds good.. i'll proceed that way.. thank you..18:32
*** hitlin37 <hitlin37!uid16371@gateway/web/irccloud.com/x-yzqpgigqvhnxmrvh> has quit IRC18:32
nerdboynot sure what the image is, but ideally you can "bitbake image_name -c populate_sdk"18:32
*** aehs29 <aehs29!~aehernan@> has joined #yocto18:32
neverpanicnerdboy: you meant Casper_, right?18:32
*** Nitin <Nitin!~nakamble@> has joined #yocto18:33
nerdboyscroll fail...18:33
*** aehs29 <aehs29!~aehernan@> has left #yocto18:33
dgm816bluelightning, so i will create a meta-pkg-name which depends on my image recipe.. i'd then issue 'bitbake meta-pkg-name' and it should take care to build the image as well?18:34
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC18:34
dgm816and add "DEPENDS += 'package1 package2'" to the meta recipe18:34
nerdboyCasper_: ^^  meta-toolchain will build you a toolchain with minimal sysroot, the other one is full sdk but needs an image target18:35
*** benjamirc1 <benjamirc1!~besquive@> has quit IRC18:36
rewittdgn816: You would actually want to use "RDEPENDS" for the packages, "DEPENDS" essentially means do_populate_sysroot() has ran for those recipes, "RDEPENDS" would be if you need the packaging routine to have ran18:38
*** Nitin1 <Nitin1!nakamble@nat/intel/x-glszonqcwyfekmxo> has joined #yocto18:39
*** Nitin <Nitin!~nakamble@> has quit IRC18:39
rewittdgm816: Whoops I mistyped your id ^^ applies to you :)18:39
*** belen <belen!Adium@nat/intel/x-dihpwowkikagzhia> has quit IRC18:40
dgm816rewitt, thank you.. i'll use RDEPENDS18:40
Casper_neverpanic & nerdboy: Thanks for your inputs. Not being familiar with Yocto the terms "full sdk" and "meta-toolchain" are unclear to me in the context of the Poky build system. I see I have some more research to do. However from your writing I see that using the Yocto project could be the way to go. You do not see a more suitable/easier solution?18:44
nerdboyread the yocto quick start yet?18:48
nerdboytoolchain is your cross-compiler/libc/headers18:48
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has quit IRC18:49
nerdboy"bitbake metatoochain" will make you a basic cross-compile setup with env script, etc18:49
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has joined #yocto18:49
nerdboyer, meta-toolchain even18:49
nerdboyCasper_: maybe look at this and use the reference links => https://github.com/VCTLabs/yocto-crash-course/blob/master/bin/yocto_scale_handout.pdf18:52
*** varibull <varibull!~varibull@ta.tainstruments.com> has quit IRC18:55
*** varibull <varibull!~varibull@ta.tainstruments.com> has joined #yocto18:55
*** mario-goulart <mario-goulart!~user@email.parenteses.org> has quit IRC19:01
*** mario-goulart <mario-goulart!~user@email.parenteses.org> has joined #yocto19:02
Casper_nerdboy: Thanks for the link. I will have a look at the pdf and at the Yocto docs, keeping an eye out for what you mentioned. I think I got my answer. Yocto is the way to go.19:02
*** behanw <behanw!~behanw@2001:470:b26c:0:3030:a2c6:1344:5d3b> has quit IRC19:07
*** aehs29 <aehs29!~aehernan@> has joined #yocto19:08
*** aehs29 <aehs29!~aehernan@> has left #yocto19:08
*** behanw <behanw!~behanw@2001:470:b26c:0:3030:a2c6:1344:5d3b> has joined #yocto19:08
*** mario-goulart <mario-goulart!~user@email.parenteses.org> has quit IRC19:09
*** mario-goulart <mario-goulart!~user@email.parenteses.org> has joined #yocto19:11
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto19:14
lpapphi, how can I avoid Yocto automatically putting my .so files into the -dev package?19:14
lpappI want to get them into my ${PN}19:14
khem`lpapp: you could do it like this19:17
khem`FILES_SOLIBSDEV = ""19:17
khem`SOLIBS = ".so"19:17
*** pidge <pidge!~eflanagan@2a02:8084:0:3000:6680:99ff:fe6c:8a40> has quit IRC19:17
khem`INSANE_SKIP_${PN} += "dev-so"19:17
khem`but I would rather fix the component to generate versioned libs19:17
khem`it has other benefits along with clean recipe19:17
khem`but some thirdparty libs cant be done that way so I do understand that usecase19:18
lpappwell, I would rather not do big changes now in the pressure of release ;-)19:18
lpappwill the aforementioned idea work with dylan?19:18
lpappit is not thirdparty lib, by the way, it is our own lib which I and my colleagues develop.19:18
lpappwe can do cosmethic changes later, that is fine.19:19
nerdboylpapp: ship it!19:20
lpappcannot find FILES_SOLIBSDEV.19:21
lpappnerdboy: if it only worked ...19:21
lpappif only it worked*, hack, stress is not good for typing :)19:21
lpappkhem`: the so name is probably a quick fix though19:21
lpappkhem`: see, the architecture is relatively complex, we do not have time to establish proper layers in Yocto.19:22
lpappI am happy to ship it as a bit more monoltythic than that.19:22
* nerdboy left the agile-train-to-hell last year19:22
lpappnerdboy: I have never joined that train ;-)19:22
nerdboyneither did i19:23
rewittnot having proper layers shouldn't impact the ability to create versioned libs :)19:23
nerdboymore like a hijacking19:23
lpapprewitt: that is exactly why I said I would do that.19:23
lpappbut thinking about package layering is comethic at this point. It is not simply my lib and my app.19:24
lpappit is my kernel + my utils + my lib + my apps + mylibs + myapps, etc19:24
lpappit is a quite complex stack ;-)19:24
nerdboyyou're supposed to grow it the right way...19:25
lpappneeds half a day to think about packaging, implementing it and testing.19:25
lpappnerdboy: I am supposed to find a rich woman, too :D19:25
lpappI am still surprised that FILES_SOLIBSDEV is undocumented.19:25
lpappI will open a ticket for that.19:26
neverpanicDoesn't Yocto only put .so files that are symlinks into -dev packages, anyway?19:26
khem`it does19:26
khem`but he wants to devoid that19:26
neverpanicThen I really don't know why they would be needed at runtime.19:27
lpappneverpanic: nope19:27
lpappyou can disable that.19:27
lpappsee above, the insake skips, I did that in the past, too.19:27
khem`lpapp: you should really bite the bullet once and do it right in component19:27
khem`good engineering goes long way19:27
lpappkhem`: like I wrote many times above, sure.. Now? No.19:27
lpappkhem`: well, you are used to Intel with shitload of money19:28
lpapptry a startup where you have to ship stuff asap to survive19:28
khem`what ?19:28
lpappcosmethic stuff will not be high priority :)19:28
nerdboylpapp: i am just giving you crap...  i got stalled in the middle of restructuring my meta-alt layer and all the images19:28
lpappI have been on both side as an ex-"nokian".19:28
nerdboyneed get back to that someday...19:28
lpappI notice the differences of the business stuff...19:28
nerdboylpapp: khem is juniper afaik, not intel19:29
*** Casper_ <Casper_!2eb6e353@gateway/web/freenode/ip.> has quit IRC19:29
nerdboystill a nice place, not so big though19:30
lpappnerdboy: Intel was just a name ...19:30
nerdboy*big as intel19:30
lpappthe important bit is the focus you have to put on stuff.19:30
nerdboywell, some of these guys do work at intel...19:30
nerdboyyou didn't notice the crap part?19:31
lpappWould I like to do everything perfect like in my dreams? Sure! Can I afford that in a small company playing for survival? Absolutely not.19:31
lpappthere are layers above technical stuff... e.g. business.19:31
rewittbut it's really just making the .so a symlink and the real library have a .1 on the end of it. You don't even have to ever increment the version number if you don't want to. I guess I fail to see why that takes any more time than working around it.19:32
lpappit is annoying that "yocto bugreport" does not give any good result on the first page of Google results. I am not joking!19:32
lpapprewitt: that is the thing. You have not even understood the use case.19:33
lpappif it was just like that, sure.19:33
lpappbut it is not....19:33
* nerdboy glad to see nothing has changed too much...19:33
lpappalthough even that requires gcc knowledge in the buildsystem how to do it properly with Makefiles, etc, which I simply do not have at this point.19:34
lpappskills do not come for free.19:34
lpappI still do not get why google cannot find me where to report bugs against Yocto. This is ... suboptimal.19:34
rewitthttps://www.yoctoproject.org/tools-resources/bugs is the first hit on google for "yocto bugs" that page then has a link to the bugzilla19:35
yoctiBug 7358: normal, Undecided, ---, david.c.stewart, NEW , FILES_SOLIBSDEV is not documented19:36
lpapprewitt: I was not looking for that page.19:36
lpappI was looking for the bugzilla.19:36
lpappand yes, I know where to find it as I reported many bugs in the past.19:36
lpappI am simply telling that it is not indexed properly by Google which is a fail.19:36
lpappI do not know why it is happening though ... The Yocto project is the first where I see this failure on Google.19:36
lpappe.g. type qt bugreport19:37
lpappgnome bugreport19:37
rewittkhem: I'm curious did you figure out what was different in core-image-sato that was causing init to segfault?19:38
lpappetc, I do not know why the Yocto bugzilla is not indexed.19:38
lpappkde bugreport, etc, etc, g2g...19:38
khem`rewitt: no time19:38
khem`I use systemd so sysvinit is like a step child19:39
khem`and it works with systemd19:39
rewittkhem: I agree it's really hard for me to switch back to sysvinit19:39
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC19:40
nerdboywhat branch?19:40
*** mario-goulart <mario-goulart!~user@email.parenteses.org> has quit IRC19:40
* rewitt off to lunch19:40
nerdboyguess i should deploy a recent build...19:40
*** mario-goulart <mario-goulart!~user@email.parenteses.org> has joined #yocto19:41
*** mario-goulart <mario-goulart!~user@email.parenteses.org> has quit IRC19:43
*** mario-goulart <mario-goulart!~user@email.parenteses.org> has joined #yocto19:45
*** Svendsen <Svendsen!~Thunderbi@0128800289.0.fullrate.dk> has joined #yocto19:48
*** bobdog555 <bobdog555!~bobdog555@> has quit IRC19:54
*** Nitin <Nitin!~nakamble@> has joined #yocto19:59
*** hugovs <hugovs!~hugo@> has joined #yocto20:00
khem`OK so kernel headers updated to 3.19 but conman was not fixed to take it20:01
khem`                 from /home/ubuntu/work/bleeding/openembedded-core/build/tmp-glibc/work/core2-64-oe-linux/connman/1.28-r0/connman-1.28/src/tethering.c:39:20:01
khem`:8: error: redefinition of 'struct in6_addr'20:02
*** Nitin1 <Nitin1!nakamble@nat/intel/x-glszonqcwyfekmxo> has quit IRC20:02
rburtonhuh works here20:06
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto20:06
*** jimBaxter <jimBaxter!~jbaxter@jimbax.plus.com> has quit IRC20:09
*** toxickore <toxickore!toxickore@nat/intel/x-tnpojqjdbeabncrq> has joined #yocto20:12
*** Nitin1 <Nitin1!~nakamble@> has joined #yocto20:14
*** hugovs <hugovs!~hugo@> has quit IRC20:14
*** Nitin <Nitin!~nakamble@> has quit IRC20:15
*** sarahsharp <sarahsharp!~sarah@> has joined #yocto20:16
*** hugovs <hugovs!~hugo@> has joined #yocto20:17
*** memcpy <memcpy!~memcpy@unaffiliated/memcpy> has joined #yocto20:19
*** Bully4u <Bully4u!~tgraydon@> has joined #yocto20:22
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-hyzidqesrcrydejp> has quit IRC20:23
*** jmd <jmd!~user@de.cellform.com> has quit IRC20:27
khem`rburton: It was a local cruft20:28
*** memcpy <memcpy!~memcpy@unaffiliated/memcpy> has quit IRC20:31
*** dmoseley <dmoseley!~dmoseley@cpe-174-096-222-251.carolina.res.rr.com> has quit IRC20:54
dgm816is there a way to set only the locales i want to generate in local.conf?20:56
* paulg notes that the python upgrade breaks build-appliance related stuff.20:57
paulg File "/usr/lib/python2.7/ctypes/__init__.py", line 10, in <module>20:58
paulg    from _ctypes import Union, Structure, Array20:58
paulgImportError: No module named _ctypes20:58
paulgget the above when trying to invoke bitbake in the build appliance...20:58
*** dmoseley <dmoseley!~dmoseley@cpe-174-096-222-251.carolina.res.rr.com> has joined #yocto21:00
*** benjamirc <benjamirc!~besquive@> has joined #yocto21:01
paulgTo be fair, I am _guessing_ it is the python uprev.21:03
khem`dgm816: yes set IMAGE_LINGUAS21:04
khem`paulg: it seems it did not configure ctype.so21:05
dgm816khem`, aren't those only tne installed package locales into the image? i'd like to not even generate them to keep my Packages.gz smaller.. we will have to be updating over slow/unreliable links..21:05
khem`paulg: usually happens when python detects wrong CC21:05
khem`dgm816: http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-GLIBC_GENERATE_LOCALES21:06
khem`is all you need to read21:06
paulgkhem`, zeddii and I were just looking at part of the recipe which looked to specifically error out if ctype wasn't configured..21:11
paulgbut AFAIK that never tripped.21:12
*** vmeson <vmeson!~rmacleod@> has quit IRC21:13
*** khem` is now known as khem[away]21:22
*** toxickore <toxickore!toxickore@nat/intel/x-tnpojqjdbeabncrq> has quit IRC21:24
nerdboydgm816: last time i messed with those settings it broke my X keyboard config21:26
nerdboyi set IMAGE_LINGUAS = "en-us" in local.conf and it all went kablooey21:29
nerdboyso obviously that's not all of it...21:30
*** ddalex1 <ddalex1!~ddalex@> has joined #yocto21:30
*** varibull <varibull!~varibull@ta.tainstruments.com> has quit IRC21:31
*** angolini <angolini!uid62003@gateway/web/irccloud.com/x-agqgvwqvsgfvvlmv> has quit IRC21:44
*** khem[away] is now known as khem`21:45
*** rcw <rcw!~rwoolley@> has quit IRC21:46
*** rburton <rburton!~Adium@> has quit IRC21:52
khem`paulg: ok that good21:59
*** aehs29 <aehs29!aehernan@nat/intel/x-fszftlddfobvqgbh> has joined #yocto21:59
*** aehs29 <aehs29!aehernan@nat/intel/x-fszftlddfobvqgbh> has left #yocto22:01
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC22:01
*** [Sno] <[Sno]!~Sno]@static-87-79-200-121.netcologne.de> has quit IRC22:02
*** sameo <sameo!~samuel@> has joined #yocto22:04
*** pohly <pohly!~pohly@p5DE8ED5F.dip0.t-ipconnect.de> has quit IRC22:05
*** ddalex1 <ddalex1!~ddalex@> has quit IRC22:05
*** sameo <sameo!~samuel@> has quit IRC22:08
*** sameo <sameo!~samuel@> has joined #yocto22:08
*** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has joined #yocto22:08
*** ant_home <ant_home!~ant__@host16-169-dynamic.56-82-r.retail.telecomitalia.it> has joined #yocto22:09
*** hugovs <hugovs!~hugo@> has quit IRC22:25
*** toxickore <toxickore!~toxickore@> has joined #yocto22:26
*** memcpy <memcpy!~memcpy@unaffiliated/memcpy> has joined #yocto22:27
*** melio_cc <melio_cc!~melio_cc@static-194-113-26-69.axsne.net> has quit IRC22:31
khem`has someone used make-native22:31
khem`instead of host make22:32
*** paul_G <paul_G!~paulg@24-52-251-107.cable.teksavvy.com> has joined #yocto22:33
paul_Gbluelightning, just a heads up ; "populate_sdk_ext: add extensible SDK" somehow trips up the tab completion I'd added to git;  we now try to find a nativesdk-bash-completion when building the native git, and that gives...22:38
paul_GERROR: Nothing PROVIDES 'nativesdk-bash-completion' (but virtual:nativesdk:/home/paul/poky/meta/recipes-devtools/git/git_2.3.0.bb DEPENDS on or otherwise requires it). Close matches:22:40
paul_GLooking into it now....22:40
*** [Sno] <[Sno]!~Sno]@p578b540c.dip0.t-ipconnect.de> has joined #yocto22:49
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC22:50
*** Nitin1 <Nitin1!~nakamble@> has quit IRC22:52
*** sjolley <sjolley!~sjolley@> has quit IRC22:52
*** sjolley <sjolley!sjolley@nat/intel/x-xfyyfmqkoqpeadbb> has joined #yocto22:52
rewittpaul_G: that happens just by doing a "bitbake git-native"?22:55
paul_Grewitt,  as it turns out no....  just getting to the bottom of it this very minute.22:57
paul_GI had a local layer change that caused it...22:57
rewittpaul_G: ok, let me know the sdk patch series really does end up causing problems22:58
*** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC23:01
*** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto23:01
paul_Gso, here is what broke.  The part of the git tab completion that I didn't send upstream because bash-completion isn't (yet?) outside of meta-oe, was this, in a local bbappend for git.23:01
paul_GPACKAGECONFIG ?= "bash-completion"23:01
paul_GPACKAGECONFIG[bash-completion] = ",,bash-completion,bash-completion ${BPN}-bash-completion"23:01
*** benjamirc1 <benjamirc1!~besquive@> has joined #yocto23:01
paul_Gbut w/o meta-oe in your bblayers, you can't do that.23:02
paul_GIt was just a fancy way to say use git tab completion if bash completion is present.  That said, others may have similar constructs that now behave differently.23:04
*** benjamirc <benjamirc!~besquive@> has quit IRC23:04
paul_Grewitt, looking at your commit, it was over my head as to why the behaviour changed from it...23:05
*** memcpy <memcpy!~memcpy@unaffiliated/memcpy> has quit IRC23:05
*** marka <marka!~marka@> has quit IRC23:06
rewittI wouldn't expect the behavior to be any different unless you were actually trying to build an sdk23:06
paul_GI can easily drop my  git bbappend and unconditionally call out bash-completion and git-completion in my packagelist23:06
paul_Grewitt, well it probably is beacuse git has this...23:06
paul_GBBCLASSEXTEND = "native nativesdk"23:07
paul_Gso when I added tab completion, as this...23:07
paul_GPACKAGES =+ "${PN}-bash-completion"23:07
paul_Git was generally right in thinking a native one made sense.23:08
paul_Ganyway, testing without the two PACKAGECONFIG lines quoted above and things are ok ; not failing looking for a native-bash-completion23:08
paul_Grewitt, and fwiw, I wasn't directly trying to build an sdk, but I am building a layer based on the build appliance, so it kind of / sort of is an sdk of sorts....23:09
*** nicktick <nicktick!~john@unaffiliated/nicktick> has joined #yocto23:13
*** nicktick <nicktick!~john@unaffiliated/nicktick> has quit IRC23:14
paul_Gnow, with that solved, do I feel brave enough to try and figure out why the python uprev broke build appliance....23:17
*** toxickore2 <toxickore2!~toxickore@> has joined #yocto23:18
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto23:19
*** toxickore <toxickore!~toxickore@> has quit IRC23:21
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has joined #yocto23:23
*** pidge <pidge!~eflanagan@2a02:8084:0:3000:6680:99ff:fe6c:8a40> has joined #yocto23:26
*** SorenHolm <SorenHolm!~quassel@5634f191.rev.stofanet.dk> has quit IRC23:34
*** benjamirc1 <benjamirc1!~besquive@> has quit IRC23:36
*** khem` is now known as khem[away]23:47
*** khem[away] is now known as khem`23:48

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