| *** nslu2-log <nslu2-log!~nslu2-log@leia.nas-admin.org> has quit IRC | 00:01 | |
| *** nslu2-log_ <nslu2-log_!~nslu2-log@milla.nas-admin.org> has quit IRC | 00:02 | |
| *** zkrx <zkrx!~slimshady@adsl-89-217-237-59.adslplus.ch> has quit IRC | 00:06 | |
| *** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has quit IRC | 00:07 | |
| *** zkrx <zkrx!~slimshady@adsl-89-217-237-59.adslplus.ch> has joined #yocto | 00:26 | |
| opello | hi, i'm trying to use some older layers with a newer poky release, and am having a few problems with the kernel and u-boot recipes being vendor provided and older, such that i'm trying to say RPROVIDES_u-boot-mkimage += "u-boot-tools" which doing that (and -native versions) complainx about virtual/kernel having an unmet dependency (nothing PROVIDES u-boot-tools-native, u-boot-mkimage-native RPROVIDES u-boot-tools-native)... but apparently ... | 00:30 |
|---|---|---|
| opello | ... that's insufficient? | 00:30 |
| opello | complains* even | 00:31 |
| *** bps <bps!~bps@80.71.142.18> has quit IRC | 00:32 | |
| *** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-zvyiwhliltdzelbm> has quit IRC | 00:41 | |
| *** tedfernau <tedfernau!~tedfernau@c-76-104-226-12.hsd1.wa.comcast.net> has quit IRC | 00:45 | |
| *** leon-anavi <leon-anavi!~Leon@78.130.197.211> has quit IRC | 01:03 | |
| *** bobo <bobo!~bobo@customer-145-14-101-3.stosn.net> has quit IRC | 01:14 | |
| *** ssajal <ssajal!~ssajal@bras-base-otwaon0147w-grc-11-70-48-65-11.dsl.bell.ca> has quit IRC | 01:14 | |
| *** sakoman <sakoman!~steve@72.173.249.164> has quit IRC | 02:40 | |
| *** kaspter <kaspter!~Instantbi@27.39.124.200> has joined #yocto | 03:06 | |
| *** ahadi <ahadi!~ahadi@i5E86AEAF.versanet.de> has quit IRC | 03:06 | |
| *** ahadi <ahadi!~ahadi@i59F44DAA.versanet.de> has joined #yocto | 03:13 | |
| *** itseris <itseris!~itseris@d154-5-56-162.bchsia.telus.net> has joined #yocto | 03:26 | |
| *** fatalhalt <fatalhalt!~fatalhalt@2601:244:4d01:52df:225:90ff:feda:2428> has joined #yocto | 04:06 | |
| *** Kyubi <Kyubi!~Kyubi@149.199.62.129> has quit IRC | 04:50 | |
| yates | RobertBerger: you're on! | 04:55 |
| *** Kyubi <Kyubi!~Kyubi@149.199.62.129> has joined #yocto | 05:03 | |
| *** jobroe <jobroe!~manjaro-u@p579ebafa.dip0.t-ipconnect.de> has joined #yocto | 05:28 | |
| *** beneth <beneth!~beneth@irc.beneth.fr> has joined #yocto | 05:30 | |
| *** JaMa <JaMa!~martin@ip-109-238-218-228.aim-net.cz> has quit IRC | 05:31 | |
| *** dreyna <dreyna!~dreyna@2601:646:4201:e280:508e:5d7f:90be:919f> has quit IRC | 05:34 | |
| *** JaMa <JaMa!~martin@ip-109-238-218-228.aim-net.cz> has joined #yocto | 05:34 | |
| *** JosephAntony <JosephAntony!a5e10863@165.225.8.99> has joined #yocto | 06:11 | |
| *** kpo_ <kpo_!~kpo@bwu34.internetdsl.tpnet.pl> has quit IRC | 06:12 | |
| *** kpo_ <kpo_!~kpo@bwu34.internetdsl.tpnet.pl> has joined #yocto | 06:13 | |
| *** AndersD <AndersD!~AndersD@h83-209-96-136.cust.a3fiber.se> has joined #yocto | 06:31 | |
| *** bobo <bobo!~bobo@customer-145-14-101-3.stosn.net> has joined #yocto | 06:45 | |
| *** agust <agust!~agust@p508b6964.dip0.t-ipconnect.de> has joined #yocto | 06:47 | |
| *** ENPJ <ENPJ!~ENPJ@2001:a61:3a33:7901:6de9:a24b:3d4e:f73b> has joined #yocto | 06:57 | |
| *** ThomasD13 <ThomasD13!~thomas@DSL01.212.114.255.148.ip-pool.NEFkom.net> has joined #yocto | 07:01 | |
| *** jobroe <jobroe!~manjaro-u@p579ebafa.dip0.t-ipconnect.de> has quit IRC | 07:03 | |
| *** B0ned1ger2 <B0ned1ger2!~B0ned1ger@82-135-139-249.static.zebra.lt> has joined #yocto | 07:06 | |
| *** jobroe <jobroe!~manjaro-u@p579ebafa.dip0.t-ipconnect.de> has joined #yocto | 07:07 | |
| *** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto | 07:17 | |
| *** bobo <bobo!~bobo@customer-145-14-101-3.stosn.net> has quit IRC | 07:27 | |
| *** alexlarsson <alexlarsson!~alexl@c-31a4e255.022-110-73746f36.bbcust.telenor.se> has joined #yocto | 07:32 | |
| *** mckoan|away is now known as mckoan | 07:36 | |
| mckoan | good morning | 07:36 |
| hmw1 | good morning | 07:40 |
| *** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has joined #yocto | 07:53 | |
| *** hpsy <hpsy!~hpsy@2c0f:fc89:8022:9245:a4e0:cdd5:31f8:b108> has joined #yocto | 08:19 | |
| *** yannholo <yannholo!~yannholo@fs-141-0-205-41.fullsave.info> has joined #yocto | 08:19 | |
| *** Yumasi <Yumasi!~guillaume@2a01:e0a:5cb:4430:71ee:168f:367c:6d70> has joined #yocto | 08:30 | |
| *** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has quit IRC | 08:30 | |
| *** fl0v0 <fl0v0!~fvo@89.244.121.59> has joined #yocto | 08:34 | |
| *** kpo_ <kpo_!~kpo@bwu34.internetdsl.tpnet.pl> has quit IRC | 08:36 | |
| *** kpo_ <kpo_!~kpo@bwu34.internetdsl.tpnet.pl> has joined #yocto | 08:37 | |
| *** hpsy <hpsy!~hpsy@2c0f:fc89:8022:9245:a4e0:cdd5:31f8:b108> has quit IRC | 08:45 | |
| *** rubdos <rubdos!~rubdos@2a02:578:859d:700:8b44:5716:382d:a7da> has quit IRC | 08:49 | |
| *** rubdos <rubdos!~rubdos@2a02:578:859d:700:8b44:5716:382d:a7da> has joined #yocto | 08:49 | |
| *** mihai <mihai!~mihai@unaffiliated/mihai> has joined #yocto | 08:54 | |
| *** ahadi <ahadi!~ahadi@i59F44DAA.versanet.de> has quit IRC | 08:56 | |
| *** ahadi <ahadi!~ahadi@i59F44DAA.versanet.de> has joined #yocto | 08:57 | |
| *** hpsy <hpsy!~hpsy@2c0f:fc89:8012:be3f:a4e0:cdd5:31f8:b108> has joined #yocto | 08:59 | |
| *** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto | 09:09 | |
| *** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has joined #yocto | 09:12 | |
| *** Firuxabade <Firuxabade!~firuxabad@2001:e68:544d:97df:d883:3182:1191:8ed9> has joined #yocto | 09:13 | |
| *** psnsilva <psnsilva!~psnsilva@161.230.35.203> has joined #yocto | 09:23 | |
| *** Firuxabade <Firuxabade!~firuxabad@2001:e68:544d:97df:d883:3182:1191:8ed9> has quit IRC | 09:24 | |
| *** gsalazar <gsalazar!~gsalazar@173.111.90.149.rev.vodafone.pt> has joined #yocto | 09:28 | |
| *** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has quit IRC | 09:31 | |
| *** simonpe^^ <simonpe^^!~starlord@c83-252-164-58.bredband.comhem.se> has joined #yocto | 09:34 | |
| *** tnovotny <tnovotny!~tnovotny@ip-78-45-64-220.net.upcbroadband.cz> has joined #yocto | 09:37 | |
| *** gsalazar <gsalazar!~gsalazar@173.111.90.149.rev.vodafone.pt> has quit IRC | 09:40 | |
| *** hpsy <hpsy!~hpsy@2c0f:fc89:8012:be3f:a4e0:cdd5:31f8:b108> has quit IRC | 09:43 | |
| *** Blackbetty <Blackbetty!540affd6@84-10-255-214.static.chello.pl> has joined #yocto | 09:48 | |
| Blackbetty | hello, do you guys use kas? is there an irc channel for kas? | 09:48 |
| * derRichard uses it from time to time | 09:50 | |
| derRichard | no idea whether there is an irc for it | 09:50 |
| Blackbetty | couldnt find it anywhere | 09:50 |
| derRichard | does it matter? | 09:50 |
| Blackbetty | I wonder if there is any possibility to maintain layers order from kas.yml | 09:51 |
| Blackbetty | kas team decided to stick with alphabetic ordering which kinda destroys my build | 09:51 |
| Blackbetty | looking for a way to get in touch with them ;) | 09:53 |
| *** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has quit IRC | 09:53 | |
| derRichard | i'd try their github | 09:54 |
| *** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has joined #yocto | 09:55 | |
| *** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-vdawyoxmliyawdni> has joined #yocto | 10:03 | |
| *** Firuxabade <Firuxabade!~firuxabad@2001:e68:544d:97df:d883:3182:1191:8ed9> has joined #yocto | 10:03 | |
| simonpe^^ | I'm looking for a compatibility matrix between imx evk boards and fslc kernel/u-boot versions. Is there such a thing? | 10:10 |
| simonpe^^ | What I need is a u-boot with a certain commit for the u-boot patches we have for other boards to work, and the currently supported stuff by NXP is all on zeus and we run dunfell | 10:16 |
| simonpe^^ | And for some stupid reason there is a version dependency on u-boot from the imx kernels | 10:16 |
| simonpe^^ | I can't for the life of me figure out what they have messed up to end up in that situation | 10:16 |
| *** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC | 10:23 | |
| *** Kyubi <Kyubi!~Kyubi@149.199.62.129> has quit IRC | 10:27 | |
| *** mrslash <mrslash!d9e072f4@pd9e072f4.dip0.t-ipconnect.de> has joined #yocto | 10:42 | |
| rburton | Blackbetty: no irc for kas annoyingly, the google group is the best way | 10:43 |
| Blackbetty | rburton: derRichard: thank you, I already posted in the topic. | 10:44 |
| rburton | kanavin_: config.log is *huge* | 10:44 |
| *** JosephAntony <JosephAntony!a5e10863@165.225.8.99> has quit IRC | 11:15 | |
| *** mrslash <mrslash!d9e072f4@pd9e072f4.dip0.t-ipconnect.de> has quit IRC | 11:16 | |
| *** Sponge5 <Sponge5!~adam@cst2-170-164.cust.vodafone.cz> has joined #yocto | 11:18 | |
| *** tnovotny <tnovotny!~tnovotny@ip-78-45-64-220.net.upcbroadband.cz> has quit IRC | 11:19 | |
| *** B0ned1ger <B0ned1ger!~B0ned1ger@78-63-48-72.static.zebra.lt> has joined #yocto | 11:23 | |
| *** B0ned1ger2 <B0ned1ger2!~B0ned1ger@82-135-139-249.static.zebra.lt> has quit IRC | 11:27 | |
| *** B0ned1ger <B0ned1ger!~B0ned1ger@78-63-48-72.static.zebra.lt> has quit IRC | 11:28 | |
| *** mckoan is now known as mckoan|away | 11:33 | |
| *** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto | 11:33 | |
| *** Firuxabade <Firuxabade!~firuxabad@2001:e68:544d:97df:d883:3182:1191:8ed9> has quit IRC | 11:35 | |
| *** adosch <adosch!b8536a50@184-83-106-80-dynamic.midco.net> has joined #yocto | 11:38 | |
| RP | https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/1965/steps/14/logs/stdio is a fun failure, its caused by my sstate cleanup patches :( | 11:49 |
| RP | I think it is exposing a race | 11:49 |
| *** lumbergeek <lumbergeek!~geek@159.203.31.16> has joined #yocto | 11:53 | |
| lumbergeek | Ok, my google foo apparently sucks. Is there a database of available packages out there that can be used in a build? | 11:53 |
| neverpanic | http://layers.openembedded.org/layerindex/branch/master/recipes/ | 11:56 |
| lumbergeek | many thanks! i feel like I was bouncing all over oe.org and never quite found my way there | 11:59 |
| *** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto | 12:09 | |
| *** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has quit IRC | 12:14 | |
| *** Firuxabade <Firuxabade!~firuxabad@2001:e68:544d:97df:d883:3182:1191:8ed9> has joined #yocto | 12:35 | |
| *** ThomasD13 <ThomasD13!~thomas@DSL01.212.114.255.148.ip-pool.NEFkom.net> has quit IRC | 12:43 | |
| *** Firuxabade <Firuxabade!~firuxabad@2001:e68:544d:97df:d883:3182:1191:8ed9> has quit IRC | 12:47 | |
| *** rcoote <rcoote!~rcoote@2a02:908:692:81c0:fcd7:52e:1af4:518c> has joined #yocto | 13:00 | |
| *** plntyk <plntyk!~plntyk@ip5b40590c.dynamic.kabel-deutschland.de> has quit IRC | 13:03 | |
| *** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC | 13:06 | |
| *** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto | 13:08 | |
| *** ecdhe_ <ecdhe_!~ecdhe@unaffiliated/ecdhe> has joined #yocto | 13:24 | |
| Sponge5 | Hi, until now I've been using separate weston.ini files with separate .bbappends for each machine (each machine has a dedicated layer). I've now replaced those with weston.ini.patch and a base weston.ini, but I still have 5 .bbappends. How can I clean this up even further? | 13:26 |
| *** kothz <kothz!~geek@159.203.31.16> has joined #yocto | 13:26 | |
| Sponge5 | The idea is to have 5x weston.ini.patch and just one .bbappend (or no .bbappends at all) | 13:27 |
| *** jobroe_ <jobroe_!~manjaro-u@p579ebafa.dip0.t-ipconnect.de> has joined #yocto | 13:27 | |
| *** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has joined #yocto | 13:28 | |
| *** jobroe_ <jobroe_!~manjaro-u@p579ebafa.dip0.t-ipconnect.de> has quit IRC | 13:32 | |
| *** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC | 13:33 | |
| *** lumbergeek <lumbergeek!~geek@159.203.31.16> has quit IRC | 13:33 | |
| *** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has quit IRC | 13:33 | |
| *** kpo_ <kpo_!~kpo@bwu34.internetdsl.tpnet.pl> has quit IRC | 13:33 | |
| *** jobroe <jobroe!~manjaro-u@p579ebafa.dip0.t-ipconnect.de> has quit IRC | 13:33 | |
| *** ecdhe <ecdhe!~ecdhe@unaffiliated/ecdhe> has quit IRC | 13:33 | |
| *** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto | 13:35 | |
| *** otavio_ <otavio_!~otavio@200-180-244-11.user3p.brasiltelecom.net.br> has joined #yocto | 13:37 | |
| *** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has joined #yocto | 13:41 | |
| *** sakoman <sakoman!~steve@72.173.249.164> has joined #yocto | 13:42 | |
| derRichard | i'm analysing a build issue, all files in the rootfs are owned by the build users. looks like the fakeroot mechanism didn't work. and indeed, looking into the image's pseudo.log i see tons of messages such as: find_dev: select returned neither a row nor done: database disk image is malformed | 13:42 |
| derRichard | can it be the case that pseudo fails silently instead of aborting the build in case of such fatal errors? :-( | 13:43 |
| *** leon-anavi <leon-anavi!~Leon@78.130.197.211> has joined #yocto | 13:50 | |
| *** Chrys <Chrys!a5e15f2b@165.225.95.43> has joined #yocto | 13:56 | |
| Chrys | Hello everyone :) | 13:57 |
| Chrys | In my recipe, i modify u-boot env file in the "${WORKDIR}". | 13:57 |
| Chrys | Problem is, when using devtool modify... It prompt an error because the construction of the path for this is quite modified. | 13:57 |
| Chrys | What would be the workaround? | 13:57 |
| *** plntyk <plntyk!~plntyk@ip5b40590c.dynamic.kabel-deutschland.de> has joined #yocto | 13:59 | |
| *** B0ned1ger <B0ned1ger!~B0ned1ger@78-63-48-72.static.zebra.lt> has joined #yocto | 14:07 | |
| *** caiortp <caiortp!~caiortp@92-108-245-63.cable.dynamic.v4.ziggo.nl> has quit IRC | 14:08 | |
| Sponge5 | I found the answer to my question: https://stackoverflow.com/a/49281083/8779643 | 14:12 |
| Sponge5 | Kind of | 14:12 |
| *** B0ned1ger <B0ned1ger!~B0ned1ger@78-63-48-72.static.zebra.lt> has quit IRC | 14:12 | |
| *** kaspter <kaspter!~Instantbi@27.39.124.200> has quit IRC | 14:17 | |
| *** mrslash <mrslash!d9e072f4@pd9e072f4.dip0.t-ipconnect.de> has joined #yocto | 14:25 | |
| *** linums <linums!~linums@catv-80-99-160-36.catv.broadband.hu> has joined #yocto | 14:34 | |
| derRichard | hmm, yes. pseudo ignores fatal sqlite errors :-( | 14:38 |
| *** Blackbetty <Blackbetty!540affd6@84-10-255-214.static.chello.pl> has quit IRC | 14:40 | |
| *** ssajal <ssajal!~ssajal@bras-base-otwaon1146w-grc-06-184-146-108-8.dsl.bell.ca> has joined #yocto | 14:40 | |
| sgw | Morning folks, swatting a couple of failures. | 14:49 |
| sgw | RP: have we seen liblzma: memory allocation failed before? This smells a little like an Autobuilder intermittent I could not find any bugzilla entries | 14:50 |
| *** BobPungartnik <BobPungartnik!~BobPungar@187.113.135.108> has joined #yocto | 14:54 | |
| derRichard | sgw: does you have many cpus? | 14:55 |
| derRichard | *do you | 14:55 |
| *** BobPungartnik <BobPungartnik!~BobPungar@187.113.135.108> has quit IRC | 14:57 | |
| sgw | derRichard: it's has 56 cpu with 128G memory, seems 3 packages failed with memory issues | 14:57 |
| *** champagneg2 <champagneg2!~gchamp@ipagstaticip-d73c7528-4de5-0861-800b-03d8b15e3869.sdsl.bell.ca> has quit IRC | 14:57 | |
| yates | sgw: holy cow! | 14:58 |
| *** Chrys <Chrys!a5e15f2b@165.225.95.43> has quit IRC | 14:58 | |
| *** champagneg2 <champagneg2!~gchamp@ipagstaticip-d73c7528-4de5-0861-800b-03d8b15e3869.sdsl.bell.ca> has joined #yocto | 14:59 | |
| sgw | yates: this is part of the YP Autobuilder infrastructure, not unsurprising actually | 14:59 |
| sgw | The memory failure is though! | 14:59 |
| derRichard | sgw: yeah, then xz might run out of memory. | 14:59 |
| derRichard | i'm facing the same issues on super large build systems | 14:59 |
| derRichard | let me find the fix | 14:59 |
| *** marc1 <marc1!~marc@ipagstaticip-ad9375f2-382c-b511-8ac1-9541f69fe50f.sdsl.bell.ca> has quit IRC | 15:00 | |
| *** marc1 <marc1!~marc@ipagstaticip-ad9375f2-382c-b511-8ac1-9541f69fe50f.sdsl.bell.ca> has joined #yocto | 15:00 | |
| derRichard | see in poky | 15:01 |
| derRichard | commit 27ff81bfd880280607c79dce2f724c8bfafce02d | 15:01 |
| derRichard | Author: Mike Looijmans <mike.looijmans@topic.nl> | 15:01 |
| derRichard | Date: Fri Mar 20 15:45:20 2020 +0100 | 15:01 |
| derRichard | classes/populate_sdk_base: Implement xz compression options | 15:01 |
| derRichard | maybe you hit an other place where parallel compression is done... | 15:01 |
| sgw | derRichard: this is a recent master build on the autobuilder, I would think that fix is in. I have to bail for an hour, back after meeting | 15:01 |
| *** Firuxabade <Firuxabade!~firuxabad@2001:e68:544d:97df:d883:3182:1191:8ed9> has joined #yocto | 15:02 | |
| derRichard | yeah but maybe yet another bug of the same class.. | 15:02 |
| *** azimazlan_ <azimazlan_!~firuxabad@2001:e68:544d:97df:d883:3182:1191:8ed9> has joined #yocto | 15:02 | |
| derRichard | like i said, another parallel compression going one somewhere | 15:02 |
| sgw | 3 likely | 15:02 |
| derRichard | for 56 cpus, only 128gb ram is a little too few | 15:03 |
| derRichard | even on my 24 core system with 128gb ram, i'm hitting such issues | 15:03 |
| sgw | derRichard: it's funny to think that's small! | 15:03 |
| JPEW | xz seems particularly bad about that for some reason | 15:03 |
| yates | what is xz? | 15:03 |
| JPEW | A compression tool | 15:04 |
| yates | ah | 15:04 |
| derRichard | in parallel mode it wastes per core tons of memory | 15:04 |
| JPEW | yates: I believe it's the tool that does LZMA compression | 15:05 |
| yates | looks like 7z does it too | 15:07 |
| *** linums <linums!~linums@catv-80-99-160-36.catv.broadband.hu> has quit IRC | 15:16 | |
| yates | kergoth: yesterday, when discussing 'do_build[recrdeptask] += "do_deploy"', you spoke of build-time dependencies and run-time dependencies. what is a run-time dependency? | 15:17 |
| RP | sgw: we've not seen that one for a long time. Which worker was it? | 15:17 |
| *** linums <linums!~linums@apn-94-44-233-87.vodafone.hu> has joined #yocto | 15:18 | |
| *** azimazlan_ <azimazlan_!~firuxabad@2001:e68:544d:97df:d883:3182:1191:8ed9> has quit IRC | 15:21 | |
| sgw | RP: debian10-ty-1 | 15:21 |
| RP | sgw: hmm, strange to hit that now... | 15:23 |
| vdl | hi all -- I assume that it is still unsafe to build multiple distros using the same build/ directory, correct? | 15:25 |
| RP | vdl: not so much unsafe as inefficient | 15:26 |
| sgw | Ok, I will file it as a AB intermittent so we can track | 15:26 |
| vdl | RP: if your project includes multiple distros, how do you deal with it, simply one build-foo/ directory per distro? | 15:28 |
| RP | vdl: that or multiconfig | 15:28 |
| vdl | RP: but multiconfig is useful when you can a link at build time between 2 distincts images, like embedding a dist/mach/image combination into another dist/mach/image combination, correct? | 15:29 |
| JPEW | vdl: multiconfig has many uses, that's one of them | 15:30 |
| RP | vdl: multiconfig would also allow you to build two different distro configs in parallel in separate tmpdirs | 15:30 |
| RP | one distro could have images including images from the other, lots of possibilities | 15:31 |
| JPEW | vdl: For example, we have multiple products we can choose to build, and build each on in it's own multiconfig. This allows us to choose to build one or more with a single invocation of bitbake | 15:31 |
| JPEW | vdl: We us this tool to wrangle it all, but at the end of the day, it's just multiconfig: https://github.com/garmin/whisk | 15:32 |
| *** AndersD <AndersD!~AndersD@h83-209-96-136.cust.a3fiber.se> has quit IRC | 15:32 | |
| kergoth | yates: https://www.aosabook.org/en/yocto.html scroll down to Dependencies | 15:33 |
| kergoth | as i've linked or directed you to 4 or 5 times now | 15:33 |
| *** aleblanc <aleblanc!~textual@192-222-183-114.qc.cable.ebox.net> has quit IRC | 15:33 | |
| vdl | JPEW: RP: I understand that multiconfig is the way to go if you need to build multiple distro combinations at once, even though if they aren't packaged together (but they could) | 15:38 |
| *** aleblanc <aleblanc!~textual@192-222-183-114.qc.cable.ebox.net> has joined #yocto | 15:39 | |
| vdl | Finally I need to prepare a release archive, like <customer>-release-<version>.tar.xz including the .wic image, README and so on. Is there a way to integrate this step within the single invokation of bitbake? | 15:40 |
| *** aleblanc <aleblanc!~textual@192-222-183-114.qc.cable.ebox.net> has quit IRC | 15:40 | |
| yates | kergoth: i don't appreciate being addressed in this manner. we all know yocto is a huge, sprawing tool, with multiple sources of documentation. i guarantee that i will ask another question for which i've already been directed, just because my brain (like many others) is not good at absorbing the large amount of inter-related, parallel information which yocto requires | 15:43 |
| tlwoerner | i want to compare the boot times of various builds/tweaks. is there a way to get one of those nice kernel timestamp thingies on the console right as the login prompt is appearing? | 15:44 |
| RP | vdl: you could add a task to an image or add a recipe which does it | 15:44 |
| yates | at least not instantly and/or perfectly | 15:46 |
| vdl | RP: an image recipe with IMAGE_FSTYPES = "tar.xz" seems the way to go, but I fail to depends on image-a.wic being deployed. I tried do_rootfs[depends] += "image-a:do_build" without success | 15:46 |
| RP | vdl: personally, I'd just write a recipe with a custom task which does it | 15:47 |
| RP | trying to reuse the image code is probably going to just be a pain | 15:48 |
| vdl | yates: I do not wish to step into this topic, but people in the open source community often expect you to look up for questions already answered. For example this channel is logged, so you can easily ask again your question to google with your username to retrieve your last interaction about the topic. | 15:49 |
| vdl | RP: I see. How do you ensure that your recipe is called after image-a.wic has been deployed? (do you have any example in mind I could look into?) | 15:50 |
| RobertBerger | Should we all attend "From Yocto + Buildroot to Ubuntu core" and ask some questions? https://ubuntu.com/engage/yocto-buildroot-to-ubuntu-core | 15:51 |
| tlwoerner | RobertBerger: lol | 15:51 |
| RobertBerger | ;) | 15:52 |
| RP | vdl: you'd just do something like do_mytask[depends] = "imagerecipe:do_image_complete" I don't have a specific example in mind | 15:53 |
| vdl | RP: so you're not even inheriting an image, correct? This way you need to handle the archiving yourself instead of relying on IMAGE_FSTYPES = "tar.xz" for example, am I correct? | 15:56 |
| RP | vdl: Correct, that is how I would do it | 15:58 |
| RP | vdl: tar commands aren't complex | 15:58 |
| vdl | They aren't complex, but since the archiving is abstracted by yocto already, it'd be nice to re-use it. | 15:59 |
| *** linums <linums!~linums@apn-94-44-233-87.vodafone.hu> has quit IRC | 16:07 | |
| *** linums <linums!~linums@catv-80-99-160-36.catv.broadband.hu> has joined #yocto | 16:07 | |
| vdl | RP: it looks like a good candidate for something like a release.bbclass supporting RELEASE_FSTYPES and a file listing similar to IMAGE_BOOT_FILES (e.g. RELEASE_FILES = "some-image.wic;sdcard.img some-doc.txt;README" and so on) | 16:10 |
| linums | Hi | 16:15 |
| RP | vdl: reuse is nice but you aren't wanting a large portion of what the image code is doing (building a rootfs from packages) | 16:15 |
| linums | I'm building yocto for arm (rpi) now | 16:15 |
| linums | And I regularly run into segmentation fault issues, and those are disappearing when I re-run the build | 16:16 |
| RP | vdl: What you're after to do is something like a 5 line custom task vs a ton of work with classes and variables for reusable code | 16:16 |
| linums | Do anyone has a clu why can it happen? | 16:16 |
| RP | linums: checked you memory for errrors? | 16:16 |
| linums | Nope | 16:17 |
| linums | Thanks | 16:17 |
| linums | So it might be the device | 16:17 |
| vdl | RP: isn't the archiving code distinct from building a rootfs from packages? I understand what you're saying though, I'm just surprised such class doesn't exist yet. I wanted to avoid writing a custom script or recipe before making sure such infrastructure doesn't exist yet. | 16:19 |
| RP | vdl: I think you'd struggle to separate the rootfs and image archive code as it stands today | 16:21 |
| *** Sponge5 <Sponge5!~adam@cst2-170-164.cust.vodafone.cz> has quit IRC | 16:21 | |
| RP | linums: random segfaults which don't reproduce are usually hardware or a kernel problem, most often bad memory | 16:21 |
| RP | I have seen bad virtualisation before too | 16:22 |
| vdl | RP: ho ok, so unfortunately the archiver class (or whatever it's called) is currently bound to the creation of a rootfs from packages. | 16:23 |
| vdl | that's unlucky | 16:23 |
| vdl | JPEW: how does whisk compare to a tool like kas? They look similar tome | 16:25 |
| linums | RP: now I fear it's from the swap file, since the ram seems ok, but thanks, I guess that is the issue | 16:27 |
| *** sgw <sgw!~sgw@2601:642:c400:ecf0:e84a:317d:c341:256c> has quit IRC | 16:35 | |
| paulg | https://ubuntu.com/engage/yocto-buildroot-to-ubuntu-core | 16:36 |
| paulg | Guess we should all pull up our tent pegs and go home. | 16:37 |
| *** kyrix <kyrix!~ashwoods@78.142.65.171> has joined #yocto | 16:39 | |
| *** sgw <sgw!~sgw@2601:642:c400:ecf0:9c7a:1b9d:bd52:c567> has joined #yocto | 16:47 | |
| sgw | RP: I am digging into the other set of selftest failures in WIC, but the log files seems to have gone already, is that normal? | 16:47 |
| *** Firuxabade <Firuxabade!~firuxabad@2001:e68:544d:97df:d883:3182:1191:8ed9> has quit IRC | 16:48 | |
| *** bobo <bobo!~bobo@customer-145-14-101-3.stosn.net> has joined #yocto | 16:51 | |
| RP | sgw: is this the rawcopy one? I have a fix for that | 16:52 |
| RP | sgw: you probaby need a s/build/build-renamed/ in the path? | 16:52 |
| sgw | There does not seem to be a build-renamed in /home/pokybuild/yocto-worker/oe-selftest-debian/build/ or /home/pokybuild/yocto-worker/oe-selftest-debian/build/build | 16:53 |
| RP | sgw: selftest will run in build-st-<pid> | 16:54 |
| RP | sgw: (it runs multiple in parallel) | 16:54 |
| sgw | This is a file not found issue in wic looking for the .ext4 | 16:54 |
| sgw | Right, the -<pid> that I am trying to find is gone | 16:54 |
| sgw | RP: I wanted to look at the build tmp/deploy dir area | 16:56 |
| *** aleblanc <aleblanc!~textual@192-222-183-114.qc.cable.ebox.net> has joined #yocto | 16:56 | |
| RP | sgw: hmm, I thought failed builds were preserved | 16:57 |
| *** kiwi_29 <kiwi_29!~kiwi_29@c-73-231-211-214.hsd1.ca.comcast.net> has joined #yocto | 16:57 | |
| RP | sgw: I have a fix out for the wic/ext4 one, I spent most of the day figuring that one out. Its caused by my sstate cleanup patch | 16:58 |
| sgw | RP: I thought they were also, Ok, I will swat those out as handled then. | 16:58 |
| sgw | RP: thanks for that update and I hope you can break away and have a good weekend. | 16:59 |
| *** kiwi_29 <kiwi_29!~kiwi_29@c-73-231-211-214.hsd1.ca.comcast.net> has quit IRC | 17:00 | |
| *** kiwi_29 <kiwi_29!~kiwi_29@c-73-231-211-214.hsd1.ca.comcast.net> has joined #yocto | 17:00 | |
| Saur | RP: Wasn't the idea with commit 73d538f2 (bitbake.conf: Prevent pyc file generation in pseudo context) that fakeroot tasks should no longer create .pyc files? Because we are having occasional pseudo aborts after upgrading to Gatesgarth (24.0.2) when we create our final image. We use our own tool, which is similar to wic. We finally managed to get the psudo.log from one of the failed builds and found this: path mismatch [1 link]: ino 12085 | 17:07 |
| Saur | 2760 db '.../poky/bitbake/lib/bb/ui/__pycache__/__init__.cpython-38.pyc' req '.../poky/bitbake/lib/bb/ui/__pycache__/uievent.cpython-38.pyc.140666647610112'. And when I check the environment the tool is running in, I cannot see PYTHONDONTWRITEBYTECODE being set. | 17:07 |
| Saur | Or does that change only apply to fakeroot python tasks? | 17:08 |
| *** champagneg2 <champagneg2!~gchamp@ipagstaticip-d73c7528-4de5-0861-800b-03d8b15e3869.sdsl.bell.ca> has quit IRC | 17:10 | |
| RP | Saur: good questions. Would need to be debugged, I don't know offhand how it should/would work out. The intent was to disable them | 17:11 |
| RP | Saur: I think the option is python version dependent | 17:12 |
| *** champagneg2 <champagneg2!~gchamp@ipagstaticip-d73c7528-4de5-0861-800b-03d8b15e3869.sdsl.bell.ca> has joined #yocto | 17:12 | |
| Saur | When is FAKEROOTBASEENV vs FAKEROOTENV used? | 17:12 |
| RP | Saur: I'd have to grep, I don't remember | 17:25 |
| Saur | RP: :) Ok, then I can just as well grep myself. ;) | 17:26 |
| *** leon-anavi <leon-anavi!~Leon@78.130.197.211> has quit IRC | 17:28 | |
| Saur | Ok, for fakeroot, FAKEROOTBASEENV is the environment that is used when starting bitbake-worker. | 17:28 |
| *** Yumasi <Yumasi!~guillaume@2a01:e0a:5cb:4430:71ee:168f:367c:6d70> has quit IRC | 17:35 | |
| Saur | And if I understand the code in bitbake-worker correctly, none of the environment that was used to start the bitbake-worker is left when it actually starts a task. Instead it is then the environment from FAKEROOTENV that is used. So this means that adding PYTHONDONTWRITEBYTECODE=1 to FAKEROOTBASEENV does in fact not affect python code started by, e.g., a fakeroot shell task. :( | 17:38 |
| *** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC | 17:39 | |
| *** psnsilva <psnsilva!~psnsilva@161.230.35.203> has quit IRC | 17:39 | |
| Saur | Thankfully this means that it should be simple to solve the problem we are seeing by just adding FAKEROOTENV += "PYTHONDONTWRITEBYTECODE=1" to our distro.conf. | 17:40 |
| Saur | I'll send a corresponding patch for OE-Core as well. | 17:41 |
| Saur | Meh, I have a strong feeling I will have to create a test case for this as well... :) | 17:46 |
| *** bobo <bobo!~bobo@customer-145-14-101-3.stosn.net> has quit IRC | 17:46 | |
| *** rcoote <rcoote!~rcoote@2a02:908:692:81c0:fcd7:52e:1af4:518c> has quit IRC | 17:52 | |
| *** kyanres <kyanres!~kyanres@ecascr.ecatou.fr> has quit IRC | 17:53 | |
| RP | Saur: sounds like good progress on figuring out the issue :) | 18:03 |
| Saur | The weirdest thing is that we are only seeing this fail when building the image for one out of all the products we build images for... | 18:05 |
| *** bobo <bobo!~bobo@customer-145-14-101-3.stosn.net> has joined #yocto | 18:09 | |
| *** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto | 18:17 | |
| JPEW | vdl: Ya, it overlaps with kas some | 18:18 |
| JPEW | Especially if you do whisk + pyrex (build in a container) | 18:19 |
| *** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC | 18:20 | |
| *** jwessel <jwessel!~jwessel@128.224.252.2> has left #yocto | 18:21 | |
| *** fl0v0 <fl0v0!~fvo@89.244.121.59> has quit IRC | 18:27 | |
| *** yannholo <yannholo!~yannholo@fs-141-0-205-41.fullsave.info> has quit IRC | 18:27 | |
| *** dreyna <dreyna!~dreyna@2601:646:4201:e280:8ec:f86e:d0fb:6a62> has joined #yocto | 18:32 | |
| *** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto | 18:34 | |
| *** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto | 18:43 | |
| *** B0ned1ger <B0ned1ger!~B0ned1ger@78-63-48-72.static.zebra.lt> has joined #yocto | 18:44 | |
| *** B0ned1ger <B0ned1ger!~B0ned1ger@78-63-48-72.static.zebra.lt> has quit IRC | 18:48 | |
| *** oobitots <oobitots!ad26d108@aer01-mda1-dmz-wsa-3.cisco.com> has joined #yocto | 18:54 | |
| *** oobitots <oobitots!ad26d108@aer01-mda1-dmz-wsa-3.cisco.com> has quit IRC | 19:07 | |
| *** bobo <bobo!~bobo@customer-145-14-101-3.stosn.net> has quit IRC | 19:08 | |
| *** oobitots <oobitots!ad26d10b@aer01-mda2-dmz-wsa-6.cisco.com> has joined #yocto | 19:20 | |
| *** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC | 19:36 | |
| *** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto | 19:37 | |
| *** BCMM_ <BCMM_!~BCMM@unaffiliated/bcmm> has joined #yocto | 19:37 | |
| *** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC | 19:38 | |
| *** aleblanc <aleblanc!~textual@192-222-183-114.qc.cable.ebox.net> has quit IRC | 19:45 | |
| *** BCMM_ is now known as BCMM | 19:47 | |
| vdl | JPEW: and kas does handle multiconfig already | 19:48 |
| *** aleblanc <aleblanc!~textual@192-222-183-114.qc.cable.ebox.net> has joined #yocto | 19:50 | |
| *** champagneg2 <champagneg2!~gchamp@ipagstaticip-d73c7528-4de5-0861-800b-03d8b15e3869.sdsl.bell.ca> has quit IRC | 19:51 | |
| *** champagneg2 <champagneg2!~gchamp@ipagstaticip-d73c7528-4de5-0861-800b-03d8b15e3869.sdsl.bell.ca> has joined #yocto | 19:53 | |
| *** oobitots <oobitots!ad26d10b@aer01-mda2-dmz-wsa-6.cisco.com> has quit IRC | 20:03 | |
| *** yizhao <yizhao!~zhaoyi@60.247.85.82> has quit IRC | 20:08 | |
| *** aleblanc <aleblanc!~textual@192-222-183-114.qc.cable.ebox.net> has quit IRC | 20:09 | |
| *** leon-anavi <leon-anavi!~Leon@78.130.197.211> has joined #yocto | 20:21 | |
| *** gpanders <gpanders!~gpanders@gateway/tor-sasl/gpanders> has quit IRC | 20:23 | |
| *** gpanders <gpanders!~gpanders@gateway/tor-sasl/gpanders> has joined #yocto | 20:24 | |
| *** mrslash <mrslash!d9e072f4@pd9e072f4.dip0.t-ipconnect.de> has quit IRC | 20:27 | |
| moto-timo | kas handles multiconfig very well, it's just not well documented | 20:33 |
| * moto-timo still needs to try whisk | 20:34 | |
| moto-timo | JPEW: do you run whisk/pyrex in any cloud providers? | 20:35 |
| JPEW | moto-timo: K8s on baremetal | 20:38 |
| moto-timo | JPEW: the battlestar cluster... but at work also? | 20:38 |
| JPEW | OpenStack maybe? I'm not exactly sure | 20:39 |
| JPEW | Not "in the cloud" its all on-prem | 20:39 |
| moto-timo | got it | 20:39 |
| JPEW | If someone want to fund a trial on AWS, I'd be up for it :) | 20:39 |
| JPEW | But I can't throw down a few $1000 to try it myself | 20:40 |
| moto-timo | at some point here I'll be testing AWS/Azure/GCE... need to be agnostic to the provider | 20:40 |
| *** B0ned1ger <B0ned1ger!~B0ned1ger@78-63-48-72.static.zebra.lt> has joined #yocto | 20:40 | |
| JPEW | moto-timo: Right, AWS was just an example | 20:40 |
| moto-timo | yeah... this is mostly own money | 20:40 |
| moto-timo | I can't actually tell you what providers we use internally | 20:41 |
| moto-timo | so I live vicariously through open source projects that have donated compute slices | 20:41 |
| moto-timo | but I have seen a cluster crash and burn, be restarted, crash and burn and then had to be taken out back and shot in the head | 20:42 |
| moto-timo | no free lunch | 20:42 |
| JPEW | moto-timo: Right. That's why my latest expirement was to build my own cluster | 20:43 |
| * JPEW Really needs to get labgrid working on that again | 20:43 | |
| moto-timo | JPEW: and why I have an rpi cluster | 20:43 |
| JPEW | moto-timo: What's the build time like on that? | 20:44 |
| * moto-timo needs to get labgrid and ceph running | 20:44 | |
| JPEW | moto-timo: Oh, I tried ceph... it's actually what took down my cluster | 20:44 |
| moto-timo | JPEW: ugh... I'm not to that point yet. still working on the ansible bring up | 20:44 |
| moto-timo | nooooo | 20:44 |
| moto-timo | don't tell me that | 20:44 |
| JPEW | It's.... slower then molassas... and I have 4Gbit links (LCAP) between my servers | 20:44 |
| moto-timo | there has GOT TO BE something better than NFS | 20:45 |
| moto-timo | or CIFS/samba | 20:45 |
| *** B0ned1ger <B0ned1ger!~B0ned1ger@78-63-48-72.static.zebra.lt> has quit IRC | 20:45 | |
| JPEW | So far, my best option has been local for working dir, share sstate over NFS | 20:45 |
| JPEW | You could probably share sstate of CEPH and that would work fine | 20:45 |
| JPEW | *over CEPH | 20:46 |
| moto-timo | sstate is the sticky wicket that doesn't scale well to the cloud :( | 20:46 |
| moto-timo | that was my intent. sstate over ceph | 20:46 |
| moto-timo | I figure hadoop would be slower than molasses | 20:46 |
| JPEW | Ya, that might be better. I was trying to use it for the working volume, had a build with took over 10 hours, timed out, and broke tekton somehow | 20:47 |
| moto-timo | oh... no that's not how I wanted to use it | 20:47 |
| JPEW | It never recovered, so I had to re-image the cluster | 20:47 |
| moto-timo | ugh | 20:47 |
| * moto-timo feels slightly less panicked now | 20:47 | |
| moto-timo | I still need to expand the PDU drivers for labgrid and enable PXE boot | 20:48 |
| rburton | you can do sstate over http to fetch and then push back through some other means post-build | 20:48 |
| rburton | which removes the NFS aspect but give you bigger windows when stuff can get built twice as you don't push as often | 20:49 |
| moto-timo | yeah... post build write is what I want to experiment with | 20:49 |
| rburton | that's what paulbarker did | 20:49 |
| JPEW | We do that with rsync.... it's too slow IMHO | 20:49 |
| rburton | backblaze, http to fetch and sync post-build with b2sync | 20:49 |
| moto-timo | I figure if the options are "might build twice" or "zero sstate", I'll take the first. | 20:50 |
| rburton | for small clusters, i'm still happy with NFS for fast and shjared | 20:50 |
| rburton | especially when i have someone i can say "i want a NFS share" to :) | 20:50 |
| moto-timo | Konrad also commented on the slowness of rsync... instead suggested tarballs | 20:50 |
| * moto-timo asks moto-timo for an NFS share | 20:51 | |
| moto-timo | nope | 20:51 |
| rburton | shame | 20:51 |
| rburton | you should have a word with moto-timo, he sounds like a lame admin | 20:51 |
| moto-timo | it's friday and nearly beer-thirty | 20:51 |
| * moto-timo is a lazy greedy curmudgeon sometimes | 20:51 | |
| JPEW | moto-timo: What's the aversion to NFS? | 20:51 |
| moto-timo | I've heard too many stories about brittleness and failures and weird slowdowns | 20:52 |
| moto-timo | and it's old tech... feels like something should be better by now | 20:52 |
| moto-timo | also... security folks have been very very "NOPE" about it | 20:53 |
| JPEW | Well.... you *do* know that if you use CEPH as a shared disk, it does so over NFS protocol :) | 20:53 |
| rburton | ha! | 20:53 |
| moto-timo | yeah... don't remind me. | 20:53 |
| moto-timo | of course, the security folks' solution is FUSE ssh | 20:54 |
| * JPEW belgh | 20:54 | |
| * moto-timo runs to find a bucket | 20:54 | |
| JPEW | NFS4 is way better than NFS3 | 20:54 |
| moto-timo | So I've heard from multiple sources... so my data is old I think | 20:55 |
| *** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto | 20:55 | |
| * JPEW Wrote an NFS4 server from scratch for an RTOS.... fun times! | 20:55 | |
| moto-timo | also, you can get very many Gbits over fiber these days | 20:55 |
| moto-timo | JPEW is a madman | 20:55 |
| *** snikulov <snikulov!~snikulov@109.252.49.163> has joined #yocto | 20:56 | |
| moto-timo | rpi pcie is only 1x so you'd saturate it very easily with normal network | 20:56 |
| moto-timo | but that might be "fast enough" for a home lab that cost less than a used car | 20:56 |
| JPEW | Right, I didn't really notice it being slow before I had 4GB LCAP links | 20:57 |
| moto-timo | and doesn't need a nuclear reactor to power it | 20:57 |
| moto-timo | lol | 20:57 |
| * moto-timo dreams of 10Gbit backbone in the LAN | 20:57 | |
| moto-timo | stuff is starting to get affordable on eBay | 20:58 |
| JPEW | I bought a switch that can do 10Gbit... just need the NICs on my servers | 20:58 |
| JPEW | .... some day | 20:58 |
| moto-timo | JPEW: there are some nics that are not expensive on eBay... take a look | 20:58 |
| moto-timo | broadcom I think | 20:58 |
| moto-timo | my problem is my mobos are old so the base throughput won't benefit | 21:00 |
| moto-timo | not going to complain about the price I paid for the compute power though... | 21:00 |
| JPEW | moto-timo: Ditto... I found some pretty cheap Dell R610s | 21:02 |
| *** zkrx <zkrx!~slimshady@adsl-89-217-237-59.adslplus.ch> has quit IRC | 21:08 | |
| *** zkrx <zkrx!~slimshady@adsl-89-217-237-59.adslplus.ch> has joined #yocto | 21:12 | |
| JaMa | hmm python3 PACKAGECONFIG can no longer be used to disable gdbm (it worked fine in gatesgarth with 3.8) in master with 3.9 it fails with: | 21:13 |
| JaMa | The necessary bits to build these optional modules were not found: | 21:13 |
| JaMa | _dbm _gdbm | 21:13 |
| moto-timo | hmmm | 21:14 |
| moto-timo | just oe-core? can you file a bug? | 21:14 |
| JaMa | yes, will debug a bit more and then send a fix or bug report | 21:16 |
| *** sbach <sbach!~sbachmatr@192.184.90.156> has quit IRC | 21:18 | |
| *** sbach <sbach!~sbachmatr@192.184.90.156> has joined #yocto | 21:18 | |
| *** aidanh_ <aidanh_!~aidanh@unaffiliated/aidanh> has joined #yocto | 21:19 | |
| *** aidanh <aidanh!~aidanh@unaffiliated/aidanh> has quit IRC | 21:21 | |
| *** aidanh_ is now known as aidanh | 21:21 | |
| *** adosch <adosch!b8536a50@184-83-106-80-dynamic.midco.net> has quit IRC | 21:24 | |
| *** snikulov <snikulov!~snikulov@109.252.49.163> has quit IRC | 21:27 | |
| *** snikulov <snikulov!~snikulov@109-252-49-163.nat.spd-mgts.ru> has joined #yocto | 21:27 | |
| *** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has quit IRC | 21:30 | |
| *** snikulov <snikulov!~snikulov@109-252-49-163.nat.spd-mgts.ru> has quit IRC | 21:35 | |
| *** snikulov <snikulov!~snikulov@109-252-49-163.nat.spd-mgts.ru> has joined #yocto | 21:35 | |
| *** yocti <yocti!~supybot@mail.yoctoproject.org> has joined #yocto | 22:13 | |
| *** psycor4m4 <psycor4m4!~psycorama@datenhalde.de> has joined #yocto | 22:13 | |
| *** ak77 <ak77!~ak77@93-103-81-73.static.t-2.net> has quit IRC | 22:13 | |
| *** fitzsim` <fitzsim`!~user@69-165-165-189.dsl.teksavvy.com> has joined #yocto | 22:13 | |
| *** King_InuYasha <King_InuYasha!~King_InuY@fedora/ngompa> has quit IRC | 22:13 | |
| *** psycor4m4 is now known as psycorama | 22:13 | |
| *** fitzsim` is now known as fitzsim | 22:13 | |
| *** ak77 <ak77!~ak77@93-103-81-73.static.t-2.net> has joined #yocto | 22:14 | |
| *** agust <agust!~agust@p508b6964.dip0.t-ipconnect.de> has quit IRC | 22:16 | |
| *** ahadi <ahadi!~ahadi@i59F44DAA.versanet.de> has quit IRC | 22:16 | |
| *** hackspider <hackspider!5dec02a1@p5dec02a1.dip0.t-ipconnect.de> has joined #yocto | 22:16 | |
| hackspider | Hi guys, is it wise to set the machine in the distro conf? | 22:17 |
| *** ahadi <ahadi!~ahadi@i59F44DAA.versanet.de> has joined #yocto | 22:17 | |
| derRichard | i'd not do it. actually i'm not even sure whether this is allowed | 22:29 |
| derRichard | usually you have more than one machine | 22:30 |
| *** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC | 22:38 | |
| *** ENPJ <ENPJ!~ENPJ@2001:a61:3a33:7901:6de9:a24b:3d4e:f73b> has quit IRC | 22:41 | |
| *** leon-anavi <leon-anavi!~Leon@78.130.197.211> has quit IRC | 22:44 | |
| *** aleblanc <aleblanc!~textual@192-222-183-114.qc.cable.ebox.net> has joined #yocto | 22:53 | |
| hackspider | My setup is more like this: I've got a reference board with the most likely hardware config. For this hardware (machine) I've created a machine config for this. If a customer wants exactly this config he gets an own meta layer with an image recipe for his applications/sources. But if the customer needs a custom hardware with removed or added | 23:00 |
| hackspider | peripheral he gets also an own machine config in his meta layer to adapt uboot/kernel/kernel_modules. Does this make sense so far? | 23:00 |
| hackspider | What I then did was to create in the meta layer of the reference board a distro config where I defined what I needed in the distro (musl, systemd,etc.). But know I wonder where to set the machine config. Should I add a distro in all customer specific meta layers where I define the machine or should I add it to env variables with every build? | 23:06 |
| *** aleblanc <aleblanc!~textual@192-222-183-114.qc.cable.ebox.net> has quit IRC | 23:09 | |
| *** simonpe^^ <simonpe^^!~starlord@c83-252-164-58.bredband.comhem.se> has quit IRC | 23:15 | |
| RobertBerger | @hackspider: for your use case I would use MACHINEOVERRIDES | 23:17 |
| derRichard | yes, sounds like a case for MACHINEOVERRIDES | 23:25 |
| hackspider | I haven't known this variable yet, but this seems like the way to go. So I need a distro file in each customer layer with a require statement to the distro of the refernce distro so I can set the MACHINEOVERRIDES value? So basically each customer gets an "own" distro? | 23:25 |
| *** yates <yates!~user@fv-nc-f7af8b91e1-234237-1.tingfiber.com> has quit IRC | 23:28 | |
| RobertBerger | @hackspider - nope why in the distro? | 23:29 |
| RobertBerger | @hackspider: you have a "default" machine config for all and whoever wants to make a change can extend it by an override. Let me try to find an example. | 23:30 |
| RobertBerger | https://www.yoctoproject.org/pipermail/meta-xilinx/2017-August/003138.html | 23:30 |
| RobertBerger | There he uses some eval board as the "base" and adds his own stuff in addition to it. | 23:31 |
| hackspider | But where do I define the machine to use? Since something needs to point to the correct <machine>.conf | 23:35 |
| *** fatalhalt <fatalhalt!~fatalhalt@2601:244:4d01:52df:225:90ff:feda:2428> has quit IRC | 23:35 | |
| hackspider | lets say in the meta-referencehardware layer I defined a "referencehardware.conf" and then in a customer layer lets say meta-customer I have a "customhardware.conf" machine file with a require statement to "referencehardware.conf". But where do I specify to use "referencehardware.conf" | 23:38 |
| *** otavio_ <otavio_!~otavio@200-180-244-11.user3p.brasiltelecom.net.br> has quit IRC | 23:45 | |
| RobertBerger | @hackspider: as usual in the machine.conf | 23:46 |
| RobertBerger | MACHINEOVERRIDES .= ":zc706-zynq7" this adds to the list also zc706-zynq7 | 23:46 |
| RobertBerger | maybe you should also check how override lists work | 23:47 |
| *** otavio_ <otavio_!~otavio@200-180-244-11.user3p.brasiltelecom.net.br> has joined #yocto | 23:47 | |
| RobertBerger | bitbake busybox -e | grep ^OVERRIDES= | 23:48 |
| RobertBerger | bitbake busybox -e | grep ^MACHINEOVERRIDES= | 23:48 |
| RobertBerger | if you see the output of MACHINEOVERRIDES you could imagine like at the left it's more generic and at the right is more specific and further right overrides further left | 23:49 |
| RobertBerger | BTW the machine to use you define in local.conf | 23:51 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!