| aelmadhoun | anyone setup a slack group for yocto yet? :) | 00:00 |
|---|---|---|
| *** madisox <madisox!~madison@216-75-232-11.static.wiline.com> has quit IRC | 00:04 | |
| *** aehs29 <aehs29!~aehernan@134.134.139.77> has left #yocto | 00:05 | |
| *** nrossi <nrossi!~nrossi@103.26.61.197> has joined #yocto | 00:07 | |
| *** focus <focus!~Doug@164.39.177.154> has joined #yocto | 00:14 | |
| -YoctoAutoBuilder- build #536 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/536 | 00:17 | |
| *** lamego <lamego!~jose@134.134.139.70> has quit IRC | 00:21 | |
| *** aelmadhoun <aelmadhoun!4066f90c@gateway/web/freenode/ip.64.102.249.12> has quit IRC | 00:23 | |
| *** benjamirc <benjamirc!~besquive@134.134.137.75> has quit IRC | 00:26 | |
| *** t0mmy <t0mmy!~tprrt@ram31-2-82-228-88-46.fbx.proxad.net> has quit IRC | 00:27 | |
| *** paulg <paulg!~paulg@198-84-207-67.cpe.teksavvy.com> has quit IRC | 00:35 | |
| *** sjolley <sjolley!sjolley@nat/intel/x-diiflduaohhmxfmx> has quit IRC | 00:45 | |
| *** sjolley <sjolley!~sjolley@134.134.137.75> has joined #yocto | 00:45 | |
| *** sameo <sameo!~samuel@192.55.54.40> has quit IRC | 01:21 | |
| -YoctoAutoBuilder- build #531 of nightly-ipk is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ipk/builds/531 | 01:23 | |
| -YoctoAutoBuilder- build #527 of nightly-rpm is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-rpm/builds/527 | 01:28 | |
| -YoctoAutoBuilder- build #197 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/197 | 01:45 | |
| -YoctoAutoBuilder- build #191 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/191 | 01:55 | |
| -YoctoAutoBuilder- build #519 of nightly-deb is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/519 | 01:59 | |
| *** fledermaus <fledermaus!~vivek@78.32.176.249> has quit IRC | 02:02 | |
| *** varibull_ <varibull_!~varibull@ta.tainstruments.com> has joined #yocto | 02:20 | |
| *** Mustafa <Mustafa!~Mustafa@203-174-190-170.mel.static-ipl.aapt.com.au> has joined #yocto | 02:21 | |
| *** stefans_ <stefans_!stefans@nat/intel/session> has joined #yocto | 02:22 | |
| *** dshwang_ <dshwang_!~dshwang@192.55.54.38> has joined #yocto | 02:22 | |
| *** justanotherboy1 <justanotherboy1!mlopezva@nat/intel/session> has joined #yocto | 02:22 | |
| *** marquiz_ <marquiz_!marquiz@nat/intel/session> has joined #yocto | 02:23 | |
| *** edtyler <edtyler!~edt@ip68-4-156-81.oc.oc.cox.net> has quit IRC | 02:23 | |
| *** justanotherboy <justanotherboy!mlopezva@nat/intel/x-umfevccihbnwpicg> has quit IRC | 02:23 | |
| *** jmesmon <jmesmon!~ydoc@vcr.einic.org> has quit IRC | 02:23 | |
| *** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has quit IRC | 02:23 | |
| *** alimon1 <alimon1!~alimon@192.55.54.42> has quit IRC | 02:23 | |
| *** tismith <tismith!~toby@203.62.184.110> has quit IRC | 02:23 | |
| *** hanDerPe1er <hanDerPe1er!~peder@li307-49.members.linode.com> has quit IRC | 02:23 | |
| *** ausjke <ausjke!~xxiao@45.55.175.66> has quit IRC | 02:23 | |
| *** Mustafa_ <Mustafa_!~Mustafa@203-174-190-170.mel.static-ipl.aapt.com.au> has quit IRC | 02:23 | |
| *** varibull <varibull!~varibull@ta.tainstruments.com> has quit IRC | 02:23 | |
| *** georgem <georgem!~georgem@mail.novatech-llc.com> has quit IRC | 02:23 | |
| *** joseppc <joseppc!~Josep@sestofw01.enea.se> has quit IRC | 02:23 | |
| *** marquiz <marquiz!~marquiz@134.134.139.70> has quit IRC | 02:23 | |
| *** dshwang <dshwang!~dshwang@134.134.139.77> has quit IRC | 02:23 | |
| *** lexano_ <lexano_!~lexano@CPEa021b7ac59c9-CMbcc81006f6ee.cpe.net.cable.rogers.com> has quit IRC | 02:23 | |
| *** blitz00 <blitz00!stefans@unaffiliated/blitz00> has quit IRC | 02:23 | |
| *** rtollert <rtollert!~rtollert@130.164.62.197> has quit IRC | 02:23 | |
| *** Hauke <Hauke!~Hauke@hauke-m.de> has quit IRC | 02:23 | |
| *** hanDerPeder <hanDerPeder!~peder@li307-49.members.linode.com> has joined #yocto | 02:24 | |
| *** alimon1 <alimon1!alimon@nat/intel/session> has joined #yocto | 02:24 | |
| *** tismith <tismith!~toby@203.62.184.110> has joined #yocto | 02:24 | |
| *** ausjke <ausjke!~xxiao@45.55.175.66> has joined #yocto | 02:24 | |
| *** Hauke <Hauke!~Hauke@hauke-m.de> has joined #yocto | 02:24 | |
| *** jmesmon <jmesmon!~ydoc@vcr.einic.org> has joined #yocto | 02:24 | |
| *** georgem <georgem!~georgem@mail.novatech-llc.com> has joined #yocto | 02:25 | |
| *** lexano_ <lexano_!~lexano@CPEa021b7ac59c9-CMbcc81006f6ee.cpe.net.cable.rogers.com> has joined #yocto | 02:25 | |
| *** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has joined #yocto | 02:25 | |
| *** rtollert <rtollert!~rtollert@130.164.62.197> has joined #yocto | 02:25 | |
| *** joseppc <joseppc!~Josep@sestofw01.enea.se> has joined #yocto | 02:25 | |
| *** stefans_ <stefans_!stefans@nat/intel/session> has quit IRC | 02:25 | |
| *** stefans_ <stefans_!stefans@nat/intel/x-ozihcrwmlurqhdel> has joined #yocto | 02:25 | |
| *** justanotherboy1 <justanotherboy1!mlopezva@nat/intel/session> has quit IRC | 02:25 | |
| *** justanotherboy1 <justanotherboy1!mlopezva@nat/intel/x-fistrhstomfzhdsj> has joined #yocto | 02:25 | |
| *** marquiz_ <marquiz_!marquiz@nat/intel/session> has quit IRC | 02:25 | |
| *** marquiz_ <marquiz_!marquiz@nat/intel/x-prhpwegsbilxrvzt> has joined #yocto | 02:25 | |
| *** alimon1 <alimon1!alimon@nat/intel/session> has quit IRC | 02:25 | |
| *** alimon1 <alimon1!alimon@nat/intel/x-tvoghackaijnggiy> has joined #yocto | 02:25 | |
| *** edtyler <edtyler!~edt@ip68-4-156-81.oc.oc.cox.net> has joined #yocto | 02:27 | |
| *** onoffon is now known as khem` | 02:41 | |
| *** khem` is now known as onoffon | 02:42 | |
| *** bananadev <bananadev!~bananadev@117.6.99.240> has joined #yocto | 02:54 | |
| *** nrossi <nrossi!~nrossi@103.26.61.197> has quit IRC | 03:07 | |
| *** nrossi <nrossi!~nrossi@103.26.61.197> has joined #yocto | 03:29 | |
| *** t0mmy <t0mmy!~tprrt@ram31-2-82-228-88-46.fbx.proxad.net> has joined #yocto | 03:56 | |
| *** bananadev <bananadev!~bananadev@117.6.99.240> has quit IRC | 05:23 | |
| *** bananadev <bananadev!~bananadev@117.6.99.240> has joined #yocto | 05:24 | |
| *** sno <sno!~sno@p578b540c.dip0.t-ipconnect.de> has quit IRC | 05:28 | |
| *** psadro <psadro!~Thunderbi@2620:0:ed0:800a:72f3:95ff:fe1d:9866> has quit IRC | 05:40 | |
| *** psadro <psadro!~Thunderbi@216.234.148.134> has joined #yocto | 05:41 | |
| *** roric <roric!~roric@h196n19-vrr-a31.ias.bredband.telia.com> has joined #yocto | 06:30 | |
| *** pohly <pohly!~pohly@p5DE8FABA.dip0.t-ipconnect.de> has joined #yocto | 06:46 | |
| *** slidercrank <slidercrank!~slidercra@unaffiliated/slidercrank> has joined #yocto | 06:56 | |
| *** marek_ <marek_!~marek@81.89.61.168.host.vnet.sk> has joined #yocto | 07:04 | |
| *** sno <sno!~sno@rademacherexchange.de> has joined #yocto | 07:05 | |
| *** frsc <frsc!~frsc@80.149.173.68> has joined #yocto | 07:06 | |
| *** Mustafa <Mustafa!~Mustafa@203-174-190-170.mel.static-ipl.aapt.com.au> has quit IRC | 07:12 | |
| *** Mustafa <Mustafa!~Mustafa@203-174-190-170.mel.static-ipl.aapt.com.au> has joined #yocto | 07:12 | |
| *** Mustafa_ <Mustafa_!~Mustafa@203-174-190-170.mel.static-ipl.aapt.com.au> has joined #yocto | 07:17 | |
| *** Mustafa <Mustafa!~Mustafa@203-174-190-170.mel.static-ipl.aapt.com.au> has quit IRC | 07:17 | |
| *** deviosity <deviosity!~deviosity@c-67-160-33-141.hsd1.wa.comcast.net> has quit IRC | 07:17 | |
| *** Mustafa_ <Mustafa_!~Mustafa@203-174-190-170.mel.static-ipl.aapt.com.au> has quit IRC | 07:22 | |
| *** Mustafa <Mustafa!~Mustafa@203-174-190-170.mel.static-ipl.aapt.com.au> has joined #yocto | 07:23 | |
| *** frsc <frsc!~frsc@80.149.173.68> has quit IRC | 07:24 | |
| *** Mustafa <Mustafa!~Mustafa@203-174-190-170.mel.static-ipl.aapt.com.au> has quit IRC | 07:24 | |
| *** Mustafa <Mustafa!~Mustafa@203-174-190-170.mel.static-ipl.aapt.com.au> has joined #yocto | 07:25 | |
| *** frsc <frsc!~frsc@80.149.173.68> has joined #yocto | 07:28 | |
| *** o_ndra <o_ndra!50bc8cba@gateway/web/freenode/ip.80.188.140.186> has joined #yocto | 07:29 | |
| *** Mustafa <Mustafa!~Mustafa@203-174-190-170.mel.static-ipl.aapt.com.au> has quit IRC | 07:29 | |
| *** Mustafa <Mustafa!~sheikh.mu@203-174-190-170.mel.static-ipl.aapt.com.au> has joined #yocto | 07:29 | |
| *** Mustafa_ <Mustafa_!~Mustafa@203-174-190-170.mel.static-ipl.aapt.com.au> has joined #yocto | 07:31 | |
| *** Mustafa <Mustafa!~sheikh.mu@203-174-190-170.mel.static-ipl.aapt.com.au> has quit IRC | 07:31 | |
| *** Mustafa <Mustafa!~Mustafa@203-174-190-170.mel.static-ipl.aapt.com.au> has joined #yocto | 07:34 | |
| *** roric <roric!~roric@h196n19-vrr-a31.ias.bredband.telia.com> has quit IRC | 07:34 | |
| *** egavinc <egavinc!~egavinc@40.Red-83-34-184.dynamicIP.rima-tde.net> has joined #yocto | 07:49 | |
| *** Mustafa <Mustafa!~Mustafa@203-174-190-170.mel.static-ipl.aapt.com.au> has quit IRC | 07:49 | |
| *** Mustafa <Mustafa!~Mustafa@203-174-190-170.mel.static-ipl.aapt.com.au> has joined #yocto | 07:49 | |
| *** Mustafa <Mustafa!~Mustafa@203-174-190-170.mel.static-ipl.aapt.com.au> has quit IRC | 07:49 | |
| *** Mustafa <Mustafa!~Mustafa@203-174-190-170.mel.static-ipl.aapt.com.au> has joined #yocto | 07:50 | |
| *** townxelliot <townxelliot!~ell@94.13.69.111> has joined #yocto | 07:50 | |
| *** onoffon <onoffon!~khem@unaffiliated/khem> has quit IRC | 07:50 | |
| *** rob_w <rob_w!~bob@93.104.205.194> has joined #yocto | 07:52 | |
| *** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto | 07:52 | |
| *** Pixionus <Pixionus!~Pixionus@unaffiliated/pixionus> has quit IRC | 07:53 | |
| *** Pixionus <Pixionus!~Pixionus@unaffiliated/pixionus> has joined #yocto | 07:54 | |
| *** tasslehoff <tasslehoff!~Tasslehof@82.147.55.166> has joined #yocto | 07:56 | |
| *** Mustafa <Mustafa!~Mustafa@203-174-190-170.mel.static-ipl.aapt.com.au> has quit IRC | 07:59 | |
| *** hamis_lt_u <hamis_lt_u!~irfan@110.93.212.98> has joined #yocto | 07:59 | |
| *** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-rlsvsblppeonbfek> has joined #yocto | 08:03 | |
| *** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has joined #yocto | 08:03 | |
| *** jbrianceau_away is now known as jbrianceau | 08:03 | |
| *** mago is now known as Guest75314 | 08:03 | |
| *** hamis <hamis!~irfan@110.93.212.98> has joined #yocto | 08:04 | |
| *** yann|work <yann|work!~yann@nan92-1-81-57-214-146.fbx.proxad.net> has quit IRC | 08:05 | |
| *** Guest75314 is now known as mago_ | 08:06 | |
| *** mckoan|away is now known as mckoan | 08:07 | |
| mckoan | good morning | 08:07 |
| *** hamis_lt_u <hamis_lt_u!~irfan@110.93.212.98> has quit IRC | 08:07 | |
| *** jku <jku!~jku@192.198.151.44> has joined #yocto | 08:15 | |
| *** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto | 08:22 | |
| *** fl0v0 <fl0v0!~fvo@p5DDC7134.dip0.t-ipconnect.de> has joined #yocto | 08:30 | |
| *** sameo <sameo!~samuel@192.55.54.43> has joined #yocto | 08:32 | |
| *** rZr <rZr!~RzR@unaffiliated/rzr> has quit IRC | 08:35 | |
| *** csanchezdll <csanchezdll!~user@galileo.kdpof.com> has joined #yocto | 08:35 | |
| *** ZrZ <ZrZ!~RzR@82.236.136.171> has joined #yocto | 08:35 | |
| *** t0mmy <t0mmy!~tprrt@ram31-2-82-228-88-46.fbx.proxad.net> has quit IRC | 08:37 | |
| *** rperier_ is now known as rperier | 08:38 | |
| *** rperier <rperier!~quassel@ubuntu/member/rperier> has joined #yocto | 08:38 | |
| *** cesdv <cesdv!~cesdv@client-188-168-43-165.spb-teleport.ru> has quit IRC | 08:44 | |
| *** Biliogadafr <Biliogadafr!~User@port-35-adslby-pool45.infonet.by> has joined #yocto | 08:45 | |
| *** aime-Pierre <aime-Pierre!~Thunderbi@bob75-2-81-56-46-209.fbx.proxad.net> has joined #yocto | 08:47 | |
| *** cesdv <cesdv!~cesdv@client-188-168-43-165.spb-teleport.ru> has joined #yocto | 08:48 | |
| *** aragua <aragua!~flahouder@212.194.216.83> has joined #yocto | 08:58 | |
| *** cesdv <cesdv!~cesdv@client-188-168-43-165.spb-teleport.ru> has quit IRC | 09:02 | |
| *** cesdv <cesdv!~cesdv@client-188-168-43-165.spb-teleport.ru> has joined #yocto | 09:04 | |
| *** nighty-_ <nighty-_!~nighty@s1000249.xgsspn.imtp.tachikawa.spmode.ne.jp> has joined #yocto | 09:08 | |
| *** [Sno] <[Sno]!~sno@rademacherexchange.de> has joined #yocto | 09:11 | |
| *** sno <sno!~sno@rademacherexchange.de> has quit IRC | 09:14 | |
| *** bananadev_ <bananadev_!~bananadev@117.6.99.240> has joined #yocto | 09:19 | |
| *** bananadev <bananadev!~bananadev@117.6.99.240> has quit IRC | 09:20 | |
| *** hamis <hamis!~irfan@110.93.212.98> has quit IRC | 09:31 | |
| *** t0mmy <t0mmy!~tprrt@217.114.201.133> has joined #yocto | 09:31 | |
| *** yann|work <yann|work!~yann@LFbn-1-1026-146.w86-247.abo.wanadoo.fr> has joined #yocto | 09:31 | |
| *** jonathanmaw <jonathanmaw!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has joined #yocto | 09:35 | |
| *** rburton <rburton!~Adium@35.106.2.81.in-addr.arpa> has joined #yocto | 09:36 | |
| *** Ulfalizer <Ulfalizer!~ulf@217.89.178.116> has joined #yocto | 09:37 | |
| *** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC | 09:41 | |
| *** marek_ <marek_!~marek@81.89.61.168.host.vnet.sk> has quit IRC | 09:41 | |
| *** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto | 09:41 | |
| Ulfalizer | is an increasing PR important in any way at system build time, or is it purely for the package manager on the target to know when important changes have been introduced? | 09:42 |
| *** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-qirqptywdzjnnhit> has joined #yocto | 09:44 | |
| *** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-qirqptywdzjnnhit> has left #yocto | 09:44 | |
| *** matteo <matteo!~matteo@openwrt/developer/matteo> has joined #yocto | 09:54 | |
| rburton | Ulfalizer: the latter, and if you enable the PR service it happens for you | 10:08 |
| rburton | manual PR bumps are historical now | 10:08 |
| *** frsc <frsc!~frsc@80.149.173.68> has quit IRC | 10:10 | |
| *** frsc <frsc!~frsc@80.149.173.68> has joined #yocto | 10:10 | |
| *** CTtpollard <CTtpollard!~tom@82-70-136-246.dsl.in-addr.zen.co.uk> has quit IRC | 10:16 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 10:31 | |
| *** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC | 10:31 | |
| *** psnsilva_ <psnsilva_!~psnsilva@193-126-29-154.net.novis.pt> has quit IRC | 10:33 | |
| *** psnsilva <psnsilva!~psnsilva@193-126-29-154.net.novis.pt> has joined #yocto | 10:40 | |
| *** csanchezdll <csanchezdll!~user@galileo.kdpof.com> has quit IRC | 10:42 | |
| Ulfalizer | rburton: ok, ty | 10:43 |
| *** slips <slips!~slips@156.179.164.82.customer.cdi.no> has quit IRC | 10:43 | |
| *** slips <slips!~slips@156.179.164.82.customer.cdi.no> has joined #yocto | 10:46 | |
| *** LoganG_ <LoganG_!~LoganG@2607:5300:60:47bc:dead:beef:dead:beef> has joined #yocto | 11:00 | |
| *** mario-go` <mario-go`!~user@email.parenteses.org> has joined #yocto | 11:00 | |
| *** tanuk_ <tanuk_!~tanu@a88-114-103-157.elisa-laajakaista.fi> has joined #yocto | 11:00 | |
| *** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC | 11:01 | |
| *** LoganG <LoganG!~LoganG@2607:5300:60:47bc:dead:beef:dead:beef> has quit IRC | 11:01 | |
| *** tanuk <tanuk!~tanu@a88-114-103-157.elisa-laajakaista.fi> has quit IRC | 11:01 | |
| *** mario-goulart <mario-goulart!~user@email.parenteses.org> has quit IRC | 11:01 | |
| *** LoganG_ is now known as LoganG | 11:01 | |
| *** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has quit IRC | 11:01 | |
| *** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto | 11:02 | |
| *** demonimin <demonimin!~demonimin@pro75-5-88-162-203-35.fbx.proxad.net> has joined #yocto | 11:02 | |
| *** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has joined #yocto | 11:02 | |
| *** bananadev_ <bananadev_!~bananadev@117.6.99.240> has quit IRC | 11:05 | |
| *** mario-go` is now known as mario-goulart | 11:10 | |
| *** aime-Pierre <aime-Pierre!~Thunderbi@bob75-2-81-56-46-209.fbx.proxad.net> has quit IRC | 11:36 | |
| *** Levi1 <Levi1!vlevidas@nat/intel/x-xdmdeltuwqbwkfhn> has joined #yocto | 11:39 | |
| mcfrisk | Hi, has anyone installed perf to target? It depends on binutils and nothing provides it for the rootfs, I just find packages for build time and (native) sdk. | 11:40 |
| *** frsc <frsc!~frsc@80.149.173.68> has quit IRC | 11:42 | |
| *** focus <focus!~Doug@164.39.177.154> has quit IRC | 11:44 | |
| mcfrisk | ah gplv3 issue in bitbake, sorry | 11:45 |
| *** DarkKnight <DarkKnight!~quassel@HSI-KBW-095-208-243-227.hsi5.kabel-badenwuerttemberg.de> has quit IRC | 11:48 | |
| *** sameo <sameo!~samuel@192.55.54.43> has quit IRC | 11:49 | |
| *** DarkKnight <DarkKnight!~quassel@HSI-KBW-095-208-243-227.hsi5.kabel-badenwuerttemberg.de> has joined #yocto | 11:52 | |
| *** DarkKnight <DarkKnight!~quassel@HSI-KBW-095-208-243-227.hsi5.kabel-badenwuerttemberg.de> has quit IRC | 11:57 | |
| *** jonathanmaw <jonathanmaw!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has quit IRC | 11:59 | |
| *** jonathanmaw <jonathanmaw!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has joined #yocto | 12:00 | |
| *** roccof <roccof!~roccof@93-51-177-218.ip268.fastwebnet.it> has joined #yocto | 12:01 | |
| *** CTtpollard <CTtpollard!~tom@82-70-136-246.dsl.in-addr.zen.co.uk> has joined #yocto | 12:04 | |
| CTtpollard | if I have a recipe with a src uri that has a pv tag on the git url, but PV is not explicitly set in the recipe what does it default to? | 12:05 |
| *** DarkKnight <DarkKnight!~quassel@HSI-KBW-095-208-243-227.hsi5.kabel-badenwuerttemberg.de> has joined #yocto | 12:07 | |
| joseppc | CTtpollard: it's taken from the recipe file name | 12:09 |
| CTtpollard | joseppc: ty | 12:10 |
| *** T0mW <T0mW!~Tom@24.102.243.3.res-cmts.t132.ptd.net> has quit IRC | 12:25 | |
| *** fledermaus <fledermaus!~vivek@pakora.collabora.co.uk> has joined #yocto | 12:35 | |
| *** tsramos <tsramos!tsramos@nat/intel/x-ykttmlffnjejkecd> has joined #yocto | 12:36 | |
| *** hundebol1 is now known as hundeboll | 12:36 | |
| *** varibull_ <varibull_!~varibull@ta.tainstruments.com> has quit IRC | 12:37 | |
| *** varibull_ <varibull_!~varibull@ta.tainstruments.com> has joined #yocto | 12:37 | |
| *** tsramos <tsramos!tsramos@nat/intel/x-ykttmlffnjejkecd> has quit IRC | 12:37 | |
| *** tsramos <tsramos!tsramos@nat/intel/x-nkqxiqwtixbubhnn> has joined #yocto | 12:38 | |
| -YoctoAutoBuilder- build #554 of nightly-arm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/554 | 12:41 | |
| *** _4urele_ <_4urele_!~aurele@srvmail.castel.fr> has joined #yocto | 12:42 | |
| *** focus <focus!~Doug@164.39.177.154> has joined #yocto | 12:52 | |
| *** aime-Pierre <aime-Pierre!~Thunderbi@193.56.60.161> has joined #yocto | 12:52 | |
| *** frsc <frsc!~frsc@80.149.173.68> has joined #yocto | 13:06 | |
| *** ryansturmer <ryansturmer!~ryansturm@cpe-75-189-150-192.nc.res.rr.com> has quit IRC | 13:17 | |
| *** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has joined #yocto | 13:19 | |
| *** dv__ <dv__!~quassel@chello062178118086.5.14.vie.surfer.at> has quit IRC | 13:21 | |
| *** nighty-_ <nighty-_!~nighty@s1000249.xgsspn.imtp.tachikawa.spmode.ne.jp> has quit IRC | 13:30 | |
| *** anselmolsm <anselmolsm!~anselmols@192.55.54.43> has joined #yocto | 13:31 | |
| *** challinan <challinan!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has joined #yocto | 13:41 | |
| *** milan_ <milan_!~milan@111.93.218.67> has joined #yocto | 13:50 | |
| *** lamego <lamego!~jose@134.134.139.74> has joined #yocto | 14:03 | |
| *** ryansturmer <ryansturmer!~ryansturm@cpe-75-189-150-192.nc.res.rr.com> has joined #yocto | 14:04 | |
| ryansturmer | Is there any guidance on building initramfs images with the oe build system? | 14:05 |
| ryansturmer | I have found the OE layer for it, and there's some mention of initramfs kernels in the yocto development manual | 14:06 |
| *** Guest83 <Guest83!~textual@83.233.227.60> has joined #yocto | 14:07 | |
| *** Guest83 is now known as ionte | 14:07 | |
| *** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto | 14:13 | |
| *** khem` is now known as onoffon | 14:13 | |
| *** onoffon <onoffon!~khem@unaffiliated/khem> has quit IRC | 14:15 | |
| milan_ | Is it possible to build multiple versions of a package for a single rootfs ? | 14:16 |
| CTtpollard | milan_: I would think so | 14:17 |
| milan_ | CTtpollard: How can we achieve it ? since only one version of a particular recipe can be built at at a time | 14:19 |
| ryansturmer | I guess what I'm trying to achieve is the same as building a "live" image - is adding "live" to the IMAGE_FSTYPES all that should be required to build a live image? | 14:24 |
| ryansturmer | That can't be right ... | 14:24 |
| ryansturmer | Does anyone know how the "live" images are achieved in yocto? | 14:28 |
| ryansturmer | (As in, what filesystem overlay software is used? Union, aufs, overlayfs, etc?) | 14:28 |
| *** jonathanmaw_ <jonathanmaw_!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has joined #yocto | 14:28 | |
| rburton | milan_: you'd need to have the version in the recipe name, like there's gcc-5.2 and gcc-4.9 | 14:29 |
| rburton | and then ensure that they don't conflict | 14:30 |
| rburton | (or libpng and libpng12, or glib and glib-2.0) | 14:30 |
| rburton | basically you just need to make sure that PN is unique | 14:30 |
| *** focus <focus!~Doug@164.39.177.154> has quit IRC | 14:31 | |
| *** jonathanmaw <jonathanmaw!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has quit IRC | 14:32 | |
| milan_ | rbutton: Ok. Thanks! Going to try that now. | 14:32 |
| milan_ | rburton: Ok. Thanks! Going to try that now | 14:33 |
| *** focus <focus!~Doug@164.39.177.154> has joined #yocto | 14:36 | |
| *** rburton1 <rburton1!~Adium@35.106.2.81.in-addr.arpa> has joined #yocto | 14:41 | |
| *** rburton <rburton!~Adium@35.106.2.81.in-addr.arpa> has quit IRC | 14:41 | |
| *** PTBD <PTBD!2eedcbbe@gateway/web/freenode/ip.46.237.203.190> has joined #yocto | 14:50 | |
| *** psadro <psadro!~Thunderbi@216.234.148.134> has quit IRC | 14:50 | |
| *** khem <khem!~khem@unaffiliated/khem> has quit IRC | 14:50 | |
| *** kscherer <kscherer!~kscherer@128.224.252.2> has quit IRC | 14:51 | |
| *** khem <khem!~khem@unaffiliated/khem> has joined #yocto | 14:52 | |
| PTBD | I'm sorry if this is a stupid question but I am extremely new to yocto. How would I install python3 on a yocto linux without access to the internet? | 14:52 |
| *** tasslehoff <tasslehoff!~Tasslehof@82.147.55.166> has quit IRC | 14:53 | |
| ryansturmer | Yocto is built from scratch, so the correct way to install it is to include it in the build | 14:57 |
| ryansturmer | but I'm assuming you've got an installed yocto linux system that you want to add python3 to | 14:57 |
| PTBD | correct | 14:57 |
| ryansturmer | What else is available in your system? You can always build python3 from source if you have dev tools on your target | 14:58 |
| PTBD | Which kind of tools would be available on yocto to install packages (except building from source?) | 14:59 |
| *** jchonig <jchonig!~quassel@firewall.honig.net> has quit IRC | 15:00 | |
| rburton1 | PTBD: depends on what is in your image | 15:00 |
| rburton1 | there's no such thing as a "standard yocto image" | 15:00 |
| rburton1 | that's pretty much the point | 15:00 |
| PTBD | rburton1: I understand that but I don't know what to start looking for on my image. I did not create that image and I am not familiar with any tools that yocto uses to acomplish what I need | 15:01 |
| *** psadro <psadro!~Thunderbi@2620:0:ed0:800a:72f3:95ff:fe1d:9866> has joined #yocto | 15:01 | |
| ryansturmer | In your case, I think your best bet right out of the gate is to download the python3 source distribution, transfer it to your target, and try to build it from source | 15:02 |
| ryansturmer | following the instructions from python.org | 15:02 |
| ryansturmer | you can do a quick check for tools like make, gcc, etc to see if that's feasible first, to save yourself some time. | 15:02 |
| ryansturmer | What is your target system? | 15:02 |
| rburton1 | or more to the point where did your image come from, and can the people who provided it give you python3 packages. | 15:03 |
| *** rburton1 is now known as rburton | 15:03 | |
| ryansturmer | Yeah, that | 15:03 |
| *** madisox <madisox!~madison@12.30.244.5> has joined #yocto | 15:03 | |
| -YoctoAutoBuilder- build #192 of nightly-arm64 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm64/builds/192 | 15:05 | |
| PTBD | make is available but it looks like gcc is not. | 15:05 |
| ryansturmer | @rburton1 is right - you're best off going to the maintainers of the image you're running, and seeing if they provide python3 package files | 15:05 |
| PTBD | I see | 15:06 |
| ryansturmer | Whats your target? (Curiosity, here) | 15:06 |
| PTBD | a router with a guest os | 15:06 |
| ryansturmer | Ah yeah. | 15:06 |
| *** jchonig <jchonig!~quassel@firewall.honig.net> has joined #yocto | 15:07 | |
| ryansturmer | Is this a custom installed image, or did it come from the manufacturer? | 15:07 |
| PTBD | The guest os came with the router preinstalled | 15:07 |
| ryansturmer | Yick | 15:07 |
| PTBD | there was a short tutorial on how to install (for example) python. they used a ubuntu virtual machine as a rpm server from which they used 'smart install ...' | 15:07 |
| PTBD | But I wouldn't know how to apply that. Would the command 'smart install' have to build the rpm? Or do rpms come precompiled for a architecture? | 15:08 |
| ryansturmer | I think you're clear out of yocto territory here and into your vendor specific software for package management | 15:09 |
| *** kscherer <kscherer!~kscherer@128.224.252.2> has joined #yocto | 15:09 | |
| ryansturmer | I don't think "smart install" maps to anything anyone here is familiar with. Best to go with your vendors documentation, or if that fails, get in touch with them. | 15:10 |
| PTBD | you mean you don't know what smart install is? | 15:10 |
| ryansturmer | Yeah, that's not a yocto thing | 15:11 |
| ryansturmer | (to my knowledge) | 15:11 |
| ryansturmer | That's probably something provided by your vendor for package management. | 15:11 |
| PTBD | oh, I thought it is the default package manger on yocto. | 15:11 |
| ryansturmer | There's essentially no default *anything* on yocto | 15:12 |
| PTBD | https://www.yoctoproject.org/blogs/khem/2013/get-smart-smart-package-manager or am I terribly misunderstanding something here | 15:12 |
| ryansturmer | oh! I can totally be mistaken, then! | 15:12 |
| ryansturmer | Welp! I've never used it, so you're at least out of *my* depths | 15:12 |
| PTBD | ok | 15:13 |
| ryansturmer | But stick around and maybe someone else here can help. | 15:13 |
| __b4ub | Got an issue with the same iptables command not behaving in the same way on yocto and on my desktop pc (mainly --dport and -p, silently not working on yocto). Any idea about where I could find the information related to what's working ? | 15:14 |
| *** jonathanmaw_ <jonathanmaw_!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has quit IRC | 15:15 | |
| PTBD | ryansturmer: thank you | 15:15 |
| *** c10ud <c10ud!~c10ud@emesene/dictator/c10ud> has joined #yocto | 15:19 | |
| PTBD | ryansturmer: may I ask an stupid question again? the routers architecture is i686, wouldn't I be able to use a precompiled package? | 15:20 |
| *** jchonig <jchonig!~quassel@firewall.honig.net> has quit IRC | 15:20 | |
| *** jchonig <jchonig!~quassel@firewall.honig.net> has joined #yocto | 15:20 | |
| *** Rallis <Rallis!~chris@208-53-195-38.static.ravenind.com> has quit IRC | 15:21 | |
| *** Rallis <Rallis!~chris@208-53-195-38.static.ravenind.com> has joined #yocto | 15:22 | |
| *** justanotherboy1 <justanotherboy1!mlopezva@nat/intel/x-fistrhstomfzhdsj> has quit IRC | 15:22 | |
| *** justanotherboy <justanotherboy!mlopezva@nat/intel/x-adhtydrwzpiuvted> has joined #yocto | 15:22 | |
| *** milan_ <milan_!~milan@111.93.218.67> has quit IRC | 15:23 | |
| *** jonathanmaw_ <jonathanmaw_!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has joined #yocto | 15:28 | |
| *** igor1 <igor1!~Igor_Stop@134.134.139.77> has quit IRC | 15:28 | |
| *** igor <igor!~Igor_Stop@134.134.139.77> has joined #yocto | 15:29 | |
| *** ulf` <ulf`!ulf@nat/intel/x-ndwjiafoidzgkzbu> has quit IRC | 15:29 | |
| *** ulf` <ulf`!~ulf@134.134.137.73> has joined #yocto | 15:35 | |
| *** jzhang1 <jzhang1!jzhang@nat/intel/x-afvhhegoyrnfzxzs> has quit IRC | 15:35 | |
| *** Rallis <Rallis!~chris@208-53-195-38.static.ravenind.com> has quit IRC | 15:36 | |
| *** jzhang <jzhang!~jzhang@134.134.139.70> has joined #yocto | 15:36 | |
| *** pedroalvarez <pedroalvarez!~pedroalva@ec2-52-27-154-6.us-west-2.compute.amazonaws.com> has joined #yocto | 15:38 | |
| *** jku <jku!~jku@192.198.151.44> has quit IRC | 15:39 | |
| pedroalvarez | Hi guys! quick question: can you build systems with yocto in any architecture? or only in x86? | 15:39 |
| paulg_ | pedroalvarez, do you mean like an ARM host system building for say a powerpc target deployment image, or .... ? | 15:50 |
| pedroalvarez | yes, for example | 15:51 |
| rburton | yes | 15:52 |
| rburton | x86 host is the most tested as its the fastest, but there's no reason why arm host shouldn't work | 15:52 |
| pedroalvarez | good, thanks :) | 15:53 |
| *** benjamirc <benjamirc!~besquive@134.134.137.71> has joined #yocto | 15:54 | |
| *** o_ndra <o_ndra!50bc8cba@gateway/web/freenode/ip.80.188.140.186> has quit IRC | 16:03 | |
| *** stwcx <stwcx!~stwcx@32.97.110.52> has joined #yocto | 16:07 | |
| *** seebs <seebs!~seebs@home.seebs.net> has quit IRC | 16:08 | |
| *** seebs <seebs!~seebs@home.seebs.net> has joined #yocto | 16:09 | |
| -YoctoAutoBuilder- build #550 of nightly-ppc is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds/550 | 16:12 | |
| *** ionte <ionte!~textual@83.233.227.60> has quit IRC | 16:12 | |
| *** NileshKokane <NileshKokane!uid116340@gateway/web/irccloud.com/x-jkbgsvvzffolopkr> has joined #yocto | 16:12 | |
| *** Nilesh_ <Nilesh_!uid116340@gateway/web/irccloud.com/x-pwawfihfopotlxfq> has joined #yocto | 16:13 | |
| *** tsramos <tsramos!tsramos@nat/intel/x-nkqxiqwtixbubhnn> has quit IRC | 16:16 | |
| *** sjolley <sjolley!~sjolley@134.134.137.75> has quit IRC | 16:17 | |
| *** tsramos <tsramos!~tsramos@134.134.139.70> has joined #yocto | 16:19 | |
| *** c10ud <c10ud!~c10ud@emesene/dictator/c10ud> has quit IRC | 16:20 | |
| *** c10ud <c10ud!~c10ud@emesene/dictator/c10ud> has joined #yocto | 16:21 | |
| *** mckoan is now known as mckoan|away | 16:23 | |
| *** tsramos <tsramos!~tsramos@134.134.139.70> has quit IRC | 16:27 | |
| *** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC | 16:27 | |
| *** tsramos_ <tsramos_!~tsramos@192.55.54.43> has joined #yocto | 16:29 | |
| *** frsc <frsc!~frsc@80.149.173.68> has quit IRC | 16:29 | |
| *** Ulfalizer <Ulfalizer!~ulf@217.89.178.116> has quit IRC | 16:30 | |
| *** justanotherboy <justanotherboy!mlopezva@nat/intel/x-adhtydrwzpiuvted> has quit IRC | 16:32 | |
| ryansturmer | @PTBD You may be able to use a precompiled package | 16:32 |
| ryansturmer | you can always grab an rpm or something and try it out | 16:33 |
| *** justanotherboy <justanotherboy!mlopezva@nat/intel/x-awurxzecdipgvzxy> has joined #yocto | 16:33 | |
| ryansturmer | Guys I've convinced my yocto build process to build an initramfs image to run a "live" installation | 16:33 |
| ryansturmer | but I'm having difficulty with my boot process getting the kernel to use that image. | 16:33 |
| ryansturmer | Does anyone know if, when I build with "live" in my IMAGE_FSTYPES is the image built into the kernel? Or is it stored externally such that I have to tell the kernel where to find it. | 16:34 |
| ryansturmer | I can see in my installation that it's placed at /boot/initrd | 16:34 |
| ryansturmer | but passing initrd=/boot/initrd to my kernel command line doesn't seem to work. | 16:35 |
| ryansturmer | (I am booting with u-boot) | 16:35 |
| -YoctoAutoBuilder- build #545 of nightly-mips is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/545 | 16:40 | |
| *** adtec <adtec!~adtec@107-0-144-157-ip-static.hfc.comcastbusiness.net> has joined #yocto | 16:47 | |
| *** PTBD <PTBD!2eedcbbe@gateway/web/freenode/ip.46.237.203.190> has quit IRC | 16:47 | |
| adtec | Hi, can anyone tell me if it is possible to have two *.inc files in different layers? | 16:47 |
| *** aime-Pierre <aime-Pierre!~Thunderbi@193.56.60.161> has quit IRC | 16:49 | |
| *** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-mdaapfieoibjontc> has joined #yocto | 16:49 | |
| adtec | I need to change the SRC_URI in meta-fsl-arm/.../linux-ls1.inc from the Freescale repository to my own clone | 16:49 |
| *** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-mdaapfieoibjontc> has left #yocto | 16:49 | |
| *** sjolley <sjolley!sjolley@nat/intel/x-vpokuwplesuvhpxp> has joined #yocto | 16:49 | |
| *** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto | 16:51 | |
| *** bluelightning <bluelightning!~paul@122-62-222-219.jetstream.xtra.co.nz> has joined #yocto | 16:53 | |
| *** bluelightning <bluelightning!~paul@122-62-222-219.jetstream.xtra.co.nz> has quit IRC | 16:53 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 16:53 | |
| *** aragua <aragua!~flahouder@212.194.216.83> has quit IRC | 16:57 | |
| *** jonathanmaw_ is now known as jonathanmaw | 16:57 | |
| *** belen <belen!~Adium@192.198.151.43> has quit IRC | 17:01 | |
| *** belen <belen!Adium@nat/intel/x-htfdqgzqfidofypi> has joined #yocto | 17:06 | |
| *** toscalix <toscalix!~agustinbe@92.58.21.123> has joined #yocto | 17:06 | |
| *** maxin1 <maxin1!~maxin@194.136.86.45> has quit IRC | 17:12 | |
| *** fl0v0 <fl0v0!~fvo@p5DDC7134.dip0.t-ipconnect.de> has quit IRC | 17:16 | |
| *** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC | 17:18 | |
| *** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has joined #yocto | 17:19 | |
| *** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto | 17:19 | |
| *** vmrod25 <vmrod25!vrodri3@nat/intel/x-aapmxbxktjtevcdw> has joined #yocto | 17:25 | |
| vmrod25 | benjamirc: ping | 17:25 |
| *** vmrod25 is now known as vmrod | 17:25 | |
| *** tsramos_ <tsramos_!~tsramos@192.55.54.43> has quit IRC | 17:26 | |
| *** yann|work <yann|work!~yann@LFbn-1-1026-146.w86-247.abo.wanadoo.fr> has quit IRC | 17:26 | |
| *** khem` <khem`!~khem@unaffiliated/khem> has quit IRC | 17:26 | |
| *** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto | 17:28 | |
| *** LocutusOfBorg1 <LocutusOfBorg1!~LocutusOf@93.51.30.27> has quit IRC | 17:34 | |
| benjamirc | jes vmrod | 17:35 |
| *** armpit <armpit!~akuster@2601:202:4000:1239:ad41:a0ff:4903:cbc> has quit IRC | 17:37 | |
| ryansturmer | What do I need to clean with bitbake to get a rebuild of the kernel? | 17:42 |
| ryansturmer | I have changed CONFIG_INITRAMFS_SOURCE in my image .bb file, but this hasn't provoked a kernel rebuild, so I want to clean whatever is appropriate to trigger a rebuild | 17:43 |
| bluelightning | ryansturmer: so our manual claims that CONFIG_INITRAMFS_SOURCE is a variable you can set, but searching around I don't think that it is | 17:44 |
| bluelightning | so I don't think any cleaning will help | 17:44 |
| bluelightning | what are you attempting to do exactly | 17:45 |
| ryansturmer | Ha! | 17:45 |
| bluelightning | ? | 17:45 |
| ryansturmer | Well, I thought it was suspicious that that happened also to be the name of a kernel config parameter | 17:45 |
| ryansturmer | Thought bitbake was doing something clever for me. | 17:45 |
| ryansturmer | Do you have any experience with building a 'live' image? | 17:45 |
| ryansturmer | I feel like what I want to do is simple, but it's really fighting me | 17:46 |
| bluelightning | a little | 17:46 |
| *** jbrianceau is now known as jbrianceau_away | 17:47 | |
| ryansturmer | Well, so I want a "live" distribution, which I understand is achieved the way most live distros are, where in an initrd you mount the rootfs read only, then do a tmpfs (or similar) overlay with union,aufs, or overlayfs | 17:49 |
| *** tsramos <tsramos!~tsramos@192.55.54.40> has joined #yocto | 17:49 | |
| ryansturmer | so I added "live" to my IMAGE_FSTYPES variable, which according to the manual, is supposed to do most of the work | 17:49 |
| ryansturmer | it did indeed build a core-image-minimal-initramfs-machine.cpio.gz image for me | 17:50 |
| ryansturmer | and that image does indeed land in my final distribution, in /boot alongside my linux kernel image | 17:50 |
| ryansturmer | however, nothing I pass to the kernel by way of parameters seems to be able to convince it to use the initrd | 17:51 |
| ryansturmer | it seems like a lot of kids these days are just building the initramfs into the kernel image itself to simplify things - but I'm not sure how to tell it "hey, go here for this image, and build it in as your initrd" - that's what that kernel parameter is all about, I just don't know how to hook it up. | 17:52 |
| ryansturmer | Although, I kind of like the idea of the initramfs being a separate file - so I can tinker with it if I want (and I almost certainly will want) without repackaging my kernel. | 17:53 |
| ryansturmer | So that's my life story, basically. | 17:53 |
| bluelightning | it's supposed to do that for you by way of INITRAMFS_IMAGE being set to point to the image recipe | 17:53 |
| ryansturmer | supposed to build it into the kernel | 17:53 |
| bluelightning | if you "git grep CONFIG_INITRAMFS_SOURCE" you can see how it does that | 17:53 |
| *** tsramos <tsramos!~tsramos@192.55.54.40> has quit IRC | 17:53 | |
| ryansturmer | by including "live" though in that FSTYPES variable, that should be happening for me, you're saying? | 17:54 |
| *** townxelliot <townxelliot!~ell@94.13.69.111> has quit IRC | 17:54 | |
| ryansturmer | (And of course by not obliterating INITRAMFS_IMAGE myself somewhere else | 17:55 |
| bluelightning | yes | 17:55 |
| *** deviosity <deviosity!~deviosity@c-67-160-33-141.hsd1.wa.comcast.net> has joined #yocto | 17:56 | |
| *** belen <belen!Adium@nat/intel/x-htfdqgzqfidofypi> has quit IRC | 17:56 | |
| *** roccof <roccof!~roccof@93-51-177-218.ip268.fastwebnet.it> has quit IRC | 17:58 | |
| *** Biliogadafr <Biliogadafr!~User@port-35-adslby-pool45.infonet.by> has quit IRC | 18:00 | |
| *** NileshKokane <NileshKokane!uid116340@gateway/web/irccloud.com/x-jkbgsvvzffolopkr> has quit IRC | 18:01 | |
| *** Nilesh_ <Nilesh_!uid116340@gateway/web/irccloud.com/x-pwawfihfopotlxfq> has quit IRC | 18:01 | |
| *** jonathanmaw <jonathanmaw!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has quit IRC | 18:02 | |
| ryansturmer | Well, my system doesn't appear to be doing the initramfs thing, because I see no evidence of it in the log, at startup or in the kernel message buffer | 18:02 |
| ryansturmer | Is there a place I can see the kernel configuration after it's been all fused with configuration fragments etc? | 18:08 |
| ryansturmer | because I should be able to see that configuration parameter in there, right? if INITRAMFS_IMAGE is doing its job? | 18:09 |
| bluelightning | ryansturmer: yes, there should be a .config file in a build-<architecture> subdirectory under the workdir for the kernel | 18:09 |
| bluelightning | yes, it should show up there | 18:09 |
| *** tastycactus <tastycactus!~aaron@ip68-2-230-180.ph.ph.cox.net> has joined #yocto | 18:11 | |
| ryansturmer | Man there's a lot of directories | 18:16 |
| ryansturmer | which is the workdir for the kernel | 18:16 |
| ryansturmer | if I'm in tmp/ | 18:16 |
| vmrod | benjamirc: I was thinking if yocto could be benefict from autoGFDO | 18:16 |
| challinan | ryansturmer: bitbake -e virtual/kernel | grep ^WORKDIR= will point you to the kernel's workdir | 18:17 |
| bluelightning | right, what challinan said ;) | 18:17 |
| ryansturmer | There's a defconfig here, and it doesn't contain the CONFIG_INITRD_SOURCE (it's set to empty string) | 18:21 |
| ryansturmer | INITRAMFS_SOURCE excuse me | 18:21 |
| bluelightning | hmm | 18:23 |
| ryansturmer | is it possible I Have a recipe that's just overwriting the kernel configuration | 18:23 |
| bluelightning | is INITRAMFS_IMAGE actually set? | 18:23 |
| *** tsramos <tsramos!~tsramos@192.55.54.40> has joined #yocto | 18:23 | |
| ryansturmer | how do I check that? | 18:23 |
| bluelightning | bitbake -e virtual/kernel | less then search for INITRAMFS_IMAGE with / | 18:24 |
| *** jmpdelos <jmpdelos!~polk@delos.delosent.com> has quit IRC | 18:25 | |
| ryansturmer | No, it appears never to be set. | 18:25 |
| *** NileshKokane <NileshKokane!uid116340@gateway/web/irccloud.com/x-gldjrvspqeugmcxu> has joined #yocto | 18:25 | |
| ryansturmer | INITRAMFS_IMAGE does not appear in the output of bitbake -e virtual/kernel at all | 18:25 |
| *** Nilesh_ <Nilesh_!uid116340@gateway/web/irccloud.com/x-isgvmxzljkvcucbu> has joined #yocto | 18:26 | |
| bluelightning | ah, I guess it's doing it through INITRD_IMAGE | 18:27 |
| bluelightning | which is something subtly different | 18:27 |
| *** kratsg <kratsg!82c703a5@gateway/web/freenode/ip.130.199.3.165> has joined #yocto | 18:29 | |
| *** psadro <psadro!~Thunderbi@2620:0:ed0:800a:72f3:95ff:fe1d:9866> has quit IRC | 18:29 | |
| kratsg | In meta-python, how do I use a different version of a package? | 18:29 |
| kratsg | (what is $PV?) | 18:30 |
| bluelightning | kratsg: http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-PV | 18:31 |
| bluelightning | kratsg: PREFERRED_VERSION_<recipename> is how you select between different versions if the one built by default isn't the one you want | 18:31 |
| *** psadro <psadro!~Thunderbi@2620:0:ed0:800a:72f3:95ff:fe1d:9866> has joined #yocto | 18:32 | |
| tastycactus | Trying to build on Ubuntu 15.10 and running into this problem with qemu-native: http://patchwork.openembedded.org/patch/106579/ | 18:32 |
| kratsg | What if there is only one version? I'm looking at python-twisted right now. | 18:32 |
| tastycactus | Is there a workaround? | 18:32 |
| kratsg | It has only 13.2.0 -- so I think I need to make a new recipe in there, update the hash and version. | 18:32 |
| bluelightning | kratsg: er, then you wouldn't need to select one... ? | 18:32 |
| bluelightning | kratsg: ah right now I understand | 18:32 |
| kratsg | I need a later version of twisted. | 18:32 |
| bluelightning | kratsg: right yes, you'd need to create a recipe for that version | 18:32 |
| kratsg | [pip install on the board doesn't work] | 18:32 |
| kratsg | Should there be a pull request to the github repo with the new version added? It's not clear what people normally do. | 18:33 |
| bluelightning | tastycactus: yes - see https://bugzilla.yoctoproject.org/show_bug.cgi?id=8553 | 18:33 |
| yocti | Bug 8553: normal, Medium+, 2.1, eduard.bartosh, IN PROGRESS REVIEW , qemu-native to build on Ubuntu 15.10 | 18:33 |
| bluelightning | kratsg: http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded | 18:34 |
| *** khem` <khem`!~khem@unaffiliated/khem> has quit IRC | 18:35 | |
| tastycactus | bluelightning, thanks | 18:35 |
| kratsg | gotcha. | 18:35 |
| *** jmpdelos <jmpdelos!~polk@delos.delosent.com> has joined #yocto | 18:38 | |
| kratsg | bluelightning: now that I've written the recipe for the new version | 18:40 |
| kratsg | what's the straightforward way of making sure it's right? | 18:41 |
| *** toscalix <toscalix!~agustinbe@92.58.21.123> has quit IRC | 18:44 | |
| kratsg | Hrmm, it can't find it. I tried "15.4.0_python-twisted" | 18:44 |
| bluelightning | kratsg: bitbake python-twisted should be building the new version if you've put it in a place that bitbake can find it | 18:45 |
| *** LocutusOfBorg1 <LocutusOfBorg1!~LocutusOf@151.44.222.121> has joined #yocto | 18:46 | |
| kratsg | Right, it looks like `bitbake -s` reports the new version | 18:46 |
| kratsg | if I wanted to select the older version (13.2.0) I would have to do `13.2.0_python-twisted` instead? | 18:46 |
| kratsg | or, you mean edit the local.conf and add the PREFERRED_VERSION_python-twisted = 13.2.0 ? | 18:47 |
| ryansturmer | bluelightning FWIW INITRD_IMAGE doesn't appear in the bitbake -e virtual/kernel output either. | 18:47 |
| bluelightning | ryansturmer: INITRD_IMAGE is handled at the image level | 18:48 |
| bluelightning | rather than the kernel | 18:49 |
| ryansturmer | so again, though that's not something I should have to specify, right? | 18:49 |
| bluelightning | kratsg: you can't build a specific version on the command line - you can set PREFERRED_VERSION_python-twisted though | 18:49 |
| bluelightning | kratsg: it should pick the latest version (assuming you haven't put it in a layer that has a lower priority than the one with the older version) | 18:50 |
| kratsg | Oh, I see. This makes sense. | 18:50 |
| kratsg | I'm running into the license file checksum not matching. | 18:50 |
| ryansturmer | and the kernel .config in the workdir should be turning up with the CONFIG_INITRAMFS_SOURCE by way of the live-image class? | 18:51 |
| kratsg | i think I got it. Thanks. I'll see if I can do a PR successfully later. | 18:51 |
| *** LocutusOfBorg1 <LocutusOfBorg1!~LocutusOf@151.44.222.121> has quit IRC | 18:51 | |
| kratsg | But I might create my own meta specifically for the series of python packages I need for sure. | 18:52 |
| kratsg | so that I can install/roll my own. | 18:52 |
| kratsg | since I have a custom pypi python package I wrote that depends on the twisted version, etc. | 18:52 |
| kratsg | errr, so I have the warning that files/directories were installed but not shipped | 18:53 |
| kratsg | I should probably update the recipe to include/ship them. | 18:54 |
| kratsg | Do you have a good link explaining how to write that portion of the recipe? | 18:54 |
| *** vmrod <vmrod!vrodri3@nat/intel/x-aapmxbxktjtevcdw> has left #yocto | 18:57 | |
| *** ZrZ is now known as RzR | 18:58 | |
| *** matteo <matteo!~matteo@openwrt/developer/matteo> has quit IRC | 19:11 | |
| bluelightning | kratsg: here's the section talking about that warning FWIW: http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#qa-issue-installed-vs-shipped | 19:14 |
| *** t0mmy <t0mmy!~tprrt@217.114.201.133> has quit IRC | 19:24 | |
| kratsg | thanks! | 19:37 |
| kratsg | when a recipe does something like "inherit core-image" | 19:41 |
| kratsg | where is core-image? | 19:41 |
| mario-goulart | kratsg: since it is used with "inherit", it is a class. You can usually find classes in the toplevel directory of layers. The suffix is .bbclass | 19:43 |
| kratsg | Oh I see, this makes sense. | 19:43 |
| jmesmon | I'm trying to build crda from meta-openembedded, and it keeps complainin about "No module named _m2crypto" during the build. The crda_3.18.bb file does have a DEPENDS that includes python-m2crypto-native, so I'm not sure what is going on here | 19:43 |
| mario-goulart | kratsg: I mean, you can usually find a "class" directory in the toplevel directory of layers. | 19:44 |
| jmesmon | from some googling, it sounds like __m2crypto (2 underscores) is a shared library it builds, but I haven't seen anything about the 1 underscore version | 19:44 |
| mario-goulart | kratsg: that particular one is openembedded-core/meta/classes/core-image.bbclass | 19:44 |
| kratsg | yep, I found it -- thanks. | 19:45 |
| kratsg | Still trying to get the hang of how it finds everything, but coo. | 19:45 |
| kratsg | When I write a recipe for an image (that bitbake uses) - do I let bitbake handle dependency resolution? | 19:45 |
| kratsg | (image features) | 19:45 |
| kratsg | would that recipe be also where I do something like `PREFERRED_VERSION_<recipe> = x.y.z` as well? | 19:47 |
| kratsg | or does that go in the local.conf file? | 19:47 |
| kratsg | err* layer.conf | 19:47 |
| mario-goulart | You usually specify build (DEPENDS) and runtime dependencies (RDEPENDS). | 19:48 |
| kratsg | So, I'm creating a new layer that specifies a bunch of recipes - since I'll need to maintain it more often than say the meta-python one. | 19:49 |
| kratsg | so it's here: https://github.com/kratsg/meta-l1calo | 19:50 |
| *** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-rlsvsblppeonbfek> has quit IRC | 19:50 | |
| kratsg | In particular, I have recipes-core/python/python-twisted_15.4.0.bb | 19:50 |
| kratsg | nominally, I would need to make sure the image in recipes-core/images/zynq-base.bb enforces that we want 15.4.0? | 19:50 |
| mario-goulart | Where to put PREFERRED_VERSION_<recipe> depends on the recipe, I'd say. For BSP-related recipes, I think the best place is the machine configuration file. Some core recipes may have their versions specified in distro configuration files. Other specific uses can go to regular recipes and/or include files. | 19:51 |
| mario-goulart | local.conf is not a good place for such configurations, IMO. I don't tend to keep local.conf under version control. But maybe that's just my workflow. | 19:52 |
| kratsg | I'm not really creating a BSP. | 19:53 |
| kratsg | meta-xilinx is a BSP-specific recipe, so I need to have a recipe that basically defines the specific image features | 19:53 |
| kratsg | and one of the features is python-twisted, 13.2.0 is in meta-python, but i should ensure, in zynq-base.bb, that i have 15.4.0 | 19:53 |
| kratsg | if that makes sense. | 19:54 |
| *** fledermaus <fledermaus!~vivek@pakora.collabora.co.uk> has quit IRC | 19:55 | |
| mario-goulart | It makes sense. The confusing bit is that you are talking about "image features" which has a special meaning: http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#ref-features-image I suppose that's not what you are talking about. | 19:59 |
| jmesmon | on my m2crypto issue: it looks like _m2crypto.py should be a swig generated python file, but it isn't being installed | 19:59 |
| mario-goulart | kratsg: If I understand correctly, you just want to add a package at a particular version to your image, right? | 20:00 |
| *** var_x <var_x!~varx.org@wsip-98-178-241-136.oc.oc.cox.net> has joined #yocto | 20:00 | |
| kratsg | right, but it won't be just one python package | 20:00 |
| kratsg | I'll be adding a few specific python packages (xmltodict, construct, twisted) with specific minimal versions | 20:00 |
| *** maxin <maxin!~maxin@dsl-espbrasgw1-54fa70-49.dhcp.inet.fi> has joined #yocto | 20:00 | |
| *** maxin <maxin!~maxin@dsl-espbrasgw1-54fa70-49.dhcp.inet.fi> has left #yocto | 20:00 | |
| jmesmon | and now after a cleanall and retry, it is there >.> | 20:03 |
| *** stwcx <stwcx!~stwcx@32.97.110.52> has quit IRC | 20:05 | |
| *** seebs <seebs!~seebs@home.seebs.net> has quit IRC | 20:08 | |
| *** adtec <adtec!~adtec@107-0-144-157-ip-static.hfc.comcastbusiness.net> has quit IRC | 20:10 | |
| *** armpit <armpit!~akuster@64.2.3.194> has joined #yocto | 20:15 | |
| kratsg | mario-goulart: https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/images/zynq-base.bb | 20:16 |
| kratsg | this is an example of a recipe -- the IMAGE_FEATURES is there. | 20:16 |
| *** seebs <seebs!~seebs@home.seebs.net> has joined #yocto | 20:17 | |
| kratsg | So while I don't need it hardware specific, it seems like people add a PREFERRED_VERSION into their local.conf file when bitbaking. Maybe that should be enough and hope it picks up the later version. | 20:18 |
| kratsg | I'm still trying to get it to produce a uramdisk image so I don't need to do it. | 20:18 |
| *** stwcx <stwcx!~stwcx@32.97.110.55> has joined #yocto | 20:19 | |
| *** Nilesh_ <Nilesh_!uid116340@gateway/web/irccloud.com/x-isgvmxzljkvcucbu> has quit IRC | 20:35 | |
| *** NileshKokane <NileshKokane!uid116340@gateway/web/irccloud.com/x-gldjrvspqeugmcxu> has quit IRC | 20:35 | |
| kratsg | awkward, "python-modules" is not a valid image feature. | 20:42 |
| mario-goulart | kratsg: those don't look like valid IMAGE_FEATURES. | 20:42 |
| mario-goulart | You probably want something like CORE_IMAGE_EXTRA_INSTALL | 20:43 |
| mario-goulart | http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#ref-features-image lists the valid image features. | 20:44 |
| kratsg | mario-goulart: Those were valid. I used it before. | 20:44 |
| *** LocutusOfBorg1 <LocutusOfBorg1!~LocutusOf@host141-33-dynamic.54-79-r.retail.telecomitalia.it> has joined #yocto | 20:45 | |
| *** [Sno] <[Sno]!~sno@rademacherexchange.de> has quit IRC | 20:46 | |
| bluelightning | kratsg: unless you have taken steps to define python-modules as a feature, it never has been | 20:47 |
| bluelightning | kratsg: it's the name of a package, so you'd add it to IMAGE_INSTALL or CORE_IMAGE_EXTRA_INSTALL to add it to the image | 20:47 |
| kratsg | bluelightning: where is the package? I can't find it. | 20:48 |
| bluelightning | it's produced by the main python recipe | 20:48 |
| kratsg | bitbake doesn't list it, but it's in some other recipes, so I'm not sure how I don't have it. | 20:48 |
| bluelightning | packages (i.e. what you install into an image) and recipes aren't mapped 1-1... most recipes produce more than one package | 20:49 |
| bluelightning | how are you determining you don't have it? | 20:49 |
| *** tsramos <tsramos!~tsramos@192.55.54.40> has quit IRC | 20:49 | |
| kratsg | bitbake complains. | 20:50 |
| bluelightning | complains when you add it where? | 20:50 |
| kratsg | so it must be some weird misconfiguration of the layer I'm making. | 20:50 |
| kratsg | I added it to https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/images/zynq-base.bb | 20:50 |
| bluelightning | that's because you added it to IMAGE_FEATURES, as I said it's not an image feature | 20:50 |
| bluelightning | add it to IMAGE_INSTALL instead | 20:51 |
| bluelightning | (none of the other things you are adding are features either, they're all packages) | 20:51 |
| *** benjamirc <benjamirc!~besquive@134.134.137.71> has quit IRC | 20:52 | |
| kratsg | how does a recipe produce more than one package? | 20:52 |
| *** anselmolsm <anselmolsm!~anselmols@192.55.54.43> has quit IRC | 20:52 | |
| bluelightning | kratsg: during do_package, the set of files installed during do_install are almost always split into multiple packages | 20:52 |
| *** roric <roric!~roric@h196n19-vrr-a31.ias.bredband.telia.com> has joined #yocto | 20:53 | |
| bluelightning | in the simplest case, the files for the recipe (e.g. libraries, executables) go into the main package (named the same as the recipe); docs go into the *-doc package, debug symbols go into the *-dbg package, headers and other development files go into the *-dev package, etc. | 20:53 |
| kratsg | so if I have something like recipes-core/package.bb | 20:54 |
| kratsg | then I need recipes-core/package/ as well as recipes-core/package-docs/ and so on? | 20:54 |
| bluelightning | a recipe can add or change the packages it produces by adjusting the PACKAGES and FILES variables (which control which packages are generated and which files go into each package, respectively) | 20:54 |
| bluelightning | kratsg: no - you're conflating packages and recipes... there's only one recipe required, PACKAGES set within it (or the default value) specifies which packages it generates | 20:55 |
| kratsg | so everything the recipe produces goes into whatever package it makes? | 20:56 |
| bluelightning | whatever packages yes | 20:57 |
| bluelightning | (or it should, otherwise you'll get the "installed-vs-shipped" warning we talked about earlier) | 20:57 |
| kratsg | so i'm looking at python-twisted | 20:57 |
| kratsg | I had to remove `lore` completely. | 20:57 |
| kratsg | Why is it making like 18 different packages? | 20:57 |
| kratsg | shouldn't it all go under a `twisted` folder? | 20:57 |
| kratsg | inside of python2.7/site-packages? | 20:58 |
| kratsg | (also not sure what RDEPENDS is doing here) | 20:58 |
| bluelightning | kratsg: it's been split that way so you have some control over what pieces you install into your image | 20:59 |
| bluelightning | kratsg: in the embedded context usually you want to tune what goes into your image to save space | 21:00 |
| kratsg | so.. how does one tune that? | 21:00 |
| kratsg | what is a person actually doing to get, twisted-core and nothing else? | 21:00 |
| kratsg | (python-twisted seems to get everything) | 21:00 |
| bluelightning | simply by only adding the packages you want to IMAGE_INSTALL | 21:01 |
| kratsg | so it's called python-twisted-core instead of python-twisted if they just want core? | 21:01 |
| kratsg | I see, well, i have to completely change this twisted though, since 15.4.0 got rid of like 90% of the files that were in 13.2.0 | 21:01 |
| bluelightning | right, the RDEPENDS_${PN} line in there specifies that the main package (${PN} which will translate to python-twisted) depends on all of the listed packages, so it will pull all of those in | 21:01 |
| kratsg | I see. | 21:02 |
| bluelightning | assuming you'll be sending this as an update it would be nice to preserve some flexibility about which components to install if it's practical to do so | 21:02 |
| kratsg | I'll try. but i have to remove portions. | 21:02 |
| bluelightning | fair enough | 21:03 |
| kratsg | since they don't exist anymore. | 21:03 |
| kratsg | Do you have to do this manually for any python package you want? | 21:03 |
| bluelightning | the package splitting ? | 21:04 |
| kratsg | well, defining all the files and so on. | 21:04 |
| kratsg | i'm not entirely sure if twisted can be split like this anymore though. | 21:04 |
| bluelightning | it depends whether it's practical and really necessary... if you look at some other python recipes you'll see they don't bother doing this kind of thing | 21:05 |
| kratsg | (I used it in 13.X and now 15.4 and it's entirely different) | 21:05 |
| kratsg | (interface-wise) | 21:05 |
| kratsg | oh, wait, so that means if twisted depends on zope.interface (which it does), I need to write a bb recipe for installing that as well? | 21:06 |
| bluelightning | assuming one doesn't exist already | 21:07 |
| kratsg | oh, hrmm. | 21:08 |
| bluelightning | http://layers.openembedded.org/layerindex/branch/master/recipes/ is the place to find that out | 21:08 |
| *** sameo <sameo!~samuel@192.55.54.38> has joined #yocto | 21:08 | |
| bluelightning | I just noticed... this recipe uses ${libdir}/${PYTHON_DIR}/site-packages everywhere, but there is a variable PYTHON_SITEPACKAGES_DIR you can use to save typing all of that | 21:09 |
| kratsg | oh that's cool that python-construct exists.. actually. | 21:09 |
| kratsg | so | 21:09 |
| kratsg | i need to make sure all dependencies are resolved? | 21:09 |
| kratsg | if I have package A->B->C | 21:09 |
| kratsg | I have to make sure A (depending on B) and B (depending on C) and C -- have all their dependencies resolved. | 21:10 |
| bluelightning | yes | 21:10 |
| kratsg | I see, ok. I guess I ahve a bit of work to do, but that's fine. | 21:10 |
| bluelightning | note that sometimes recipes (such as python-construct) are in layers that aren't the most convenient place for re-use | 21:10 |
| *** stwcx <stwcx!~stwcx@32.97.110.55> has quit IRC | 21:11 | |
| kratsg | what does that mean specifically? | 21:11 |
| bluelightning | if you're using 2.0 / master, I'd suggest using "devtool add" (or "recipetool create") to create new python recipes, it will figure out a lot of the dependencies for you and take out a lot of the drudgery of writing the recipe | 21:11 |
| kratsg | Oh, that would be nice. | 21:11 |
| kratsg | I have an overall python package that I'm writing | 21:12 |
| kratsg | https://pypi.python.org/pypi/ironman | 21:12 |
| bluelightning | kratsg: well, python-construct seems to be in meta-netmodule-extras; that appears to be a layer someone has thrown together for their own purposes rather than one that is meant to be generally used by others | 21:12 |
| kratsg | so my focus is revolving around making sure that works (and this depends on twisted, construct, xmltodict, etc) | 21:12 |
| *** yann|work <yann|work!~yann@nan92-1-81-57-214-146.fbx.proxad.net> has joined #yocto | 21:12 | |
| *** cbzx <cbzx!~cbzx@CPE0015f275ecd5-CM00195edd810c.cpe.net.cable.rogers.com> has joined #yocto | 21:12 | |
| bluelightning | ah ok, cool | 21:12 |
| kratsg | I don't intend for my python-ironman recipe to be general use, so I'm ok with building my own little metalayer that encapsulates whatever I can't normally grab. | 21:13 |
| moto-timo | might be a candidate to add to meta-python? | 21:13 |
| bluelightning | moto-timo: indeed | 21:13 |
| kratsg | which, construct? | 21:13 |
| moto-timo | yes | 21:13 |
| kratsg | that would be great. | 21:13 |
| kratsg | Super useful package. | 21:13 |
| moto-timo | I'll look into it, unless you beat me to it | 21:14 |
| kratsg | I noticed people suggest something like a .bbappend | 21:15 |
| kratsg | when you're making changes to an existing recipe | 21:15 |
| kratsg | this isn't true when you need an entirely new version, right? | 21:15 |
| *** sameo <sameo!~samuel@192.55.54.38> has quit IRC | 21:16 | |
| *** sameo <sameo!~samuel@192.55.54.38> has joined #yocto | 21:16 | |
| *** yann|work <yann|work!~yann@nan92-1-81-57-214-146.fbx.proxad.net> has quit IRC | 21:17 | |
| kratsg | ok, everything looks good. i'll see about getting devtool add working | 21:18 |
| bluelightning | kratsg: right... bbappends are generally where you want to customise the recipe in a way that is specific to your usage (as opposed to being something that would be generally usefull to others and ought to be upstreamed) | 21:19 |
| *** paulg <paulg!~paulg@173.239.178.230> has joined #yocto | 21:19 | |
| bluelightning | you can use bbappends for doing any modifications though, upstreamable or otherwise - but updating to a newer version is often a bit awkward within a bbappend | 21:20 |
| kratsg | ok, so i was able to actually just update twisted, preliminarily. | 21:20 |
| kratsg | to 15.4.0 | 21:20 |
| kratsg | (a bunch of files it tries to copy don't exist, but ok) | 21:20 |
| kratsg | and then `pip install ironman` on the board seems to get everything working normally! | 21:20 |
| jmesmon | so I've got a '/var/log' symlink in my filesystem/sysroot. oe-pkgdata-util claims that no package produces the path /var/log. How can I figure out what is going on here? | 21:20 |
| *** yann|work <yann|work!~yann@nan92-1-81-57-214-146.fbx.proxad.net> has joined #yocto | 21:21 | |
| jmesmon | ah, looks like links created by fs-perms.txt don't show up as owned by any package, and I hadn't placed my override of fs-perms.txt early enough in the BBLAYERS list. | 21:22 |
| *** stwcx <stwcx!~stwcx@32.97.110.52> has joined #yocto | 21:23 | |
| *** sandsmark <sandsmark!~sandsmark@kde/sandsmark> has quit IRC | 21:24 | |
| kratsg | bluelightning: how do you use devtool add? | 21:24 |
| moto-timo | latest python-construct on pypi is 2.5.2 vs. 2.5.1 in meta-netmodule-extras | 21:24 |
| moto-timo | I'll give the maintainer of that layer a heads up and get it into meta-python | 21:25 |
| kratsg | also, where do I find the python-modules package? it seems like a virtual package, no actual recipe exists for it? | 21:25 |
| *** roric <roric!~roric@h196n19-vrr-a31.ias.bredband.telia.com> has quit IRC | 21:25 | |
| bluelightning | kratsg: as I mentioned earlier, python-modules is produced by the main python recipe | 21:26 |
| kratsg | the main python recipe? is that in openembedded-core? | 21:27 |
| moto-timo | see line 159 in http://git.openembedded.org/openembedded-core/tree/meta/recipes-devtools/python/python_2.7.9.bb | 21:27 |
| bluelightning | kratsg: yes, what moto-timo said ^ | 21:27 |
| bluelightning | kratsg: basically devtool add name-of-recipe sourcepath (where name-of-recipe is just the name portion e.g. python-modulename, and sourcepath is a local path) - you can also add -f http://some/url/to/file to fetch a remote source tarball or git repo and unpack it to the specified location | 21:27 |
| *** pohly <pohly!~pohly@p5DE8FABA.dip0.t-ipconnect.de> has quit IRC | 21:29 | |
| moto-timo | meh, the actual python-modules is defined in python-2.7-manifest.inc | 21:29 |
| kratsg | yeah, i was going to ask | 21:29 |
| moto-timo | see line 284 in http://git.openembedded.org/openembedded-core/tree/meta/recipes-devtools/python/python-2.7-manifest.inc | 21:29 |
| kratsg | it looks like `python-modules` depends on `python-misc` in the first file | 21:29 |
| kratsg | ahhh, so there it is. huh. | 21:30 |
| kratsg | bluelightning: let me try the devtool right now | 21:30 |
| kratsg | using a pypi tarball for ironman. | 21:30 |
| moto-timo | that manifest is generated by a script: http://git.openembedded.org/openembedded-core/tree/scripts/contrib/python/generate-manifest-2.7.py | 21:31 |
| kratsg | oh wow. | 21:32 |
| kratsg | that seems really convoluted. | 21:32 |
| moto-timo | necessary evil | 21:32 |
| moto-timo | it's a pain to maintain otherwise | 21:32 |
| kratsg | Ok, so the devtool add command needs a git commit? | 21:32 |
| kratsg | oh, i guess `--no-git` | 21:33 |
| kratsg | ok, do most people do recipes-*/python/python-package_version.bb ? | 21:34 |
| kratsg | instead of recipes-*/python/python-package/python-package_version.bb ? | 21:35 |
| *** paulg <paulg!~paulg@173.239.178.230> has quit IRC | 21:35 | |
| moto-timo | that's a personal preference... when we set-up meta-python JaMa preferred a flatter structure | 21:35 |
| kratsg | i think i prefer a flatter structure. | 21:35 |
| moto-timo | I mostly agree... | 21:36 |
| moto-timo | lol | 21:36 |
| kratsg | so i ran the devtool add. | 21:36 |
| kratsg | I noticed a `PACKAGECONFIG[testing] = ",,,python-pytest"` | 21:36 |
| kratsg | not entirely sure what that does. | 21:37 |
| kratsg | it also doesn't seem to need to do any FILES or PACKAGES. | 21:37 |
| kratsg | but I imagine I need to do that, so I'll have to set that up manually. | 21:38 |
| moto-timo | it's a semi-smart skeleton | 21:38 |
| moto-timo | so there will often be manual tweaks | 21:38 |
| kratsg | I see. | 21:38 |
| kratsg | I definitely need to get twisted updated to remove the extra stuff that's not needed. | 21:39 |
| kratsg | https://github.com/netmodule/meta-netmodule-extras/blob/master/recipes-devtools/python/python-construct_2.5.1.bb | 21:39 |
| kratsg | looks like i'll be making something similar to python-construct :) | 21:39 |
| moto-timo | as for ptest.. see e.g. https://wiki.yoctoproject.org/wiki/Ptest | 21:39 |
| kratsg | ahh, yeah, so I won't need pytest. | 21:40 |
| *** sandsmark <sandsmark!~sandsmark@kde/sandsmark> has joined #yocto | 21:40 | |
| kratsg | The testing can be done with travis CI. | 21:40 |
| moto-timo | also: http://www.yoctoproject.org/docs/1.6.1/dev-manual/dev-manual.html#testing-packages-with-ptest | 21:40 |
| kratsg | it just needs to run on the board, so the test directory can be omitted hopefully. | 21:40 |
| moto-timo | depends on whether you want to run tests on your target | 21:40 |
| moto-timo | for QA purposes, it's best to have the ptest included | 21:41 |
| moto-timo | but we don't require it | 21:41 |
| moto-timo | the more packages you maintain, the happier you will be that you have ptest | 21:41 |
| moto-timo | lol | 21:41 |
| kratsg | but ptest has to have access to the target? | 21:42 |
| *** WarheadsSE <WarheadsSE!~WarheadsS@c-174-54-190-115.hsd1.pa.comcast.net> has joined #yocto | 21:42 | |
| kratsg | I have to take the generated image and do more with it that bitbake can't do easily before I can get it on the target. | 21:42 |
| moto-timo | when you build an image with ptest, it installs on the target | 21:42 |
| WarheadsSE | What would be the fastest way to clean up kernel-module-* ? I am htting one of these after changing the assigned kernel 4.3.0-rc3 does not match kernel-abiversion (4.2.6) | 21:43 |
| WarheadsSE | What would be the fastest way to clean up kernel-module-* ? I am htting one of these after changing the assigned kernel 4.3.0-rc3 does not match kernel-abiversion (4.2.6)/bu11 | 21:44 |
| moto-timo | kratsg: like an emmc flasher or what? | 21:44 |
| WarheadsSE | sorry :/ | 21:44 |
| kratsg | well, I have to put it through mkimage first | 21:44 |
| *** fledermaus <fledermaus!~vivek@78.32.176.249> has joined #yocto | 21:45 | |
| kratsg | and then walk over and boot from SDCard. | 21:45 |
| kratsg | (also python-core versus python-lang? I think python-core is the more reasonable dependency) | 21:46 |
| moto-timo | you might want to look into 'wic' which helps with creating flash images, etc. | 21:46 |
| *** stwcx <stwcx!~stwcx@32.97.110.52> has quit IRC | 21:47 | |
| moto-timo | I'd start with python-core, yes | 21:47 |
| kratsg | So I have to pass it through mkimage first. | 21:47 |
| kratsg | mkimage -A arm -T ramdisk -C gzip -d inputFile.cpio.gz uramdisk.image.gz | 21:47 |
| kratsg | presumably, this would be part of a local.conf setting for a post execute | 21:48 |
| kratsg | but that does require u-boot-tools on the computer | 21:48 |
| moto-timo | http://www.yoctoproject.org/docs/1.8/dev-manual/dev-manual.html#creating-partitioned-images | 21:48 |
| kratsg | moto-timo: I don't get it? | 21:50 |
| kratsg | see, that's not the only thing I have to do though. | 21:50 |
| kratsg | since I need to take the kernel image and pass it through xilinx's SDK to produce a special boot.bin | 21:50 |
| moto-timo | just a suggestion, YMMV | 21:50 |
| moto-timo | ah | 21:50 |
| kratsg | It's not the easiest procedure. | 21:51 |
| kratsg | Once I have the uramdisk image, I still need to recompile and generate some stuff based on it. | 21:51 |
| kratsg | so right now, i'm focusing on a nice workflow that is sensible, and then will try and clean things up later. | 21:52 |
| moto-timo | yes | 21:52 |
| kratsg | so the automated testing is a nice feature, but i at least have that done with travis + landscape + coverage, so things are ok. | 21:52 |
| moto-timo | depends on your QA requirements, ultimately :) | 21:53 |
| moto-timo | but certainly you sound like you have some reason to be confident :) | 21:54 |
| kratsg | https://github.com/kratsg/ironman#ironman | 21:54 |
| kratsg | i like to think all my automation here is covering whatever I add in the meantime | 21:54 |
| kratsg | Ok, i think I have most everyhing settled for right now, thanks. | 21:56 |
| kratsg | The last question is with layers. | 21:56 |
| kratsg | When someone sets up a poky, and then sources oe -- do you just instruct them on adding all the necessary layers they need? | 21:57 |
| kratsg | EG: I'm making a layer: `meta-l1calo` which depends on `meta-python` and `meta-oe`. I can just tell them to get `meta-l1calo` and bitbake will let them know how to get the other layers it depends on? | 21:57 |
| bluelightning | Toaster can take care of that if meta-l1calo appears in the layer index (you should submit it when it's usable by others) | 22:01 |
| bluelightning | also that's the idea behind bitbake-layers layerindex-add although that has some minor usability issues that need working out | 22:01 |
| *** [Sno] <[Sno]!~sno@p578b540c.dip0.t-ipconnect.de> has joined #yocto | 22:03 | |
| kratsg | huh. layerindex-add? | 22:03 |
| bluelightning | bitbake-layers layerindex-add --help | 22:04 |
| bluelightning | er | 22:04 |
| bluelightning | sorry | 22:04 |
| bluelightning | layerindex-fetch | 22:04 |
| kratsg | oh, that's very cool | 22:04 |
| kratsg | basically like pip for layers. | 22:04 |
| bluelightning | pretty much yeah | 22:05 |
| moto-timo | so much better than 5 years ago :) | 22:05 |
| kratsg | but it has to be from that centralized index? | 22:05 |
| kratsg | i'm surprised you can't pass in a custom layer location | 22:05 |
| kratsg | since my layer depends only on layers that exist in the index. | 22:05 |
| bluelightning | if you want the dependency resolution yes | 22:05 |
| kratsg | i feel like I don't want to pollute the layer index with my layer... | 22:06 |
| kratsg | for now, I'll just develop with this layer | 22:06 |
| kratsg | and any of the python packages I build, I can patch request to meta-python. | 22:06 |
| bluelightning | the layer index is open to anyone who wants to share their layer, FWIW, but it's entirely optional | 22:06 |
| bluelightning | right, makes sense | 22:06 |
| *** c10ud <c10ud!~c10ud@emesene/dictator/c10ud> has quit IRC | 22:07 | |
| kratsg | alright, thanks. I've got more packages to write apparently. | 22:07 |
| bluelightning | it's possible we could add something to handle the situation you describe i.e. resolve dependencies for a local layer, but the code for that hasn't been written | 22:07 |
| kratsg | right. | 22:07 |
| kratsg | I looked at the python-construct bb file | 22:07 |
| kratsg | it doesn't do anything with FILES | 22:07 |
| kratsg | should it? | 22:07 |
| bluelightning | if the defaults work (as they should for the simple cases, most of the time) then there's no need to set FILES or PACKAGES | 22:08 |
| *** abelloni <abelloni!~abelloni@88.191.26.124> has quit IRC | 22:11 | |
| *** varibull_ <varibull_!~varibull@ta.tainstruments.com> has quit IRC | 22:11 | |
| *** varibull_ <varibull_!~varibull@ta.tainstruments.com> has joined #yocto | 22:11 | |
| kratsg | ok, looking at dependency resolution | 22:15 |
| *** cbzx <cbzx!~cbzx@CPE0015f275ecd5-CM00195edd810c.cpe.net.cable.rogers.com> has quit IRC | 22:15 | |
| kratsg | it looks like construct doesn't need all the packages it lists, just python-six [and maybe python-core] | 22:16 |
| kratsg | for right now this is what I got: https://github.com/kratsg/meta-l1calo/tree/master/recipes-core/python | 22:18 |
| moto-timo | setup.py only lists six, it's possible other deps are hidden and show up when you run it | 22:19 |
| *** clambers <clambers!~clambers@38.104.105.146> has joined #yocto | 22:19 | |
| kratsg | I used `pip show <>` to resolve dependencies. | 22:20 |
| moto-timo | python-core is needed for binascii | 22:23 |
| moto-timo | so that looks like that's it | 22:24 |
| moto-timo | :) | 22:24 |
| *** abelloni <abelloni!~abelloni@88.191.26.124> has joined #yocto | 22:25 | |
| kratsg | Hrmm, why is my LICENSE file missing? | 22:27 |
| kratsg | (pypi seems to not include it) | 22:29 |
| *** WarheadsSE <WarheadsSE!~WarheadsS@c-174-54-190-115.hsd1.pa.comcast.net> has left #yocto | 22:30 | |
| kratsg | welp, duh, fixed it | 22:32 |
| tastycactus | So I'm currently building the kernel with dtb and a ubifs rootfs image. What's the easiest way to either add the kernel and dtb to /boot of the rootfs ubifs image or create a new ubifs image containing the kernel and dtb? | 22:34 |
| tastycactus | Should I do that from a bitbake recipe or an external script? | 22:35 |
| kratsg | thanks for all the help. gonna keep working on this! | 22:38 |
| *** kratsg <kratsg!82c703a5@gateway/web/freenode/ip.130.199.3.165> has left #yocto | 22:38 | |
| *** yann|work <yann|work!~yann@nan92-1-81-57-214-146.fbx.proxad.net> has quit IRC | 22:46 | |
| *** kratsg <kratsg!82c703a5@gateway/web/freenode/ip.130.199.3.165> has joined #yocto | 22:47 | |
| kratsg | Hey, I just did the entire chain moto-timo | 22:47 |
| kratsg | looks like I'm running into a "no module named cgi" error with twisted. | 22:47 |
| bluelightning | kratsg: I think that's one of the standard modules | 22:54 |
| kratsg | does `python-core` not include it? | 22:54 |
| kratsg | I think `python-lang` is needed then. | 22:54 |
| bluelightning | I think it's in python-netserver | 22:54 |
| *** peacetoall <peacetoall!d0573896@gateway/web/freenode/ip.208.87.56.150> has joined #yocto | 22:55 | |
| kratsg | python-netserver? | 22:56 |
| bluelightning | yes, it's a package produced by the standard python recipe | 22:56 |
| bluelightning | this sort of thing is what devtool add / recipetool create should figure out for you | 22:56 |
| peacetoall | hello i am having a dependency issue that maybe someone can help me with. i made a recipe to build exiv2 and expose to pkg-config via the pkg-config class. i have another recipe which wants to include some of the hpp's from the first recipe when building | 22:57 |
| kratsg | devtool add doesn't figure that out for twisted. | 22:57 |
| peacetoall | i thought DEPENDS="recipe1" would expose hpp's in recipe1 to recipe2 | 22:57 |
| bluelightning | kratsg: hmm, that's interesting... should probably look into that | 22:58 |
| peacetoall | but it can't seem to find them (however pkg-config from recipe2 can see the a pc made be recipe1) | 22:58 |
| kratsg | bluelightning: how do I easily find those "dynamic" packages? | 22:58 |
| kratsg | if i'm exploring the space, it's not easy to look in every file to find something | 22:59 |
| peacetoall | i *don't* see the hpp's in /tmp/sysroots/.... | 22:59 |
| peacetoall | and i think i am supposed to? | 22:59 |
| peacetoall | since i added that dependency | 22:59 |
| bluelightning | peacetoall: in that case they may not be being installed into the correct location | 23:00 |
| *** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC | 23:01 | |
| *** fmeerkoetter <fmeerkoetter!~quassel@service.basyskom.com> has quit IRC | 23:01 | |
| *** fmeerkoetter <fmeerkoetter!~quassel@service.basyskom.com> has joined #yocto | 23:01 | |
| *** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto | 23:01 | |
| bluelightning | kratsg: oe-pkgdata-util can be used if the recipe has been built | 23:01 |
| bluelightning | kratsg: e.g. oe-pkgdata-util find-path */cgi.py | 23:01 |
| kratsg | oh, that's actually convenient. | 23:02 |
| peacetoall | bluelightning: i don't have any install_append now, only FILES_${PN}. so it sounds like i should write an install append and install them to ${D}/${libdir}? | 23:02 |
| bluelightning | kratsg: also oe-pkgdata-util list-pkgs -p python | 23:02 |
| kratsg | but that's assuming one had built python-netserver itself? | 23:02 |
| *** sandsmark <sandsmark!~sandsmark@kde/sandsmark> has quit IRC | 23:02 | |
| bluelightning | peacetoall: that might be what's needed yes | 23:02 |
| bluelightning | kratsg: assuming you had built python, yes | 23:02 |
| kratsg | lemme try the devtool add again | 23:04 |
| *** sandsmark <sandsmark!~sandsmark@kde/sandsmark> has joined #yocto | 23:05 | |
| kratsg | oh wow | 23:06 |
| kratsg | it works much better on 15.4.0 | 23:06 |
| kratsg | then it did on 13.2.0 | 23:06 |
| *** rburton <rburton!~Adium@35.106.2.81.in-addr.arpa> has quit IRC | 23:08 | |
| bluelightning | one thing to note is that how good devtool add / recipetool create are at figuring out the depencies will depend on what's been built beforehand | 23:08 |
| bluelightning | if it's not yet built then it may not be able to see it | 23:08 |
| *** lamego <lamego!~jose@134.134.139.74> has quit IRC | 23:09 | |
| kratsg | i see. | 23:09 |
| kratsg | lemme gist one of the standard outputs | 23:09 |
| kratsg | https://gist.github.com/c17b9e429545a6f47ed7 | 23:10 |
| kratsg | here's what devtool add generated | 23:10 |
| kratsg | that list looks a lot better imo | 23:10 |
| kratsg | but there's a section of comments | 23:10 |
| kratsg | and im not sure if I need to handle that. | 23:11 |
| *** halfhalo <halfhalo!halfhalo@nasadmin/webteam/halfhalo> has quit IRC | 23:11 | |
| moto-timo | many of those packages in the comments probably haven't been built yet | 23:14 |
| moto-timo | and some are not going to be neededd | 23:15 |
| *** halfhalo <halfhalo!halfhalo@nasadmin/webteam/halfhalo> has joined #yocto | 23:15 | |
| kratsg | so how would I know what's needed or not? when I develop the 15.4.0 recipe for twisted, it should be good enough to submit a patch to meta-python | 23:16 |
| kratsg | so clearly, i don't want to half-ass it. | 23:16 |
| moto-timo | there is a reason the 13.2.0 recipe is so long and complicated | 23:17 |
| *** reanguiano <reanguiano!~devnull@godel.ricardoanguiano.com> has joined #yocto | 23:17 | |
| moto-timo | so you need to compare the autogenerated 15.4.0 recipe to the 13.2.0 recipe and manually merge | 23:17 |
| kratsg | that's probably what I'll do | 23:18 |
| kratsg | unfortunately, the entire interface changed, so | 23:18 |
| kratsg | i'll do my best to maintain the... separation of pieces | 23:18 |
| *** sandsmark <sandsmark!~sandsmark@kde/sandsmark> has quit IRC | 23:18 | |
| moto-timo | also, notice how the 13.2.0 recipe breaks it up into a bunch of sub-packages | 23:20 |
| moto-timo | that helps keep your final images smaller, since you might not need the entire beast | 23:20 |
| kratsg | twisted isn't that big anymore! | 23:21 |
| kratsg | but i'll keep that in mind | 23:21 |
| kratsg | I'll split it up by top-level folder under `twisted` | 23:21 |
| kratsg | and try to figure out the dependencies somehow | 23:21 |
| *** sandsmark <sandsmark!~sandsmark@kde/sandsmark> has joined #yocto | 23:21 | |
| *** kratsg <kratsg!82c703a5@gateway/web/freenode/ip.130.199.3.165> has left #yocto | 23:22 | |
| peacetoall | how do know where i *should* install header files? ${D}/usr/lib/SOMENAME/ ? | 23:24 |
| *** slidercrank <slidercrank!~slidercra@unaffiliated/slidercrank> has quit IRC | 23:32 | |
| clambers | ${D}${includedir}/SOMENAME | 23:34 |
| *** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC | 23:39 | |
| *** benjamirc <benjamirc!~besquive@134.134.137.73> has joined #yocto | 23:47 | |
| *** cbzx <cbzx!~cbzx@CPE0015f275ecd5-CM00195edd810c.cpe.net.cable.rogers.com> has joined #yocto | 23:48 | |
| *** peacetoall <peacetoall!d0573896@gateway/web/freenode/ip.208.87.56.150> has quit IRC | 23:55 | |
Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!