Friday, 2023-01-06

RPJPEW: I think python is a bit cleverer about how it handles the gc in forks but I'm still worried about the memory usage, particularly as I think the kernel OOM killer might not understand the shared pages00:01
*** azcraft <azcraft!~AzCraft@195.214.248.221> has quit IRC (Remote host closed the connection)00:05
*** florian_kc <florian_kc!~florian@dynamic-002-243-037-045.2.243.pool.telefonica.de> has quit IRC (Ping timeout: 268 seconds)00:13
*** yann <yann!~yann@88.120.44.86> has quit IRC (Remote host closed the connection)00:27
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Remote host closed the connection)00:38
*** sakoman <sakoman!~steve@dhcp-72-253-5-74.hawaiiantel.net> has quit IRC (Quit: Leaving.)01:14
*** nerdboy <nerdboy!~nerdboy@gentoo/developer/nerdboy> has quit IRC (Ping timeout: 255 seconds)01:31
*** nerdboy <nerdboy!~nerdboy@gentoo/developer/nerdboy> has joined #yocto01:44
*** Ram-Z <Ram-Z!~Ram-Z@li1814-254.members.linode.com> has quit IRC (Ping timeout: 252 seconds)02:01
*** Ram-Z <Ram-Z!~Ram-Z@li1814-254.members.linode.com> has joined #yocto02:03
*** davidinux <davidinux!~davidinux@81.22.36.234> has quit IRC (Ping timeout: 260 seconds)02:04
*** davidinux <davidinux!~davidinux@81.22.36.235> has joined #yocto02:06
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 268 seconds)02:29
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto02:29
*** jmk1 <jmk1!~jmk1@lcs07-lyo-176-188-208-171.sfr.lns.abo.bbox.fr> has quit IRC (Read error: Connection reset by peer)02:31
*** jmk1 <jmk1!~jmk1@lcs07-lyo-176-188-208-171.sfr.lns.abo.bbox.fr> has joined #yocto02:33
*** mrpelotazo <mrpelotazo!~mrpelotaz@user/mrpelotazo> has quit IRC (Ping timeout: 246 seconds)02:33
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 260 seconds)02:34
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto02:34
*** mrpelotazo <mrpelotazo!~mrpelotaz@user/mrpelotazo> has joined #yocto02:35
*** sakoman <sakoman!~steve@dhcp-72-253-5-74.hawaiiantel.net> has joined #yocto02:35
*** Estrella__ <Estrella__!~quassel@cpe-24-26-195-197.hot.res.rr.com> has joined #yocto02:37
*** starblue <starblue!~juergen@dslb-094-221-179-114.094.221.pools.vodafone-ip.de> has quit IRC (Ping timeout: 260 seconds)02:37
*** starblue <starblue!~juergen@dslb-094-220-113-022.094.220.pools.vodafone-ip.de> has joined #yocto02:39
*** Estrella_ <Estrella_!~quassel@cpe-24-26-195-197.hot.res.rr.com> has quit IRC (Ping timeout: 252 seconds)02:39
*** Estrella <Estrella!~quassel@cpe-24-26-195-197.hot.res.rr.com> has quit IRC (Ping timeout: 260 seconds)02:39
*** Estrella___ <Estrella___!~quassel@cpe-24-26-195-197.hot.res.rr.com> has joined #yocto02:39
*** Bgaertner <Bgaertner!~Bgaertner@2600:1700:1d56:3600:f5ea:a38:62ea:1ff1> has joined #yocto02:43
*** Bgaertner <Bgaertner!~Bgaertner@2600:1700:1d56:3600:f5ea:a38:62ea:1ff1> has quit IRC (Quit: Client closed)02:53
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Ping timeout: 260 seconds)03:10
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)03:15
*** jclsn <jclsn!~jclsn@2a04:4540:6520:fc00:2ce:39ff:fecf:efcd> has quit IRC (Ping timeout: 252 seconds)03:48
*** jclsn <jclsn!~jclsn@2a04:4540:6507:8f00:2ce:39ff:fecf:efcd> has joined #yocto03:50
*** Wouter010067 <Wouter010067!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat)04:05
*** Wouter010067 <Wouter010067!~Wouter010@entry.nbg.netvos.nl> has joined #yocto04:05
*** sakoman <sakoman!~steve@dhcp-72-253-5-74.hawaiiantel.net> has quit IRC (Quit: Leaving.)04:43
*** invalidopcode <invalidopcode!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has quit IRC (Remote host closed the connection)04:50
*** invalidopcode <invalidopcode!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has joined #yocto04:50
*** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC (Quit: install gentoo)05:00
*** alicef <alicef!~none@gentoo/developer/alicef> has joined #yocto05:01
*** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC (Remote host closed the connection)05:01
*** alicef <alicef!~none@gentoo/developer/alicef> has joined #yocto05:04
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 268 seconds)05:10
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto05:10
*** beneth <beneth!5cb2199230@xmpp.beneth.fr> has quit IRC (Remote host closed the connection)05:13
*** beneth <beneth!5cb2199230@xmpp.beneth.fr> has joined #yocto05:50
*** demirok <demirok!~bell@user/demirok> has joined #yocto05:51
*** dmoseley <dmoseley!~dmoseley@d4-50-205-187.evv.wideopenwest.com> has quit IRC (Excess Flood)06:40
*** dmoseley <dmoseley!~dmoseley@d4-50-205-187.evv.wideopenwest.com> has joined #yocto06:42
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto07:01
*** amitk_ <amitk_!~amit@103.208.69.15> has joined #yocto07:42
*** amitk <amitk!~amit@103.208.69.169> has quit IRC (Ping timeout: 268 seconds)07:43
*** bps <bps!~bps@80.71.142.18.ipv4.parknet.dk> has joined #yocto07:55
*** gho <gho!~gho@i59f5cd22.versanet.de> has joined #yocto08:12
*** bps <bps!~bps@user/bps> has quit IRC (Ping timeout: 252 seconds)08:27
*** vvmeson <vvmeson!~rmacleod@23-233-86-175.cpe.pppoe.ca> has quit IRC (Ping timeout: 272 seconds)08:29
*** vmeson <vmeson!~rmacleod@23-233-86-175.cpe.pppoe.ca> has joined #yocto08:30
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto08:35
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Client Quit)08:36
*** gsalazar <gsalazar!~gsalazar@139.0.166.178.rev.vodafone.pt> has joined #yocto08:44
*** mvlad <mvlad!~mvlad@2a02:2f08:470d:8800:24d7:51ff:fed6:906d> has joined #yocto09:01
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection)09:11
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto09:12
*** bps <bps!~bps@193.89.194.60> has joined #yocto09:21
*** bps2 <bps2!~bps@193.89.194.60> has joined #yocto09:23
*** bps <bps!~bps@user/bps> has quit IRC (Ping timeout: 246 seconds)09:26
*** mihai <mihai!~mihai@user/mihai> has joined #yocto09:47
*** mabnhdev <mabnhdev!~mabnhdev@162-224-117-232.lightspeed.rlghnc.sbcglobal.net> has joined #yocto09:58
*** Wouter010067 <Wouter010067!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat)10:05
*** Wouter010067 <Wouter010067!~Wouter010@entry.nbg.netvos.nl> has joined #yocto10:05
*** mihai- <mihai-!~mihai@user/mihai> has joined #yocto10:27
*** mihai-- <mihai--!~mihai@user/mihai> has joined #yocto10:28
*** mihai is now known as Guest630410:29
*** mihai-- is now known as mihai10:29
*** Guest6304 <Guest6304!~mihai@user/mihai> has quit IRC (Ping timeout: 252 seconds)10:30
*** mihai- <mihai-!~mihai@user/mihai> has quit IRC (Ping timeout: 246 seconds)10:32
*** azcraft <azcraft!~AzCraft@195.214.248.221> has joined #yocto10:41
*** starblue <starblue!~juergen@dslb-094-220-113-022.094.220.pools.vodafone-ip.de> has quit IRC (Ping timeout: 272 seconds)11:02
*** starblue <starblue!~juergen@dslb-094-220-113-022.094.220.pools.vodafone-ip.de> has joined #yocto11:03
*** alex88 <alex88!~alex88@user/alex88> has quit IRC (Read error: Connection reset by peer)11:04
*** alex88 <alex88!~alex88@user/alex88> has joined #yocto11:06
*** seninha <seninha!~seninha@user/seninha> has joined #yocto11:39
*** florian_kc <florian_kc!~florian@dynamic-093-135-065-207.93.135.pool.telefonica.de> has joined #yocto11:57
*** demirok <demirok!~bell@user/demirok> has quit IRC (Quit: Leaving.)11:57
*** gsalazar <gsalazar!~gsalazar@139.0.166.178.rev.vodafone.pt> has quit IRC (Ping timeout: 246 seconds)11:58
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving)11:59
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto12:07
*** demirok <demirok!~bell@user/demirok> has joined #yocto12:13
*** seninha <seninha!~seninha@user/seninha> has joined #yocto12:17
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Quit: camus)12:18
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving)12:39
*** seninha <seninha!~seninha@user/seninha> has joined #yocto12:40
rburtonmy biannual blog post about something yocto related: https://www.burtonini.com/blog/2023/01/06/pysnooper/12:41
JaManice12:45
JaMawill try to remember that next time I'm adding a lot of print() in some bbclass12:46
rburtonyeah, its neat12:53
rburtonas great as bb.plain(f"{foo=}") is, pysnooper is better12:53
*** florian_kc <florian_kc!~florian@dynamic-093-135-065-207.93.135.pool.telefonica.de> has quit IRC (Ping timeout: 255 seconds)13:05
mabnhdevrburton For various reasons I think I need to downgrade Kirstone's python to 3.9.  I copied Honister's 3.9 python into my meta layer and fixed the parse errors.  However, when I try to build, I'm getting build errors while trying to build python3-installer.  The 3.9 python doesn't provide python3-installer and I think its being grabbed from13:07
mabnhdevpoky/meta.  I trying to figure out why python3-install is even being build since python 3.9 doesn't provide it.  Any ideas?13:07
rburtonpython3-installer isn't part of python, it's a dependency needed to build python code13:07
mabnhdevIs that dependency new to Kirkstone?13:08
rburtonyes13:10
rburtonit should work with 3.7 onwards13:10
rburtonobviously the right thing to do here is fix the reason you need 3.9 to work with 3.10, not backport 3.913:11
*** mvlad <mvlad!~mvlad@2a02:2f08:470d:8800:24d7:51ff:fed6:906d> has quit IRC (Remote host closed the connection)13:14
*** mvlad <mvlad!~mvlad@2a02:2f08:470d:8800:24d7:51ff:fed6:906d> has joined #yocto13:16
mabnhdevAh, that's the rub.  My hand is being forced by needing to stay on OpenSSL 1.0.2 for another 9 months or so - we're working on upgrading to 3.0.  Python 3.10 dropped support for OpenSSL 1.0.2 and now needs 1.1.1 or greater.  This is all a transition effort.13:16
mabnhdevOnce we're compatible with OpenSSL 3.0, I can drop all this transition hacking.13:17
kanavinmabnhdev, moving major pieces between yocto releases is asking for pain and suffering.13:18
mabnhdevkanavin Don't I know it ;)13:19
mabnhdevThis is a short-ish term hack to keep making progress.  I'm trying to jump from Yocto LTS to LTS.13:21
kanavinif you are staying on openssl 1.0.2, then you have to stay on a yocto release which has 1.0.213:21
rburtonthe openssl carnage isn't fun or easy13:21
rburtonthough installer claims to work with 3.7 onwards, so you should debug that13:22
kanavinand jumping from LTS to LTS isn't a great idea either, you do need to set up branches and a build that track upstream master milestones13:22
kanavinI know almost every yocto user does big bang transitions, still a bad idea in my eyes13:22
mabnhdevIsn't that the idea behind LTS; release stability for years.  I'm currently based on Dunfell; looking to advance to Kirkstone before Dunfell EOL.  Rinse, wash, repeat.13:24
rburtonsure, but it's a big transition thats harder to do.13:25
kanavinNo. The idea is to avoid accumulating years of technical debt by staying on a stale LTS release.13:25
rburtoneasier to not do it in stages, because you end up with situations like "we need openssl 1.0 but python 3.10 won't work but we need python 3.10 for something else"13:25
kanavinRather, you follow master, then when a new LTS release happens, you branch to that, and continue following master.13:25
mabnhdevagreed, from a Yocto POV.  But the non-Yocto side of things is much more difficult to transition, so it's much easier if I reduce Yocto version thrashing.13:26
JaMaagreed, also easier to fix regressions as soon as they are introduced in master, instead of trying to bisect what broke your code/layer in last 2 years13:27
JaManon-yocto side teams can use whatever released LTS the company uses, but build/yocto team should track master in parallel13:28
mabnhdevJaMa in a perfect world.13:29
JaMaI live in perfect world for last 10+ years, doing that as 1-person yocto team for really big builds13:31
rburtonyeah but i bet you never deployed anything at scale13:37
rburton(runs)13:37
*** Notgnoshi <Notgnoshi!~quassel@184-83-95-131-dynamic.midco.net> has joined #yocto13:39
kanavinno more retro x86 \0/13:40
kanavinwe can claim superiority over all 'classic' distros now :)13:41
kanavinand parity with a certain x86 demo distro by Intel13:41
kanavinthe likes of RHEL still have to work on e.g. pre-2022 Atoms13:42
kanavinhttps://git.yoctoproject.org/poky/commit/?h=master-next&id=ba0326071edc4aa988ad5bfaa4215e24e31fc75b13:45
kanavinis now in master13:45
JaMaluckily I no longer use AMD Bulldozer for OE builds :)13:46
kanavinJaMa, this wouldn't break the builds, only runqemu (and only if using kvm)13:47
JaMaIIRC IvyBridge was too new for that as well and qt was failing in runtime with Illegal Instructions13:47
rburtonyeah i remember fun and games with clearlinux when i had an ivybridge xeon13:48
kanavinrburton, I think nowadays they build everything three times13:48
kanavinv2, v3, v413:48
kanavinI think it's kind of hilarious that intel made huge amounts of noise about avx512 being glorious, then dropped it from products accessible to regular people13:49
JaMahttps://www.openembedded.org/pipermail/openembedded-core/2018-April/150178.html13:55
*** sakoman <sakoman!~steve@dhcp-72-253-5-74.hawaiiantel.net> has joined #yocto13:56
JaMaso on Bulldozer it was EDX.ss and ssse3 for me and I was switching qemu to Nehalem as reasonable compromise13:57
*** yann <yann!~yann@88.120.44.86> has joined #yocto14:04
*** dgriego <dgriego!~dgriego@user/dgriego> has quit IRC (Quit: dgriego)14:22
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has quit IRC (Ping timeout: 255 seconds)14:57
*** demirok <demirok!~bell@user/demirok> has quit IRC (Quit: Leaving.)15:02
*** mabnhdev <mabnhdev!~mabnhdev@162-224-117-232.lightspeed.rlghnc.sbcglobal.net> has quit IRC (Quit: Client closed)15:03
*** Wouter010067 <Wouter010067!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat)15:05
*** Wouter010067 <Wouter010067!~Wouter010@entry.nbg.netvos.nl> has joined #yocto15:05
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto15:07
*** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has joined #yocto15:08
*** florian <florian!~florian@dynamic-093-135-065-207.93.135.pool.telefonica.de> has joined #yocto15:10
*** mabnhdev <mabnhdev!~mabnhdev@162-224-117-232.lightspeed.rlghnc.sbcglobal.net> has joined #yocto15:15
*** florian <florian!~florian@dynamic-093-135-065-207.93.135.pool.telefonica.de> has quit IRC (Ping timeout: 246 seconds)15:19
rburtonis elfutils failing to build debuginfod for everyone else with master?15:30
rburtonah15:33
rburtonkanavin: your elfutils fix for curl was BUILD_CFLAGS so doesn't fix the target build15:33
*** bps2 <bps2!~bps@193.89.194.60> has quit IRC (Ping timeout: 246 seconds)15:43
*** gho <gho!~gho@i59f5cd22.versanet.de> has quit IRC (Quit: Leaving.)15:45
*** gho <gho!~gho@i59F5CD22.versanet.de> has joined #yocto15:46
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Quit: Leaving)15:48
*** ccf <ccf!~ccf@user/ccf> has joined #yocto16:18
*** victoridaho[m] <victoridaho[m]!~victorida@2001:470:69fc:105::2:ee9e> has joined #yocto16:22
*** Guest59 <Guest59!~Guest59@50.207.83.251> has joined #yocto16:30
Guest59Is this an acceptable place to ask questions related to a problem I am having?16:32
abelloniprobably16:33
victoridaho[m]Ok. I am seeing the error "ERROR: os-release-1.0-r0 do_package_qa: QA Issue: os-release rdepends on os-release-dev [dev-deps]". I understand what it means but I can't seem to find any info on how to fix it.16:34
*** dmoseley <dmoseley!~dmoseley@d4-50-205-187.evv.wideopenwest.com> has quit IRC (Ping timeout: 260 seconds)16:36
JaMavictoridaho[m]: have you read log.do_package?16:37
JaMait often shows why this is happening16:37
Guest59It has the following:16:42
Guest59NOTE: Package os-release-dbg skipping libdir QA test for PACKAGE_DEBUG_SPLIT_STYLE equals debug-file-directory16:42
Guest59I'm trying to add "perf" to the distribution and have added this to local.conf:16:42
Guest59INHIBIT_PACKAGE_STRIP = "1"16:42
Guest59PACKAGE_DEBUG_SPLIT_STYLE = 'debug-file-directory'16:42
Guest59FILES:${PN} += "${debugsrcdir}/*"16:42
Guest59FILES:${PN}-dev = "${debugsrcdir}/* ${includedir} ${libdir}"16:42
rburtonerm don't do that16:45
rburtonwhy did you do that?16:45
rburtonif you want to add perf, just add perf to IMAGE_INSTALL16:45
rburtonthen install the -dbg packages which contain all the symbols.  you can do that easily by adding dbg-pkgs to IMAGE_FEATURES.16:46
*** ccf <ccf!~ccf@user/ccf> has quit IRC (Remote host closed the connection)16:48
*** Estrella <Estrella!~quassel@cpe-24-26-195-197.hot.res.rr.com> has joined #yocto16:49
victoridaho[m]I was trying to follow the instructions at https://developer.ridgerun.com/wiki/index.php/Preparing_Yocto_Development_Environment_for_Debugging. I will give your suggestion a try.16:51
*** dmoseley <dmoseley!~dmoseley@d4-50-205-187.evv.wideopenwest.com> has joined #yocto16:52
rburtonthose instructions are *terrible*16:55
kergothGotta love random blog posts :)16:55
kergothand wikis16:55
victoridaho[m]rburton: Lovely :)16:56
*** dmoseley <dmoseley!~dmoseley@d4-50-205-187.evv.wideopenwest.com> has quit IRC (Ping timeout: 272 seconds)16:57
rburtonliterally just EXTRA_IMAGE_FEATURES = "dbg-pkgs tools-profile" will work16:57
rburtondbg-pkgs adds all dbg packages for the contents of the image, tools-profile adds perf (and others)16:58
kanavinrburton, soon we'll have terrible instructions about yocto written by chatgpt all over the internet :-/16:58
rburtonkanavin: thank to LetoThe2nd we already do16:58
kanavincode submissions by chatgpt we can reject hopefully, bad information less so16:59
*** florian <florian!~florian@dynamic-093-135-065-207.93.135.pool.telefonica.de> has joined #yocto17:01
rburtonhttps://docs.yoctoproject.org/dev-manual/common-tasks.html#debugging-with-the-gnu-project-debugger-gdb-on-the-target should talk about perf aswell, but if gdb works, so does perf17:01
kanavinrburton, I'd like to understand how the elfutils fix made it through all the builds though17:04
kanavinbuilding it myself now17:04
*** florian <florian!~florian@dynamic-093-135-065-207.93.135.pool.telefonica.de> has quit IRC (Ping timeout: 268 seconds)17:06
*** florian <florian!~florian@dynamic-093-135-065-207.93.135.pool.telefonica.de> has joined #yocto17:07
*** gho <gho!~gho@i59F5CD22.versanet.de> has quit IRC (Quit: Leaving.)17:08
rburtonkanavin: i'm surprised nothing in qa built target elfutils17:13
kanavinrburton, I just built target elfutils. And world builds include it too.17:14
*** Estrella <Estrella!~quassel@cpe-24-26-195-197.hot.res.rr.com> has quit IRC (Remote host closed the connection)17:14
*** mabnhdev <mabnhdev!~mabnhdev@162-224-117-232.lightspeed.rlghnc.sbcglobal.net> has quit IRC (Quit: Client closed)17:14
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has quit IRC (Ping timeout: 265 seconds)17:15
RPrburton: was this not clang specific?17:15
*** Payam <Payam!~Payam@c83-250-236-236.bredband.tele2.se> has joined #yocto17:16
rburtonhm.  just had another look at the builds, it only triggered on armgcc.17:16
rburtoni wonder why thats emitting different deprecation warnings?17:16
Payamhi, I know I have asked it before but I already forgot it. so bitbake first looks at DL_DIR if specified then it looks att Mirror if specified right? How about sstate? does it look for at local one and then remote?17:16
rburtonPayam: it would be madness to look at remote first, wouldn't it?17:17
Payamrburton, yes but I wana make sure that it looks at the mirror and doesn't just skip it17:17
kanavinrburton, I'm looking at target log.do_compile, and I see no deprecation warnings at all :-/17:17
kanavinfor native they're there17:17
rburtonPayam: do_fetch will check the file is in DL_DIR and if that fails, try "the network", that is PREMIRRORS then SRC_URI then MIRRORS.17:18
rburtonPayam: sstate lookups will try SSTATE_DIR first and then SSTATE_MIRRORS17:18
PayamWhat do you mean by MIRRORS? you mean premirror:append?17:19
rburtonkanavin: some gcc thing.  makes me wonder if our gcc is doing the right thing17:19
rburtonPayam: i mean the variable MIRRORS17:19
Payamah17:20
rburtoneverything in uppercase is a variable name17:20
Payamrburton, As you know I uploaded the sstate to s3 and when I download it and wana use it, it takes alot of time almost like it doesn't use it at all.17:20
rburtonwithout your config, your setup, your logs, it's literally impossible to help17:21
rburtonbitbake will tell you exactly how much sstate its using17:21
rburton"Sstate summary: Wanted 92 Local 58 Mirrors 0 Missed 34 Current 294 (63% match, 91% complete)"17:22
JaMa"when I download it" you seem to run in circles17:25
rburtonalso i hope you're not downloading the sstate before the build, instead use the s3 as a sstate mirror. downloading all the sstate will get increasingly slow as it grows.17:25
rburtonof course the easier solution is to not use s3, but we told you this yesterday.17:26
rburtonkanavin: so why is our gcc not emitting deprecation warnings?17:26
kanavinrburton, curl.h makes those conditional (look for #define CURL_DEPRECATED at the top_, and I'm trying to figure out if the condition differs between native and target builds somehow17:27
rburtoni presume gcc12 doesn't pretend to be __INTEL_COMPILER :)17:28
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)17:43
*** demirok <demirok!~bell@user/demirok> has joined #yocto17:44
RPkanavin: thanks for the qemu fixes btw. We're a little backlogged on patches but getting there :)17:44
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto17:45
kanavinRP: cheers. We should be pretty good overall now in the up-to-dateness.17:47
kanavinthe next AUH should not bomb the list like the last few17:47
khemmcfrisk: If meta-clang master still works with kirkstone thats a side effect. I would expect it to break at some point since its not a validated combination if some one is interested in keeping master of meta-clang working for kirkstone layers working I am happy to take patches17:49
RPkanavin: Getting things caught up is very much appreciated!17:49
kanavinRP: thanks :-)17:53
kanavinRP: by the way, this x86-v3 feature was not asked by intel or anyone at LX. it's something of a personal peeve for me.17:54
kanavinRP: we'll get better performance out of mesa's software renderer that way, for example.17:55
RPkanavin: I gathered that, I think it is nice to have. I'm just hoping we run on hosts that can handle it17:55
kanavinRP: for builds and non-kvm runqemu we're fine. For runqemu kvm, yes, it will crash out with illegal instruction on anything pre-haswell, or on any Atom cpu that's over a year old (people do run yocto builds on all sorts of weird hosts, so you never know).17:57
*** dmoseley <dmoseley!~dmoseley@d4-50-205-187.evv.wideopenwest.com> has joined #yocto17:58
khemJaMa: I have pushed few more fixes into https://github.com/meta-qt5/meta-qt5/pull/500, please take a look whenever you have time17:58
kanavinRP: and before you know it, chatgpt and other AI in yocto will be a major use case, so I can imagine vector instructions would come in super handy to train and exercise those neural nets :)17:59
JaMakhem: I've seen them, but I haven't set a build to reproduce those 64bit time_t issues, so I might just test it in regular 64bit build17:59
khemyou can enable 64bit time_t it in your distro see https://git.yoctoproject.org/poky-contrib/commit/?h=yoe/mut&id=bc510355cc301aa7fca6fd0d0bbe2523d430b9da18:01
RPkanavin: the AI can take care of those issues though right? :)18:02
*** dmoseley <dmoseley!~dmoseley@d4-50-205-187.evv.wideopenwest.com> has quit IRC (Ping timeout: 252 seconds)18:02
*** florian <florian!~florian@dynamic-093-135-065-207.93.135.pool.telefonica.de> has quit IRC (Ping timeout: 252 seconds)18:03
kanavinRP: yes, as long as it doesn't decide that to achieve that goal most efficiently it also needs to kill all humans.18:03
kanavin(also known as 'the paperclip argument')18:03
RPkanavin: I'm sure the software engineers will have put the right safeguards in18:05
kanavinRP: the problem is, AI will develop to a point where it is smarter than all of the human intelligence combined. Then it will work around any possible safeguards, and quicker than those can be built.18:06
kanavinso it shouldn't be connected to the internet, except that ship has sailed :-)18:06
kanavinthe most convincing argument I've heard is that before AI is able to destroy the world in a competent manner, it will try to do so incompetently - kind of like chatgpt writing about yocto today18:07
kanavinat that point we can catch it and try to figure out how it got to that decision18:08
JaMathen solar flare will kill AI and human kind will start again from scratch (seen some post like that today, but cannot find it now)18:08
JaMakhem: thanks, that was the bit I've seen on ML, but then haven't seen it in oe-core/yoe/mut to cherry-pick from18:09
*** gsalazar <gsalazar!~gsalazar@2001:818:c408:ea00:3770:824e:3afb:4399> has joined #yocto18:10
JaMaas I didn't notice that you've switched to poky repo as a base (which explains last oe-core/yoe/mut change couple months ago)18:10
kanavinrburton, I confirmed that curl's deprecation declarations have no effect on our target gcc 12.x :-/ do we do something to it that subverts the checks?18:11
rburtonnot afaik. i just checked that the sysroot poison thing didn't break warning flags and it looks right18:12
rburtonkhem: ^^^ help!18:12
rburtoni need to go now18:12
kanavini'd like to get a glass of wine, and be afk too :-)18:13
khemrburton: interesting hmm18:21
khemlet me take a look18:21
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Quit: WeeChat 3.7.1)18:36
*** dgriego <dgriego!~dgriego@user/dgriego> has joined #yocto18:37
*** invalidopcode <invalidopcode!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has quit IRC (Remote host closed the connection)18:53
*** florian <florian!~florian@dynamic-093-135-065-207.93.135.pool.telefonica.de> has joined #yocto18:53
*** invalidopcode <invalidopcode!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has joined #yocto18:53
*** goliath <goliath!~goliath@user/goliath> has joined #yocto18:56
*** armhzjz <armhzjz!eindemwort@user/armhzjz> has joined #yocto19:07
*** armhzjz <armhzjz!eindemwort@user/armhzjz> has left #yocto19:08
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)19:15
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto19:17
*** uniqdom <uniqdom!~uniqdom@45.232.92.107> has joined #yocto19:34
*** mark_ <mark_!~mark@bras-base-stsvon1507w-grc-03-76-71-76-243.dsl.bell.ca> has joined #yocto19:34
*** Wouter010067 <Wouter010067!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat)19:35
*** Wouter010067 <Wouter010067!~Wouter010@entry.nbg.netvos.nl> has joined #yocto19:35
uniqdomHello, I need to run base64 command inside a recipe. But it fails, as it seems to not be avaialble when using bitbake, i.e. "Command not found".19:35
uniqdomwhat can I do to have base64 available in the recipe?19:36
uniqdomJust to be clear, I don't need base64 in the image.19:37
kanavinuniqdom, DEPENDS += "coreutils-native"19:43
JPEWhmm, I don't think my builds have been going _that_ long: `qemu-native-7.2.0-r0 do_fetch - 172h22m54s`19:45
JaMahehe19:45
uniqdomkanavin: THANKS A LOT!!!19:46
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto19:47
*** sakoman <sakoman!~steve@dhcp-72-253-5-74.hawaiiantel.net> has quit IRC (Quit: Leaving.)19:57
*** sakoman <sakoman!~steve@dhcp-72-253-5-74.hawaiiantel.net> has joined #yocto20:03
*** gsalazar <gsalazar!~gsalazar@2001:818:c408:ea00:3770:824e:3afb:4399> has quit IRC (Ping timeout: 248 seconds)20:08
*** Guest59 <Guest59!~Guest59@50.207.83.251> has quit IRC (Quit: Client closed)20:18
*** Estrella <Estrella!~quassel@cpe-24-26-195-197.hot.res.rr.com> has joined #yocto20:26
*** Estrella__ <Estrella__!~quassel@cpe-24-26-195-197.hot.res.rr.com> has quit IRC (Ping timeout: 252 seconds)20:28
*** Estrella___ <Estrella___!~quassel@cpe-24-26-195-197.hot.res.rr.com> has quit IRC (Ping timeout: 260 seconds)20:28
*** Estrella_ <Estrella_!~quassel@cpe-24-26-195-197.hot.res.rr.com> has joined #yocto20:29
*** dmoseley <dmoseley!~dmoseley@d4-50-205-187.evv.wideopenwest.com> has joined #yocto20:30
*** dmoseley <dmoseley!~dmoseley@d4-50-205-187.evv.wideopenwest.com> has quit IRC (Ping timeout: 256 seconds)20:35
*** Payam <Payam!~Payam@c83-250-236-236.bredband.tele2.se> has quit IRC (Quit: Leaving)20:45
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 272 seconds)21:04
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto21:04
*** uniqdom <uniqdom!~uniqdom@45.232.92.107> has quit IRC (Ping timeout: 268 seconds)21:05
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has quit IRC (Ping timeout: 264 seconds)21:09
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 268 seconds)21:09
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto21:10
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)21:23
*** dmoseley <dmoseley!~dmoseley@d4-50-205-187.evv.wideopenwest.com> has joined #yocto21:24
*** dmoseley <dmoseley!~dmoseley@d4-50-205-187.evv.wideopenwest.com> has quit IRC (Ping timeout: 268 seconds)21:29
*** dmoseley <dmoseley!~dmoseley@d4-50-205-187.evv.wideopenwest.com> has joined #yocto21:57
*** dmoseley <dmoseley!~dmoseley@d4-50-205-187.evv.wideopenwest.com> has quit IRC (Ping timeout: 272 seconds)22:02
*** uniqdom <uniqdom!~uniqdom@45.232.92.107> has joined #yocto22:09
*** uniqdom <uniqdom!~uniqdom@45.232.92.107> has quit IRC (Client Quit)22:11
*** uniqdom <uniqdom!~uniqdom@45.232.92.107> has joined #yocto22:15
*** Haxxa <Haxxa!~Haxxa@202-65-79-43.ip4.superloop.com> has quit IRC (Ping timeout: 268 seconds)22:35
*** Haxxa <Haxxa!~Haxxa@202-65-79-43.ip4.superloop.com> has joined #yocto22:36
*** BobPungartnik <BobPungartnik!~Pung@179.177.251.214> has joined #yocto22:40
*** azcraft <azcraft!~AzCraft@195.214.248.221> has quit IRC (Remote host closed the connection)22:40
*** BobPungartnik <BobPungartnik!~Pung@179.177.251.214> has quit IRC (Client Quit)22:41
uniqdomI wonder what's the error here, can't figure out from the output. Paste of the build and recipe here: https://paste.debian.net/1266377/22:45
uniqdomcan you confirm to me if "install" doensn't like * wildcard?22:47
tangofoxtrotuniqdom, you should not need the '*' in the FILES stanza, and I'd recommend specifying every directory and file needed in your install_append().  Alternatively you could use cp -r oor something similar, but I've found it's best to be precise.22:53
uniqdomtangofoxtrot: Thanks, I'm going to change that22:56
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 260 seconds)23:14
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto23:14
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 272 seconds)23:19
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto23:19
JaMaRP "I'm just hoping we run on hosts that can handle it" heh looks like our hosts aren't, a lot of recipes failing today with "fribidi-1.0.12/meson.build:1:0: ERROR: Executables created by c compiler x86_64-webos-linux-gcc -m64 -march=x86-64-v3 -fstack-protector-strong -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Werror=return-type23:26
JaMa--sysroot=/data001/jenkins/gecko/webos_qemux86-64/build/BUILD/work/qemux86_64-webos-linux/fribidi/1.0.12-r0/recipe-sysroot are not runnable."23:26
*** demirok <demirok!~bell@user/demirok> has quit IRC (Quit: Leaving.)23:28
JaMafribidi, orc, libsigc++-2.0, xorgproto, pixman, libdrm, glib-2.0, systemd-boot, systemd, iputils in do_configure (all using meson), nodejs do_compile (also uses qemu to run v8 mksnapshot - Illegal instruction (core dumped))23:29
*** bps2 <bps2!~bps@80.71.142.18.ipv4.parknet.dk> has joined #yocto23:41
*** florian <florian!~florian@dynamic-093-135-065-207.93.135.pool.telefonica.de> has quit IRC (Ping timeout: 252 seconds)23:44
*** mvlad <mvlad!~mvlad@2a02:2f08:470d:8800:24d7:51ff:fed6:906d> has quit IRC (Remote host closed the connection)23:48
RPJaMa: hmm, that is qemu failing to run target binaries? :(23:51
JaMaRP: yes, I'll find out what CPUs we have in builders and in worst case change DEFAULTTUNE for our qemux86-64 builds until we're ready to upgrade (cannot ssh into the builders rn, will check on Monday)23:52
RPJaMa: ok, I guess it should be easy to switch back to an older tune23:53
*** invalidopcode <invalidopcode!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has quit IRC (Remote host closed the connection)23:54
*** invalidopcode <invalidopcode!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has joined #yocto23:54
JaMaRP: yes, tune-x86-64-v3.inc includes the "old" tune-corei7.inc as well, so it should be easy23:56

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