| *** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto | 00:07 | |
| *** phantoneD <phantoneD!destroy@a89-152-21-144.cpe.netcabo.pt> has joined #yocto | 00:32 | |
| *** phantoxeD <phantoxeD!destroy@a89-152-21-144.cpe.netcabo.pt> has quit IRC | 00:36 | |
| *** Mohican <Mohican!~Doug@177.138.200.94> has joined #yocto | 00:50 | |
| *** Mohican <Mohican!~Doug@177.138.200.94> has quit IRC | 01:00 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto | 01:22 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC | 01:26 | |
| *** phantoxeD <phantoxeD!destroy@a89-152-21-144.cpe.netcabo.pt> has joined #yocto | 01:32 | |
| *** phantoneD <phantoneD!destroy@a89-152-21-144.cpe.netcabo.pt> has quit IRC | 01:36 | |
| *** bigwyrm <bigwyrm!~wyrm@73.151.217.0> has quit IRC | 01:58 | |
| *** bigwyrm <bigwyrm!~wyrm@73.151.217.0> has joined #yocto | 02:10 | |
| *** phantoneD <phantoneD!destroy@a89-152-21-144.cpe.netcabo.pt> has joined #yocto | 02:32 | |
| *** phantoxeD <phantoxeD!destroy@a89-152-21-144.cpe.netcabo.pt> has quit IRC | 02:36 | |
| *** khem` <khem`!~khem@unaffiliated/khem> has quit IRC | 02:51 | |
| *** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC | 03:02 | |
| *** dlan <dlan!~dennis@116.228.88.131> has joined #yocto | 03:03 | |
| *** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto | 03:03 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto | 03:23 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC | 03:27 | |
| *** behanw <behanw!~behanw@205-214-226-20.static-ip.telepacific.net> has quit IRC | 04:06 | |
| *** behanw <behanw!~behanw@205-214-226-20.static-ip.telepacific.net> has joined #yocto | 04:08 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 04:13 | |
| *** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto | 04:15 | |
| *** hitlin37 <hitlin37!uid16371@gateway/web/irccloud.com/x-dyvvecvagqtvppob> has joined #yocto | 04:27 | |
| *** [Sno] <[Sno]!~sno@p578b540c.dip0.t-ipconnect.de> has quit IRC | 04:57 | |
| *** hamis <hamis!~irfan@110.93.212.98> has joined #yocto | 05:09 | |
| *** grma <grma!~gruberm@chello213047201250.tirol.surfer.at> has quit IRC | 05:09 | |
| *** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has joined #yocto | 05:11 | |
| *** zecke <zecke!~ich@ip5b41fb99.dynamic.kabel-deutschland.de> has joined #yocto | 05:13 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto | 05:24 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC | 05:28 | |
| *** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@host251-110-dynamic.27-79-r.retail.telecomitalia.it> has joined #yocto | 05:32 | |
| *** em|fb <em|fb!~fb@mail.emtrion.de> has quit IRC | 05:45 | |
| *** sujith_h <sujith_h!~sharidas@kde/developers/sujithh> has joined #yocto | 06:00 | |
| *** frsc <frsc!~frsc@80.149.173.68> has joined #yocto | 06:18 | |
| *** jku <jku!jku@nat/intel/x-pjhhztagohjezdcj> has joined #yocto | 06:28 | |
| *** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@host251-110-dynamic.27-79-r.retail.telecomitalia.it> has quit IRC | 06:30 | |
| *** nighty^ <nighty^!~nighty@hokuriku.rural-networks.com> has joined #yocto | 06:32 | |
| *** pohly <pohly!~pohly@p57A56DBD.dip0.t-ipconnect.de> has joined #yocto | 06:34 | |
| *** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has joined #yocto | 06:42 | |
| *** [Sno] <[Sno]!~sno@rademacherexchange.de> has joined #yocto | 06:46 | |
| *** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-rkawyngncmkhwkiq> has joined #yocto | 06:51 | |
| *** jbrianceau_away is now known as jbrianceau | 06:52 | |
| *** noraply <noraply!~nora@sestofw01.enea.se> has joined #yocto | 07:06 | |
| *** noraply <noraply!~nora@sestofw01.enea.se> has quit IRC | 07:08 | |
| *** noraply <noraply!~nora@sestofw01.enea.se> has joined #yocto | 07:08 | |
| *** hitlin37 <hitlin37!uid16371@gateway/web/irccloud.com/x-dyvvecvagqtvppob> has quit IRC | 07:12 | |
| *** fredcadete <fredcadete!d4a63893@gateway/web/freenode/ip.212.166.56.147> has joined #yocto | 07:17 | |
| *** egavinc <egavinc!~egavinc@43.Red-2-139-180.staticIP.rima-tde.net> has joined #yocto | 07:17 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC | 07:18 | |
| *** ant_work <ant_work!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has joined #yocto | 07:19 | |
| *** AzaToth <AzaToth!~AzaToth__@wikipedia/AzaToth> has joined #yocto | 07:20 | |
| *** egavinc <egavinc!~egavinc@43.Red-2-139-180.staticIP.rima-tde.net> has quit IRC | 07:22 | |
| *** egavin <egavin!~egavin@43.Red-2-139-180.staticIP.rima-tde.net> has joined #yocto | 07:22 | |
| *** belen <belen!Adium@nat/intel/x-tylomatqeydrnfuc> has joined #yocto | 07:22 | |
| *** joseppc <joseppc!~Josep@sestofw01.enea.se> has joined #yocto | 07:23 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto | 07:25 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC | 07:29 | |
| *** sameo <sameo!~samuel@192.55.54.42> has joined #yocto | 07:30 | |
| *** behanw <behanw!~behanw@205-214-226-20.static-ip.telepacific.net> has quit IRC | 07:39 | |
| *** psnsilva <psnsilva!~psnsilva@193-126-29-154.net.novis.pt> has joined #yocto | 07:41 | |
| *** roccof <roccof!~rocco@93-51-177-218.ip268.fastwebnet.it> has joined #yocto | 07:41 | |
| *** TobSnyder <TobSnyder!~schneider@ip923450f2.dynamic.kabel-deutschland.de> has joined #yocto | 07:47 | |
| *** topik <topik!topik@kapsi.fi> has joined #yocto | 07:55 | |
| topik | hey, has anyone stumbled on a circular dependency error on initscripts_1.0.bb? | 07:56 |
|---|---|---|
| topik | apparently it used to be problem with intel-iot-devkit but i'm not using that | 07:56 |
| *** khem` <khem`!~khem@unaffiliated/khem> has quit IRC | 07:58 | |
| *** bluelightning <bluelightning!~paul@83.217.123.106> has joined #yocto | 08:03 | |
| *** bluelightning <bluelightning!~paul@83.217.123.106> has quit IRC | 08:03 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 08:03 | |
| *** sameo <sameo!~samuel@192.55.54.42> has quit IRC | 08:06 | |
| *** zwerch <zwerch!~Adium@ip-178-200-96-248.hsi07.unitymediagroup.de> has joined #yocto | 08:09 | |
| *** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto | 08:15 | |
| *** jimBaxter <jimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto | 08:18 | |
| *** malkauns <malkauns!~neil@c-50-131-4-242.hsd1.ca.comcast.net> has quit IRC | 08:18 | |
| *** dieter_ <dieter_!~quassel@pD9FCD43E.dip0.t-ipconnect.de> has joined #yocto | 08:20 | |
| *** dieter__ <dieter__!~quassel@pD9FCD43E.dip0.t-ipconnect.de> has joined #yocto | 08:20 | |
| *** dieter_ <dieter_!~quassel@pD9FCD43E.dip0.t-ipconnect.de> has quit IRC | 08:21 | |
| *** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-bncchaodqhkjrjvn> has joined #yocto | 08:22 | |
| *** jonathanmaw <jonathanmaw!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has joined #yocto | 08:22 | |
| *** igor <igor!~Igor_Stop@134.134.137.73> has joined #yocto | 08:23 | |
| bluelightning | morning all | 08:29 |
| *** florian_kc is now known as florian | 08:41 | |
| *** malkauns <malkauns!~neil@c-50-131-4-242.hsd1.ca.comcast.net> has joined #yocto | 08:41 | |
| *** sameo <sameo!~samuel@192.55.54.42> has joined #yocto | 08:42 | |
| zwerch | good morning :) | 08:47 |
| *** zwerch1 <zwerch1!~Adium@82.113.106.154> has joined #yocto | 08:54 | |
| *** zwerch2 <zwerch2!~Adium@ip-178-200-96-248.hsi07.unitymediagroup.de> has joined #yocto | 08:56 | |
| *** zwerch <zwerch!~Adium@ip-178-200-96-248.hsi07.unitymediagroup.de> has quit IRC | 08:56 | |
| *** zwerch1 <zwerch1!~Adium@82.113.106.154> has quit IRC | 08:59 | |
| *** zwerch2 <zwerch2!~Adium@ip-178-200-96-248.hsi07.unitymediagroup.de> has quit IRC | 08:59 | |
| *** zwerch <zwerch!~Adium@ip-178-200-96-248.hsi07.unitymediagroup.de> has joined #yocto | 09:00 | |
| *** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-bncchaodqhkjrjvn> has left #yocto | 09:12 | |
| *** zecke <zecke!~ich@ip5b41fb99.dynamic.kabel-deutschland.de> has quit IRC | 09:12 | |
| *** malkauns <malkauns!~neil@c-50-131-4-242.hsd1.ca.comcast.net> has quit IRC | 09:12 | |
| nerdboy | same thing over here... | 09:12 |
| nerdboy | https://www.youtube.com/watch?v=kerUbfOQTW0 | 09:12 |
| *** jeremiah <jeremiah!~jeremiah@83.218.80.242> has joined #yocto | 09:18 | |
| jeremiah | OHAI! | 09:18 |
| jeremiah | Is there a separate IRC channel for OE? | 09:18 |
| jeremiah | I'm hoping to speak to the maintainer of the perl layers for OE | 09:18 |
| jeremiah | and I wonder if it is best to try here or somewhere else. | 09:19 |
| jeremiah | The yak I wish to shave is why are there two perl versions given for perl in in yocto 1.7 (perl 5.20.0 and 5.14.2) | 09:20 |
| bluelightning | jeremiah: there is #oe yes | 09:20 |
| *** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@93-33-57-140.ip43.fastwebnet.it> has joined #yocto | 09:21 | |
| jeremiah | bluelightning: Thanks, I guess I'll hop over there. :-) | 09:21 |
| *** sameo_ <sameo_!samuel@nat/intel/x-ihqgwwyllggzqjez> has joined #yocto | 09:24 | |
| *** sameo <sameo!~samuel@192.55.54.42> has quit IRC | 09:24 | |
| *** zecke <zecke!~ich@ip5b41fb99.dynamic.kabel-deutschland.de> has joined #yocto | 09:30 | |
| *** malkauns <malkauns!~neil@c-50-131-4-242.hsd1.ca.comcast.net> has joined #yocto | 09:37 | |
| *** milan_ <milan_!~milan@111.93.218.67> has joined #yocto | 10:09 | |
| *** malkauns <malkauns!~neil@c-50-131-4-242.hsd1.ca.comcast.net> has quit IRC | 10:11 | |
| milan_ | bluelightning: I want to add "TARGET_CC_ARCH_append_pn-<package> = " -fPIC -pie " to all packages of a packagegroup. Can I do it with a bbappend for the packagegroup.bb file, instead of changing each package recipe ? | 10:12 |
| bluelightning | milan_: I'm afraid not; one recipe cannot influence the build process of another in that way | 10:13 |
| milan_ | ok | 10:13 |
| milan_ | Is it at all possible to achieve this for a particular image ? I do not want to affect other images (using the same packages) with this change. Probably that's why I am not able to add this to distro.conf file as well :( | 10:16 |
| milan_ | bluelightning : Would appreciate any advice on the above scenario | 10:21 |
| bluelightning | there are only two practical ways really - have two recipes (perhaps sharing a common inc file) that deploy differently named packages that you can select from the image; or, completely separate builds with separate distro configurations | 10:23 |
| zwerch | I am currently working on cleaning up my system on the machine, and I have some packages I absolutely do not need. For example "avahi-daemon". But opkg says it is depended upon by some packages: packagegroup-base-zeroconf & libnss-mdns. Is there a way to overwrite these dependencies and force bitbake to not install them at all? | 10:24 |
| milan_ | bluelightning : thanks | 10:26 |
| *** rburton <rburton!~Adium@35.106.2.81.in-addr.arpa> has joined #yocto | 10:26 | |
| *** zecke <zecke!~ich@ip5b41fb99.dynamic.kabel-deutschland.de> has quit IRC | 10:29 | |
| *** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto | 10:30 | |
| bluelightning | zwerch: have a look at the packagegroup-base recipe and see how those packagegroups come in - it's all based on MACHINE_FEATURES and DISTRO_FEATURES, so you should set those appropriately | 10:33 |
| bluelightning | zwerch: mostly it'll be about DISTRO_FEATURES | 10:33 |
| *** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@93-33-57-140.ip43.fastwebnet.it> has quit IRC | 10:36 | |
| *** ant__ <ant__!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has joined #yocto | 10:43 | |
| *** malkauns <malkauns!~neil@c-50-131-4-242.hsd1.ca.comcast.net> has joined #yocto | 10:45 | |
| *** ant_work <ant_work!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has quit IRC | 10:46 | |
| *** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@93-33-57-140.ip43.fastwebnet.it> has joined #yocto | 10:48 | |
| *** xulfer <xulfer!~xulfer@2001:41d0:2:5ee0::> has quit IRC | 10:49 | |
| *** erbo <erbo!~erik@li444-24.members.linode.com> has quit IRC | 10:50 | |
| *** tingleby <tingleby!~tom@luna.ewsting.org> has quit IRC | 10:51 | |
| *** rperier <rperier!~quassel@2001:41d0:52:100::44a> has quit IRC | 10:51 | |
| *** ndec <ndec!~ndec@linaro/ndec> has quit IRC | 10:51 | |
| *** rperier <rperier!~quassel@2001:41d0:52:100::44a> has joined #yocto | 10:53 | |
| *** ndec <ndec!~ndec@linaro/ndec> has joined #yocto | 10:53 | |
| *** malkauns <malkauns!~neil@c-50-131-4-242.hsd1.ca.comcast.net> has quit IRC | 10:54 | |
| *** pegu` <pegu`!~user@c28823E56.dhcp.as2116.net> has joined #yocto | 10:55 | |
| *** xulfer <xulfer!~xulfer@2001:41d0:2:5ee0::> has joined #yocto | 10:57 | |
| *** pegu <pegu!~user@c28823E56.dhcp.as2116.net> has quit IRC | 10:59 | |
| *** tingleby <tingleby!~tom@luna.ewsting.org> has joined #yocto | 10:59 | |
| *** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC | 11:02 | |
| *** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto | 11:03 | |
| zwerch | bluelightning: thanks, I'll have a look | 11:04 |
| *** erbo <erbo!~erik@li444-24.members.linode.com> has joined #yocto | 11:06 | |
| *** mcfrisk <mcfrisk!mcfrisk@kapsi.fi> has joined #yocto | 11:07 | |
| *** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC | 11:08 | |
| *** zecke <zecke!~ich@ip5b41c1ec.dynamic.kabel-deutschland.de> has joined #yocto | 11:10 | |
| mcfrisk | Hi! I'm trying to do static code analysis with CodeSonar on yocto, using codesonar's compiler wrapper. Is there a way I can wrap all do_compile funcions with this compiler wrapper? I could extend base.bbclass to run oe_runmake with codesonar wrapper but that would not match custom do_compile's in various recipes. | 11:10 |
| *** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has joined #yocto | 11:10 | |
| AzaToth | Anyone knows where "watchdog watchdog0: watchdog did not stop!" comes from, and how to disable it spamming logs? | 11:11 |
| zwerch | AzaToth: obviously from some watchdog ^^ maybe have a look at your /etc/watchdog.conf (if it exists) | 11:12 |
| joseppc | AzaToth: probably it has the magic close feature | 11:14 |
| zwerch | bluelightning: the base for my image is the core-x11 image, but I can't find packagegroup-base-zeroconf anywhere :( | 11:15 |
| bluelightning | mcfrisk: hmm... I suspect you'd prepend CC or something like that in order to have the wrapper invoked | 11:15 |
| bluelightning | zwerch: packagegroup-base-zeroconf is a package produced from the packagegroup-base recipe that I mentioned earlier - meta/recipes-core/packagegroups/packagegroup-base.bb | 11:16 |
| AzaToth | joseppc, what's the magic close feature? | 11:16 |
| zwerch | bluelightning: yeah I know, already found it's declaration, but how can I exclude this packagegroup from packagegroup-base without rewriting it? | 11:17 |
| AzaToth | zwerch, we've enabled the watchdog chip in the kernel config, but we've no watchdog.conf | 11:17 |
| zwerch | bluelightning: ooooooh never mind | 11:17 |
| mcfrisk | bluelightning: actually I could just call "codesonar analyze bitbake image_name", but codesonar doesn't know how to split results after compiling like this. With Coverity the analysis results can be post-processed and split to recipies based on source file locations in the build tree. | 11:17 |
| zwerch | bluelightning: I think I got it, thanks so much | 11:17 |
| joseppc | AzaToth: to start the WD you open the device, normally it is disabled if you close the file descriptor. With the magic close the WD keeps ticking even after the file is closed | 11:18 |
| zwerch | AzaToth, then maybe this is the problem. Try installing the watchdog package and enable it's hardware-device | 11:18 |
| joseppc | AzaToth: at least unless you write the "magic string", which is the V character to the file, then the WD will be disabled upon closing the fd | 11:18 |
| AzaToth | looking; thanks | 11:19 |
| mcfrisk | bluelightning: ... so I'd like a way to run all do_compile's with the 'codesonar analyze ${DISTRO}_${PN} do_compile' | 11:19 |
| zwerch | AzaToth: http://layers.openembedded.org/layerindex/recipe/122/ | 11:20 |
| *** raykinsella78 <raykinsella78!~rkinsell@192.198.151.43> has joined #yocto | 11:20 | |
| zwerch | AzaToth: one of the patches applied uses /dev/watchdog as hardware watchdog device | 11:20 |
| bluelightning | mcfrisk: I'm not sure you can easily do that, that I know of... I guess you could do something like do_compile_prepend() { codesonar analyse ... ( } do_compile_append() { ) }, but I really don't know that that will work or even parse for that matter | 11:21 |
| bluelightning | mcfrisk: another hacky way around it would perhaps to be use anonymous python to grab the value of do_compile, set that as another function, then set do_compile_prepend() to call that function within the wrapper and then exit | 11:23 |
| AzaToth | zwerch, ah | 11:24 |
| mcfrisk | bluelightning: the prepend&append I could try out, maybe with a here text though it does feel really hacky too. | 11:24 |
| mcfrisk | how does that anonymous python thing work, any examples I could have a look at? | 11:25 |
| bluelightning | mcfrisk: right, and whether it works is going to be dependent on your append/prepend being applied last | 11:26 |
| *** raykinsella78 <raykinsella78!~rkinsell@192.198.151.43> has quit IRC | 11:27 | |
| bluelightning | mcfrisk: git grep 'python \(__anonymous \)\?() {' | 11:29 |
| bluelightning | (the __anonymous is optional, I believe the modern convention is not to include it) | 11:29 |
| mcfrisk | hmm, all of these depend on the order of execution, when is the anonymous python thing executed? When parsing the recipe? | 11:31 |
| *** rperier <rperier!~quassel@2001:41d0:52:100::44a> has quit IRC | 11:42 | |
| *** rperier <rperier!~quassel@ubuntu/member/rperier> has joined #yocto | 11:42 | |
| *** zecke <zecke!~ich@ip5b41c1ec.dynamic.kabel-deutschland.de> has quit IRC | 11:50 | |
| -YoctoAutoBuilder- build #454 of nightly-qa-skeleton is complete: Failure [failed Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-skeleton/builds/454 | 11:50 | |
| -YoctoAutoBuilder- build #454 of nightly-qa-pam is complete: Failure [failed Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-pam/builds/454 | 11:52 | |
| ericbutt1rs | hi.. i am interested in the testimage stuff.. but i do not want to boot the target and deploy stuff. i only want to get the tests generated and afterwards run them from a different machine. is there a way to get rid of the masterimage stuff.. only getting the tests? | 11:56 |
| milan_ | bluelightning: If I add a DISTROOVERRIDES in an image.bb file, should it affect the included packages for that image this way ? | 11:57 |
| rburton | no | 11:58 |
| *** grma <grma!~gruberm@HSI-KBW-46-237-193-133.hsi.kabel-badenwuerttemberg.de> has joined #yocto | 11:59 | |
| *** malkauns <malkauns!~neil@c-50-131-4-242.hsd1.ca.comcast.net> has joined #yocto | 11:59 | |
| milan_ | rburton: But when I run bitbake -e image, I can see the DISTROOVERRIDES included in to the overrides list! Not sure why it should not reflect for the listed packages under it. | 12:01 |
| *** tasslehoff <tasslehoff!~Tasslehof@77.40.182.98> has joined #yocto | 12:02 | |
| rburton | milan_: it won't rebuild the recipes though | 12:02 |
| *** zecke <zecke!~ich@ip5b41c1ec.dynamic.kabel-deutschland.de> has joined #yocto | 12:02 | |
| milan_ | ok,understood | 12:03 |
| *** grma <grma!~gruberm@HSI-KBW-46-237-193-133.hsi.kabel-badenwuerttemberg.de> has quit IRC | 12:06 | |
| *** fredcadete <fredcadete!d4a63893@gateway/web/freenode/ip.212.166.56.147> has quit IRC | 12:06 | |
| *** grma <grma!~gruberm@HSI-KBW-46-237-193-133.hsi.kabel-badenwuerttemberg.de> has joined #yocto | 12:07 | |
| milan_ | rburton: Will it make sense to add "SSTATE_DISABLE="1" as well into the image file here ? | 12:07 |
| milan_ | Hope that should help rebuild all the packages | 12:07 |
| rburton | you can't manipulate distro-wide settings from inside an image | 12:09 |
| rburton | inside the image recipe any changes you make are specific to the image recipe | 12:09 |
| milan_ | rburton: My changes are focussed on a particular image ( meant for a specific customer). Hope I am on the right path then ? | 12:11 |
| milan_ | I dont want it to be reflected across all images of the distro | 12:11 |
| -YoctoAutoBuilder- build #455 of nightly-x32 is complete: Failure [failed Running Sanity Tests_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/455 | 12:15 | |
| zwerch | How can I delete some DISTRO_FEATURES without rewriting them completely? | 12:22 |
| *** challinan <challinan!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has joined #yocto | 12:23 | |
| bluelightning | milan_: as I said earlier, you simply cannot do things the way you're trying to do them - you cannot influence the build one recipe from another - i.e. you can't make these changes from the packagegroup or the image recipe | 12:24 |
| rburton | zwerch: DISTRO_FEATURES_remove, if you have a recent enough OE | 12:24 |
| zwerch | rburton: is 1.7 recent enough? | 12:24 |
| bluelightning | yes | 12:25 |
| zwerch | nice, thansk | 12:25 |
| zwerch | Can I do this in the image / layer.conf or does it have to be done in the local.conf? | 12:26 |
| bluelightning | zwerch: local.conf or custom distro config (preferably the latter) | 12:27 |
| bluelightning | zwerch: doing things like that in the layer.conf is evil | 12:28 |
| zwerch | Okay, thanks | 12:28 |
| zwerch | I still don't get when to use which conf ^^ | 12:29 |
| bluelightning | local.conf is for local settings, the less you put in there the better (it's supposed to be something you create for the specific install and completely replicable without having to put it into version control) | 12:30 |
| bluelightning | anything that is "policy" about how the system is built i.e. which recipes to select, what options to enable, etc. should go into the custom distro config that you point to from DISTRO | 12:31 |
| zwerch | okay, then we did it intuitively right :) thanks | 12:32 |
| bluelightning | the layer.conf should just add the paths such that items in the layer can be found and set the priority, and that's pretty much it | 12:33 |
| zwerch | so, our DISTRO is by default set to "poky", where do I find the distro config (and how do I append it)? | 12:38 |
| *** zecke <zecke!~ich@ip5b41c1ec.dynamic.kabel-deutschland.de> has quit IRC | 12:39 | |
| *** AzaToth <AzaToth!~AzaToth__@wikipedia/AzaToth> has quit IRC | 12:40 | |
| *** AzaToth_ <AzaToth_!~AzaToth__@www3.mikrolund.ideon.se> has joined #yocto | 12:40 | |
| *** Crofton <Crofton!~balister@pool-108-44-118-114.ronkva.east.verizon.net> has quit IRC | 12:42 | |
| zwerch | Ah, I found the poky.conf, but how can I create a new distro that inherits from poky.conf? Or just plain copy the file? | 12:43 |
| zwerch | Can I just use the "poky-bleeding.conf" and copy it? | 12:47 |
| zwerch | And then simply set my DISTRO in the layer.conf? | 12:47 |
| milan_ | bluelightning: Does SSTATE_DISABLE="1" force all dependencies to be re-built ? | 12:52 |
| *** lamego <lamego!lamego@nat/intel/x-yjndrqdjsbgnqdmb> has joined #yocto | 12:56 | |
| *** pohmelie <pohmelie!bca2400e@gateway/web/freenode/ip.188.162.64.14> has joined #yocto | 12:58 | |
| bluelightning | milan_: I don't think it will no | 12:59 |
| bluelightning | zwerch: you can do either of those | 13:00 |
| bluelightning | zwerch: you may wish to read http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#creating-your-own-distribution | 13:00 |
| milan_ | ok | 13:00 |
| pohmelie | Hi, everyone! Where can I read documentation for matchbox? Where is config files, what can I config, etc… | 13:00 |
| zwerch | bluelightning: thanks! | 13:02 |
| *** fredcadete <fredcadete!d4a63893@gateway/web/freenode/ip.212.166.56.147> has joined #yocto | 13:02 | |
| zwerch | pohmelie: https://github.com/openembedded/openembedded-core/blob/master/meta/recipes-graphics/matchbox-wm/matchbox-wm_git.bb this is the recipe (or the one in of the branches), there is a homepage http://matchbox-project.org, you should be able to get some information there | 13:04 |
| pohmelie | zwerch: matchbox-project.org just a mirror for yocto page, which has no information I need. Recepie also have no information about configuring. | 13:07 |
| *** Nilesh_ <Nilesh_!~nilesh@27.107.59.71> has joined #yocto | 13:09 | |
| *** anselmolsm <anselmolsm!~anselmols@192.55.55.39> has joined #yocto | 13:10 | |
| *** aehs29 <aehs29!aehernan@nat/intel/x-wwqlcmmevswkocbz> has joined #yocto | 13:10 | |
| zwerch | pohmelie: you are right, sorry, but I could find a https://github.com/openembedded/openembedded-core/blob/master/meta/recipes-graphics/matchbox-wm/matchbox-wm/kbdconfig#L7 reference here, which was not helpful because it didn't load. But I found this, maybe it helps you: http://wiki.openmoko.org/wiki/Window_Manager_Startup | 13:11 |
| pohmelie | zwerch: thanks ;) | 13:15 |
| zwerch | pohmelie: but there seem not to be that many options :D | 13:16 |
| zwerch | pohmelie: http://manpages.ubuntu.com/manpages/lucid/man1/matchbox-window-manager.1.html | 13:16 |
| *** zecke <zecke!~ich@ip5b41fb99.dynamic.kabel-deutschland.de> has joined #yocto | 13:18 | |
| *** Aethenelle <Aethenelle!~Aethenell@166.175.189.230> has joined #yocto | 13:21 | |
| *** aehs29 <aehs29!aehernan@nat/intel/x-wwqlcmmevswkocbz> has quit IRC | 13:21 | |
| pohmelie | zwerch: Wow, it is just what I looking for! Great! | 13:22 |
| *** jku <jku!jku@nat/intel/x-pjhhztagohjezdcj> has quit IRC | 13:23 | |
| *** milan_ <milan_!~milan@111.93.218.67> has quit IRC | 13:28 | |
| *** ntl <ntl!~ntl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has joined #yocto | 13:35 | |
| *** Cardoe <Cardoe!~Cardoe@gentoo/developer/Cardoe> has joined #yocto | 13:40 | |
| *** smartin_ is now known as smartin | 13:45 | |
| *** scot <scot!~scot@130.164.62.160> has joined #yocto | 13:46 | |
| *** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-xqokecsrvqiwfewo> has joined #yocto | 13:48 | |
| *** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-xqokecsrvqiwfewo> has left #yocto | 13:52 | |
| *** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has quit IRC | 13:52 | |
| Cardoe | I’m wondering what the proper SRCREV and PV for a package is that’s from git but I’m trying to build an RC tag? | 13:53 |
| Cardoe | Do I use the commit-ish fully or the tag? | 13:53 |
| *** behanw <behanw!~behanw@205-214-226-20.static-ip.telepacific.net> has joined #yocto | 13:56 | |
| zwerch | Cardoe: if your recipe is named mypackage_git.bb it's correct | 14:00 |
| zwerch | Cardoe: more information on fetching code is here: http://www.yoctoproject.org/docs/1.8/dev-manual/dev-manual.html#new-recipe-fetching-code | 14:01 |
| bluelightning | Cardoe: http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#properly-versioning-pre-release-recipes | 14:02 |
| bluelightning | i.e. if you do use the RC version in PV, then do it in the manner described so that you don't get the version seemingly going backwards when you upgrade to the final release | 14:02 |
| *** aehs29 <aehs29!~aehernan@134.134.137.73> has joined #yocto | 14:03 | |
| bluelightning | Cardoe: also, use the full commit hash in SRCREV, and specify the branch it comes from in branch= in SRC_URI (if it's not a commit that's on master) | 14:03 |
| *** tsramos <tsramos!tsramos@nat/intel/x-yiriywtczspkqrhp> has joined #yocto | 14:03 | |
| Cardoe | It’s on master | 14:03 |
| Cardoe | I’m trying to clean up Xen in meta-virtualization | 14:03 |
| zwerch | Cardoe: you should not use master in production stuff | 14:04 |
| Cardoe | This isn’t for production. | 14:04 |
| zwerch | Cardoe: just saying ^^ | 14:04 |
| Cardoe | meta-virtualization has their xen_git.bb on some random Xen 4.4 master commit. | 14:04 |
| Cardoe | It has xen_4.5.0.bb as well | 14:04 |
| Cardoe | And then it has pulled out “common” bits into xen.inc | 14:04 |
| zwerch | You can also use ${AUTOREV} variable | 14:05 |
| Cardoe | I’m trying to get ready for Xen 4.6.0 to drop (its only at 4.6.0-rc1 right now) | 14:05 |
| bluelightning | zwerch: well, SRCREV = "${AUTOREV}" in a layer you publish for others is generally frowned upon | 14:06 |
| zwerch | bluelightning: I know, but he said it's not for production | 14:06 |
| bluelightning | zwerch: even so | 14:07 |
| Cardoe | Well I’m looking to update meta-virtualization’s xen_git.bb to be at least 4.6.0 | 14:09 |
| *** opennandra <opennandra!~marek@81.89.61.168.vnet.sk> has quit IRC | 14:12 | |
| Cardoe | bluelightning: thanks | 14:14 |
| *** madisox <madisox!~madison@64-71-1-115.static.wiline.com> has joined #yocto | 14:15 | |
| *** grma <grma!~gruberm@HSI-KBW-46-237-193-133.hsi.kabel-badenwuerttemberg.de> has quit IRC | 14:16 | |
| *** alimon <alimon!~alimon@134.134.137.73> has joined #yocto | 14:17 | |
| *** dcyrille18 <dcyrille18!59fb345d@gateway/web/freenode/ip.89.251.52.93> has joined #yocto | 14:21 | |
| dcyrille18 | Hi all ! I've got a problem with Yocto. The /sys/class/gpio directory, subdirectories and files have root:root owner:group with 744/644 rights. Do you now a way to change these for a user without use sudo. Or most simply, to add the gpio sysfs subdirectories on another group ? Thanks in advance. | 14:29 |
| *** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC | 14:32 | |
| zwerch | dcryille18: if you know which recipe is responsible for the directory (i assume one of the following http://layers.openembedded.org/layerindex/branch/master/recipes/?q=gpio) you can bbappend it and add a chroot or chmod to do_install_append() | 14:32 |
| *** hamis <hamis!~irfan@110.93.212.98> has quit IRC | 14:32 | |
| *** Aethenelle <Aethenelle!~Aethenell@166.175.189.230> has quit IRC | 14:32 | |
| *** pohmelie <pohmelie!bca2400e@gateway/web/freenode/ip.188.162.64.14> has quit IRC | 14:34 | |
| *** Nilesh_ <Nilesh_!~nilesh@27.107.59.71> has quit IRC | 14:38 | |
| bluelightning | zwerch: I don't think that's going to help, this will be something generated by a kernel driver | 14:40 |
| *** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-qjwdipnzvdwrloxh> has joined #yocto | 14:40 | |
| dcyrille18 | Yes, I've configured my kernel to add gpio on sysfs. But all rights are root and unexecutable by users. | 14:41 |
| *** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-qjwdipnzvdwrloxh> has left #yocto | 14:41 | |
| dcyrille18 | Do you known a way to add gpio sysfs directories on a dedicated group ? | 14:42 |
| bluelightning | I don't, if you're asking me | 14:43 |
| bluelightning | I suspect it's more of a generic Linux thing than specific to our system though | 14:43 |
| bluelightning | it's possible you might be able to do it through udev, but that's really more for /dev/ nodes even if it can match on sysfs nodes | 14:44 |
| *** frsc <frsc!~frsc@80.149.173.68> has quit IRC | 14:47 | |
| *** tasslehoff <tasslehoff!~Tasslehof@77.40.182.98> has quit IRC | 14:47 | |
| *** ka6sox is now known as zz_ka6sox | 14:48 | |
| *** zz_ka6sox is now known as Guest80885 | 14:49 | |
| dcyrille18 | Ok, thanks anyway :-/ | 14:51 |
| dcyrille18 | I'm regarding to use udev :) | 14:51 |
| *** belen1 <belen1!~Adium@192.198.151.43> has joined #yocto | 14:52 | |
| *** belen <belen!Adium@nat/intel/x-tylomatqeydrnfuc> has quit IRC | 14:53 | |
| *** afxez0r <afxez0r!~afxez0r@134.134.139.76> has joined #yocto | 14:57 | |
| *** zwerch <zwerch!~Adium@ip-178-200-96-248.hsi07.unitymediagroup.de> has left #yocto | 14:58 | |
| *** behanw <behanw!~behanw@205-214-226-20.static-ip.telepacific.net> has quit IRC | 14:58 | |
| *** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC | 15:00 | |
| *** 7GHAA056D <7GHAA056D!~quassel@p5797ED67.dip0.t-ipconnect.de> has joined #yocto | 15:04 | |
| *** armpit <armpit!~akuster@2601:202:4000:1239:e17c:4679:6483:8991> has joined #yocto | 15:05 | |
| *** belen1 <belen1!~Adium@192.198.151.43> has quit IRC | 15:35 | |
| *** sjolley <sjolley!sjolley@nat/intel/x-ryufbsaxmkbwfuon> has quit IRC | 15:40 | |
| *** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC | 15:43 | |
| *** dmoseley <dmoseley!~dmoseley@cpe-75-181-75-239.carolina.res.rr.com> has quit IRC | 15:45 | |
| *** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has joined #yocto | 15:45 | |
| *** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto | 15:46 | |
| *** psnsilva <psnsilva!~psnsilva@193-126-29-154.net.novis.pt> has quit IRC | 15:48 | |
| *** dmoseley <dmoseley!~dmoseley@cpe-75-181-75-239.carolina.res.rr.com> has joined #yocto | 15:56 | |
| *** tsramos_ <tsramos_!~tsramos@134.134.139.72> has joined #yocto | 15:56 | |
| *** moto_timo <moto_timo!~timo@mail2.trustautomation.com> has quit IRC | 15:56 | |
| *** sameo_ <sameo_!samuel@nat/intel/x-ihqgwwyllggzqjez> has quit IRC | 15:56 | |
| *** moto-timo <moto-timo!~timo@fsf/member/moto-timo> has joined #yocto | 15:57 | |
| *** tsramos <tsramos!tsramos@nat/intel/x-yiriywtczspkqrhp> has quit IRC | 15:58 | |
| *** afxez0r <afxez0r!~afxez0r@134.134.139.76> has quit IRC | 16:01 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 16:02 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 16:04 | |
| *** fredcadete <fredcadete!d4a63893@gateway/web/freenode/ip.212.166.56.147> has quit IRC | 16:09 | |
| *** behanw <behanw!~behanw@63.110.89.212> has joined #yocto | 16:09 | |
| *** sjolley <sjolley!sjolley@nat/intel/x-undyssthddcxxdbv> has joined #yocto | 16:10 | |
| *** afxez0r <afxez0r!~afxez0r@134.134.139.74> has joined #yocto | 16:19 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto | 16:20 | |
| *** jonathanmaw <jonathanmaw!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has quit IRC | 16:22 | |
| *** grma <grma!~gruberm@HSI-KBW-46-237-193-133.hsi.kabel-badenwuerttemberg.de> has joined #yocto | 16:25 | |
| *** dfaught <dfaught!~dfaught@cpe-70-119-105-90.tx.res.rr.com> has joined #yocto | 16:26 | |
| *** TobSnyder <TobSnyder!~schneider@ip923450f2.dynamic.kabel-deutschland.de> has quit IRC | 16:26 | |
| rburton | khem: your six patch series to oe-core over the weekend appears to be missing part 2. is it in a branch somewhere? | 16:31 |
| *** madisox <madisox!~madison@64-71-1-115.static.wiline.com> has quit IRC | 16:36 | |
| *** madisox <madisox!~madison@64-71-1-115.static.wiline.com> has joined #yocto | 16:36 | |
| *** madisox <madisox!~madison@64-71-1-115.static.wiline.com> has quit IRC | 16:43 | |
| *** roccof <roccof!~rocco@93-51-177-218.ip268.fastwebnet.it> has quit IRC | 16:43 | |
| *** behanw <behanw!~behanw@63.110.89.212> has quit IRC | 16:46 | |
| *** vdehors <vdehors!~vincent@LAubervilliers-656-1-235-184.w193-248.abo.wanadoo.fr> has quit IRC | 16:47 | |
| *** ant__ <ant__!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has quit IRC | 16:52 | |
| *** afxez0r <afxez0r!~afxez0r@134.134.139.74> has quit IRC | 16:54 | |
| *** afxez0r <afxez0r!~afxez0r@134.134.139.74> has joined #yocto | 16:58 | |
| *** jbrianceau is now known as jbrianceau_away | 17:00 | |
| *** tsramos_ <tsramos_!~tsramos@134.134.139.72> has quit IRC | 17:02 | |
| *** tsramos <tsramos!tsramos@nat/intel/x-aauwyjtqkpsuuysh> has joined #yocto | 17:03 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 17:04 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 17:05 | |
| *** challinan <challinan!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has quit IRC | 17:05 | |
| *** belen1 <belen1!Adium@nat/intel/x-ucqeoflnktfxmzbb> has joined #yocto | 17:06 | |
| *** challinan <challinan!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has joined #yocto | 17:07 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC | 17:10 | |
| *** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto | 17:10 | |
| *** belen1 <belen1!Adium@nat/intel/x-ucqeoflnktfxmzbb> has quit IRC | 17:13 | |
| *** radzy <radzy!~radzy@unknown-216-78.windriver.com> has quit IRC | 17:23 | |
| *** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has quit IRC | 17:23 | |
| *** [Sno] <[Sno]!~sno@rademacherexchange.de> has quit IRC | 17:24 | |
| *** radzy_lunch <radzy_lunch!~radzy@unknown-216-78.windriver.com> has joined #yocto | 17:27 | |
| *** radzy_lunch is now known as radzy | 17:27 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 17:29 | |
| *** paulg_ <paulg_!~paulg@128.224.252.2> has quit IRC | 17:54 | |
| *** benjamirc <benjamirc!~besquive@134.134.139.70> has joined #yocto | 17:59 | |
| *** sameo_ <sameo_!~samuel@192.55.54.40> has joined #yocto | 18:02 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC | 18:03 | |
| *** varibull <varibull!~varibull@ta.tainstruments.com> has joined #yocto | 18:05 | |
| *** varibull <varibull!~varibull@ta.tainstruments.com> has joined #yocto | 18:05 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 18:06 | |
| *** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto | 18:08 | |
| *** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has quit IRC | 18:11 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC | 18:20 | |
| fishey1 | bitbake issue: I'm using the gitsm fetcher with the same URL in a number of different .bb files. Every now and then, all of the fetches of that gitsm url appear to fail in the bitbake code around where .gitmodules is retrieved | 18:22 |
| fishey1 | It looks like a simple race: we move the git repo to grab .gitmodules, but at the same time others are trying to do similar things | 18:22 |
| fishey1 | so the question: Is there a locking mechanism I can use in the gitsm fetcher to fix this? | 18:23 |
| *** sameo_ <sameo_!~samuel@192.55.54.40> has quit IRC | 18:30 | |
| *** grma <grma!~gruberm@HSI-KBW-46-237-193-133.hsi.kabel-badenwuerttemberg.de> has quit IRC | 18:31 | |
| *** khem` <khem`!~khem@unaffiliated/khem> has quit IRC | 18:38 | |
| *** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC | 19:01 | |
| *** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto | 19:01 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 19:02 | |
| *** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-rkawyngncmkhwkiq> has quit IRC | 19:06 | |
| *** pohly <pohly!~pohly@p57A56DBD.dip0.t-ipconnect.de> has quit IRC | 19:10 | |
| -YoctoAutoBuilder- build #10 of nightly-wic is complete: Failure [failed BuildImages CreateWicImages CreateWicImages_1 BuildImages_2 CreateWicImages_2 CreateWicImages_3] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-wic/builds/10 | 19:11 | |
| *** paulg <paulg!~paulg@72.1.195.9> has joined #yocto | 19:16 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 19:17 | |
| *** paulg <paulg!~paulg@72.1.195.9> has quit IRC | 19:20 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 19:20 | |
| *** paulg <paulg!~paulg@72.1.195.9> has joined #yocto | 19:22 | |
| *** rburton1 <rburton1!~Adium@35.106.2.81.in-addr.arpa> has joined #yocto | 19:22 | |
| *** rburton <rburton!~Adium@35.106.2.81.in-addr.arpa> has quit IRC | 19:23 | |
| Cardoe | So this might be a weird request but is it possible to include an image within an image? | 19:32 |
| Cardoe | Exact use case is for Xen. Building up a domU that’s then placed inside the dom0 so that I can boot the domU on startup. | 19:33 |
| *** [Sno] <[Sno]!~sno@p578b540c.dip0.t-ipconnect.de> has joined #yocto | 19:36 | |
| khem | rburton1: hmm | 19:38 |
| khem | let me push them to a branch for ease of use | 19:39 |
| *** [Sno] <[Sno]!~sno@p578b540c.dip0.t-ipconnect.de> has quit IRC | 19:41 | |
| rburton1 | Cardoe: that's exactly what hddimgs are, so yes | 19:42 |
| Cardoe | rburton1: | 19:42 |
| *** [Sno] <[Sno]!~sno@p578b540c.dip0.t-ipconnect.de> has joined #yocto | 19:42 | |
| Cardoe | So I’m building up 2 but I’m not sure how to include one wholesale into another one | 19:42 |
| rburton1 | make one image depends on the other image's do_deploy task | 19:43 |
| Cardoe | ah | 19:43 |
| rburton1 | then during generation you copy the image from deploy dir into the other's image's staging directory | 19:43 |
| Cardoe | ok that makes sense | 19:43 |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 19:44 | |
| khem | rburton1: http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/for-master | 19:44 |
| khem | I have few more patches in there as well. | 19:44 |
| rburton1 | thanks khem | 19:44 |
| khem | but thats the current list I would like to consider for master | 19:45 |
| rburton1 | khem: can you send the new ones to the list? | 19:48 |
| khem | OK, I will create a pull request | 19:49 |
| khem | that will be easy | 19:49 |
| *** jimBaxter <jimBaxter!~jbaxter@jimbax.plus.com> has quit IRC | 19:53 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC | 19:56 | |
| kergoth | Does it annoy anyone else that we have a boneblack machine in three different layers? | 20:10 |
| kergoth | er, beaglebone machine, that is | 20:13 |
| *** zecke <zecke!~ich@ip5b41fb99.dynamic.kabel-deutschland.de> has quit IRC | 20:22 | |
| * armpit should have one layer to bind them all | 20:27 | |
| *** jukkar2_ <jukkar2_!~sailfish@a91-152-83-56.elisa-laajakaista.fi> has joined #yocto | 20:34 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto | 20:34 | |
| fishey1 | armpit: "build them all" | 20:35 |
| *** jukkar2_ <jukkar2_!~sailfish@a91-152-83-56.elisa-laajakaista.fi> has quit IRC | 20:37 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC | 20:39 | |
| khem | kergoth: it does | 21:04 |
| khem | kergoth: meta-bb is quite different it has cape support and many users still use it especially angstrom users | 21:05 |
| kergoth | huh, meta-ti doesnt' have cape support? | 21:06 |
| khem | kergoth: jason was to work on upstreaming that to kernel if it has happened then meta-bb wouldnt exist | 21:06 |
| khem | AFAIK no | 21:06 |
| khem | and meta-yocto-bsp is just trying to be BSP independent layer | 21:06 |
| khem | or rather vendor independent | 21:06 |
| khem | not particularly pretty | 21:08 |
| gholms | nerdboy: Oh, right, I was supposed to remind you about building a trimslice BSP. Should we save that for the next hackfest/demo/whatever? | 21:09 |
| khem | I think it would be ideal if it picked machines that are fully supported in upstream components e.g. kernel toolchaine etc. and graphics too | 21:09 |
| khem | its possible for x86 only as of now reliably | 21:09 |
| kergoth | hmm, that does seem odd, i'd think meta-yocto-bsp would be machines that are either 100% upstream, or machines whose vendors aren't directly supporting them themselves | 21:09 |
| khem | right | 21:10 |
| kergoth | otherwise it's too easy to be out of sync, and add confusion | 21:10 |
| khem | may be meta-ti should just drop it | 21:10 |
| khem | but then binary graphics drivers :) | 21:10 |
| khem | ideally we shouldnt even need linux-yocto as core kernel | 21:11 |
| *** paulg <paulg!~paulg@72.1.195.9> has quit IRC | 21:11 | |
| khem | only emulators supported upstream | 21:12 |
| khem | and some reference machines | 21:12 |
| -YoctoAutoBuilder- build #448 of nightly-rpm is complete: Failure [failed Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-rpm/builds/448 | 21:12 | |
| * kergoth nods | 21:12 | |
| denix | kergoth: correct, meta-ti doesn't have cape support - it is coming from upstream with 4.1/4.2 | 21:12 |
| khem | linux-yocto has advantage for certain vendors which is a skew imo | 21:12 |
| kergoth | hmmm | 21:13 |
| *** rburton1 <rburton1!~Adium@35.106.2.81.in-addr.arpa> has quit IRC | 21:13 | |
| denix | kergoth: and meta-yocto-bsp is indeed the reference bsp with everything that is already upstream, at least for beaglebone | 21:13 |
| khem | denix: it adds to confusion why meta-ti should also have it | 21:13 |
| denix | khem: should also have it what? | 21:14 |
| khem | bbb | 21:15 |
| *** paulg <paulg!~paulg@72.1.195.9> has joined #yocto | 21:15 | |
| denix | kergoth: reading a bit earlier - why do you say 3 layers? I only know 2 | 21:16 |
| kergoth | meta-ti, meta-beagleboard, and meta-yocto-bsp | 21:16 |
| denix | meta-beagleboard is long since dead | 21:16 |
| khem | if cape support is coming to 4.1 then meta-bb might be able to drop it | 21:16 |
| kergoth | nothing indicates this | 21:16 |
| kergoth | not hte readme, not the layer descriptions, nothing | 21:16 |
| kergoth | if htey're obsolete, someone should mention it | 21:16 |
| khem | its still used in angstrom | 21:17 |
| khem | for cape support reasons | 21:17 |
| denix | kergoth: this question is being raised every year and nothing changes | 21:17 |
| moto-timo | I have dim hope of getting meta-beagleboard up to date, but beagleboard.org moved on to debian | 21:17 |
| denix | kergoth: https://github.com/beagleboard/meta-beagleboard - last commit was in 2013 | 21:18 |
| moto-timo | at least koen has been doing _some_ updates to angstrom | 21:19 |
| denix | the only point of meta-bb was to carry over cape support from when it was initially developed for 3.2/3.8 until it accepted upstream. | 21:19 |
| denix | nobody estimated it would take that long, but it finally happened | 21:19 |
| moto-timo | +1 | 21:19 |
| denix | so, there's no reason to keep on dragging it further | 21:20 |
| khem | if it has landed in 4.1 upstream then I agree | 21:21 |
| -YoctoAutoBuilder- build #112 of nightly-arm64 is complete: Failure [failed BuildImages Running Sanity Tests Building Toolchain Images Building Toolchain Images_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm64/builds/112 | 21:22 | |
| *** ant_home <ant_home!~ant__@host167-191-dynamic.52-82-r.retail.telecomitalia.it> has joined #yocto | 21:23 | |
| denix | cape support is rather very unorthodox... | 21:23 |
| khem | there were large set of users of it so you just couldnt throw it out | 21:25 |
| denix | well, many peripherals on modern SOCs are unusual, really, with all the accelerators, engines and other heterogeneous cores... | 21:25 |
| denix | but, CircuitCo/koen picked up cape support and the rest was picked up by TI... | 21:27 |
| denix | since then panto continued working to get it upstream, which is pretty much there with 4.1/4.2 | 21:28 |
| denix | and TI also contributed a lot to upstream, that's why meta-yocto-bsp can do basic BBB support from pure mainline | 21:28 |
| khem | yes, however, it would be good if we could really pick up ko kernel and build it | 21:29 |
| khem | for ref BSP | 21:29 |
| denix | khem: and why you can't? | 21:30 |
| khem | you can, I am talking about recipes from meta-yocto-bsp | 21:30 |
| khem | same for qemu machines in OE-Core | 21:31 |
| denix | khem: meta-yocto-bsp does use pure ko kernel at least for bbb | 21:31 |
| khem | isnt it linux-yocto ? | 21:31 |
| fray | as far as I understand it, you can do that in master (or if not yet, will be able to soon) | 21:31 |
| denix | khem: at least that's what I pushed back in 3.14 days - it was pure mainline | 21:32 |
| khem | thats good | 21:32 |
| fray | master has the metadata (config fragments) and constructed linux-yocto separated.. so they can be used independently | 21:32 |
| denix | khem: linux-yocto is just a wrapper | 21:32 |
| fray | and linux-yocto is pretty much KO.. | 21:32 |
| khem | I was talking to some kernel devs at plumbers and they said linux yocto was a fork | 21:32 |
| fray | it's like anything else.. KO + patches.. | 21:32 |
| fray | but the patches are targeted to boards, features, etc.. | 21:33 |
| khem | but if its ko/linux-stable thats good to hear | 21:33 |
| fray | if you don't want hte patches you don't need them | 21:33 |
| fray | it's LTSI AFAIK | 21:33 |
| denix | khem: different machines can add patches in linux-yocto, but in 1.6 there were no patches for bbb | 21:33 |
| khem | denix: thats what I was eluding too | 21:33 |
| fray | denix, that matches my understanding.. | 21:33 |
| khem | build ko kernel w/o patching | 21:34 |
| khem | which is true upstream | 21:34 |
| fray | yes.. and separating the metadata (kernel config) and the kernel source in (again I think master) allows that | 21:34 |
| ant_home | in my little experience, there is a long way to go in order to convince joe kernel developer to use linux-yocto | 21:34 |
| fray | it just means if you try to enable kernel configs that don't exist upstream you get stopped | 21:34 |
| ant_home | I had to revert back to ko, back on popular request :/ | 21:34 |
| khem | ant_home: they dont bother unless you talk ko | 21:34 |
| denix | khem: it does no patches for bbb. but linux-yocto wrapper was the requirement for oe-core/meta-yocto-bsp | 21:35 |
| fray | ant_home, the issue is most developers don't support 1000 combinations.. so they don't see the immediate need that is solved | 21:35 |
| kergoth | afaik linux-yocto's main advantage is maintainance of multiple bsps in a single tree with support for flowing common changes into them all. i've seen similar tools developed internally at companies. so your average developer probably *wouldnt'* see the ned | 21:35 |
| fray | (and I'm not kidding when I talk about 1000 or more combinations) | 21:35 |
| khem | fray: OE doesnt do that either | 21:35 |
| ant_home | honestly I can only talk about old unsupported hw, maybe for new stuff it is different | 21:36 |
| khem | it enables someone to doso | 21:36 |
| kergoth | but for companies stuck on the bsp treadmill, such things are useful | 21:36 |
| denix | khem: and due to linux-yocto complexity I had to add linux-mainline recipe, but I fail to update it regularly... :) | 21:36 |
| khem | doesnt mean it should be default | 21:36 |
| khem | I was bantered by every dev to whomeever I said to use linux yocto | 21:36 |
| fray | denix, then have a conversation with all of the board manufacturers out there and tell them to start working upstream.. :P | 21:36 |
| ant_home | the risk with linux-yocto is to get stale .bbappend...it happened to me twice... | 21:37 |
| fray | I don't think the KO developers understand that it's KO + patches.. what they often think is that it's a hacked up kernel.. | 21:37 |
| khem | fray: they dont want to | 21:37 |
| fray | ant_home, that is why the recommended method is reference clones.. | 21:37 |
| kergoth | i don't think those two are mutually exclusive. KO + patches can be pretty hacked up, dependign on what those patches are up to | 21:38 |
| ant_home | the you loose the updates... | 21:38 |
| fray | khem, thats fine.. and part of the reason the metadata was split form the kernel sources | 21:38 |
| khem | for reference machines we should just have ko I am convinced | 21:38 |
| fray | kergoth, I consider the end results to be possibly hacked up.. but it's a lot cleaner way to handle it | 21:38 |
| kergoth | agreed. | 21:38 |
| fray | you can at least see and unwind the hacks.. vs a lot of the board vendor kernels which are just tarballs of crap | 21:38 |
| khem | some even did not trust out UAPIs | 21:38 |
| khem | who knows how OE patches the kernel UAPIs | 21:39 |
| khem | was the response | 21:39 |
| fray | git log | 21:39 |
| fray | :) | 21:39 |
| fray | part of the reason that it was done the way it was.. make things transparent to anyone who can use git | 21:39 |
| fray | vs .. "tarball of crap" | 21:39 |
| khem | kergoth: I see linux-yocto is good for OSVs or platform folks thats ok | 21:41 |
| khem | but ODMs dont have 1000 machines | 21:42 |
| fray | khem, customers I've talked to that work with more then 1 platform on a common base.. they really like it | 21:42 |
| khem | they usally have 2 to 4 | 21:42 |
| khem | fray that base could be linux-stable | 21:42 |
| fray | These are customers who make common 'software' for usually 2-10 different boards... (often different architectures) | 21:42 |
| khem | yes I am in same boat | 21:42 |
| fray | but for the guys working on a project with -1- board.. they don't like the overhead.. until they understand that the configuration patching is useful.. | 21:42 |
| fray | but usually they "get" it after the project is nearly done and they are down chasing problems in patches or trying to resync | 21:43 |
| ant_home | the benefits of kern-tools and config checks are out of discussion. The 'dark' part are the common patches, not immediate to find (I was told so) | 21:45 |
| -YoctoAutoBuilder- build #441 of nightly-deb is complete: Failure [failed Running Sanity Tests Running Sanity Tests_1 Running Sanity Tests_2] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/441 | 21:46 | |
| fray | well the common base is KO for all.. but with that said, the split of meta-data and source should be making it easier to see.. | 21:46 |
| fray | before being intermingled had the effect of confusing people cause they saw a branch and thought it was the whole tree.. where it was just a fragment | 21:46 |
| ant_home | so in the end I don't dare to send patches upstream based on linux-yocto... | 21:47 |
| fray | I don't think anyone has ever said linux-yocto should be the basis of KO work | 21:47 |
| ant_home | not only for linux-next, even for stable | 21:48 |
| seebs | So I have new-pseudo probably ready for more thorough testing. I am sort of going to recommend that we NOT enable the extended attribute database code by default yet, but it might be a good bet for autobuilds. I'd want a lot more burn-in time before using it in production. | 21:48 |
| khem | with raspbian's success on rpi I still think cross compiling is still a voodoo and no matter how slow the machine is people still like feed based distros | 21:50 |
| fray | well I don't think it's voodoo, but I know some people do.. | 21:50 |
| fray | and feed based distros can easily be done with OE | 21:50 |
| ant_home | fray, in the case of new devices, with more than 1-2 active developers, it probably does make sense to invest in linux-yocto :) | 21:50 |
| khem | fray: it should be possible for upstream work | 21:50 |
| fray | (if my talk had been accepted, I'd have talked about it at ELC) | 21:50 |
| khem | OE is at that point where it should start fixing packages upstream | 21:51 |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 21:51 | |
| fray | khem, that was the point of the upstream-status.. but frankly the resources to "force" it up is not there.. | 21:51 |
| fray | and often the stuff is ignored by upstream (still) because they just don't care | 21:51 |
| kergoth | or it's not even maintained anymore | 21:52 |
| kergoth | heh | 21:52 |
| fray | ya that too | 21:52 |
| fray | but reality is that people try.. but once you 'try' once.. things fall away quickly | 21:52 |
| fray | it's the laziness factor.. it's easier to contribute to OE then 1000 upstream projects.. | 21:52 |
| fray | and with there being realistically only about a dozen maintainers within the OE world.. it's hard to convince people to contribute back to the 1000 upstreams | 21:53 |
| kergoth | I should do a better job of it. I can't push stuff during crunch time, but when we work on a new release and i start pushing my backlog up to oe-core, i should push more direct to upstream at that time | 21:53 |
| fray | I don't mean for that to be an excuse, just reality.. something we need to keep working to improve.. (yocto project and OE) | 21:53 |
| fray | kergoth, thats what our guys are told to do.. | 21:53 |
| khem | if we really have to improve on quality then this should be must, sometimes upstreams fixes the issues properly for things which we carry patches which may be workarounds etc. | 21:54 |
| fray | -everything- goes to OE, no exceptions.. upstream (above OE) when there is time.. exceptions being bintuils/gcc/kernel.. those always go back (if applicable) | 21:54 |
| ant_home | happily now and then it just happens upstream devs are lured by some OE patches and get interested in OE | 21:54 |
| kergoth | we occasionally carry something through multiple releases, but it's usually when we know it belongs in oe-core, but it has to be completely reworked to be suitable there, so the hack stays local for a while | 21:55 |
| khem | I think devtool will help in component development and upstreaming effort | 21:55 |
| kergoth | heh | 21:55 |
| kergoth | devtool modify -x is pretty sweet | 21:55 |
| fray | devtool stuff is still on my TODO list.. :/ | 21:55 |
| * kergoth devtool create-workspace; recipetool kernel_set_configs workspace CONFIG_USB_G_MULTI_CDC=y; bitbake virtual/kernel | 21:55 | |
| denix | +1 | 21:56 |
| khem | kergoth: why recipetool is not a subsystem of devtool ? | 21:56 |
| kergoth | not sure, paul would be the one to ask about the separation | 21:57 |
| *** dfaught <dfaught!~dfaught@cpe-70-119-105-90.tx.res.rr.com> has quit IRC | 21:58 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC | 22:00 | |
| *** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC | 22:01 | |
| *** fmeerkoetter <fmeerkoetter!~quassel@service.basyskom.com> has quit IRC | 22:01 | |
| *** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto | 22:01 | |
| *** fmeerkoetter <fmeerkoetter!~quassel@service.basyskom.com> has joined #yocto | 22:01 | |
| ant_home | khem: btw, about glibc, it seems buildroot carries some mips patches (not upstreamed) so that the two fine developers I'm trying to convert to OE/Yocto are still hesitating | 22:01 |
| khem | OK which ones | 22:03 |
| khem | we can convert them | 22:03 |
| ant_home | MXU simd | 22:03 |
| ant_home | also binutils iirc | 22:04 |
| fray | I think the real question is what do the patches do, what cores do they affect.. :) | 22:04 |
| ant_home | best would be someone from Imgtek jump in... | 22:04 |
| fray | I've seen some really nasty glibc patches in some other systems I'd hesitate to generically include | 22:04 |
| *** sameo_ <sameo_!samuel@nat/intel/x-txmmqtrdwrfidbvw> has joined #yocto | 22:05 | |
| fray | (I'm thinking of some "not to be named" vendor who makes a certain SDK... <shudder>) breaking gcc behavior to eek out a slightly better artificial benchmark is a BAD way to go about life | 22:05 |
| fray | what you want predictable sign extensions?! na.. | 22:06 |
| kergoth | yikes | 22:11 |
| *** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto | 22:11 | |
| *** dmoseley <dmoseley!~dmoseley@cpe-75-181-75-239.carolina.res.rr.com> has quit IRC | 22:12 | |
| *** Cardoe <Cardoe!~Cardoe@gentoo/developer/Cardoe> has quit IRC | 22:12 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 22:13 | |
| *** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC | 22:19 | |
| *** nighty^ <nighty^!~nighty@hokuriku.rural-networks.com> has quit IRC | 22:21 | |
| *** tsramos_ <tsramos_!tsramos@nat/intel/x-zutjointknbvskki> has joined #yocto | 22:25 | |
| *** tsramos <tsramos!tsramos@nat/intel/x-aauwyjtqkpsuuysh> has quit IRC | 22:28 | |
| *** lamego <lamego!lamego@nat/intel/x-yjndrqdjsbgnqdmb> has quit IRC | 22:29 | |
| *** tsramos_ <tsramos_!tsramos@nat/intel/x-zutjointknbvskki> has quit IRC | 22:30 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto | 22:31 | |
| *** paulg <paulg!~paulg@72.1.195.9> has quit IRC | 22:31 | |
| kergoth | Anyone feel like poking at https://github.com/openembedded/bitbake/compare/openembedded:master...kergoth:shallow-git-mirror-tarballs ? I could use testers other than myself to check sanity | 22:33 |
| *** paulg <paulg!~paulg@72.1.195.9> has joined #yocto | 22:35 | |
| *** aehs29 <aehs29!~aehernan@134.134.137.73> has quit IRC | 22:37 | |
| -YoctoAutoBuilder- build #450 of nightly-qa-extras is complete: Failure [failed Running Sanity Tests BuildImages_1 Running Sanity Tests_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-extras/builds/450 | 22:38 | |
| *** aehs29 <aehs29!~aehernan@134.134.137.73> has joined #yocto | 22:39 | |
| *** adelcast <adelcast!~adelcast@130.164.62.82> has quit IRC | 22:41 | |
| *** adelcast <adelcast!~adelcast@130.164.62.82> has joined #yocto | 22:44 | |
| *** Aethenelle <Aethenelle!~Aethenell@199.15.128.78> has joined #yocto | 22:50 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 22:52 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 22:53 | |
| kergoth | hmm, i should probably split the general bb.fetch bugfixes from the git shallow support for easier review | 22:57 |
| * armpit knows Frey's SDK woes too well | 22:57 | |
| *** sgw_ <sgw_!~sgw_@c-73-164-210-189.hsd1.or.comcast.net> has quit IRC | 23:03 | |
| ntl | $ git diff --shortstat v4.1.6...linux-yocto-4.1/standard/base | 23:03 |
| ntl | 271 files changed, 61963 insertions(+), 96 deletions(-) | 23:03 |
| ntl | that's a fork :) | 23:04 |
| *** Cardoe <Cardoe!~Cardoe@gentoo/developer/Cardoe> has joined #yocto | 23:15 | |
| *** Cardoe <Cardoe!~Cardoe@gentoo/developer/Cardoe> has quit IRC | 23:21 | |
| *** Cardoe <Cardoe!~Cardoe@gentoo/developer/Cardoe> has joined #yocto | 23:22 | |
| *** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto | 23:27 | |
| *** Aethenelle <Aethenelle!~Aethenell@199.15.128.78> has quit IRC | 23:28 | |
| kergoth | ntl: heh, indeed, that does seem substantial | 23:30 |
| kergoth | Hmm, wonder if we should switch to tar.xz or something for the git mirror tarballs eventually, though we'd need my multiple-mirror-tarball-support patch for compatibility | 23:31 |
| -YoctoAutoBuilder- build #449 of nightly-intel-gpl is complete: Failure [failed BuildImages BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-intel-gpl/builds/449 | 23:32 | |
| *** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC | 23:32 | |
| *** Cardoe <Cardoe!~Cardoe@gentoo/developer/Cardoe> has quit IRC | 23:33 | |
| *** sgw_ <sgw_!~sgw_@c-73-164-210-189.hsd1.or.comcast.net> has joined #yocto | 23:40 | |
| *** paulg <paulg!~paulg@72.1.195.9> has quit IRC | 23:42 | |
| kergoth | thoughts on https://github.com/MentorEmbedded/meta-mentor/commit/b058cda ? | 23:46 |
| -YoctoAutoBuilder- build #456 of nightly-qa-pam is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-pam/builds/456 | 23:48 | |
| *** sjolley <sjolley!sjolley@nat/intel/x-undyssthddcxxdbv> has quit IRC | 23:49 | |
| -YoctoAutoBuilder- build #451 of nightly-qa-extras is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-extras/builds/451 | 23:52 | |
| kergoth | hmm, afaict bitbake-whatchanged no longer works, at least it's not very effective. it changes STAMPS_DIR, but STAMPS_DIR is in some task signatures now. | 23:54 |
| * kergoth looks into what's pulling it in | 23:54 | |
| *** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto | 23:55 | |
| khem | bazel.io is pretty neat, | 23:56 |
| kergoth | runtaskdeps changed from ['dbdb_6.0.30.bb.do_configure:virtual:native'] to ['dbdb_6.0.30.bb.do_configure:virtual:native'] ... seriously, bitbake? | 23:57 |
| kergoth | RP: runtaskdeps changed from ['dbdb_6.0.30.bb.do_configure:virtual:native'] to ['dbdb_6.0.30.bb.do_configure:virtual:native'] in -S printdiff. | 23:57 |
| -YoctoAutoBuilder- build #11 of nightly-wic is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-wic/builds/11 | 23:59 | |
| -YoctoAutoBuilder- build #454 of nightly-qa-logrotate is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-logrotate/builds/454 | 23:59 | |
Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!