*** ecdhe <ecdhe!~ecdhe@173-22-126-166.client.mchsi.com> has joined #yocto | 00:00 | |
*** DriverCoder <DriverCoder!~mdrustad@134.134.139.76> has joined #yocto | 00:07 | |
*** eraineri <eraineri!~eraineri@2605:6000:151e:814d:224:d7ff:febc:c3d0> has quit IRC | 00:08 | |
*** sjolley <sjolley!sjolley@nat/intel/x-gljtlmoiuhwftrgs> has joined #yocto | 00:09 | |
*** ecdhe <ecdhe!~ecdhe@173-22-126-166.client.mchsi.com> has quit IRC | 00:26 | |
*** clopez <clopez!~tau@neutrino.es> has quit IRC | 00:36 | |
*** sameo <sameo!~samuel@192.55.55.37> has quit IRC | 00:36 | |
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-mpdbyxawewmfvlxl> has quit IRC | 00:38 | |
*** ecdhe <ecdhe!~ecdhe@173-22-126-166.client.mchsi.com> has joined #yocto | 00:39 | |
*** clopez <clopez!~tau@neutrino.es> has joined #yocto | 00:40 | |
*** evanmeagher <evanmeagher!~evanmeagh@73.71.33.109> has quit IRC | 00:44 | |
*** dreyna4529 <dreyna4529!~dreyna@unknown-216-199.windriver.com> has quit IRC | 00:44 | |
*** roccof <roccof!~rocco@151.48.167.148> has quit IRC | 00:47 | |
*** evanmeagher <evanmeagher!~evanmeagh@73.71.33.109> has joined #yocto | 00:49 | |
*** dreyna4529 <dreyna4529!~dreyna@unknown-4-99.windriver.com> has joined #yocto | 00:52 | |
*** sgw_ <sgw_!~sgw_@c-73-164-210-189.hsd1.or.comcast.net> has quit IRC | 00:56 | |
*** evanmeagher <evanmeagher!~evanmeagh@73.71.33.109> has quit IRC | 01:02 | |
*** evanmeagher <evanmeagher!~evanmeagh@73.71.33.109> has joined #yocto | 01:03 | |
*** deviosity_ <deviosity_!~deviosity@c-24-143-96-146.customer.broadstripe.net> has joined #yocto | 01:10 | |
*** deviosity <deviosity!~deviosity@c-24-143-96-146.customer.broadstripe.net> has quit IRC | 01:13 | |
*** deviosity_ is now known as deviosity | 01:13 | |
*** deviosity_ <deviosity_!~deviosity@c-24-143-96-146.customer.broadstripe.net> has joined #yocto | 01:14 | |
*** seebs <seebs!~seebs@home.seebs.net> has quit IRC | 01:16 | |
*** seebs <seebs!~seebs@home.seebs.net> has joined #yocto | 01:17 | |
*** deviosity <deviosity!~deviosity@c-24-143-96-146.customer.broadstripe.net> has quit IRC | 01:17 | |
*** deviosity_ is now known as deviosity | 01:17 | |
*** ecdhe <ecdhe!~ecdhe@173-22-126-166.client.mchsi.com> has quit IRC | 01:43 | |
*** Lucretia <Lucretia!~laguest@pdpc/supporter/active/lucretia> has quit IRC | 01:43 | |
*** PortaLu <PortaLu!~laguest@pdpc/supporter/active/lucretia> has joined #yocto | 01:43 | |
*** PortaLu <PortaLu!~laguest@pdpc/supporter/active/lucretia> has quit IRC | 01:48 | |
*** PortaLu <PortaLu!~laguest@pdpc/supporter/active/lucretia> has joined #yocto | 01:49 | |
*** ecdhe <ecdhe!~ecdhe@173-22-126-166.client.mchsi.com> has joined #yocto | 01:55 | |
*** evanmeagher <evanmeagher!~evanmeagh@73.71.33.109> has quit IRC | 02:08 | |
*** PortaLu <PortaLu!~laguest@pdpc/supporter/active/lucretia> has quit IRC | 02:12 | |
*** PortaLu <PortaLu!~laguest@pdpc/supporter/active/lucretia> has joined #yocto | 02:13 | |
*** coolmouse <coolmouse!~coolmouse@113.201.138.202> has joined #yocto | 02:14 | |
*** DriverCoder <DriverCoder!~mdrustad@134.134.139.76> has quit IRC | 02:16 | |
*** cbzx <cbzx!~cbzx@CPE0015f275ecd5-CM00195edd810c.cpe.net.cable.rogers.com> has joined #yocto | 02:25 | |
*** cbzx <cbzx!~cbzx@CPE0015f275ecd5-CM00195edd810c.cpe.net.cable.rogers.com> has quit IRC | 02:30 | |
*** coolmouse <coolmouse!~coolmouse@113.201.138.202> has joined #yocto | 02:30 | |
*** deviosity <deviosity!~deviosity@c-24-143-96-146.customer.broadstripe.net> has quit IRC | 02:33 | |
*** PortaLu is now known as Lucretia | 02:41 | |
*** coolmouse <coolmouse!~coolmouse@113.201.138.202> has quit IRC | 02:41 | |
*** coolmouse <coolmouse!~coolmouse@113.201.243.32> has joined #yocto | 02:54 | |
*** Aethenelle_ <Aethenelle_!~Aethenell@199.15.128.78> has joined #yocto | 03:21 | |
*** sa2ajj <sa2ajj!~quassel@dsl-espbrasgw1-50de2f-243.dhcp.inet.fi> has joined #yocto | 03:21 | |
*** aehs291 <aehs291!~aehernan@134.134.139.77> has joined #yocto | 03:23 | |
*** sujith_h_ <sujith_h_!~toaster@139.181.35.34> has joined #yocto | 03:24 | |
*** Aethenelle <Aethenelle!~Aethenell@107.138.98.226> has quit IRC | 03:30 | |
*** aehs29 <aehs29!~aehernan@134.134.139.77> has quit IRC | 03:30 | |
*** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has quit IRC | 03:30 | |
*** vquicksilver <vquicksilver!~nobody@gentoo/contributor/vquicksilver> has quit IRC | 03:30 | |
*** Aethenelle_ is now known as Aethenelle | 03:30 | |
*** sujith_h_ is now known as sujith_h | 03:30 | |
*** vquicksilver <vquicksilver!~nobody@gentoo/contributor/vquicksilver> has joined #yocto | 03:31 | |
*** vquicksilver_ <vquicksilver_!~nobody@gentoo/contributor/vquicksilver> has joined #yocto | 03:54 | |
*** vquicksilver <vquicksilver!~nobody@gentoo/contributor/vquicksilver> has quit IRC | 03:55 | |
*** pidge <pidge!~pidge@2a02:8084:ac1:d80:f1ff:1b95:401c:359b> has quit IRC | 03:56 | |
*** dreyna4529 <dreyna4529!~dreyna@unknown-4-99.windriver.com> has quit IRC | 04:02 | |
*** cbzx <cbzx!~cbzx@CPE0015f275ecd5-CM00195edd810c.cpe.net.cable.rogers.com> has joined #yocto | 04:58 | |
*** cbzx <cbzx!~cbzx@CPE0015f275ecd5-CM00195edd810c.cpe.net.cable.rogers.com> has quit IRC | 05:00 | |
*** driftingblues <driftingblues!~driftingb@139.181.35.34> has joined #yocto | 05:08 | |
*** driftingblues <driftingblues!~driftingb@139.181.35.34> has left #yocto | 05:09 | |
*** hamis_lt_u <hamis_lt_u!~irfan@110.93.212.98> has joined #yocto | 05:15 | |
*** coolmouse <coolmouse!~coolmouse@113.201.243.32> has quit IRC | 05:17 | |
*** Aethenelle <Aethenelle!~Aethenell@199.15.128.78> has quit IRC | 05:24 | |
*** ka6sox is now known as zz_ka6sox | 05:47 | |
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has quit IRC | 05:48 | |
*** blitz00 <blitz00!stefans@nat/intel/x-qnvzhrirgwmloxfa> has joined #yocto | 05:48 | |
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has joined #yocto | 05:48 | |
*** |Sno| <|Sno|!~sno@p578b540c.dip0.t-ipconnect.de> has joined #yocto | 05:50 | |
*** Lucretia <Lucretia!~laguest@pdpc/supporter/active/lucretia> has quit IRC | 05:51 | |
*** Nilesh__ <Nilesh__!uid116340@gateway/web/irccloud.com/x-qqnwyevruwymgmof> has joined #yocto | 05:52 | |
*** marquiz <marquiz!~marquiz@134.191.220.73> has joined #yocto | 05:52 | |
*** marquiz_ <marquiz_!~marquiz@134.191.220.73> has quit IRC | 05:52 | |
*** [Sno] <[Sno]!~sno@p578b540c.dip0.t-ipconnect.de> has quit IRC | 05:52 | |
*** icanicant <icanicant!~icanicant@195.88.236.129> has quit IRC | 05:53 | |
*** freanux <freanux!~freanux@unaffiliated/freanux> has quit IRC | 05:54 | |
*** Nilesh__ <Nilesh__!uid116340@gateway/web/irccloud.com/x-qqnwyevruwymgmof> has quit IRC | 05:56 | |
*** fitzsim <fitzsim!~user@2001:420:284a:1300:6e0b:84ff:fe09:4e9f> has quit IRC | 05:56 | |
*** morphis <morphis!~morphis@p5480DE48.dip0.t-ipconnect.de> has joined #yocto | 05:57 | |
*** Nilesh__ <Nilesh__!uid116340@gateway/web/irccloud.com/session> has joined #yocto | 06:02 | |
*** fitzsim <fitzsim!~user@2001:420:284a:1300:6e0b:84ff:fe09:4e9f> has joined #yocto | 06:02 | |
*** Nilesh__ <Nilesh__!uid116340@gateway/web/irccloud.com/session> has quit IRC | 06:02 | |
*** Nilesh__ <Nilesh__!uid116340@gateway/web/irccloud.com/x-lvmshtzqjfddhxab> has joined #yocto | 06:02 | |
*** icanicant <icanicant!~icanicant@195.88.236.129> has joined #yocto | 06:03 | |
*** Lucretia <Lucretia!~laguest@pdpc/supporter/active/lucretia> has joined #yocto | 06:03 | |
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has joined #yocto | 06:08 | |
*** agust <agust!~agust@pD9E2FEE4.dip0.t-ipconnect.de> has joined #yocto | 06:33 | |
*** sujith_h <sujith_h!~toaster@139.181.35.34> has quit IRC | 06:34 | |
*** pohly <pohly!~pohly@p5DE8C5D0.dip0.t-ipconnect.de> has joined #yocto | 06:44 | |
*** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has joined #yocto | 06:53 | |
*** t0mmy <t0mmy!~tprrt@ram31-2-82-228-88-46.fbx.proxad.net> has quit IRC | 07:06 | |
*** Nilesh__ <Nilesh__!uid116340@gateway/web/irccloud.com/x-lvmshtzqjfddhxab> has quit IRC | 07:10 | |
*** fitzsim <fitzsim!~user@2001:420:284a:1300:6e0b:84ff:fe09:4e9f> has quit IRC | 07:10 | |
*** marek_ <marek_!~marek@81.89.61.168.host.vnet.sk> has joined #yocto | 07:14 | |
*** freanux <freanux!~freanux@unaffiliated/freanux> has joined #yocto | 07:15 | |
*** Nilesh__ <Nilesh__!uid116340@gateway/web/irccloud.com/session> has joined #yocto | 07:21 | |
*** fitzsim <fitzsim!~user@2001:420:284a:1300:6e0b:84ff:fe09:4e9f> has joined #yocto | 07:21 | |
*** Nilesh__ <Nilesh__!uid116340@gateway/web/irccloud.com/session> has quit IRC | 07:21 | |
*** Nilesh__ <Nilesh__!uid116340@gateway/web/irccloud.com/x-nhludumytffzxluj> has joined #yocto | 07:21 | |
*** yann|work <yann|work!~yann@nan92-1-81-57-214-146.fbx.proxad.net> has quit IRC | 07:27 | |
*** TobSnyder <TobSnyder!~schneider@ip9234b44d.dynamic.kabel-deutschland.de> has joined #yocto | 07:39 | |
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:1208:b1ff:fee8:f733> has joined #yocto | 07:42 | |
*** Nilesh__ <Nilesh__!uid116340@gateway/web/irccloud.com/x-nhludumytffzxluj> has quit IRC | 07:47 | |
*** fitzsim <fitzsim!~user@2001:420:284a:1300:6e0b:84ff:fe09:4e9f> has quit IRC | 07:47 | |
*** t0mmy <t0mmy!~tprrt@217.114.201.133> has joined #yocto | 07:47 | |
*** tasslehoff <tasslehoff!~Tasslehof@82.147.55.166> has joined #yocto | 07:49 | |
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-hzlksyiytjjsjdht> has joined #yocto | 07:53 | |
*** dreyna4529 <dreyna4529!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto | 07:53 | |
*** jbrianceau_away is now known as jbrianceau | 07:53 | |
*** Nilesh__ <Nilesh__!uid116340@gateway/web/irccloud.com/x-tdklevlxevrpayks> has joined #yocto | 07:54 | |
*** fitzsim <fitzsim!~user@2001:420:284a:1300:6e0b:84ff:fe09:4e9f> has joined #yocto | 07:54 | |
*** Nilesh__ <Nilesh__!uid116340@gateway/web/irccloud.com/x-tdklevlxevrpayks> has quit IRC | 07:57 | |
boucman_work | hello, I have a patch I want to contribute to yocto (meta/) but I can't figure out what branch to follow, is it master or master-next | 08:01 |
---|---|---|
boucman_work | it seems master-next is regularly rebased, so I would guess master, but i couldn't find any doc | 08:01 |
*** mckoan|away is now known as mckoan | 08:03 | |
*** zz_ka6sox is now known as ka6sox | 08:03 | |
*** vmesons <vmesons!~rmacleod@24-212-184-107.cable.teksavvy.com> has joined #yocto | 08:04 | |
*** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has quit IRC | 08:05 | |
*** dreyna4529 <dreyna4529!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC | 08:06 | |
-YoctoAutoBuilder- build #702 of nightly-world is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-world/builds/702 | 08:07 | |
*** jonatan <jonatan!~jonatan@83.218.80.242> has quit IRC | 08:09 | |
*** fl0v0 <fl0v0!~fvo@pD9F6B5B1.dip0.t-ipconnect.de> has joined #yocto | 08:14 | |
*** townxelliot <townxelliot!~ell@176.252.21.78> has joined #yocto | 08:15 | |
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto | 08:20 | |
mborzecki | boucman_work: master | 08:22 |
boucman_work | thx | 08:22 |
boucman_work | and do you follow the convention of using --- in the commit message to separate the actual message from the comment to the ML ? or do you rather have a [0/1] message where i discuss stuff about the patch ? | 08:24 |
*** matteo <matteo!~matteo@openwrt/developer/matteo> has joined #yocto | 08:28 | |
mborzecki | boucman_work: i prefer cover letter if the patch requires more explanation than what's in the commit message | 08:36 |
*** joshuagl <joshuagl!joshuagl@nat/intel/x-meaifydlbujjlmip> has joined #yocto | 08:39 | |
*** tasslehoff <tasslehoff!~Tasslehof@82.147.55.166> has quit IRC | 08:42 | |
*** edbart <edbart!ebartosh@nat/intel/x-bfandqbrkulfimch> has joined #yocto | 08:42 | |
*** yann|work <yann|work!~yann@LFbn-1-1026-146.w86-247.abo.wanadoo.fr> has joined #yocto | 08:42 | |
*** sameo <sameo!samuel@nat/intel/x-bmcsaizoqtsxuiuh> has joined #yocto | 08:43 | |
*** belen <belen!~Adium@134.134.139.77> has joined #yocto | 08:46 | |
RP | boucman_work: [0/1] is for the discussion | 08:47 |
RP | boucman_work: although the commit message should be self supporting | 08:48 |
*** ant_work <ant_work!~ant__@host213-59-dynamic.50-79-r.retail.telecomitalia.it> has joined #yocto | 08:49 | |
*** LinuxMice <LinuxMice!~LinuxMice@193.140.134.110> has joined #yocto | 08:49 | |
*** roccof <roccof!~roccof@93-51-177-218.ip268.fastwebnet.it> has joined #yocto | 08:50 | |
LinuxMice | hi everyone Good Morning, i build java 7 jre package with bitbake, i must to run this command: bitbake openjdk-7-jre, Am i right ? | 08:55 |
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:1208:b1ff:fee8:f733> has quit IRC | 08:57 | |
LinuxMice | LetoThe2nd: i think LetoThe2nd exactly know this question ^_^ ? | 08:57 |
LetoThe2nd | huh? | 08:58 |
LetoThe2nd | why should i? | 08:58 |
LinuxMice | LetoThe2nd: My question is : hi everyone Good Morning, i build java 7 jre package with bitbake, i must to run this command: bitbake openjdk-7-jre, Am i right?? and i think u exactly know this answer ^_^ | 08:59 |
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:1208:b1ff:fee8:f733> has joined #yocto | 08:59 | |
LetoThe2nd | LinuxMice: i actually fail to understand the question, and what makes you think that i specifically know it? | 08:59 |
LetoThe2nd | LinuxMice: i guess you *want* to build that thing, right? | 09:00 |
LinuxMice | LetoThe2nd: Yes i want to build java with bitbake command and this command bitbake openjdk-7-jre is right command ? | 09:01 |
LetoThe2nd | besides that, about everything i know about java in OE is this: http://git.yoctoproject.org/cgit/cgit.cgi/meta-java/about/ | 09:02 |
*** Anticom <Anticom!~timo.m@217.6.33.234> has joined #yocto | 09:03 | |
Anticom | Hi all. | 09:03 |
LetoThe2nd | and generally speaking bibaking a package will compile and package it - not magically move it somewhere, especially not to a target or filesystem | 09:03 |
Anticom | DISTRO_FEATURES_DEFAULT features are not enabled, if i set DISTRO_FEATURES are they? | 09:03 |
*** rburton <rburton!~Adium@home.burtonini.com> has joined #yocto | 09:04 | |
*** fl0v01 <fl0v01!~fvo@pD9F6BC01.dip0.t-ipconnect.de> has joined #yocto | 09:05 | |
*** fl0v0 <fl0v0!~fvo@pD9F6B5B1.dip0.t-ipconnect.de> has quit IRC | 09:08 | |
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:1208:b1ff:fee8:f733> has quit IRC | 09:09 | |
LetoThe2nd | Anticom: thats what docs suggest, yes. http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-DISTRO_FEATURES_DEFAULT | 09:10 |
*** freanux <freanux!~freanux@unaffiliated/freanux> has quit IRC | 09:19 | |
*** maxin <maxin!~maxin@2001:998:22:0:a91b:4efe:a9f3:1e15> has joined #yocto | 09:26 | |
*** john55 <john55!3cfa6ee2@gateway/web/freenode/ip.60.250.110.226> has joined #yocto | 09:27 | |
*** wfailla <wfailla!~wfailla@92.43.51.145> has joined #yocto | 09:34 | |
*** maxin <maxin!~maxin@2001:998:22:0:a91b:4efe:a9f3:1e15> has quit IRC | 09:43 | |
*** wfailla <wfailla!~wfailla@92.43.51.145> has quit IRC | 09:43 | |
*** jonathanmaw <jonathanmaw!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has joined #yocto | 09:53 | |
*** Kakadu <Kakadu!4fad4e8c@gateway/web/freenode/ip.79.173.78.140> has joined #yocto | 09:56 | |
-YoctoAutoBuilder- build #707 of nightly-x86 is complete: Failure [failed BuildImages_2 Running ESDK Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86/builds/707 | 09:56 | |
*** joshuagl <joshuagl!joshuagl@nat/intel/x-meaifydlbujjlmip> has quit IRC | 09:56 | |
*** N-a-N <N-a-N!uid149677@gateway/web/irccloud.com/x-lbrntngexcylekme> has joined #yocto | 09:57 | |
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-xtpuowllhvedbkyk> has joined #yocto | 10:01 | |
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-xtpuowllhvedbkyk> has left #yocto | 10:01 | |
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:1208:b1ff:fee8:f733> has joined #yocto | 10:04 | |
*** jmleo <jmleo!~jmleo@LMontsouris-657-1-109-180.w80-15.abo.wanadoo.fr> has joined #yocto | 10:07 | |
jmleo | hi ! | 10:07 |
*** joshuagl <joshuagl!~joshuagl@192.198.151.43> has joined #yocto | 10:09 | |
*** jmleo <jmleo!~jmleo@LMontsouris-657-1-109-180.w80-15.abo.wanadoo.fr> has left #yocto | 10:12 | |
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:1208:b1ff:fee8:f733> has quit IRC | 10:12 | |
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has quit IRC | 10:20 | |
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has joined #yocto | 10:22 | |
*** wfailla <wfailla!~wfailla@92.43.51.145> has joined #yocto | 10:27 | |
boucman_work | ok, thx, one more question and I send my patch :P | 10:30 |
boucman_work | my patch modifies meta/recipes-core/initrdscripts/files/init-live.sh but not the recipe itself... I would have expected to have to increment something... but there is no PR in the recipe, and the recipe has no upstream | 10:31 |
boucman_work | should I create a new file, create a new .bb with a new version in its name, or should I just push and assume prserv will handle it correctly ? | 10:31 |
rburton | bitbake sees that you've modified the file and rebuilds as required | 10:31 |
boucman_work | rburton, yes it does, my question was more "do I need to increase the PV in my patch" | 10:32 |
rburton | no | 10:32 |
rburton | as bitbake sees a file modification and rebuilds as required | 10:32 |
boucman_work | ok, cool, i'm good to go then | 10:32 |
*** _4urele_ <_4urele_!~aurele@srvmail.castel.fr> has quit IRC | 10:36 | |
boucman_work | and sent... hopefully I got it right :) | 10:39 |
*** _4urele_ <_4urele_!~aurele@srvmail.castel.fr> has joined #yocto | 10:39 | |
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has joined #yocto | 10:40 | |
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has quit IRC | 10:42 | |
*** mihai <mihai!mihai@nat/intel/x-onasgefnjvxwllmo> has joined #yocto | 10:42 | |
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has joined #yocto | 10:44 | |
*** belen <belen!~Adium@134.134.139.77> has quit IRC | 10:57 | |
*** wfailla <wfailla!~wfailla@92.43.51.145> has quit IRC | 10:58 | |
*** zero_note <zero_note!~zero_note@2.238.240.162> has joined #yocto | 11:03 | |
*** john55 <john55!3cfa6ee2@gateway/web/freenode/ip.60.250.110.226> has quit IRC | 11:14 | |
*** pidge_ <pidge_!~pidge@2a02:8084:ac1:d80:e9f7:42f8:4fb:388f> has joined #yocto | 11:16 | |
*** pidge_ <pidge_!~pidge@2a02:8084:ac1:d80:e9f7:42f8:4fb:388f> has quit IRC | 11:20 | |
*** coolmouse <coolmouse!~coolmouse@124.89.110.117> has joined #yocto | 11:21 | |
*** wfailla <wfailla!~wfailla@pd95c9392.dip0.t-ipconnect.de> has joined #yocto | 11:24 | |
*** JEEB <JEEB!~jeeb@unaffiliated/jeeb> has quit IRC | 11:30 | |
*** berton <berton!~fabio@177.127.4.103> has joined #yocto | 11:31 | |
*** ka6sox is now known as zz_ka6sox | 11:31 | |
*** JEEB <JEEB!~jeeb@unaffiliated/jeeb> has joined #yocto | 11:32 | |
*** ant_work <ant_work!~ant__@host213-59-dynamic.50-79-r.retail.telecomitalia.it> has quit IRC | 11:39 | |
*** cart_man <cart_man!29a03a62@gateway/web/freenode/ip.41.160.58.98> has joined #yocto | 11:44 | |
cart_man | IS there a specific Cross compiler I need to be able to Compile on windows for my Yocto device? | 11:45 |
LetoThe2nd | cart_man: i think the meta-mingw layer works on enabling the sdk generation for windows dev hosts, but.... there be dragons! | 11:47 |
cart_man | LetoThe2nd: AWwww.... | 11:48 |
cart_man | LetoThe2nd: Ok soo do you think coding in normal GCC / G++ on Linux will work best? | 11:48 |
LetoThe2nd | cart_man: s/work best/probably be the only thing that works close to reliable/ | 11:48 |
cart_man | LetoThe2nd: So I can just work on Ubuntu standard compiler not even need to use a crosscompiler ? | 11:51 |
LetoThe2nd | cart_man: nope | 11:51 |
cart_man | fuk soo need to use the meta-mingw... so where do I get this meta-mingw ? | 11:52 |
LetoThe2nd | cart_man: given the correct arch, using your distros toolchain might work for very limited, statically linked use cases. | 11:52 |
LetoThe2nd | cart_man: for anything else, use the sdk functionality provided by OE. its there for a reason. | 11:53 |
cart_man | LetoThe2nd: Ok I am actually trying to get to the point where i can use exactly that which you are speaking of | 11:53 |
cart_man | LetoThe2nd: But I am a bit lost | 11:53 |
cart_man | I have my IMX6 board running Yocto at the moment AND its on the network soo I want to start building apps for it in C++ from my Desktop computer | 11:54 |
LetoThe2nd | cart_man: the bottom line is: you have an OE based build process that generates your image. so then just use that very same build process to provide the fitting sdk. | 11:54 |
LetoThe2nd | cart_man: for standard cases, this means only after doing "bitbake your-image", a "bitbake your-image -c populate_sdk" | 11:55 |
LetoThe2nd | which will provide you with an installable sdk, that brings the toolchain matching your target system, as well as the available libraries and a setup script for your environment to use it. | 11:56 |
*** caiortp <caiortp!~inatel@131.221.240.204> has joined #yocto | 11:57 | |
cart_man | LetoThe2nd: Ok so how does it work? Does the code gets transfered to your device and compiled on it or do you need to set up a compiler on your Host PC? | 11:59 |
LetoThe2nd | cart_man: ermmm.... | 11:59 |
*** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has joined #yocto | 11:59 | |
LetoThe2nd | 12:56 < LetoThe2nd> which will provide you with an installable sdk, that brings the toolchain matching your target system, | 11:59 |
*** clopez <clopez!~tau@neutrino.es> has quit IRC | 12:00 | |
cart_man | LetoThe2nd: Ok soo I install that then onto my Desktop? Ughh im confused | 12:01 |
LetoThe2nd | cart_man: you install it onto your development host. which is not necessarily a desktop computer ;-) | 12:01 |
LetoThe2nd | cart_man: have a good look at http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#cross-development-toolchain-generation | 12:01 |
*** ant_work <ant_work!~ant__@host213-59-dynamic.50-79-r.retail.telecomitalia.it> has joined #yocto | 12:03 | |
LetoThe2nd | cart_man: or generally anything in http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#application-development-workflow | 12:04 |
LetoThe2nd | cart_man: the alternative is, try the populate_sdk comamnd and tinker around with it to see what it does and what you get out of it. | 12:04 |
LetoThe2nd | or alternative #2: hire a consultant | 12:06 |
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC | 12:06 | |
*** clopez <clopez!~tau@neutrino.es> has joined #yocto | 12:06 | |
cart_man | LetoThe2nd: No I am just confused as to how Targeted compilations work | 12:08 |
LetoThe2nd | you probably mean "cross compilation" | 12:09 |
Anticom | How is network configuration done properly, when using systemd? currently we simply install a file to /etc/network/interfaces in a init-ifupdown.bbappend recipe that seems kind of wonky ot me | 12:11 |
cart_man | LetoThe2nd: Well how to compile onto my target.. cross probably ues | 12:11 |
cart_man | yes` | 12:11 |
LetoThe2nd | cart_man: *sigh* | 12:12 |
cart_man | LetoThe2nd: : ( | 12:12 |
LetoThe2nd | cart_man: you really have to get the terms "toolchain" "compilation" "architecture" "target" and "host" straight first. | 12:12 |
*** wfailla <wfailla!~wfailla@pd95c9392.dip0.t-ipconnect.de> has quit IRC | 12:13 | |
LetoThe2nd | cart_man: otherwise you just will misinterpret about everything you see. | 12:13 |
Anticom | think in the mega manaual there was a step by step tutorial on some hello world recipe iirc | 12:13 |
Anticom | check that one out cart_man | 12:13 |
LetoThe2nd | Anticom: generally the application development section in the yocto docs is pretty exhaustive. | 12:14 |
Anticom | LetoThe2nd: is that concerning my recommendation to cart_man or concerning my question? | 12:14 |
LetoThe2nd | cart_man: this just isn't as simple as clicking the compile button in your favorite uC-IDE with predefined projects, sorry. | 12:15 |
LetoThe2nd | Anticom: concerning the recommendation, yes. | 12:15 |
LetoThe2nd | Anticom: concerning your own one, the problem is just that there is no systemd way of network configuration. its up to whatever network management engine you choose to accompany it. | 12:16 |
Anticom | so no delicious abstractions for that yet? | 12:17 |
Anticom | meh | 12:17 |
Anticom | LetoThe2nd: How are you doing interface configuration in your projects? | 12:17 |
LetoThe2nd | Anticom: well there ist systemd-networkd, but we told you about that already yesterday - so i implied by you not asking specifically about it that you decided against it. | 12:17 |
LetoThe2nd | Anticom: we have some custom stuff in place | 12:17 |
Anticom | LetoThe2nd: Checked back with my PM and he told me i should investigate further | 12:18 |
Anticom | LetoThe2nd: i saw, that there was /etc/systemd/network or something where you can place your config when using systemd | 12:19 |
LetoThe2nd | Anticom: um, so you just mentally erased what you learned yesterday and ask the same questions again to "investigate further?" | 12:19 |
Anticom | iirc there was no exhaustive answer to that question | 12:19 |
LetoThe2nd | Anticom: no. plain wrong. there is a specific place under etc where you you can place your config when using systemd_networkd | 12:19 |
LetoThe2nd | systemd by itself just does not do that. no matter how often you repeat it. | 12:20 |
Anticom | So in the end it also comes to installing config files to rootfs? | 12:21 |
LetoThe2nd | Anticom: the exhaustive answer was "pick one of the alternatives, then one can discuss on how to use it." | 12:21 |
Anticom | that's what my question is more about | 12:21 |
LetoThe2nd | Anticom: well as your configuration probably is meant to be persistent, it will always mean some file operation of one kind or the other. that holds true for networkd, connman, nm, everything i know. | 12:21 |
LetoThe2nd | shouldn't you generally choose your solution by matching its features against your requests, instead of looking at the path where it wants his config files? | 12:22 |
Anticom | LetoThe2nd: Well as i wrote yesterday already from what i know systemd is somewhat 100% compatible with sysvinit files. The idea we had was switching to systemd before we launch our product so we can port the things from sysvinit to systemd gradually when the product has already been launched | 12:24 |
LetoThe2nd | Anticom: ... which i think is a really bad idea. | 12:24 |
Anticom | why? | 12:25 |
Anticom | Background is, that systemd should improve our boot times since it starts services in parralel instead of sequencially | 12:25 |
LetoThe2nd | systemd is very, very invasive. and it is really not sysvinit compatible, at least not in terms of "i just install systemd, it makes everything magically faster while nothing breaks." | 12:25 |
Anticom | LetoThe2nd: And now i'm curious what exactly did break and in turn how much efford it would take to fix it again | 12:26 |
*** wfailla <wfailla!~wfailla@92.43.51.145> has joined #yocto | 12:27 | |
Anticom | LetoThe2nd: also why do they claim its compatible when it's really not? | 12:27 |
LetoThe2nd | Anticom: its "enough compatible for the common desktop usecase." | 12:28 |
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has quit IRC | 12:31 | |
LetoThe2nd | Anticom: i really know that for most desktop linux distribution users systemd has the effect/impression of "hey we switched the init system and now everything boots magically faster". but under the hood that is just not true. it is not the reality. | 12:32 |
Anticom | LetoThe2nd: it doesn't have to be 'magically' faster yet | 12:33 |
cart_man | LetoThe2nd: Ok so this SDK Tool that you where talking about.. where does this get installed .. My Question is DOES bitbake Generate anything that you must use to "Prepare" the development system (My Desktop NOT the ImX6 board) | 12:33 |
Anticom | The idea is more about preparing our production image to enable making it faster int he future by providing the proper tools | 12:33 |
Anticom | Currently it only has to 'not break' | 12:34 |
LetoThe2nd | Anticom: if your image is more than trivial (it has more than one binary that has to be kicked off during boot), switching to systemd will break stuff and eat your dev time. | 12:34 |
Anticom | LetoThe2nd: Binary of what sort? custom or something from the oe layers? | 12:35 |
Anticom | i mean ntp, syslogd, etc. seemed to be running just fine | 12:35 |
LetoThe2nd | cart_man: really, this is all neatly documented, and however complicated it is not black magic. i feel that trying to explain those basics again through irc is not really a valuable use of time. | 12:35 |
LetoThe2nd | cart_man: my suggestion would be, find somebody who has already done that once and have him/her show it to you in real life. | 12:36 |
LetoThe2nd | Anticom: because those already have seen the proper dev work needed for the transition. | 12:36 |
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto | 12:36 | |
Anticom | LetoThe2nd: well then we actually do have only a single service that is brought up by us | 12:37 |
cart_man | LetoThe2nd: My problem is I am stuck not remotely close to anybody know even knows Linux : / ... I will try the docs | 12:37 |
LetoThe2nd | Anticom: then write a proper systemd unit file and have it kicked off. sacrifice a chicken in the meanwhile and pray that nothing that you implicitly took for granted breaks. | 12:38 |
Anticom | cart_man: 1st step: install linux, 2nd step: learn linux (/join #ubuntu etc.) 3rd step: get poky set up in such way you can at least build core-image-sato and run it in quemu, 4th step: come back here :) | 12:38 |
Anticom | LetoThe2nd: Are goats instead of chicken alright too? | 12:38 |
Anticom | Chicken are out currently :/ | 12:39 |
LetoThe2nd | Anticom: it becomes really, really nasty if you have runtime monitoring of your service in terms of watchdogging it, restarting/rebooting | 12:39 |
cart_man | Anticom: Lol well I at least got to installing my own Yocto build on my IMX6 so I am a bit clued up haha | 12:39 |
LetoThe2nd | Anticom: i can only repeat my practical experience - if you are not in the very, very early stages in a project - do not ponder switching to systemd. | 12:40 |
Anticom | LetoThe2nd: First of all i need to get my image to build again. Just installed lttng tools on my host and the image doesn't build anymore due to invalid kernel config ._. | 12:40 |
LetoThe2nd | Anticom: usually you can gain a lot more of bootup spped by other means. | 12:40 |
Anticom | LetoThe2nd: even if it's only a single executable that runs our system? I got about a month of time to get it working. | 12:42 |
LetoThe2nd | Anticom: depends. | 12:42 |
LetoThe2nd | Anticom: i cannot comment in a resonably sane way what will break for your specific application and usecase. | 12:42 |
Anticom | Sure there's no standard answer to this | 12:43 |
LetoThe2nd | just saw a *lot* breaking unexpected and differently fomr sysV here. | 12:43 |
Anticom | But back to the networking stuff. Googling arround for systemd_networkd yielded https://wiki.archlinux.org/index.php/systemd-networkd#Wired_adapter_using_a_static_IP | 12:44 |
Anticom | I don't get how stuff like connman relate to this | 12:44 |
LetoThe2nd | Anticom: why should connman realte to a systemd-networkd specific configuration file? | 12:44 |
Anticom | <LetoThe2nd> Anticom: well as your configuration probably is meant to be persistent, it will always mean some file operation of one kind or the other. that holds true for networkd, connman, nm, everything i know. | 12:45 |
Anticom | I was asking, whether the way to go was installing a config to /etc/systemd/network/ but you declined didn't you? | 12:46 |
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has joined #yocto | 12:46 | |
Anticom | I know i'm probably giving you a lot of *sigh*'s but i honnestly don't get it then :/ | 12:46 |
*** wfailla <wfailla!~wfailla@92.43.51.145> has quit IRC | 12:46 | |
LetoThe2nd | Anticom: read again. | 12:46 |
*** wfailla <wfailla!~wfailla@92.43.51.145> has joined #yocto | 12:47 | |
LetoThe2nd | Anticom: i said that every one of those solutions will include some config file. i did not say that they all use the same. | 12:47 |
Anticom | <Anticom> LetoThe2nd: i saw, that there was /etc/systemd/network or something where you can place your config when using systemd \\ <LetoThe2nd> Anticom: no. plain wrong. there is a specific place under etc where you you can place your config when using systemd_networkd | 12:47 |
LetoThe2nd | Anticom: read again, one more time. | 12:48 |
Anticom | So basically installing files there is the way to go? | 12:48 |
LetoThe2nd | Anticom: i pointed out that this is the place for *SYSTEMD_NETWORKD* | 12:48 |
LetoThe2nd | Anticom: not for *SYSTEMD* | 12:48 |
Anticom | is this a bb var or what are you refering to? | 12:48 |
LetoThe2nd | Anticom: i am totally not referring to anything OE specific in the least. I am *only* pointing out how these things architecturally work. | 12:49 |
Anticom | Arch wiki any many other websites state stuff like: "All configurations in this section are stored as foo.network in /etc/systemd/network." | 12:50 |
Anticom | So what is wrong about my assumption? | 12:50 |
Anticom | I just don't get it | 12:50 |
LetoThe2nd | bottom line. if you have something that works, don't break it. if bootup speed is your concern, there's a lot more options you have besides systemd | 12:51 |
LetoThe2nd | Anticom: they are just all referring to one specific network management software called systemd_networkd, which is part of the systemd source distribution. none of these places on the web applies to anything else. | 12:51 |
Anticom | so yocto doesn't use systemd_networkd ? | 12:52 |
LetoThe2nd | *pling* | 12:52 |
LetoThe2nd | now you got it. | 12:52 |
LetoThe2nd | shall i get you the backlog line where we told you that exact fact already yesterday? | 12:52 |
Anticom | LetoThe2nd: no need, i belive you | 12:53 |
Anticom | So for dummies: systemd_networkd is a networkmanager that talks systemd api? | 12:53 |
LetoThe2nd | Anticom: yeah. | 12:53 |
Anticom | and even in yocto i have multiple alternatives? | 12:54 |
Anticom | like e.g. connman? | 12:54 |
LetoThe2nd | Anticom: and again, be precise. its not "yocto that uses". its "the poky distribution that uses by default" | 12:54 |
LetoThe2nd | Anticom: exactly. pick whatever you want | 12:54 |
Anticom | Any recommendations? | 12:54 |
Anticom | or a good resource comparing them so i can pick one myself? | 12:55 |
LetoThe2nd | Anticom: recommendation "match your requirement against the provided feature sets" | 12:55 |
Anticom | requirement: should work | 12:55 |
Anticom | no special requirements | 12:56 |
Anticom | afaik | 12:56 |
LetoThe2nd | Anticom: that also holds true for an ip= line in the kernel bootargs. please don't be ridiculous. | 12:56 |
Anticom | so maybe small footprint and fast would be nice | 12:56 |
*** flihp_ <flihp_!~flihp@c-50-185-54-102.hsd1.ca.comcast.net> has quit IRC | 12:57 | |
Anticom | LetoThe2nd: we're not building an IOT device. So network connectivity has no special requirements really | 12:57 |
Anticom | didn't want to be offensive | 12:57 |
*** flihp <flihp!~flihp@c-50-185-54-102.hsd1.ca.comcast.net> has joined #yocto | 12:57 | |
LetoThe2nd | Anticom: i guess the requirement are just not qhat you think they are. | 12:57 |
LetoThe2nd | Anticom: ask your user interface people how they are willing to provide configuration data, parse it, etc. | 12:57 |
Anticom | no UI | 12:58 |
Anticom | basically it's a logging device | 12:59 |
LetoThe2nd | Anticom: ok, so they order the device from you with one single fixed network configuration? | 12:59 |
Anticom | yep | 12:59 |
LetoThe2nd | Anticom: then ask your manufacturing guys what they need. | 12:59 |
*** wfailla <wfailla!~wfailla@92.43.51.145> has quit IRC | 12:59 | |
Anticom | just another thought to ease porting from sysvinit. If systemd has a network manager what about sysvinit? is it integrated tight into sysvinit whereas systemd has it nice and modular or is there any for systemd that sysvinit also uses? | 13:00 |
LetoThe2nd | the other way round is, just include connman or networkmanager (who will probably 'jsut work') for trivial cases, and wait until it either goes unnoticed or blows up. | 13:01 |
Anticom | LetoThe2nd: and how do i instruct bitbake to use either of them? is this sufficient? http://www.yoctoproject.org/docs/2.0/mega-manual/mega-manual.html#ref-classes-systemd | 13:02 |
LinuxMice | Hi Everyone, i build java with this command: bitbake openjdk-7-jre and when i want to install this package on my arm board , i take an error : Bus error, wherem am i wrong ? | 13:03 |
Anticom | LinuxMice: got some more verbose error information? 'bus error' isn't much of information | 13:04 |
LetoThe2nd | LinuxMice: sounds like the architecture you built for doesn't match the package.... maybe. | 13:05 |
LinuxMice | Verbose of error is this: Bus error , no another thing | 13:05 |
LetoThe2nd | Anticom: see http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-connectivity/networkmanager/networkmanager_1.0.10.bb | 13:06 |
LetoThe2nd | Anticom: it comes complete with systemd unit support | 13:06 |
*** wfailla <wfailla!~wfailla@92.43.51.144> has joined #yocto | 13:06 | |
LinuxMice | LetoThe2nd: I thing i take error Which is Bus error Because I have no Space for installing ? | 13:07 |
LetoThe2nd | LinuxMice: that is something you can easily check, right? | 13:07 |
LinuxMice | Yeap You are right this way, i boot on nand flash Now i boot on sd card :) Finally i have 1.6 gb available space :) | 13:10 |
*** eengie <eengie!~eengie@static-108-40-78-74.bltmmd.fios.verizon.net> has joined #yocto | 13:15 | |
eengie | Hi all. Has anyone ever seen wic fail with an error like "exec_cmd: install -m 0644 -D <deploy path>/etc <image boot pat>/etc returned '1' instead of 0"?? | 13:16 |
*** maxin <maxin!~maxin@194.136.86.45> has joined #yocto | 13:16 | |
eengie | (I realize it's not really Yocto-related directly, but wic seems to be a pretty common way of packaging Yocto, so I was hoping someone has seen that error) | 13:19 |
*** bottazzini <bottazzini!~realBigfo@192.55.54.42> has joined #yocto | 13:20 | |
eengie | I don't see a way to force a "verbose" output or determine where it's logging information at either. But that error makes me wonder if the return value is simply saying the directory exists and shouldn't really be flagged as an "error" | 13:20 |
Crofton|work | eengie, you might need to file a bug report, the wic devs tend not to hang out on irc | 13:23 |
*** freanux <freanux!~freanux@unaffiliated/freanux> has joined #yocto | 13:24 | |
rburton | eengie: what happens if you run that command yourself? | 13:25 |
*** wfailla_ <wfailla_!~wfailla@92.43.51.144> has joined #yocto | 13:25 | |
*** wfailla <wfailla!~wfailla@92.43.51.144> has quit IRC | 13:25 | |
*** fledermaus <fledermaus!~vivek@93.93.133.71> has joined #yocto | 13:27 | |
eengie | CroftonIwork: Thanks (and thanks again for the last week of helping me out too -- made loads of progress). I may have just sniffed out the issue. I think it's all related to that first question about how to deploy and link files over onto the SD card which ended up being a multi-part approach involving the deploy class (to move the files over to that folder), a pkg_postinst function to create the links after the files were insta | 13:28 |
eengie | rburton: same error as I get when it's in my script. | 13:28 |
eengie | I think where I may have goofed is that I changed IMAGE_BOOT_FILES to simply say "etc" rather than specify explicitly all of the files... | 13:29 |
eengie | There doesn't seem to be a way to access that variable from recipes, unfortunately. | 13:29 |
*** leon-anavi <leon-anavi!~leon@5.53.209.92> has joined #yocto | 13:29 | |
leon-anavi | hi | 13:30 |
eengie | Hello | 13:30 |
rburton | eengie: i mean, run the install command | 13:30 |
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:1208:b1ff:fee8:f733> has joined #yocto | 13:30 | |
leon-anavi | rburton, thanks again for the help with nettle. I have just seen that the fix has been merged in the latest version of branch fido. | 13:31 |
eengie | rburton: sorry, not enough coffee yet... It says omitting directory. | 13:31 |
rburton | eengie: there you go then :) | 13:32 |
eengie | rburton: yeah, I forgot it was one of the changes I made to that layer's conf file...trying to let the user simply deploy files into a couple of documented folders and have wic blindly pick up those whole directories and deploy them to the boot partition. | 13:32 |
*** wfailla_ <wfailla_!~wfailla@92.43.51.144> has quit IRC | 13:33 | |
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:1208:b1ff:fee8:f733> has quit IRC | 13:36 | |
*** belen <belen!~Adium@134.134.139.70> has joined #yocto | 13:37 | |
*** lamego <lamego!jose@nat/intel/x-nvczncdzjgiejyyx> has joined #yocto | 13:37 | |
eengie | Weird, according to the docs, the "glob pattern" should work. So having a layer.conf with IMAGE_BOOT_FILES += "etc/*" should gather up everything in the deploy/..../etc directory. Right? (http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-IMAGE_BOOT_FILES) | 13:38 |
Anticom | maybe dumb question, but doesn't it have to be += "<space> etc/*" ? | 13:39 |
*** zero_note <zero_note!~zero_note@2.238.240.162> has left #yocto | 13:40 | |
eengie | Anticom: not according to that link. Then again that link is specifying with an equals, and I'm trying to append since my layer is tacking on extra things to the SD card. | 13:40 |
rburton | += adds whitespace | 13:44 |
eengie | Interesting... I did an IMAGE_BOOT_FILES += "etc/*;etc/" (equivalent to what the link shows above for the glob format) and got an error that it was malformed. | 13:45 |
eengie | The trouble I've been having with how to add things to that variable is that the most important one, the top-level Xilinx BSP layer has a weak 'set' for the kernel and u-boot, etc. Then the vendor's BSP sets it. But if I specify it, the layer order overwrites the vendor's spec even if I set my layer priority to lower than theirs. | 13:46 |
eengie | And touching the variable from a recipe does absolutely nothing. | 13:46 |
*** vdehors_ <vdehors_!~vdehors@bob75-2-81-56-46-209.fbx.proxad.net> has joined #yocto | 13:48 | |
*** ADM <ADM!~ADEM@198.0.190.238> has joined #yocto | 13:50 | |
eengie | rburton: is there a function I could insert into that variable that would recursively generate a list of directories and files from a certain point? I think I've seen something like that in other recipes using things like bb.utils but I'm having trouble finding it. | 13:52 |
*** vdehors <vdehors!~vdehors@193.56.60.161> has quit IRC | 13:52 | |
*** ant_work <ant_work!~ant__@host213-59-dynamic.50-79-r.retail.telecomitalia.it> has quit IRC | 13:56 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto | 13:57 | |
*** kscherer <kscherer!~kscherer@128.224.252.2> has joined #yocto | 14:01 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC | 14:03 | |
*** Flinger <Flinger!d51670c2@gateway/web/freenode/ip.213.22.112.194> has joined #yocto | 14:04 | |
*** egavinc <egavinc!~egavinc@43.Red-2-139-180.staticIP.rima-tde.net> has quit IRC | 14:05 | |
*** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has quit IRC | 14:12 | |
*** eengie <eengie!~eengie@static-108-40-78-74.bltmmd.fios.verizon.net> has left #yocto | 14:12 | |
*** IvanSB <IvanSB!~IvanSB@host2-50-dynamic.2-87-r.retail.telecomitalia.it> has joined #yocto | 14:16 | |
*** nighty <nighty!~nighty@q029220.ppp.asahi-net.or.jp> has joined #yocto | 14:17 | |
*** zz_ka6sox is now known as ka6sox | 14:18 | |
*** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has joined #yocto | 14:18 | |
*** paulg_ <paulg_!~paulg@198-84-239-75.cpe.teksavvy.com> has joined #yocto | 14:24 | |
tmcguire__ | I added PACKAGE_CLASSES = "package_ipk" to my local.conf, yet bitbake meta-toolchain tries to build nativesdk-rpm (which fails). Any idea how to completely get rid of RPM? | 14:24 |
*** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has quit IRC | 14:28 | |
rburton | why does that fail? | 14:31 |
JaMa | tmcguire__: rpm is used e.g. for debugedit tool even when building ipk packages | 14:32 |
fray | rpm is often built because it has tools for handing debug info and other things.. | 14:32 |
fray | what is the error? | 14:32 |
fray | and what version of rpm are you using? | 14:32 |
tmcguire__ | I'm trying to get Yocto dizzy to work. | 14:32 |
fray | wow, that is pretty old | 14:32 |
fray | why not try a newer version of the YP? | 14:33 |
tmcguire__ | yeah, but I need it to compare with some actual real project | 14:33 |
tmcguire__ | Missing or unbuildable dependency chain was: ['meta-toolchain', 'nativesdk-packagegroup-sdk-host', 'nativesdk-smartpm', 'nativesdk-rpm'] | 14:33 |
tmcguire__ | Hmm, maybe I should just edit the packagegroup | 14:33 |
fray | I don't believe dizzy supported nativesdk-rpm.. so I'm not sure why it would be in that list? | 14:33 |
tmcguire__ | FYI, error is "undefined reference to `db3Free'", but I'd rather exclude RPM than trying to fix that. | 14:34 |
fray | are you mixing dizzy with newer recipes? | 14:34 |
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC | 14:34 | |
fray | any comparison you do will be invalid w/ RPM availabel in the system as it's used to process various debugging and dependency information | 14:34 |
tmcguire__ | I don't believe I'm mixing anything, unless I did something wrong. FWIW, the actual image built fine. | 14:34 |
fray | db3Free comes from BerkleyDB | 14:34 |
tmcguire__ | well, rpm-native is used internally for dependency information, right? That actually builds fine. What doesn't build is nativesdk-rpm, is that really needed? | 14:35 |
*** cart_man <cart_man!29a03a62@gateway/web/freenode/ip.41.160.58.98> has quit IRC | 14:35 | |
* tmcguire__ tries to find the packagegroup thing now and look at it | 14:36 | |
tmcguire__ | Ok, found, let's see in what interesting ways it will break when I remove nativesdk-smartpm from that package group... | 14:38 |
tmcguire__ | Btw, "bitbake -g -u depexp nativesdk-rpm" didn't show the dependency chain, only when i tried to blacklist rpm, I got the error message "dependency chain was: ['meta-toolchain', 'nativesdk-packagegroup-sdk-host', 'nativesdk-smartpm', 'nativesdk-rpm']" | 14:40 |
tmcguire__ | Is there another way to get the dependency chain, apart from blacklisting the package with "PNBLACKLIST"? | 14:41 |
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto | 14:41 | |
*** zeechs_ <zeechs_!~zeechs@ANancy-653-1-675-6.w90-40.abo.wanadoo.fr> has joined #yocto | 14:42 | |
zeechs_ | Hi all, I'm trying to build a Yocto image with opencv installed. So I added meta-oe to have the recipe available, I added opencv to IMAGE_INSTALL, opencv is building fine but is not on the image tar.bz2. I don't understand why? Other packages are installing without any problem. | 14:45 |
zeechs_ | I'm building core-image-base | 14:45 |
*** boucman_work <boucman_work!~jrosen@bob75-2-81-56-46-209.fbx.proxad.net> has joined #yocto | 14:46 | |
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto | 14:46 | |
rburton | zeechs_: iirc opencv doesn't produce a package called "opencv" | 14:49 |
rburton | clearly i need to go and beat the opencv recipe with the work-properly stick | 14:50 |
rburton | zeechs_: assuming you have a fairly recent oe, "oe-pkgdata-util list-pkgs -p opencv" will list the packages that it actually created | 14:50 |
LinuxMice | Hi Evertyone, Finally I installed open-jdk-7 on my device, and i installed tomcat7, JRE_HOME Path needed by is tomcat7, Where find JRE_HOME, Wehere am i installed java | 14:57 |
*** madisox <madisox!~madison@216-75-232-11.static.wiline.com> has joined #yocto | 14:57 | |
zeechs_ | rburton, thanks, it indeed lists all the packages built, which I can find under the "tmp/deploy/rpm/" directory. But how come these packages are not on my target rootfs? | 14:58 |
mborzecki | LinuxMice: wow, are you sure you have enough RAM to run tomcat? :) | 14:58 |
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC | 14:59 | |
boucman_work | rburton, is there a more general command to do the recipe => package matching ? something based on PACKAGES or is that the best way ? (and is there a technicall reason or is it a case of "nobody implemente it") | 14:59 |
zeechs_ | rburton, do I have to add each package to the IMAGE_INSTALL variable ? | 14:59 |
LinuxMice | mborzecki: Yeap i have 512 mb ram and i use yocto fido 1.8 its enough for tomcat7 ;_ | 14:59 |
mborzecki | boucman_work: oe-pkgdata-util | 14:59 |
rburton | boucman_work: that is the general command. reading the recipe is the alternative but the package list can often be determined at build time. oe-pkgdata-util looks at what the recipe actually built. | 15:00 |
kergoth | Is anyone else seeing no documents listed at https://yoctoproject.org/documentation ? | 15:00 |
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has quit IRC | 15:00 | |
kergoth | hrm | 15:00 |
rburton | zeechs_: you'd have to read the recipe, but unless there's a meta-package that depends on all the libraries then yes if you want all of opencv installed. | 15:01 |
rburton | patches welcome it sounds like a lot of people get angry at opencv | 15:01 |
boucman_work | ok | 15:01 |
mborzecki | kergoth: `If there are no results for this category, something is wrong. Please contact the site administrator via the Yocto bug tracker.` | 15:01 |
kergoth | yeah, but i have a bunch of extensions installed that occasionally break sites, so i don't trust that it's not on my end :) | 15:02 |
mborzecki | also https://yoctoproject.org/documentation/active might be a bit outdated | 15:02 |
kergoth | i.e. ublock origin, chameleon, referrer control | 15:02 |
kergoth | so wanted to make sure it was a problem in general, not just here | 15:02 |
zeechs_ | rburton, ok I get it. I now have a better understanding of how the IMAGE_INSTALL works. Thanks a lot! | 15:03 |
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has quit IRC | 15:12 | |
*** pacopedraza2 <pacopedraza2!86868949@gateway/web/freenode/ip.134.134.137.73> has joined #yocto | 15:15 | |
Anticom | Is BB_DANGLINGAPPENDS_WARNONLY disabled by default? Manual doesn't tell it **directly** but it reads like it's disabled if you don't activate it in your local.conf http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-BB_DANGLINGAPPENDS_WARNONLY | 15:20 |
*** joshuagl <joshuagl!~joshuagl@192.198.151.43> has quit IRC | 15:20 | |
*** LinuxMice <LinuxMice!~LinuxMice@193.140.134.110> has quit IRC | 15:22 | |
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has joined #yocto | 15:22 | |
*** Ulfalizer <Ulfalizer!~ulf@212.118.209.82> has joined #yocto | 15:22 | |
*** joshuagl <joshuagl!~joshuagl@192.198.151.44> has joined #yocto | 15:23 | |
*** t0mmy <t0mmy!~tprrt@217.114.201.133> has quit IRC | 15:25 | |
*** t0mmy <t0mmy!~tprrt@217.114.201.133> has joined #yocto | 15:27 | |
*** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has joined #yocto | 15:30 | |
*** vmesons <vmesons!~rmacleod@24-212-184-107.cable.teksavvy.com> has quit IRC | 15:30 | |
*** marek_ <marek_!~marek@81.89.61.168.host.vnet.sk> has quit IRC | 15:36 | |
*** belen <belen!~Adium@134.134.139.70> has quit IRC | 15:40 | |
*** belen <belen!Adium@nat/intel/x-oxixkdpkasvywqdl> has joined #yocto | 15:40 | |
*** townxelliot <townxelliot!~ell@176.252.21.78> has quit IRC | 15:42 | |
*** madisox <madisox!~madison@216-75-232-11.static.wiline.com> has joined #yocto | 15:42 | |
*** gatisp <gatisp!~gp@91.237.34.118> has joined #yocto | 15:43 | |
*** benjamirc <benjamirc!besquive@nat/intel/x-zembpwkzeepcvkrp> has joined #yocto | 15:44 | |
gatisp | Hello, I was wondering does yocto have an API for setting file/dir timestaps for all files in final sysroot? | 15:44 |
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:1208:b1ff:fee8:f733> has joined #yocto | 15:46 | |
*** T0mW <T0mW!~twalsh@64.202.128.113> has joined #yocto | 15:47 | |
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:1208:b1ff:fee8:f733> has quit IRC | 15:49 | |
*** townxelliot <townxelliot!~ell@176.252.190.162> has joined #yocto | 15:49 | |
T0mW | This has been driving me crazy for a few daze. I'm trying to set a value into /etc/version in my image. Currently the "DATE+TIME" is in there, we want "1.3" in /etc/version. I've tried setting $DISTRO_VERSION, also grep'ed the OE tree + bitbake tree but cannot find anywhere which sets a value into /etc/version. | 15:50 |
Crofton|work | rofl | 15:51 |
T0mW | There is something in toolchain-scripts.bbclass which sets something like $versionfile? | 15:51 |
Crofton|work | from #oe | 15:52 |
Crofton|work | <joshuagl> Crofton|work: if you're still looking /etc/version gets written in lib/oe/rootfs.py | 15:52 |
* T0mW looks | 15:52 | |
*** hamis_lt_u <hamis_lt_u!~irfan@110.93.212.98> has quit IRC | 15:52 | |
Crofton|work | there is also an /etc/timestamp | 15:52 |
Crofton|work | joshuagl> Crofton|work: meta/classes/rootfs-postcommands.bbclass | 15:53 |
T0mW | Crofton, Thanks! wonder why egrep doesn't like python? heh | 15:53 |
T0mW | I started looking to append to something like do_populate_sysroot to change the file. | 15:55 |
T0mW | then figured "enough, go ask" | 15:56 |
*** berton <berton!~fabio@177.127.4.103> has quit IRC | 15:57 | |
*** maxin <maxin!~maxin@194.136.86.45> has quit IRC | 15:59 | |
*** T0mW <T0mW!~twalsh@64.202.128.113> has quit IRC | 16:01 | |
*** T0mW <T0mW!~twalsh@64.202.128.113> has joined #yocto | 16:02 | |
T0mW | Crofton, YAY, you da' man! | 16:04 |
Crofton|work | http://stackoverflow.com/questions/35927774/how-to-get-rootfs-build-timestamp-at-runtime | 16:04 |
* T0mW buys Crofton a pizza | 16:04 | |
Crofton|work | someone asked something similar on stackoverflow | 16:04 |
kergoth | Anticom: yes, it's disabled by default. normally dangling appends are fatal | 16:04 |
T0mW | Crofton, yeah, google the crap outa' this one, tons of hits but not answers. Maybe I need to retake remdial-google-101 ? | 16:05 |
* zeddii is locked and loaded for ELC | 16:07 | |
* fray will be there as well | 16:07 | |
* zeddii has good memories of the last time it was in San Diego | 16:07 | |
zeddii | or I should say "hazy memories" | 16:07 |
zeddii | :) | 16:07 |
*** gatisp <gatisp!~gp@91.237.34.118> has quit IRC | 16:07 | |
fray | this is more inland (by the real convention center) then the last one which was next to the airport in the marina.. | 16:08 |
Anticom | kergoth: thank's | 16:08 |
fray | I've been to this area a lot at the San Diego Comic-Con... | 16:08 |
fray | lots of stuff within walking distance | 16:08 |
*** Anticom <Anticom!~timo.m@217.6.33.234> has quit IRC | 16:08 | |
zeddii | Crofton|work. fray is convincing me to leave late enough to stay for the oedam. | 16:09 |
*** fl0v01 <fl0v01!~fvo@pD9F6BC01.dip0.t-ipconnect.de> has quit IRC | 16:11 | |
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has quit IRC | 16:14 | |
*** zero_note <zero_note!~zero_note@2.238.240.162> has joined #yocto | 16:15 | |
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has joined #yocto | 16:15 | |
*** pacopedraza2 <pacopedraza2!86868949@gateway/web/freenode/ip.134.134.137.73> has quit IRC | 16:18 | |
*** t0mmy <t0mmy!~tprrt@217.114.201.133> has quit IRC | 16:19 | |
*** t0mmy <t0mmy!~tprrt@217.114.201.133> has joined #yocto | 16:19 | |
*** edbart1 <edbart1!~ebartosh@192.198.151.44> has joined #yocto | 16:21 | |
*** edbart <edbart!ebartosh@nat/intel/x-bfandqbrkulfimch> has quit IRC | 16:22 | |
*** edbart1 <edbart1!~ebartosh@192.198.151.44> has quit IRC | 16:22 | |
*** sameo <sameo!samuel@nat/intel/x-bmcsaizoqtsxuiuh> has quit IRC | 16:26 | |
Crofton|work | zeddii, aweso,e | 16:27 |
*** afxez0r <afxez0r!~afxez0r@134.134.139.76> has quit IRC | 16:34 | |
*** Aethenelle <Aethenelle!~Aethenell@199.15.128.78> has joined #yocto | 16:36 | |
*** dmoseley <dmoseley!~dmoseley@6532158hfc157.tampabay.res.rr.com> has joined #yocto | 16:40 | |
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has quit IRC | 16:48 | |
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has joined #yocto | 16:48 | |
*** morphis <morphis!~morphis@p5480DE48.dip0.t-ipconnect.de> has quit IRC | 16:52 | |
*** IvanSB <IvanSB!~IvanSB@host2-50-dynamic.2-87-r.retail.telecomitalia.it> has quit IRC | 16:57 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto | 17:01 | |
*** joshuagl <joshuagl!~joshuagl@192.198.151.44> has quit IRC | 17:02 | |
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC | 17:05 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC | 17:08 | |
*** mckoan is now known as mckoan|away | 17:08 | |
*** zeechs_ <zeechs_!~zeechs@ANancy-653-1-675-6.w90-40.abo.wanadoo.fr> has quit IRC | 17:15 | |
*** berton <berton!~fabio@177.127.4.103> has joined #yocto | 17:19 | |
*** pohly <pohly!~pohly@p5DE8C5D0.dip0.t-ipconnect.de> has quit IRC | 17:22 | |
*** afxez0r <afxez0r!~afxez0r@134.134.139.72> has joined #yocto | 17:24 | |
*** berton <berton!~fabio@177.127.4.103> has quit IRC | 17:25 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto | 17:26 | |
*** obsrwr_home <obsrwr_home!~obsrwr@188.24.194.129> has joined #yocto | 17:26 | |
*** afxez0r <afxez0r!~afxez0r@134.134.139.72> has quit IRC | 17:34 | |
*** yann|work <yann|work!~yann@LFbn-1-1026-146.w86-247.abo.wanadoo.fr> has quit IRC | 17:35 | |
*** jbrianceau is now known as jbrianceau_away | 17:38 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC | 17:40 | |
*** berton <berton!~fabio@177.127.4.103> has joined #yocto | 17:42 | |
*** afxez0r <afxez0r!~afxez0r@134.134.139.76> has joined #yocto | 17:52 | |
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has quit IRC | 17:52 | |
*** coolmouse <coolmouse!~coolmouse@124.89.110.117> has quit IRC | 17:52 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto | 17:52 | |
*** jonathanmaw <jonathanmaw!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has quit IRC | 17:52 | |
*** Kakadu <Kakadu!4fad4e8c@gateway/web/freenode/ip.79.173.78.140> has quit IRC | 17:57 | |
*** ADM <ADM!~ADEM@198.0.190.238> has quit IRC | 17:57 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC | 17:58 | |
*** aehs291 <aehs291!~aehernan@134.134.139.77> has quit IRC | 18:02 | |
RP | halstead: I think we agreed the maintainance window was now. When you're done could you start a build of master-next please? | 18:03 |
*** aehs29 <aehs29!~aehernan@134.134.139.77> has joined #yocto | 18:03 | |
halstead | RP will do. Thank you. | 18:04 |
*** Flinger <Flinger!d51670c2@gateway/web/freenode/ip.213.22.112.194> has quit IRC | 18:04 | |
RP | halstead: thanks! | 18:04 |
*** roccof <roccof!~roccof@93-51-177-218.ip268.fastwebnet.it> has quit IRC | 18:08 | |
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has quit IRC | 18:12 | |
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has joined #yocto | 18:13 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto | 18:13 | |
*** matteo <matteo!~matteo@openwrt/developer/matteo> has quit IRC | 18:13 | |
*** fishey1 <fishey1!~jmesmon@turntable.einic.org> has quit IRC | 18:16 | |
*** benjamirc <benjamirc!besquive@nat/intel/x-zembpwkzeepcvkrp> has quit IRC | 18:17 | |
*** toddw_ <toddw_!~toddw@c-24-125-145-193.hsd1.ga.comcast.net> has quit IRC | 18:18 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC | 18:20 | |
*** pacopedraza2 <pacopedraza2!8686894b@gateway/web/freenode/ip.134.134.137.75> has joined #yocto | 18:23 | |
*** edbart <edbart!~ebartosh@192.198.151.43> has joined #yocto | 18:29 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto | 18:32 | |
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC | 18:32 | |
*** belen <belen!Adium@nat/intel/x-oxixkdpkasvywqdl> has quit IRC | 18:35 | |
*** bottazzini <bottazzini!~realBigfo@192.55.54.42> has quit IRC | 18:35 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC | 18:38 | |
*** fishey1 <fishey1!~jmesmon@turntable.einic.org> has joined #yocto | 18:42 | |
*** edbart <edbart!~ebartosh@192.198.151.43> has quit IRC | 18:45 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto | 18:48 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC | 18:55 | |
kergoth | grr, i'm really not happy with the shallow implementation, but i'm also having trouble finding any better way to do it | 18:59 |
kergoth | hmm | 18:59 |
*** townxelliot <townxelliot!~ell@176.252.190.162> has quit IRC | 19:04 | |
* kergoth grumbles | 19:05 | |
*** Snert_ <Snert_!~snert_@69-161-21-126.static.acsalaska.net> has quit IRC | 19:05 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto | 19:07 | |
*** leon-anavi <leon-anavi!~leon@5.53.209.92> has quit IRC | 19:08 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC | 19:14 | |
*** mihai <mihai!mihai@nat/intel/x-onasgefnjvxwllmo> has quit IRC | 19:15 | |
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto | 19:16 | |
*** dmoseley <dmoseley!~dmoseley@6532158hfc157.tampabay.res.rr.com> has quit IRC | 19:19 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto | 19:20 | |
*** Saur <Saur!pkj@nat/axis/x-xqblanaxsxbiefxe> has quit IRC | 19:20 | |
*** bottazzini <bottazzini!~realBigfo@192.55.54.42> has joined #yocto | 19:25 | |
*** TobSnyder <TobSnyder!~schneider@ip9234b44d.dynamic.kabel-deutschland.de> has quit IRC | 19:27 | |
*** t0mmy <t0mmy!~tprrt@217.114.201.133> has quit IRC | 19:30 | |
*** Saur <Saur!pkj@nat/axis/x-ihkoibfumvkanvwn> has joined #yocto | 19:32 | |
*** ftonello <ftonello!~felipe@81.145.202.106> has quit IRC | 19:38 | |
*** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has quit IRC | 19:45 | |
*** vquicksilver_ <vquicksilver_!~nobody@gentoo/contributor/vquicksilver> has quit IRC | 19:46 | |
*** vquicksilver <vquicksilver!~nobody@gentoo/contributor/vquicksilver> has joined #yocto | 19:46 | |
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-hzlksyiytjjsjdht> has quit IRC | 19:48 | |
*** alimon1 <alimon1!~alimon@134.134.137.73> has quit IRC | 19:55 | |
*** scottrif <scottrif!~scottrif@68-186-122-205.dhcp.knwc.wa.charter.com> has joined #yocto | 19:55 | |
*** bottazzini <bottazzini!~realBigfo@192.55.54.42> has quit IRC | 19:55 | |
*** maxin <maxin!~maxin@dsl-espbrasgw1-54fa79-93.dhcp.inet.fi> has joined #yocto | 20:02 | |
*** evanmeagher <evanmeagher!~evanmeagh@75-101-86-8.static.sonic.net> has joined #yocto | 20:05 | |
*** t0mmy <t0mmy!~tprrt@ram31-2-82-228-88-46.fbx.proxad.net> has joined #yocto | 20:06 | |
*** evanmeagher <evanmeagher!~evanmeagh@75-101-86-8.static.sonic.net> has quit IRC | 20:19 | |
*** maxin <maxin!~maxin@dsl-espbrasgw1-54fa79-93.dhcp.inet.fi> has left #yocto | 20:19 | |
*** evanmeagher <evanmeagher!~evanmeagh@75-101-86-8.static.sonic.net> has joined #yocto | 20:20 | |
*** evanmeagher <evanmeagher!~evanmeagh@75-101-86-8.static.sonic.net> has quit IRC | 20:22 | |
*** sameo <sameo!~samuel@192.55.54.40> has joined #yocto | 20:26 | |
*** N-a-N <N-a-N!uid149677@gateway/web/irccloud.com/x-lbrntngexcylekme> has quit IRC | 20:26 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC | 20:28 | |
*** T0mW <T0mW!~twalsh@64.202.128.113> has quit IRC | 20:40 | |
*** lamego <lamego!jose@nat/intel/x-nvczncdzjgiejyyx> has quit IRC | 20:41 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto | 20:42 | |
*** alimon1 <alimon1!alimon@nat/intel/x-hmsbfifgyrglxfif> has joined #yocto | 20:44 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC | 20:48 | |
*** dreyna4529 <dreyna4529!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto | 20:51 | |
*** lamego <lamego!~jose@134.134.139.77> has joined #yocto | 20:58 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto | 21:00 | |
*** pacopedraza2 <pacopedraza2!8686894b@gateway/web/freenode/ip.134.134.137.75> has quit IRC | 21:01 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC | 21:06 | |
*** fledermaus <fledermaus!~vivek@93.93.133.71> has quit IRC | 21:10 | |
*** yann|work <yann|work!~yann@nan92-1-81-57-214-146.fbx.proxad.net> has joined #yocto | 21:14 | |
*** scottrif <scottrif!~scottrif@68-186-122-205.dhcp.knwc.wa.charter.com> has left #yocto | 21:14 | |
*** caiortp <caiortp!~inatel@131.221.240.204> has quit IRC | 21:16 | |
*** berton <berton!~fabio@177.127.4.103> has quit IRC | 21:16 | |
*** obsrwr_home <obsrwr_home!~obsrwr@188.24.194.129> has quit IRC | 21:23 | |
*** sameo <sameo!~samuel@192.55.54.40> has quit IRC | 21:25 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto | 21:27 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC | 21:33 | |
*** pacopedraza <pacopedraza!86868b4e@gateway/web/freenode/ip.134.134.139.78> has joined #yocto | 21:37 | |
*** sjolley <sjolley!sjolley@nat/intel/x-gljtlmoiuhwftrgs> has quit IRC | 21:37 | |
*** sjolley <sjolley!sjolley@nat/intel/x-vbxfsizxsjwdfauh> has joined #yocto | 21:39 | |
*** scottrif <scottrif!~scottrif@68-186-122-205.dhcp.knwc.wa.charter.com> has joined #yocto | 21:42 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto | 21:47 | |
*** scottrif <scottrif!~scottrif@68-186-122-205.dhcp.knwc.wa.charter.com> has left #yocto | 21:50 | |
*** bottazzini <bottazzini!~realBigfo@192.55.54.42> has joined #yocto | 21:54 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC | 21:58 | |
*** eraineri <eraineri!~eraineri@2605:6000:151e:814d:224:d7ff:febc:c3d0> has joined #yocto | 21:59 | |
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has joined #yocto | 22:07 | |
*** lamego <lamego!~jose@134.134.139.77> has quit IRC | 22:09 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto | 22:12 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC | 22:17 | |
*** lamego <lamego!jose@nat/intel/x-ckemwqjbbdailror> has joined #yocto | 22:23 | |
*** toddw <toddw!~toddw@c-24-99-187-237.hsd1.ga.comcast.net> has joined #yocto | 22:28 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto | 22:29 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC | 22:37 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto | 22:38 | |
*** ant_home <ant_home!~ant__@host225-252-dynamic.0-87-r.retail.telecomitalia.it> has joined #yocto | 22:39 | |
*** zero_note <zero_note!~zero_note@2.238.240.162> has quit IRC | 22:40 | |
*** evanmeagher <evanmeagher!~evanmeagh@50.1.57.30> has joined #yocto | 22:49 | |
*** kscherer <kscherer!~kscherer@128.224.252.2> has quit IRC | 22:51 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC | 22:54 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has joined #yocto | 22:55 | |
*** 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 | |
*** nighty <nighty!~nighty@q029220.ppp.asahi-net.or.jp> has quit IRC | 23:02 | |
*** ant_home <ant_home!~ant__@host225-252-dynamic.0-87-r.retail.telecomitalia.it> has quit IRC | 23:05 | |
*** aehs29 <aehs29!~aehernan@134.134.139.77> has quit IRC | 23:05 | |
*** aehs29 <aehs29!~aehernan@134.134.139.77> has joined #yocto | 23:06 | |
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:5f7f:f279:59ff:fe64:3a8> has quit IRC | 23:08 | |
*** evanmeagher <evanmeagher!~evanmeagh@50.1.57.30> has quit IRC | 23:12 | |
*** alimon1 <alimon1!alimon@nat/intel/x-hmsbfifgyrglxfif> has quit IRC | 23:12 | |
*** toddw <toddw!~toddw@c-24-99-187-237.hsd1.ga.comcast.net> has quit IRC | 23:12 | |
*** evanmeagher <evanmeagher!~evanmeagh@50.1.57.30> has joined #yocto | 23:14 | |
*** rburton <rburton!~Adium@home.burtonini.com> has quit IRC | 23:20 | |
*** lamego <lamego!jose@nat/intel/x-ckemwqjbbdailror> has quit IRC | 23:21 | |
*** evanmeag_ <evanmeag_!~evanmeagh@50.1.57.30> has joined #yocto | 23:28 | |
*** evanmeagher <evanmeagher!~evanmeagh@50.1.57.30> has quit IRC | 23:30 | |
*** agust <agust!~agust@pD9E2FEE4.dip0.t-ipconnect.de> has quit IRC | 23:45 | |
-YoctoAutoBuilder- build #701 of nightly-fsl-ppc-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc-lsb/builds/701 | 23:50 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!