| *** otavio <otavio!~otavio@201-34-65-230.user3p.brasiltelecom.net.br> has joined #yocto | 00:00 | |
| vmeson | RP thanks I was going to apply that elfutils patch but you have it in master-next already ! | 00:02 |
|---|---|---|
| *** otavio <otavio!~otavio@201-34-65-230.user3p.brasiltelecom.net.br> has quit IRC (Read error: Connection reset by peer) | 00:02 | |
| *** otavio <otavio!~otavio@201-34-65-230.user3p.brasiltelecom.net.br> has joined #yocto | 00:06 | |
| *** wing0 <wing0!~wing0@2804:431:c7ec:d24:d63c:1018:c1ed:8754> has quit IRC (Quit: WeeChat 3.1) | 00:26 | |
| *** stwcx <stwcx!~stwcx@76-250-84-236.lightspeed.austtx.sbcglobal.net> has joined #yocto | 00:47 | |
| *** nerdboy_ <nerdboy_!~nerdboy@47.143.129.174> has joined #yocto | 02:15 | |
| *** nerdboy <nerdboy!~nerdboy@gentoo/developer/nerdboy> has quit IRC (Ping timeout: 265 seconds) | 02:18 | |
| *** nerdboy_ is now known as nerdboy | 02:30 | |
| *** sakoman <sakoman!~steve@172.243.4.16> has quit IRC (Quit: Leaving.) | 03:06 | |
| *** boo <boo!~boodler@104-195-159-20.cpe.teksavvy.com> has quit IRC (Ping timeout: 258 seconds) | 03:09 | |
| *** amitk <amitk!~amit@103.208.69.19> has joined #yocto | 03:44 | |
| *** Tokamak <Tokamak!~Tokamak@107.117.203.113> has quit IRC (Ping timeout: 240 seconds) | 03:45 | |
| *** roussinm <roussinm!~mroussin@bras-base-qubcpq1306w-grc-21-184-145-222-193.dsl.bell.ca> has quit IRC (Quit: WeeChat 3.3-dev) | 05:04 | |
| *** rpcme <rpcme!~rpcme@52.95.4.6> has quit IRC (Ping timeout: 246 seconds) | 05:08 | |
| *** stwcx <stwcx!~stwcx@76-250-84-236.lightspeed.austtx.sbcglobal.net> has quit IRC (Quit: Ping timeout (120 seconds)) | 05:22 | |
| *** rob_w <rob_w!~rob@ppp-93-104-39-218.dynamic.mnet-online.de> has joined #yocto | 06:02 | |
| *** davidinux <davidinux!~davidinux@217.138.219.150> has quit IRC (Ping timeout: 245 seconds) | 06:06 | |
| *** davidinux <davidinux!~davidinux@217.138.219.150> has joined #yocto | 06:09 | |
| *** lexano <lexano!~lexano@cpe00e06722f0e4-cm98524a70e35e.cpe.net.cable.rogers.com> has quit IRC (Ping timeout: 276 seconds) | 06:14 | |
| *** frieder <frieder!~frieder@7-69-142-46.pool.kielnet.net> has joined #yocto | 06:19 | |
| *** lexano <lexano!~lexano@cpe00e06722f0e4-cm98524a70e35e.cpe.net.cable.rogers.com> has joined #yocto | 06:25 | |
| *** goliath <goliath!~goliath@user/goliath> has joined #yocto | 06:36 | |
| *** sbach <sbach!~sbach@user/sbach> has quit IRC (Read error: Connection reset by peer) | 06:40 | |
| *** sbach <sbach!~sbach@user/sbach> has joined #yocto | 06:40 | |
| *** LetoThe2nd <LetoThe2nd!uid453638@id-453638.highgate.irccloud.com> has joined #yocto | 06:43 | |
| *** mckoan|away is now known as mckoan | 06:48 | |
| mckoan | good morning | 06:48 |
| *** zpfvo <zpfvo!~fvo@89.244.125.186> has joined #yocto | 06:52 | |
| *** ant__ <ant__!~ant@host-82-48-247-160.retail.telecomitalia.it> has quit IRC (Ping timeout: 252 seconds) | 07:03 | |
| LetoThe2nd | yo dudX and mckoans | 07:08 |
| *** hpsy <hpsy!~hpsy@85.203.15.6> has joined #yocto | 07:08 | |
| *** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV) | 07:28 | |
| RP | vmeson: it fixes x86 but not arm :/ | 07:35 |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto | 07:56 | |
| mihai | yo | 08:13 |
| LetoThe2nd | yö, even! | 08:22 |
| *** ant__ <ant__!~ant@host-195-31-129-205.business.telecomitalia.it> has joined #yocto | 08:27 | |
| *** goliath <goliath!~goliath@user/goliath> has joined #yocto | 08:34 | |
| *** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto | 08:47 | |
| *** leon-anavi <leon-anavi!~Leon@78.130.197.211> has joined #yocto | 08:52 | |
| *** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 252 seconds) | 09:18 | |
| *** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto | 09:28 | |
| *** mckoan <mckoan!~marco@host-79-3-92-72.business.telecomitalia.it> has quit IRC (Ping timeout: 276 seconds) | 10:19 | |
| *** mckoan <mckoan!~marco@host-79-3-92-72.business.telecomitalia.it> has joined #yocto | 10:19 | |
| *** ant__ <ant__!~ant@host-195-31-129-205.business.telecomitalia.it> has quit IRC (Quit: Leaving) | 11:07 | |
| *** jwillikers <jwillikers!~jwilliker@2604:2800:2:a403:fe91:ac3e:5153:1290> has joined #yocto | 11:18 | |
| override | /window 3 | 11:33 |
| *** rpcme <rpcme!~rpcme@52.95.4.12> has joined #yocto | 12:47 | |
| *** davidinux <davidinux!~davidinux@217.138.219.150> has quit IRC (Ping timeout: 272 seconds) | 12:51 | |
| *** davidinux <davidinux!~davidinux@net-93-146-33-94.cust.vodafonedsl.it> has joined #yocto | 12:53 | |
| *** boo <boo!~boodler@104-195-159-20.cpe.teksavvy.com> has joined #yocto | 12:55 | |
| *** mckoan <mckoan!~marco@host-79-3-92-72.business.telecomitalia.it> has quit IRC (Quit: Quitting irssi IRC Client, bye.) | 13:31 | |
| *** mckoan <mckoan!~marco@host-79-3-92-72.business.telecomitalia.it> has joined #yocto | 13:31 | |
| *** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV) | 13:32 | |
| *** sakoman <sakoman!~steve@172.243.4.16> has joined #yocto | 13:50 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 14:12 | |
| *** rpcme <rpcme!~rpcme@52.95.4.12> has quit IRC (Quit: Client closed) | 14:15 | |
| *** roussinm <roussinm!~mroussin@bras-base-qubcpq1306w-grc-21-184-145-222-193.dsl.bell.ca> has joined #yocto | 14:31 | |
| *** bps <bps!~bps@user/bps> has quit IRC (Ping timeout: 256 seconds) | 14:33 | |
| *** davidinux <davidinux!~davidinux@net-93-146-33-94.cust.vodafonedsl.it> has quit IRC (Ping timeout: 258 seconds) | 14:44 | |
| *** davidinux <davidinux!~davidinux@217.138.219.150> has joined #yocto | 14:44 | |
| *** mseeber <mseeber!~mseeber@static-91-137-63-64.net.encoline.de> has joined #yocto | 14:47 | |
| mseeber | in case a machine config file is present in two layers, how does bitbake determine which file to use? From testing, it seems to me, that the layer priority is ignored but ordering of the layers inside bblayers.conf determines which config file is used. Is this the intended behavior? (tested on on zeus) | 15:01 |
| *** frieder <frieder!~frieder@7-69-142-46.pool.kielnet.net> has quit IRC (Ping timeout: 272 seconds) | 15:03 | |
| qschulz | mseeber: it is based on BBPATH defined in layer.conf | 15:03 |
| qschulz | since each layer is appending by default to the existing BBPATH, the consequence is that indeed, the "precedence" depends on the order from BBLAYERS in bbalyers.conf | 15:04 |
| qschulz | s/appending by default/by default appending/ | 15:05 |
| *** bps <bps!~bps@80.71.142.18.ipv4.parknet.dk> has joined #yocto | 15:07 | |
| *** rob_w <rob_w!~rob@ppp-93-104-39-218.dynamic.mnet-online.de> has quit IRC (Quit: Leaving) | 15:07 | |
| qschulz | mmmm to be checked | 15:08 |
| mseeber | thanks, that explains the behavior. | 15:08 |
| qschulz | https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-ref-variables.html#term-BBPATH checked :) | 15:09 |
| qschulz | michaelo: https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-ref-variables.html#term-BBPATH and https://docs.yoctoproject.org/ref-manual/variables.html#term-BBPATH do not match and that's not good :) | 15:09 |
| qschulz | specifically leaving out an important piece of information | 15:09 |
| mseeber | That sounds to me, that there is no way to prioritize machine configs through layer priorities, which means the only safe way is to include the old config in the new one (with the same file name) and override the variables. | 15:13 |
| *** frieder <frieder!~frieder@7-69-142-46.pool.kielnet.net> has joined #yocto | 15:14 | |
| qschulz | as for bbclasses, conf files aren't meant to be extended | 15:15 |
| qschulz | so you have to write a new one which include the other | 15:15 |
| qschulz | please use different names | 15:15 |
| mseeber | ah, that makes sense | 15:16 |
| qschulz | but you can use MACHINEOVERRIDES to tell Yocto that they are in fact of the same "family" | 15:16 |
| mseeber | thanks a lot! i will look into that | 15:16 |
| qschulz | mseeber: my pleasure, have fun! | 15:17 |
| mseeber | 3rd party bsps are always fun ;) | 15:17 |
| qschulz | that's not the word I would have used :) | 15:19 |
| *** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto | 15:22 | |
| RP | moto-timo: I don't think we show the output of the link I posted to in triage so vmeson's approach to addressing this may be better, not sure | 15:33 |
| *** frieder <frieder!~frieder@7-69-142-46.pool.kielnet.net> has quit IRC (Remote host closed the connection) | 15:55 | |
| *** mseeber <mseeber!~mseeber@static-91-137-63-64.net.encoline.de> has quit IRC (Quit: Ping timeout (120 seconds)) | 15:58 | |
| *** mseeber <mseeber!~mseeber@static-91-137-63-64.net.encoline.de> has joined #yocto | 15:58 | |
| *** halstead[m] <halstead[m]!~halsteadm@2001:470:69fc:105::d0ef> has joined #yocto | 16:09 | |
| *** mseeber <mseeber!~mseeber@static-91-137-63-64.net.encoline.de> has quit IRC (Quit: Ping timeout (120 seconds)) | 16:11 | |
| *** mseeber <mseeber!~mseeber@static-91-137-63-64.net.encoline.de> has joined #yocto | 16:12 | |
| halstead[m] | dl9pf: Do you know who set up the matrix bridge? It seems it's missing messages. https://bugzilla.yoctoproject.org/show_bug.cgi?id=14494 | 16:15 |
| moto-timo | RP: agreed, ptest runner is using SIGKILL which is where the 9 came from. | 16:17 |
| moto-timo | http://git.yoctoproject.org/cgit/cgit.cgi/ptest-runner2/tree/utils.c#n352 | 16:18 |
| *** rpcme <rpcme!~rpcme@52.95.4.12> has joined #yocto | 16:20 | |
| moto_timo[m] | halstead: pretty sure shoragan was involved? | 16:23 |
| *** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat) | 16:27 | |
| *** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 268 seconds) | 16:30 | |
| *** hpsy <hpsy!~hpsy@85.203.15.6> has quit IRC (Remote host closed the connection) | 16:30 | |
| shoragan | moto_timo[m], hmm, according to the #libera-matrix topic, the bridge is up and running... | 16:38 |
| halstead[m] | shoragan: Could you respond the the bug asking for whatever detail might help? | 16:39 |
| *** mckoan is now known as mckoan|away | 16:41 | |
| shoragan | halstead[m], hmm, need to create a bugzilla account first.... | 16:41 |
| *** zpfvo <zpfvo!~fvo@89.244.125.186> has quit IRC (Remote host closed the connection) | 16:44 | |
| RP | halstead, shoragan: michaelo is here FWIW | 16:49 |
| shoragan | halstead[m], RP: i've replied to the bug | 16:52 |
| RP | shoragan: thanks | 16:52 |
| shoragan | michaelo, if you notice anything strange, you can also ping me here | 16:55 |
| michaelo | shoragan: thanks for your help. | 16:55 |
| michaelo | shoragan: the issue may be on my side, but on my Matrix client (element.io), the last message I see is the "shoragan: Could you respond..." one from almost 20 minutes ago. | 16:56 |
| michaelo | Anybody else on Matrix? khem? Do you have all the latest messages? | 16:57 |
| *** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto | 16:58 | |
| *** mseeber <mseeber!~mseeber@static-91-137-63-64.net.encoline.de> has quit IRC (Quit: Ping timeout (120 seconds)) | 16:58 | |
| shoragan[m] | michaelo: It works fine for me. | 16:58 |
| shoragan[m] | And I'm on element.io as well. | 16:58 |
| michaelo | Just received all the messages in a burst. Maybe that's because my element.io client is dealing with more than one Matrix server at the same time (which I was surprised it could do). Let me check in a dedicated tab. | 17:00 |
| shoragan|m | This is from a federated matrix server. | 17:01 |
| shoragan[m] | So currently it seems to work fine at least for my two matrix accounts. | 17:02 |
| *** mseeber <mseeber!~mseeber@static-91-137-63-64.net.encoline.de> has joined #yocto | 17:06 | |
| halstead | michaelo: Your last message on the Matrix side still hasn't arrived here. Hrmm.. | 17:06 |
| michaelo[m] | Thanks for confirming this! | 17:08 |
| *** michaelo[m]1 <michaelo[m]1!~michaelom@2001:470:69fc:105::d101> has joined #yocto | 17:09 | |
| shoragan | michaelo[m], your last message took a long time... | 17:09 |
| michaelo[m]1 | Yes, indeed | 17:09 |
| shoragan | maybe federation between matrix.bootlin.com and libera.chat is not good? | 17:09 |
| michaelo[m]1 | But not these two ones 🙃 | 17:10 |
| michaelo[m]1 | shoragan: right, that must be because of the way matrix.bootlin.com is configured. | 17:10 |
| michaelo[m]1 | Because when I use my matrix.org account, everything just works smoothly. | 17:11 |
| michaelo | halstead, shoragan: many thanks for your help and for testing on your side. I can fix the bug now. | 17:12 |
| shoragan[m] | michael.o: check if your synapse instance has enough disk IO and RAM. we had similar issues last year when the stratum0.org instance was still running on HDDs. | 17:12 |
| *** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has joined #yocto | 17:12 | |
| michaelo | ... while we address the matrix.bootlin.com issues. | 17:12 |
| vd | is do_image_squashfs_append_override supposed to work, given "override" is in OVERRIDES? | 17:14 |
| *** LetoThe2nd <LetoThe2nd!uid453638@id-453638.highgate.irccloud.com> has quit IRC (Quit: Connection closed for inactivity) | 17:18 | |
| vd | how can I append a task for a specific override? | 17:53 |
| *** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Quit: jmiehe) | 17:54 | |
| override | how can I see what PACKAGECONFIG gets resolved to for openembedded-core/meta/recipes-gnome/gtk+/gtk+3.inc | 17:56 |
| *** mseeber <mseeber!~mseeber@static-91-137-63-64.net.encoline.de> has quit IRC (Ping timeout: 246 seconds) | 18:01 | |
| *** Tokamak <Tokamak!~Tokamak@107.117.203.65> has joined #yocto | 18:02 | |
| *** frieder <frieder!~frieder@7-69-142-46.pool.kielnet.net> has joined #yocto | 18:05 | |
| *** florian_kc <florian_kc!~florian@dynamic-093-131-060-085.93.131.pool.telefonica.de> has joined #yocto | 18:09 | |
| jsbronder | override: bitbake -e gtk+3 | grep -B 20 '^PACKAGECONFIG' | 18:11 |
| override | thanks jsbronder! | 18:11 |
| *** camus <camus!~Instantbi@58.246.136.202> has joined #yocto | 18:24 | |
| *** camus1 <camus1!~Instantbi@58.246.136.202> has joined #yocto | 18:34 | |
| *** ant__ <ant__!~ant@host-87-0-28-96.retail.telecomitalia.it> has joined #yocto | 18:35 | |
| *** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Ping timeout: 252 seconds) | 18:35 | |
| *** camus1 is now known as camus | 18:35 | |
| *** aleblanc <aleblanc!~aleblanc@192-222-183-114.qc.cable.ebox.net> has joined #yocto | 18:50 | |
| *** yates_work <yates_work!~user@096-036-098-109.biz.spectrum.com> has joined #yocto | 18:52 | |
| *** TurtleCrazy[m] <TurtleCrazy[m]!~patronkre@2001:470:69fc:105::bd44> has left #yocto | 18:53 | |
| rpcme | Is there an estimate of a target date for yocto-check-layer to go active for dunfell? I will want to ensure that I am available when it goes live "just in case"... | 18:54 |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto | 19:25 | |
| RP | sakoman: see rpcme above | 19:52 |
| sakoman | rpcme: The patches were sent to the mailing list for review this morning. If there are no objections I'll send a pull request to Richard at end of day Monday, and they will go live once he takes the pull request | 19:53 |
| sakoman | The 3.1.10 QA report comes out tomorrow, so I have been avoiding pushing anything to dunfell just in case they find an issue at the last minute | 19:54 |
| sakoman | fwiw, meta-aws, meta-intel, and meta-openembedded all passed the check-layer-nightly build in my test branch | 19:58 |
| *** frieder <frieder!~frieder@7-69-142-46.pool.kielnet.net> has quit IRC (Remote host closed the connection) | 20:16 | |
| *** xtopher_ <xtopher_!sid495823@id-495823.tinside.irccloud.com> has quit IRC (Ping timeout: 272 seconds) | 20:16 | |
| *** ndec <ndec!sid219321@id-219321.tinside.irccloud.com> has quit IRC (Ping timeout: 272 seconds) | 20:16 | |
| *** nohit <nohit!sid334887@id-334887.tinside.irccloud.com> has quit IRC (Ping timeout: 256 seconds) | 20:17 | |
| *** fancer <fancer!fancer@id-180736.tinside.irccloud.com> has quit IRC (Ping timeout: 256 seconds) | 20:17 | |
| *** georgem <georgem!uid210681@id-210681.tinside.irccloud.com> has quit IRC (Ping timeout: 251 seconds) | 20:17 | |
| *** camus1 <camus1!~Instantbi@58.246.136.202> has joined #yocto | 20:21 | |
| *** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Ping timeout: 252 seconds) | 20:22 | |
| *** camus1 is now known as camus | 20:22 | |
| yates_work | there is a recipe for libffi in oe: meta/recipes-support/libffi/libffi_3.3.bb | 20:32 |
| *** xtopher_ <xtopher_!sid495823@tinside.irccloud.com> has joined #yocto | 20:32 | |
| yates_work | is there anything anywhere else in oe that depends on libffi being version 3.3? | 20:32 |
| yates_work | asked another way, is the mere presence of the libffi_3.3.bb recipe what establishes version 3.3 of libffi? | 20:33 |
| yates_work | i ask because i need to use a newer version | 20:33 |
| rpcme | sakoman: thank you very much - love the progress - will ensure I'm around Monday | 20:34 |
| *** georgem <georgem!uid210681@tinside.irccloud.com> has joined #yocto | 20:43 | |
| *** fancer <fancer!fancer@tinside.irccloud.com> has joined #yocto | 20:44 | |
| Xagen | yates_work: I've upgraded versions before by simply changing the version in the recipe filename as that's what is used when it's pulling it from the repo | 20:48 |
| Xagen | yates_work: i've generally only ever had to do that and change checksums if it's not pulling from a git repo | 20:49 |
| yates_work | Xagen: thanks. so if you have version 3.3 in one layer and version 3.4 in another, yocto will choose the latest version? | 21:03 |
| *** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has quit IRC (Quit: Client closed) | 21:03 | |
| *** ndec <ndec!sid219321@tinside.irccloud.com> has joined #yocto | 21:03 | |
| *** ChanServ sets mode: +v ndec | 21:03 | |
| Xagen | you can set your PREFERRED_VERSION_libffi to your target version if there are multiple ones available | 21:04 |
| *** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has joined #yocto | 21:08 | |
| vd | FOO ??= "A" ; FOO_append = "B"; would FOO equal "AB"? | 21:19 |
| kergoth | yes | 21:20 |
| vd | ok, _append really happens after the assignment, regardless the assignment was weak or not. | 21:21 |
| *** amitk <amitk!~amit@103.208.69.19> has quit IRC (Ping timeout: 272 seconds) | 21:50 | |
| *** rpcme <rpcme!~rpcme@52.95.4.12> has quit IRC (Quit: Client closed) | 21:50 | |
| *** yates_work <yates_work!~user@096-036-098-109.biz.spectrum.com> has quit IRC (Remote host closed the connection) | 21:51 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 21:57 | |
| *** jwillikers <jwillikers!~jwilliker@2604:2800:2:a403:fe91:ac3e:5153:1290> has quit IRC (Remote host closed the connection) | 22:10 | |
| *** creich <creich!~creich@p200300f6af354710000000000000039b.dip0.t-ipconnect.de> has joined #yocto | 22:13 | |
| *** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto | 22:19 | |
| *** goliath <goliath!~goliath@user/goliath> has joined #yocto | 22:23 | |
| *** rpcme <rpcme!~rpcme@52.95.4.12> has joined #yocto | 22:41 | |
| *** florian_kc <florian_kc!~florian@dynamic-093-131-060-085.93.131.pool.telefonica.de> has quit IRC (Ping timeout: 258 seconds) | 22:58 | |
| *** mihai <mihai!~mihai@user/mihai> has quit IRC (Ping timeout: 245 seconds) | 23:08 | |
| *** leon-anavi <leon-anavi!~Leon@78.130.197.211> has quit IRC (Quit: Leaving) | 23:44 | |
| *** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Quit: jmiehe) | 23:47 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!