Thursday, 2022-12-01

*** RobertBerger <RobertBerger!~rber|res@62-46-91-193.adsl.highway.telekom.at> has quit IRC (Remote host closed the connection)00:22
*** Minvera <Minvera!~Minvera@user/Minvera> has quit IRC (Remote host closed the connection)00:50
*** PhoenixMage <PhoenixMage!~phoenix@206.83.114.214> has quit IRC (Remote host closed the connection)00:59
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)01:13
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Ping timeout: 260 seconds)01:13
*** dreyna4529_b <dreyna4529_b!~dreyna452@2601:646:4200:cfc0:5475:f5fe:aab8:248a> has joined #yocto01:16
*** aleksandarsimono <aleksandarsimono!~aleksanda@79.142.183.177> has joined #yocto01:19
*** nemik_ <nemik_!~nemik@207.237.248.190> has quit IRC (Ping timeout: 260 seconds)01:39
*** nemik_ <nemik_!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto01:39
*** nemik_ <nemik_!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 252 seconds)01:43
*** nemik_ <nemik_!~nemik@207.237.248.190> has joined #yocto01:44
*** Wouter0100 <Wouter0100!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat)01:46
*** Wouter0100 <Wouter0100!~Wouter010@entry.nbg.netvos.nl> has joined #yocto01:47
*** aleksandarsimono <aleksandarsimono!~aleksanda@79.142.183.177> has quit IRC (Ping timeout: 260 seconds)01:51
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto02:27
*** PhoenixMage <PhoenixMage!~phoenix@206.83.114.214> has joined #yocto02:57
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)02:58
*** jclsn <jclsn!~jclsn@2a04:4540:6511:da00:2ce:39ff:fecf:efcd> has quit IRC (Ping timeout: 260 seconds)03:29
*** jclsn <jclsn!~jclsn@2a04:4540:651b:b900:2ce:39ff:fecf:efcd> has joined #yocto03:30
*** amitk <amitk!~amit@103.59.74.51> has joined #yocto03:40
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Ping timeout: 260 seconds)04:02
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)04:29
*** smurray <smurray!sid98062@id-98062.hampstead.irccloud.com> has left #yocto04:41
*** nemik_ <nemik_!~nemik@207.237.248.190> has quit IRC (Ping timeout: 268 seconds)05:14
*** nemik_ <nemik_!~nemik@162-245-20-117.public.monkeybrains.net> has joined #yocto05:14
*** nemik_ <nemik_!~nemik@162-245-20-117.public.monkeybrains.net> has quit IRC (Ping timeout: 256 seconds)05:19
*** nemik_ <nemik_!~nemik@207.237.248.190> has joined #yocto05:19
*** amitk_ <amitk_!~amit@103.208.69.161> has joined #yocto05:31
*** xcm <xcm!~xcm@user/xcm> has joined #yocto05:55
*** |Xagen <|Xagen!~Xagen@99-135-179-142.lightspeed.austtx.sbcglobal.net> has joined #yocto05:56
*** demirok <demirok!~bell@user/demirok> has quit IRC (Quit: Leaving.)05:57
*** aardo <aardo!~ardo@host-79-24-134-30.retail.telecomitalia.it> has joined #yocto05:57
*** justache- <justache-!~justache@user/justache> has joined #yocto05:58
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto05:58
*** Amynka_ <Amynka_!~amy@gentoo/developer/amynka> has joined #yocto05:59
*** risca_ <risca_!~quassel@h-155-4-62-62.A980.priv.bahnhof.se> has joined #yocto05:59
*** __ad <__ad!~heisenbug@mail.kernel-space.org> has joined #yocto05:59
*** mckoan_ <mckoan_!~marco@host-95-229-48-41.business.telecomitalia.it> has joined #yocto06:00
*** Piraty_ <Piraty_!~irc@user/piraty> has joined #yocto06:01
*** ardo <ardo!~ardo@host-79-24-134-30.retail.telecomitalia.it> has quit IRC (*.net *.split)06:05
*** dkl <dkl!~dkl@prometheus.umask.eu> has quit IRC (*.net *.split)06:05
*** mckoan|away <mckoan|away!~marco@host-95-229-48-41.business.telecomitalia.it> has quit IRC (*.net *.split)06:05
*** risca <risca!~quassel@h-155-4-62-62.a980.priv.bahnhof.se> has quit IRC (*.net *.split)06:05
*** georgem <georgem!sid210681@id-210681.tinside.irccloud.com> has quit IRC (*.net *.split)06:05
*** xcm_ <xcm_!~xcm@user/xcm> has quit IRC (*.net *.split)06:05
*** Xagen <Xagen!~Xagen@99-135-179-142.lightspeed.austtx.sbcglobal.net> has quit IRC (*.net *.split)06:05
*** Amynka <Amynka!~amy@gentoo/developer/amynka> has quit IRC (*.net *.split)06:05
*** piraty <piraty!~irc@user/piraty> has quit IRC (*.net *.split)06:05
*** justache <justache!~justache@user/justache> has quit IRC (*.net *.split)06:05
*** ad__ <ad__!~heisenbug@user/ad/x-9056428> has quit IRC (*.net *.split)06:05
*** thomasd13 <thomasd13!~thomas@DSL01.212.114.255.148.ip-pool.NEFkom.net> has joined #yocto06:11
*** invalidopcode <invalidopcode!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has quit IRC (Remote host closed the connection)06:12
*** invalidopcode <invalidopcode!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has joined #yocto06:12
*** m4ho <m4ho!~m4ho@p5098be52.dip0.t-ipconnect.de> has quit IRC (Quit: WeeChat 3.6)06:13
*** tor <tor!~tor@user/tor> has joined #yocto06:36
*** rob_w_ <rob_w_!~bob@host-82-135-31-73.customer.m-online.net> has joined #yocto07:30
*** dkl <dkl!~dkl@prometheus.umask.eu> has joined #yocto07:34
*** georgem <georgem!sid210681@id-210681.tinside.irccloud.com> has joined #yocto07:34
*** Payam <Payam!~Payam@139.96.255.6> has joined #yocto08:05
*** dreyna4529_b <dreyna4529_b!~dreyna452@2601:646:4200:cfc0:5475:f5fe:aab8:248a> has quit IRC (Ping timeout: 260 seconds)08:06
xcmmoto-timo: i ended up appending to uboot-initial-env with a .bbappend, but.. it doesn't get picked up. in /boot, a uboot.env appears, but that doesn't contain my changes. worse of all, i can't find it anywhere in tmp/08:12
*** nemik_ <nemik_!~nemik@207.237.248.190> has quit IRC (Ping timeout: 246 seconds)08:14
*** nemik_ <nemik_!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto08:14
*** zpfvo <zpfvo!~fvo@i59F5CC3B.versanet.de> has joined #yocto08:16
*** amitk__ <amitk__!~amit@103.208.71.21> has joined #yocto08:18
*** nemik_ <nemik_!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 268 seconds)08:19
*** nemik_ <nemik_!~nemik@207.237.248.190> has joined #yocto08:20
*** amitk <amitk!~amit@103.59.74.51> has quit IRC (Ping timeout: 246 seconds)08:21
PayamHi, Is it possible to develop a yocto project on Windows?08:28
mcfriskPayam: anything is possible and you can make it work, but at least I would not recommend that. Just use Linux. And don't bother with virtual machines for compiling, the performance will be poor and yocto is beast to compile...08:32
Payammcfrisk yes. unfortunately our organization only provides Windows with VM and not even VM is configured correctly.08:34
frosteyesPayam: if you are forced to it, it can be done. Also WSL2 is pretty good. But the virtual filesystem layer is very slow.08:38
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto08:38
mcfriskI would force the feedback to management that to develop Linux products you need to run Linux systems. Been fighting these battles for over 20 years and I would right away quit or not even join an organization which doesn't allow running Linux on developers machines.08:39
*** thomasd13 <thomasd13!~thomas@DSL01.212.114.255.148.ip-pool.NEFkom.net> has quit IRC (Remote host closed the connection)08:42
LetoThe2ndPayam: WSL2 is your only remotely sane bet. i agree with mcfrisk - management that wants you to work without providing adequate tooling needs to either learn about it, or should be deserted.08:42
*** manuel1985 <manuel1985!~manuel198@mobiledyn-62-240-134-31.mrsn.at> has joined #yocto08:42
*** manuel_ <manuel_!~manuel198@mobiledyn-62-240-134-31.mrsn.at> has joined #yocto08:42
LetoThe2nd... imagine being hired as a carpenter, then not getting a hammer because company police is that all work has to be done using screwdrivers. just because your manager is an electrician and the thinks that screwdrivers are like the best tool ever.08:44
PayamLetoThe2nd I am really tired of IT and tbh I dont want anything to do with them any more. Since everytime I ask for a simple thing they want a meeting with me "in 2 weeks"08:53
LetoThe2ndPayam: good time to go looking for other opportunities, then.08:54
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto08:54
paulbarkerPayam: I try to phrase it in terms of how much it is costing the company. At a guess it'd be at least 3x or more work to maintain a build using Yocto Project under Windows, so they're wasting at least 2/3 of what it costs them to employ you if they make you do that08:55
paulbarkerSo they can either hire 2 new staff or give you a Linux build environment08:55
LetoThe2ndpaulbarker: i know that this is a common technique but does not resonate always.08:55
*** Wouter0100 <Wouter0100!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat)08:56
*** Wouter0100 <Wouter0100!~Wouter010@entry.nbg.netvos.nl> has joined #yocto08:57
paulbarkerHonestly, if "giving me the right tools would make me more productive and save the company money, with a payback on the investment within weeks" does not resonate then you have poor management08:57
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto08:57
LetoThe2ndpaulbarker: there are many companies with poor management. especially lower, in a culture that likes processes and tries to avoid all precedence cases.09:00
frosteyesI can only second the others. I have been in a company where I was forced to virtual Linux. It can be done, but it is a PITA and it is just wrong.09:02
frosteyesAnd I think it is a pretty good analogy with tools. E.g. tell management that it is like forcing a carpenter to not use power tools, but only have a handsaw and hammer and some nails. Things can be build, but they take long time, and will never be as good as if you have power tools, and the correct tools for the job.09:05
*** manuel1985 <manuel1985!~manuel198@mobiledyn-62-240-134-31.mrsn.at> has quit IRC (Ping timeout: 256 seconds)09:07
*** manuel_ <manuel_!~manuel198@mobiledyn-62-240-134-31.mrsn.at> has quit IRC (Ping timeout: 260 seconds)09:08
*** manuel1985 <manuel1985!~manuel198@mobiledyn-62-240-134-31.mrsn.at> has joined #yocto09:14
*** manuel_ <manuel_!~manuel198@mobiledyn-62-240-134-31.mrsn.at> has joined #yocto09:14
*** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC (Quit: install gentoo)09:21
*** alicef <alicef!~none@gentoo/developer/alicef> has joined #yocto09:22
*** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC (Client Quit)09:23
*** manuel_ <manuel_!~manuel198@mobiledyn-62-240-134-31.mrsn.at> has quit IRC (Quit: Leaving)09:28
*** alicef <alicef!~none@gentoo/developer/alicef> has joined #yocto09:31
jclsn[m]Has someone successfully integrated the sn65dsi83 mainline driver for the imx8mm?09:31
jclsn[m]I could use an example09:31
*** mckoan_ is now known as mckoan09:32
jclsn[m]I can only find integrations for the old driver online09:33
mckoangood morning09:33
fnsr|2is there a way to make build history catch also changes to the kernel config.txt ? when setting HDMI_MODE = "4" in the local.conf it shows "No changes" while something did change09:51
*** fnsr|2 is now known as d-fens_09:51
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection)09:51
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto09:52
*** d-s-e <d-s-e!~d.s.e@muedsl-82-207-230-034.citykom.de> has joined #yocto09:55
*** nemik_ <nemik_!~nemik@207.237.248.190> has quit IRC (Ping timeout: 252 seconds)09:59
*** nemik_ <nemik_!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto09:59
*** nemik_ <nemik_!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 260 seconds)10:03
*** nemik_ <nemik_!~nemik@207.237.248.190> has joined #yocto10:04
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto10:06
d-fens_hmm, seems no buildhistoey issue, the config.txt in bootfiles hasen't actually changed - what must be done to rebuild this file? rpi-config_git.bb should apply the changes10:21
*** mvlad <mvlad!~mvlad@2a02:2f08:4503:c400:24d7:51ff:fed6:906d> has joined #yocto10:28
d-fens_ok, works now - rm -rf to the rescue...10:29
*** d-s-e <d-s-e!~d.s.e@muedsl-82-207-230-034.citykom.de> has quit IRC (Ping timeout: 256 seconds)10:31
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Ping timeout: 255 seconds)10:36
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto10:40
*** d-s-e <d-s-e!~d.s.e@muedsl-82-207-230-034.citykom.de> has joined #yocto10:45
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto11:06
*** nemik_ <nemik_!~nemik@207.237.248.190> has quit IRC (Ping timeout: 256 seconds)11:09
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto11:12
*** nemik_ <nemik_!~nemik@207.237.248.190> has joined #yocto11:14
*** manuel_ <manuel_!~manuel198@62.99.131.178> has joined #yocto11:32
*** manuel1985 <manuel1985!~manuel198@mobiledyn-62-240-134-31.mrsn.at> has quit IRC (Ping timeout: 246 seconds)11:34
*** dgriego <dgriego!~dgriego@user/dgriego> has quit IRC (Ping timeout: 268 seconds)11:40
*** dgriego <dgriego!~dgriego@user/dgriego> has joined #yocto11:42
*** dgriego <dgriego!~dgriego@user/dgriego> has quit IRC (Ping timeout: 260 seconds)11:46
*** BobPungartnik <BobPungartnik!~Pung@179.177.251.174> has joined #yocto11:47
*** dgriego <dgriego!~dgriego@user/dgriego> has joined #yocto11:48
*** gho <gho!~gho@i59F5CC3B.versanet.de> has joined #yocto11:52
*** BobPungartnik <BobPungartnik!~Pung@179.177.251.174> has quit IRC (Client Quit)11:52
*** d-s-e <d-s-e!~d.s.e@muedsl-82-207-230-034.citykom.de> has quit IRC (Ping timeout: 268 seconds)12:00
*** Qorin <Qorin!~Qorin@2001:1c00:f33:9e00:82d3:19ff:3547:512a> has joined #yocto12:04
*** EarnestSon <EarnestSon!~EarnestSo@49.171.81.222> has joined #yocto12:10
*** fvincenzo <fvincenzo!~fvincenzo@79-68-54-188.dynamic.dsl.as9105.com> has joined #yocto12:10
*** fkuran <fkuran!~fkuran@80.255.7.105> has joined #yocto12:11
*** SKaaj4 <SKaaj4!~SKaaj4@ipbcc1ad32.dynamic.kabel-deutschland.de> has joined #yocto12:12
*** noop <noop!~noop@136.228.208.111> has joined #yocto12:25
noopany reason the kirkstone branch is not on the github mirror?12:26
qschulzhalstead: ^ maybe for you this one? https://github.com/yoctoproject/poky/ no kirkstone branch in the mirror12:28
qschulznoop: is poky the only mirror you've seen with this missing branch?12:29
qschulz(thanks for the report)12:29
*** FredericOuellet <FredericOuellet!~willy562@bras-base-crnypq0201w-grc-01-76-68-181-22.dsl.bell.ca> has joined #yocto12:35
*** d-s-e <d-s-e!~d.s.e@muedsl-82-207-230-034.citykom.de> has joined #yocto12:51
ldericherHow can I tell bitbake that a recipe only applicable for a specific platform?12:54
JaMaCOMPATIBLE_HOST/COMPATIBLE_MACHINE12:55
ldericherJaMa, actually, I mean specific arch, sorry. So I assume COMPATIBLE_ARCH?12:56
noopqschulz: Yes its the only one i have tried12:58
*** noop <noop!~noop@136.228.208.111> has quit IRC (Quit: Client closed)12:58
JaMaldericher: COMPATIBLE_HOST, see examples in oe-core, which make it more clear12:58
*** amitk_ <amitk_!~amit@103.208.69.161> has quit IRC (Ping timeout: 246 seconds)12:59
*** dmoseley <dmoseley!~dmoseley@user-24-96-20-181.knology.net> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)12:59
*** dmoseley <dmoseley!~dmoseley@user-24-96-20-181.knology.net> has joined #yocto13:01
*** dmoseley <dmoseley!~dmoseley@user-24-96-20-181.knology.net> has quit IRC (Client Quit)13:01
*** dmoseley <dmoseley!~dmoseley@user-24-96-20-181.knology.net> has joined #yocto13:03
*** theophile <theophile!~theophile@205.236.76.80> has joined #yocto13:10
theophileHi, I'm creating a recipe which requires gengetopt software in order to build. It tried to add DEPENDS += " gengetopt" to my recipe but there is no success and the recipe building fails because it can't find gengetopt util. Could anyone help me sort that out ?13:13
rburtontheophile: does it need to run it at build time? you mean gengetopt-native if so.13:13
theophileIt does because I would like the file built by gengetopt to be always the most recent version13:14
theophileTherefore, they aren't included in my git repo. An easy fix could be to include them but I don't trust myself to ensure they are up to date13:14
lderichermhhhhh, so I have "foo.bb", "files/foo_1.0_arm.tar.gz", and "files/foo_1.1_aarch64.tar.gz". Will this work and automatically install foo v1.0 on an ARM platform, and v1.1 on an AARCH64?13:14
theophileBut maybe it's a bad decision13:14
rburtontheophile: just DEPENDS=gengetopt-native if you want something to run at build time13:15
ldericher… btw, my SRC_URI is `file://${PN}_${PV}_${TARGET_ARCH}.tar.gz`13:15
theophileI've seen the -native with the rust compiler. Do you have any ressource to explain the difference with a normal recipe ?13:15
rburtonnative recipes run on the build host13:16
rburtonyou can't run a binary thats been built for the target at build time13:16
theophileCan it be appended to any recipe ?13:16
rburtonany recipe that does BBCLASSEXTEND="native" to magically make a native version13:17
theophileOkay, that's good to know. Thanks !13:17
theophileIt works like a charm :)13:17
*** theophile99 <theophile99!~theophile@82.66.178.189> has joined #yocto13:24
*** theophile99 is now known as tbornon13:25
*** theophile <theophile!~theophile@205.236.76.80> has quit IRC (Ping timeout: 260 seconds)13:27
d-fens_is there a way to have "bitbake -c cve_check myimage" only log unpatched cves?13:29
d-fens_i want to send out daily mails if the command returns something13:30
*** tbornon <tbornon!~theophile@82.66.178.189> has quit IRC (Ping timeout: 260 seconds)13:32
ldericherI'm stuck. I ended up with a recipe 'foo_1.0.bb' using `COMPATIBLE_MACHINE="arm"` and 'foo_1.1.bb' using `COMPATIBLE_MACHINE="aarch64"`. Still, `bitbake foo` creates a warning that `foo_1.0` doesn't have the source for my aarch64 build target.13:39
ldericherI feel like just ignoring the warning isn't the right way13:40
*** theophile <theophile!~theophile@205.236.76.80> has joined #yocto13:41
*** theophile <theophile!~theophile@205.236.76.80> has quit IRC (Client Quit)13:41
*** goliath <goliath!~goliath@user/goliath> has joined #yocto13:41
*** mixfix41 <mixfix41!~sdenynine@user/mixfix41> has joined #yocto13:42
*** rob_w_ <rob_w_!~bob@host-82-135-31-73.customer.m-online.net> has quit IRC (Quit: Leaving)13:43
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Quit: Leaving)13:48
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto13:53
*** noop <noop!~noop@136.228.208.107> has joined #yocto13:53
*** mattes-bru <mattes-bru!~mattes-br@ksapp01-nat-ersatz.iosb.fraunhofer.de> has joined #yocto13:56
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)13:57
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto13:57
*** fvincenzo <fvincenzo!~fvincenzo@79-68-54-188.dynamic.dsl.as9105.com> has quit IRC (Quit: Ping timeout (120 seconds))13:58
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)14:03
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto14:03
*** fvincenzo <fvincenzo!~fvincenzo@79-68-54-188.dynamic.dsl.as9105.com> has joined #yocto14:10
*** noop <noop!~noop@136.228.208.107> has quit IRC (Quit: Client closed)14:12
*** d-s-e <d-s-e!~d.s.e@muedsl-82-207-230-034.citykom.de> has quit IRC (Ping timeout: 252 seconds)14:27
*** Qorin <Qorin!~Qorin@2001:1c00:f33:9e00:82d3:19ff:3547:512a> has quit IRC (Quit: Client closed)14:28
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto14:30
*** ecdhe <ecdhe!~ecdhe@user/ecdhe> has quit IRC (Read error: Connection reset by peer)14:31
*** ecdhe_ <ecdhe_!~ecdhe@user/ecdhe> has joined #yocto14:31
gsalazarHi I'm trying to get yocto to compile a binary for a secondary ARM microprocessor as a dependency for the main image. I've read the yocto manual's multiconfig documentation but I it is still not clear on how to signal that a different compiler and compiler options should be used. Anyone has used it or knows about any examples that I could check?14:35
LetoThe2ndgsalazar: its not exacly bare metal on the secondary but zephyr, but it should give you the idea: https://youtu.be/kWwzAq0x4xY14:37
gsalazarLetoThe2nd: Thank you, I'll take a look at it14:39
LetoThe2ndgsalazar: you can also look at the bare metal hello world that is already in poky, and then essential drop that in for zephyr in the example.14:40
*** noop <noop!~noop@136.228.208.107> has joined #yocto14:42
*** EarnestSon <EarnestSon!~EarnestSo@49.171.81.222> has quit IRC (Quit: Client closed)14:43
rburtongsalazar: worst case (and what meta-arm currently does) is to use meta-arm-toolchain and DEPEND on the binary M compiler.  have a look in meta-arm at eg the trusted-firmware-m recipe.14:45
*** d-s-e <d-s-e!~d.s.e@muedsl-82-207-230-034.citykom.de> has joined #yocto14:46
*** d-s-e <d-s-e!~d.s.e@muedsl-82-207-230-034.citykom.de> has quit IRC (Client Quit)14:46
*** Wouter0100 <Wouter0100!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat)14:46
*** Wouter0100 <Wouter0100!~Wouter010@entry.nbg.netvos.nl> has joined #yocto14:47
*** manuel_ <manuel_!~manuel198@62.99.131.178> has quit IRC (Read error: Connection reset by peer)15:04
*** manuel1985 <manuel1985!~manuel198@62.99.131.178> has joined #yocto15:04
*** zpfvo <zpfvo!~fvo@i59F5CC3B.versanet.de> has quit IRC (Ping timeout: 268 seconds)15:05
*** FredericOuellet <FredericOuellet!~willy562@bras-base-crnypq0201w-grc-01-76-68-181-22.dsl.bell.ca> has quit IRC (Quit: Client closed)15:10
*** Net147 <Net147!~Net147@user/net147> has quit IRC (Read error: Connection reset by peer)15:11
*** Net147 <Net147!~Net147@167-179-157-192.a7b39d.syd.nbn.aussiebb.net> has joined #yocto15:11
Saur[m]ldericher: The problem is that `COMPATIBLE_MACHINE="arm"` is not specific enough. `COMPATIBLE_MACHINE` is actually a regular expression and `arm` will match the `armv8` used for `aarch64`. If you are on Kirkstone or later you can use `bitbake-getvar --value MACHINEOVERRIDES` to get the values that `COMPATIBLE_MACHINE` is matching against. My guess is that you need to use `armv7` or something like that.15:18
*** zpfvo <zpfvo!~fvo@i59F5CC3B.versanet.de> has joined #yocto15:19
*** fvincenzo <fvincenzo!~fvincenzo@79-68-54-188.dynamic.dsl.as9105.com> has quit IRC (Ping timeout: 260 seconds)15:24
*** sgw <sgw!~swold_loc@user/sgw> has quit IRC (Ping timeout: 260 seconds)15:24
*** sgw <sgw!~swold_loc@user/sgw> has joined #yocto15:25
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)15:28
*** sgw <sgw!~swold_loc@user/sgw> has quit IRC (Ping timeout: 260 seconds)15:31
qschulzldericher: also, have a look at MACHINEOVERRIDES as used in FILESOVERRIDES15:40
qschulzyou could have the exact same recipe but the file fetched by Bitbake would be different depending on the architecture of the target15:41
qschulzthat is done by using sub directories where you'd usually directly put your files (probably files/)15:41
qschulzthere have the same name for all tarballs, just in different paths: files/armv7 for arm32 (maybe, don't know exactly what wou;d be the best match) and files/aarch64 for the arm64 one15:42
qschulzldericher: https://summit.yoctoproject.org/media/yocto-project-summit-2022-05/submissions/SCYYWD/resources/Demystifying_the_OVERRIDES_mec_2lZOP3n.pdf starting slide 8315:43
*** fvincenzo <fvincenzo!~fvincenzo@217.140.99.251> has joined #yocto15:44
*** Cir0X[m] <Cir0X[m]!~cir0xmatr@2001:470:69fc:105::2:ceeb> has joined #yocto15:44
*** sgw <sgw!~swold_loc@user/sgw> has joined #yocto15:46
*** nemik_ <nemik_!~nemik@207.237.248.190> has quit IRC (Ping timeout: 256 seconds)15:49
*** nemik_ <nemik_!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto15:49
*** fvincenzo <fvincenzo!~fvincenzo@217.140.99.251> has quit IRC (Ping timeout: 260 seconds)15:50
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)15:50
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto15:51
*** nemik_ <nemik_!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 268 seconds)15:54
*** nemik_ <nemik_!~nemik@207.237.248.190> has joined #yocto15:54
kergothRandom question: does bitbake-getvar not have a short form of --value to avoid confusion of -v sometimes being verbose, version, etc?15:57
*** fvincenzo <fvincenzo!~fvincenzo@79-68-54-188.dynamic.dsl.as9105.com> has joined #yocto16:02
*** Payam <Payam!~Payam@139.96.255.6> has quit IRC (Quit: Client closed)16:09
RPkergoth: that sounds familiar16:12
*** fkuran <fkuran!~fkuran@80.255.7.105> has quit IRC (Quit: Client closed)16:18
*** nemik_ <nemik_!~nemik@207.237.248.190> has quit IRC (Ping timeout: 256 seconds)16:19
*** nemik_ <nemik_!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto16:19
*** invalidopcode <invalidopcode!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has quit IRC (Remote host closed the connection)16:21
*** kscherer <kscherer!~kscherer@bras-base-otwaon1146w-grc-19-184-147-77-157.dsl.bell.ca> has joined #yocto16:21
*** invalidopcode <invalidopcode!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has joined #yocto16:21
*** fkuran <fkuran!~fkuran@80.255.7.105> has joined #yocto16:23
*** nemik_ <nemik_!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 260 seconds)16:24
*** nemik_ <nemik_!~nemik@207.237.248.190> has joined #yocto16:24
*** amelius <amelius!~quassel@147.161.165.34> has joined #yocto16:30
*** amelius is now known as aduda16:31
kergothSeemed odd to have to do the long argument every time. Maybe add -b and --bare as alternatives to --value?16:34
* kergoth shrugs16:34
kergothI also wonder about making --flag and --unexpand *imply* --value rather than erroring out without it16:36
*** aduda <aduda!~quassel@147.161.165.34> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)16:51
*** tor <tor!~tor@user/tor> has quit IRC (Quit: Leaving)16:52
RPkergoth: happy to consider patches. From memory I put a base implementation out there thinking we'd iterate from there16:56
*** olani_ <olani_!~olani@66.159.215.7> has quit IRC (Ping timeout: 248 seconds)16:56
RPkergoth: I think I left -v out just because it was potentially confusing, easy to add, hard to remove later16:56
*** gho <gho!~gho@i59F5CC3B.versanet.de> has quit IRC (Quit: Leaving.)16:58
*** zpfvo <zpfvo!~fvo@i59F5CC3B.versanet.de> has quit IRC (Quit: Leaving.)17:04
*** SKaaj4 <SKaaj4!~SKaaj4@ipbcc1ad32.dynamic.kabel-deutschland.de> has quit IRC (Quit: Client closed)17:08
*** mckoan is now known as mckoan|away17:17
*** dreyna4529_b <dreyna4529_b!~dreyna452@2601:646:4200:cfc0:1884:871e:51cf:2848> has joined #yocto17:19
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)17:20
* RP wonders how https://git.yoctoproject.org/poky/commit/?h=master-next&id=715501c00c0feb91ed16adfb095b7d4166a6914e would go down17:20
*** noop <noop!~noop@136.228.208.107> has quit IRC (Quit: Client closed)17:21
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Quit: Leaving)17:21
RPbasically to stop people abusing LAYERSERIES_COMPAT17:21
frayno objections here17:22
qschulzit becomes VERY important to keep the next releases name secret :D17:23
kanavinRP: what does the patch do exactly?17:23
kanavinwhat's going to happen if that phytec layer is given to it?17:23
RPkanavin: it will given an error or warning about the layer compatibility not looking right17:24
RPkanavin: basically it deletes the LAYERSERIES_COMPAT variables out the datastore as they layers are parsed so they can't be referenced by anything else17:25
kanavinRP: is it possible to simply use the value verbatim, without variable expansion?17:25
RPkanavin: I wondered about that but they'd then use := to avoid that17:26
*** fvincenzo <fvincenzo!~fvincenzo@79-68-54-188.dynamic.dsl.as9105.com> has quit IRC (Quit: Client closed)17:26
*** fvincenzo <fvincenzo!~fvincenzo@79-68-54-188.dynamic.dsl.as9105.com> has joined #yocto17:26
qschulzRP: would this also prevent overriding another layer's LAYERSERIES_COMPAT?17:27
qschulzbecause we had to do this at my previous company17:27
qschulzwe could also have patched the "upstream" layer instead, but that was more convenient at the time17:27
qschulz(but I didn't like it :) )17:27
RPqschulz: it might still allow that to work, not 100% sure17:28
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto17:28
*** nemik_ <nemik_!~nemik@207.237.248.190> has quit IRC (Ping timeout: 260 seconds)17:33
*** nemik_ <nemik_!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto17:34
vmesonrburton: asked somewhere about  removing rust-llvm and using our llvm recipe.  I replied in my talk that I looked at that when we first merged rust into oe-core but not since. Has anyone else taken time to check that out?17:38
*** nemik_ <nemik_!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 256 seconds)17:38
*** nemik_ <nemik_!~nemik@207.237.248.190> has joined #yocto17:39
*** PhoenixMage <PhoenixMage!~phoenix@206.83.114.214> has quit IRC (Ping timeout: 268 seconds)17:39
*** PhoenixMage <PhoenixMage!~phoenix@206.83.123.188> has joined #yocto17:40
*** aleksandarsimono <aleksandarsimono!~aleksanda@79.142.183.177> has joined #yocto17:43
Saur[m]RP: I rely on being able to set `LAYERSERIES_COMPAT` for other layers. Our platform is currently based on Kirkstone. During the ~6 months of preparations for the next major Poky release I use an adaptation layer (weirdly named as `meta-axis-master` since it was originally used to build with master of Poky) where I do all changes needed to make our platform build with the next Poky release. To be able to do this, this adaptation layer uses17:43
Saur[m]`LAYERSERIES_COMPAT_axis:append = " ${LAYERSERIES_COMPAT_axis-master}"` for all our layers in the platform so that they can build with the same version of Poky as the adaptation layer is compatible with.17:43
RPSaur[m]: that will proabably break :(17:44
*** PhoenixMage <PhoenixMage!~phoenix@206.83.123.188> has quit IRC (Ping timeout: 256 seconds)17:46
Saur[m]:( I am rather fond of this solution as it means I do not have to lie and set `LAYERSERIES_COMPAT` to include "langdale" for our platform layers before they actually do support Langdale.17:46
*** PhoenixMage <PhoenixMage!~phoenix@206.83.113.237> has joined #yocto17:48
qschulzSaur[m]: IIRC you could have LAYERSERIES_COMPAT_axis:append = "langdale" in your meta-axis-master layer.conf to lie in one place only17:48
qschulzIIRC the order in whcih the layers are parsed matter in there17:49
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Quit: Leaving)17:49
RPright, the append isn't the issue, the use of LAYERSERIES_COMPAT is. You could just use a different variable name?17:49
qschulzbut that was like 2/3 years ago and I don't have access to the source code anymore17:49
aleksandarsimonoHello everyone.17:50
aleksandarsimonoI'm having problem that I cannot solve for days. I have precompiled mcp2515-can2.dtbo file for Raspberry Pi3 (I dont have .dts) that I need to include in my root partition (/boot/overlay) on RPi3. After looking through meta-raspberrypi layer I found out that dtbo's are getting fetched through recipes-bsp/bootfiles/rpi-bootfiles.bb file, so I17:50
aleksandarsimonocreated rpi-bootfiles.bbappend file in my own recipe that appends to SRC_URI variable and adds my custom mcp2515-can2.dtbo file to bootfiles. Then I added RPI_KERNEL_DEVICETREE_OVERLAYS:append = " overlays/mcp2515-can2.dtbo" to my local.conf and when i run the build I get compile error: No rule to make target17:50
aleksandarsimono'arch/arm/boot/dts/overlays/mcp2515-can2.dtbo'17:50
RPI'm really torn (again) on the change to be honest. I just really object to what people are doing in layers to subvert a core feature17:50
Saur[m]Well, it depends on if it will continue to work to set LAYERSERIES_COMPATfrom one layer for another. And we do have tight control of the order of our layers in bblayers.conf, so the adaptation layer is guaranteed to be read before any of the other layers.17:51
RPSaur[m]: I think that works with the patch17:51
qschulzaleksandarsimono: just check where RPI_KERNEL_DEVICETREE_OVERLAYS is used and add your install step without the compilation step17:52
Saur[m]RP: I'll try the patch.17:52
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat)17:54
aleksandarsimonoqschulz I'm not sure how to do that17:54
rburtonvmeson: rust people at work say that upstream llvm should work if you're building releases17:55
vmesonrburton: nice. That will help tighten things up. I'll give it a go, er llvm, err you know what I mean.17:57
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 260 seconds)17:57
*** PhoenixMage <PhoenixMage!~phoenix@206.83.113.237> has quit IRC (Ping timeout: 260 seconds)17:57
kanavinvmeson, I suppose you don't want to build both llvm-native and rust-llvm-native, but llvm-native is not actually providing llvm, it only provides native llvm-config executable for the sake of building target llvm17:58
kanavin(which is very quick and doesn't affect build times)17:58
*** PhoenixMage <PhoenixMage!~phoenix@206.83.122.100> has joined #yocto17:59
vmesonkanavin: ah, so we shouldn't expect build time reduction it seems. It'll still save on largely duplicated downloads.17:59
Saur[m]RP: I can confirm that your change breaks my use case. :( `ERROR: Layer axis is not compatible with the core layer which only supports these series: langdale (layer is compatible with ${LAYERSERIES_COMPAT_axis-master} kirkstone)`18:00
*** fvincenzo <fvincenzo!~fvincenzo@79-68-54-188.dynamic.dsl.as9105.com> has quit IRC (Quit: Client closed)18:00
kanavinvmeson, rust download itself completely dwarfs any savings18:00
*** olani_ <olani_!~olani@2a02:aa1:1020:87a8:6140:e490:e1cb:293f> has joined #yocto18:00
*** rwoaenzkt <rwoaenzkt!~olani@2a02:aa1:1020:87a8:6140:e490:e1cb:293f> has joined #yocto18:01
vmesonkanavin: I suppose.18:01
RPSaur[m]: can you rename to a different variable name that doesn't have LAYERSERIES_COMPAT in it?18:01
qschulzaleksandarsimono: I believe you cannot use RPI_KERNEL_DEVICETREE_OVERLAYS for what you want18:01
qschulzbecause it's just added to KERNEL_DEVICETREE which I believe is used to tell the kernel recipe to build dtb/dtbos18:03
qschulzsince you don't have the sources, it won't find it and error out18:03
qschulzwithout looking too much into it, I'd create a recipe just to add this dtbo into the proper directory18:03
Saur[m]RP: That seems to work, but now I realized that your change breaks what devtool does too: `ERROR: Layer workspacelayer is not compatible with the core layer which only supports these series: langdale (layer is compatible with ${LAYERSERIES_COMPAT_core})`18:04
RPSaur[m]: there is a patch for that in master-next18:04
Saur[m]Ah, ok. I just cherry-picked the bitbake change.18:04
aleksandarsimonoqschulz It doesnt work that way because I need to add to boot partition and not to rootfs18:06
LetoThe2ndaleksandarsimono: https://docs.yoctoproject.org/ref-manual/variables.html#term-IMAGE_BOOT_FILES18:08
qschulzaleksandarsimono: I very much believe that everything is put into the image rootfs and then wic splits it by itself18:08
qschulzthanks to --source bootimg-partition18:08
LetoThe2ndqschulz: see the magic variable :-)18:08
qschulzLetoThe2nd: perfect, nice documentation on this18:09
Saur[m]RP: Ok, that solved that. However, there is a drawback with that solution: when we upgrade to the next major release, all developer's build environment will fail since their workspace layers are no longer automatically adapting to the new release name.18:10
vmesonkanavin: github.com.llvm.llvm-project.git 2.4 GB -- rustc-1.xx.src.tar.xz: 135 MB   rust-std-1.64.0-x86_64-unknown-linux-gnu.tar.xz 27.4 MB -- am I missing something?18:10
qschulzLetoThe2nd: I believe IMAGE_BOOT_FILES should be modified in the image recipe or in a configuration file to be taken into account18:10
qschulzSaur[m]: I'm not sure that's an issue?18:10
qschulzthat forces your devs to resync the base version18:11
qschulzotherwise your devs are debugging with devtool a version that isn't actually being used anymore18:11
Saur[m]Well, it means they will have to manually modify workspace/conf/layer.conf, a layer most of them don't even know is actually a layer...18:12
qschulzSaur[m]: they shouldn't, thats my whole point18:12
* vmeson wipes out his downloads and checks the data above.18:12
qschulzSaur[m]: remove your whole devtool workspace between yocto upgrade?18:13
*** neil499 <neil499!~neil499@c-66-31-16-167.hsd1.ma.comcast.net> has joined #yocto18:13
*** PhoenixMage <PhoenixMage!~phoenix@206.83.122.100> has quit IRC (Ping timeout: 256 seconds)18:14
kanavinvmeson, so where would the savings come from if rust is using upstream llvm? I might be missing something too :)18:15
*** amitk__ <amitk__!~amit@103.208.71.21> has quit IRC (Ping timeout: 256 seconds)18:15
Saur[m]That has never been needed before. At least in our case, the developers typically only use it together with devtool modify to (more or less) temporarily make the source available for a recipe or two. With the exception when someone changes the bitbake syntax ;) there is only a small bbappend per active recipe. In my case, most of the times, the workspace layer is just an empty layer.18:16
*** PhoenixMage <PhoenixMage!~phoenix@206.83.113.237> has joined #yocto18:16
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto18:16
Saur[m]And when I say empty, I mean without any active bbappends. The attics directory typically contains a lot of old source directories.18:17
RPSaur[m]: Right, I'm torn on the migration issue but the patch as is is probably as close as we can get18:17
kanavinI'd much rather not see that variable become meaningless.18:17
RPkanavin: that is why I'm a bit upset about this18:18
Saur[m]RP: Yeah, I am not saying the devtool regression should block the change, I am merely mentioning it as it may cause some confusion from developers (I know it will for mine).18:19
*** justache- is now known as justache18:19
*** dreyna4529_b <dreyna4529_b!~dreyna452@2601:646:4200:cfc0:1884:871e:51cf:2848> has quit IRC (Quit: Client closed)18:19
kanavinSaur[m], it is extremely unlikely anyone else is using LAYERSERIES_COMPAT in workspace this way18:20
kanavinand you're well aware, and can mitigate ahead of time18:20
*** dreyna4529_b <dreyna4529_b!~dreyna452@2601:646:4200:cfc0:1884:871e:51cf:2848> has joined #yocto18:20
Saur[m]I was referring to the devtool case. Since my adaptation layer case works by changing to another variable name, that is fine.18:21
*** tor <tor!~tor@user/tor> has joined #yocto18:22
kanavinSaur[m], ah I didn't look closely at where LAYERSERIES_CORENAMES comes from18:24
*** neil499 <neil499!~neil499@c-66-31-16-167.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 260 seconds)18:24
*** PhoenixMage <PhoenixMage!~phoenix@206.83.113.237> has quit IRC (Ping timeout: 256 seconds)18:26
RPkanavin: I handle CORENAMES separately to stop people switching to that since I'm making that obvious in the devtool fixes for core18:26
*** PhoenixMage <PhoenixMage!~phoenix@206.83.122.100> has joined #yocto18:28
Saur[m]RP: Btw, there is a typo in the commit message for the bitbake change: "thi is mechanism" -> "this mechanism"18:31
RPSaur[m]: thanks, fixed18:32
Saur[m]There is a corresponding typo in the comment in the code: "this is mechanism" -> "this mechanism"18:32
kanavinRP: hashequiv is awesome, I fixed the x86 test fail in python, and because the fix is in the test and not in the code, the rebuild shortcuts to the image18:34
RPkanavin: it is lovely when it works :)18:36
RPSaur[m]: ah, right. Also fixed18:37
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)18:39
*** fkuran <fkuran!~fkuran@80.255.7.105> has quit IRC (Quit: Client closed)18:41
hsvIf i had a http proxy (say squid maybe), can bitbake be told to use it?18:46
hsvafter googling on this i'm a bit confused what goes on under the hood, and if git needs to be configured separately to use the proxy.18:47
*** Wouter0100 <Wouter0100!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat)18:51
*** ptsneves <ptsneves!~Thunderbi@031011128073.dynamic-3-poz-k-0-2-0.vectranet.pl> has joined #yocto18:52
*** Wouter0100 <Wouter0100!~Wouter010@entry.nbg.netvos.nl> has joined #yocto18:52
*** tor <tor!~tor@user/tor> has quit IRC (Remote host closed the connection)18:52
RPhsv: bitbake will respect http_proxy from the environment19:13
hsvRP: great, thanks i'll look into it then19:15
*** manuel_ <manuel_!~manuel198@62.99.131.178> has joined #yocto19:18
*** demirok <demirok!~bell@user/demirok> has joined #yocto19:19
*** manuel1985 <manuel1985!~manuel198@62.99.131.178> has quit IRC (Ping timeout: 260 seconds)19:20
*** florian_kc <florian_kc!~florian@dynamic-093-133-027-134.93.133.pool.telefonica.de> has joined #yocto19:22
*** manuel_ <manuel_!~manuel198@62.99.131.178> has quit IRC (Ping timeout: 260 seconds)19:31
*** nemik_ <nemik_!~nemik@207.237.248.190> has quit IRC (Ping timeout: 260 seconds)19:34
JPEWRP: I didn't follow what you meant by missing a bb.util19:39
*** nemik_ <nemik_!~nemik@207.237.248.190> has joined #yocto19:39
*** aleksandarsimono <aleksandarsimono!~aleksanda@79.142.183.177> has quit IRC (Quit: Client closed)19:39
*** invalidopcode <invalidopcode!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has quit IRC (Remote host closed the connection)19:42
*** invalidopcode <invalidopcode!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has joined #yocto19:42
*** PhoenixMage <PhoenixMage!~phoenix@206.83.122.100> has quit IRC (Ping timeout: 260 seconds)19:51
*** PhoenixMage <PhoenixMage!~phoenix@206.83.113.237> has joined #yocto19:53
*** neil499 <neil499!~neil499@c-66-31-16-167.hsd1.ma.comcast.net> has joined #yocto19:53
RPJPEW: one of the commits referenced a bb.utils.<function> and I didn't see a commit adding it?19:56
JPEWbb.utils.process_profilelog ? Already exists19:57
*** olani_ <olani_!~olani@2a02:aa1:1020:87a8:6140:e490:e1cb:293f> has quit IRC (Ping timeout: 252 seconds)19:58
*** rwoaenzkt <rwoaenzkt!~olani@2a02:aa1:1020:87a8:6140:e490:e1cb:293f> has quit IRC (Ping timeout: 256 seconds)19:59
RPJPEW: oh, right. Sorry, I'm getting confused19:59
* RP even wrote that function :(19:59
JPEWno worries :)19:59
*** neil499 <neil499!~neil499@c-66-31-16-167.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 260 seconds)20:02
JPEWRP: Dropping those two patches helped a lot! 11.5s -> 16.5s now20:05
JPEWIt almost makes me think I have a bug that's preventing it from actually saving the extra parsing data.....20:06
JPEWRP: Should we make this a CookerFeature so it can be more easily toggled?20:08
JPEWAnd I think my name of "Siggen"RecipeInfo is not great20:09
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto20:09
*** PhoenixMage <PhoenixMage!~phoenix@206.83.113.237> has quit IRC (Ping timeout: 268 seconds)20:11
*** PhoenixMage <PhoenixMage!~phoenix@206.83.123.25> has joined #yocto20:12
*** PhoenixMage <PhoenixMage!~phoenix@206.83.123.25> has quit IRC (Ping timeout: 260 seconds)20:19
*** PhoenixMage <PhoenixMage!~phoenix@206.83.114.27> has joined #yocto20:20
*** ptsneves <ptsneves!~Thunderbi@031011128073.dynamic-3-poz-k-0-2-0.vectranet.pl> has quit IRC (Ping timeout: 256 seconds)20:26
RPJPEW: I was thinking we should probably not merge those two! I think making it a cooker feature might be a good move. I agree naming needs thought and is hard20:27
RPJPEW: siggen might be ok20:28
*** PhoenixMage <PhoenixMage!~phoenix@206.83.114.27> has quit IRC (Ping timeout: 246 seconds)20:29
*** PhoenixMage <PhoenixMage!~phoenix@206.83.123.25> has joined #yocto20:31
RPJPEW: I was interested in the shutdown patches, I wondered if a race was possible there but haven't looked into it yet20:34
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)20:34
*** Estrella <Estrella!~quassel@075-081-061-082.res.spectrum.com> has quit IRC (Ping timeout: 265 seconds)20:35
JPEWI'll look it over again and give it a though20:35
JPEWThe event one should be safe20:35
JPEWThe shutdown thread might possibly race; need to think20:36
RPJPEW: I was worried syncthread needs to run after the parsers exit since only at that point have they written the code parser caches it is syncing20:37
*** Estrella <Estrella!~quassel@cpe-24-26-195-197.hot.res.rr.com> has joined #yocto20:38
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto20:40
JPEWIIUC, the main thread is done pulling things from the queue before that thread starts; it will "drain" the queue to keep the child processes from getting stuck, but those are just discarded and don't make it into the stack anyway20:40
RPJPEW: the syncthread doesn't care about that. It cares about the parser processes having written their code parser caches20:41
JPEWAh, I didn't realize it was passing data out of band of the queue20:41
RPJPEW: ah, I'm getting confused again I think :/20:42
RPJPEW: I was thinking this was for bb.codeparser.parser_cache_savemerge() which calls into cache.py:save_merge() which works off a listdir()20:43
RPJPEW: we could really put that into it's own thread20:43
JPEWYa, maybe20:45
*** Estrella <Estrella!~quassel@cpe-24-26-195-197.hot.res.rr.com> has quit IRC (Ping timeout: 260 seconds)20:46
*** Estrella <Estrella!~quassel@cpe-24-26-195-197.hot.res.rr.com> has joined #yocto20:46
*** Guest70 <Guest70!~Guest70@134.41.15.199> has joined #yocto20:50
*** mattes-bru <mattes-bru!~mattes-br@ksapp01-nat-ersatz.iosb.fraunhofer.de> has quit IRC (Remote host closed the connection)21:06
JPEWRP: Ok updated the branch21:07
*** mattes-bru <mattes-bru!~mattes-br@ksapp01-nat-ersatz.iosb.fraunhofer.de> has joined #yocto21:07
*** jdavid75 <jdavid75!~jdavid75@179.110.5.253> has joined #yocto21:11
jdavid75hi there, looking for advice debugging yocto build error, just trying to replicate my colleague's successful build21:13
*** invalidopcode <invalidopcode!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has quit IRC (Remote host closed the connection)21:13
*** invalidopcode <invalidopcode!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has joined #yocto21:14
*** mattes-b_ <mattes-b_!~mattes-br@ksapp01-nat-ersatz.iosb.fraunhofer.de> has joined #yocto21:18
*** mattes-bru <mattes-bru!~mattes-br@ksapp01-nat-ersatz.iosb.fraunhofer.de> has quit IRC (Ping timeout: 268 seconds)21:22
*** Estrella <Estrella!~quassel@cpe-24-26-195-197.hot.res.rr.com> has quit IRC (Ping timeout: 260 seconds)21:31
*** Estrella <Estrella!~quassel@cpe-24-26-195-197.hot.res.rr.com> has joined #yocto21:31
*** Saur <Saur!~pkj@nebula.axis.com> has quit IRC (Remote host closed the connection)21:43
rburtonjdavid75: give details and someone might be able to help21:45
jdavid75just nuked my yocto folder in frustration and trying from scratch, will come back here with deets if/when reoccurs21:46
rburtonrandom build failures can be from recipes that really don't like building on an existing build tree, which is not uncommon and why you should always do out-of-tree builds21:50
jdavid75do you have a link for best-practice setup of out-of-tree builds?21:52
*** mark__ <mark__!~mark@142.189.254.41> has joined #yocto21:55
*** mark__ is now known as mark_L21:55
rburtonautotools, meson and cmake do it automatically21:55
rburtonautotools-brokensep is for autotools-using recipes which don't do it21:56
jdavid75oh... failure was on a recipe that I had nothing to do with21:57
jdavid75just trying to replicate base state before starting to work21:57
jdavid75a recipe that nobody at our company had anything to do with, just came in with the NXP BSP21:57
rburtonharass nxp if you paid for it :)21:58
mark_LHi, Is there a way to list all the available/enabled DISTRO_FEATURES items? My image pulls in pulseaudio after I migrated our Yocto base to Kirkstone. Trying to see if there's a new destro feature got pulled in somewhere21:59
rburtonbitbake-getvar DISTRO_FEATURES22:00
rburtonworth skimming the migration guide as that talks about new features that were added22:00
mark_LThanks rburton, I learn a new trick today!22:01
rburtonalso, this is why you should write your own distro configuration so you control the distro features22:01
*** aleksandarsimono <aleksandarsimono!~aleksanda@79.142.183.177> has joined #yocto22:04
*** starblue <starblue!~juergen@dslb-088-078-105-208.088.078.pools.vodafone-ip.de> has joined #yocto22:06
*** PhoenixMage <PhoenixMage!~phoenix@206.83.123.25> has quit IRC (Ping timeout: 260 seconds)22:10
*** PhoenixMage <PhoenixMage!~phoenix@206.83.114.27> has joined #yocto22:12
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto22:16
*** kpo <kpo!~kpo@83.18.228.34> has quit IRC (Read error: Connection reset by peer)22:38
*** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has joined #yocto22:41
*** DvorkinDmitry <DvorkinDmitry!~dvorkin@5.167.98.73> has joined #yocto22:46
DvorkinDmitryis it correct to write DEPEND = "mc:OTHERARCH:somerecipe" ?22:48
*** mvlad <mvlad!~mvlad@2a02:2f08:4503:c400:24d7:51ff:fed6:906d> has quit IRC (Remote host closed the connection)22:49
hsvCan bitbake be told *not* to use https? (via a http proxy)22:54
hsvThe problem is the proxy only caches http requests.22:55
JPEWunset http_proxy?22:59
hsvi mean still route via the proxy but use http instead of https, so the object can be cached.23:00
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has quit IRC (Ping timeout: 256 seconds)23:01
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Ping timeout: 260 seconds)23:02
RPhsv: you could probably put something in MIRRORS to make it do that23:06
RPthere are probably servers which don't support anything but https now23:06
hsvyes i imagine that too, the server could issue a redirect and we are stuck in a loop.23:08
RPJPEW: I've separated out a couple of bits of our patches and sent them to the list. Gives us something to test on more easily I hope!23:12
RPJPEW: your event one looks good to me, not sure about sync and whether we should have a bigger rework there yet23:12
RPJPEW: our patches look to be about the same speed, 4.4s -> 8s for my test on oe-core23:35
*** Starfoxxes <Starfoxxes!~Starfoxxe@ip-037-201-004-167.um10.pools.vodafone-ip.de> has quit IRC (Ping timeout: 248 seconds)23:37
RPJPEW: interestingly your on disk cache file is 96MB compared to my 60something MB file23:42
JPEWHmm, strange. I wonder why23:43
JPEWIt should be fully deduplicted afaict23:43
RPJPEW: I was a little surprised, not looked into what happened23:53
RPJPEW: oh, it is because we dropped the all in one pickle patch23:54
JPEWAh ok.23:54
RPJPEW: my patch works around that with references in later objects23:54
RPETOOMANYPATCHES23:55
JPEWWe can do the same protocol to serialize to the file as we use between the parser tasks and cooker if we want23:56
RPJPEW: I was just wondering that23:56
JPEWThe large pickle is slower?23:56
JPEWThat also is sus23:57
RPJPEW: in my tests, yes23:57
RPI think it is because it allows us to interleave the IO23:57
RPwhich makes loading faster too23:57
JPEWHmm, ok. Have to take a look23:58

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!