| moto-timo | kevinrowland: the package manager has a "cache" on target and therefore know what it has installed vs what the "package feed" (at the simplest just a 'python3 httpserver' on the proper directory in deploy) | 00:00 |
|---|---|---|
| moto-timo | this "package feed" workflow does require a "PR server" to be sane. And you might end up needing to bump "PR" in recipes to make it work. It's not without pain. | 00:00 |
| moto-timo | kevinrowland: there are also things in the wiki or TipsNTricks about it... some of that is "write once wiki" and needs updating | 00:01 |
| kevinrowland | moto-timo: gotcha. I wonder if the "package feed" thing is a little too heavy weight for us.. especially reading your latest message about ${PR}. I'll take a look either way. At the end of the day I just want to deploy valgrind or similar debug tools when needed | 00:03 |
| moto-timo | kevinrowland: it's not as _simple_ people want it to be, but a NFS root/TFPT workflow allows very very rapid developer cycles... but it is far enough from production that I rarely use that tool | 00:04 |
| moto-timo | kevinrowland: there is also the eSDK workflow, but it needs a bit of love so I won't go out on a limb on it | 00:12 |
| moto-timo | kevinrowland: "eSDK workflow" as implied by https://www.youtube.com/watch?v=d3xanDJuXRA | 00:15 |
| RP | halstead, michaelo: The docs issues are because there is a warning and the docs fail to build on multiple releases | 00:20 |
| RP | ref-manual/variables.rst:760: WARNING: term not in glossary: BB_HASHBASE_WHITELIST | 00:21 |
| *** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 256 seconds) | 00:35 | |
| moto-timo | kevinrowland: there might be room for an enhancement to devtool to allow "deploy package"... but no promises | 00:39 |
| moto-timo | kevinrowland: we honestly have almost no resources supporting devtool/recipetool and other parts of the infrastructure... sad but true | 00:40 |
| *** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto | 00:41 | |
| *** JaMa is now known as Guest2142 | 00:44 | |
| *** JaMa <JaMa!~martin@78.80.214.103> has joined #yocto | 00:44 | |
| kevinrowland | moto-timo: you mean there's a branch up for that "deploy package" work? Or it's just an idea you're kicking around? | 00:56 |
| kevinrowland | I did see this earlier today: https://patchwork.openembedded.org/patch/151466/ -- v1 of the patch has some good discussion too | 01:00 |
| moto-timo | kevinrowland: Just throwing out a random thought. No attempt at validity or verification. | 01:00 |
| moto-timo | kevinrowland: there you go. that is a GoodIdeaTM | 01:01 |
| moto-timo | I do care about this, but it is a bit draining to move forward when we are struggling to get releases out the door. And I apologize for being particularly exhausted as we push for the feature freeze. | 01:03 |
| moto-timo | I am more than willing to help advise technically and move such a feature forward | 01:03 |
| *** vmeson <vmeson!~rmacleod@198-48-226-187.cpe.pppoe.ca> has quit IRC (Remote host closed the connection) | 01:12 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 240 seconds) | 01:14 | |
| *** vmeson <vmeson!~rmacleod@198-48-226-187.cpe.pppoe.ca> has joined #yocto | 01:14 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto | 01:19 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 240 seconds) | 01:25 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto | 01:26 | |
| *** qschulz <qschulz!~weechat@ns326003.ip-37-187-106.eu> has quit IRC (Remote host closed the connection) | 01:32 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 256 seconds) | 01:32 | |
| *** Starfoxxes <Starfoxxes!~Starfoxxe@2a02:8070:5390:d00:12bf:48ff:feb8:38c8> has quit IRC (Ping timeout: 252 seconds) | 01:33 | |
| *** Starfoxxes <Starfoxxes!~Starfoxxe@2a02:8070:5390:d00:12bf:48ff:feb8:38c8> has joined #yocto | 01:34 | |
| *** qschulz <qschulz!~weechat@ns326003.ip-37-187-106.eu> has joined #yocto | 01:35 | |
| *** chep <chep!~chep@82-65-36-115.subs.proxad.net> has quit IRC (Read error: Connection reset by peer) | 01:37 | |
| *** chep` <chep`!~chep@82-65-36-115.subs.proxad.net> has joined #yocto | 01:37 | |
| *** chep` is now known as chep | 01:37 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto | 01:38 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Ping timeout: 256 seconds) | 01:44 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 272 seconds) | 01:46 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto | 01:51 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 272 seconds) | 01:57 | |
| *** GillesM <GillesM!~gilles@233.95.127.78.rev.sfr.net> has quit IRC (Remote host closed the connection) | 01:58 | |
| *** bluelightning <bluelightning!~paul@2406:e003:151f:d701:84c0:da9:568e:a3a6> has quit IRC (Ping timeout: 240 seconds) | 02:01 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto | 02:02 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto | 02:06 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 272 seconds) | 02:08 | |
| *** taco___ <taco___!~taco@94.140.9.71> has quit IRC (Quit: Client closed) | 02:10 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto | 02:14 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 256 seconds) | 02:18 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto | 02:24 | |
| *** RobertBerger <RobertBerger!~rber|res@ppp-2-86-136-96.home.otenet.gr> has joined #yocto | 02:32 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 256 seconds) | 02:33 | |
| *** rber|res <rber|res!~rber|res@ppp-2-86-136-96.home.otenet.gr> has quit IRC (Ping timeout: 245 seconds) | 02:34 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto | 02:38 | |
| *** gjm <gjm!~gjm@2603-6080-2d05-14c8-d413-41ff-fead-6ef1.res6.spectrum.com> has joined #yocto | 02:41 | |
| *** gjm is now known as gmalysa | 02:42 | |
| moto-timo | "All" the failures in the current build for python packaging are due to the /usr/bin/nativepython3 overwrite that pip is doing on installing scripts to ${bindir} https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/3272 | 02:42 |
| moto-timo | https://git.yoctoproject.org/poky/tree/meta/classes/pip_install_wheel.bbclass?h=master-next&id=7a620118433c7d3e4762760eb0fe0fcf4e4e9845#n32 | 02:43 |
| moto-timo | any help is appreciated to get us across the finishing line | 02:43 |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 240 seconds) | 02:47 | |
| *** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto | 02:50 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto | 02:52 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 02:53 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Quit: Ping timeout (120 seconds)) | 02:58 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto | 02:58 | |
| *** amitk <amitk!~amit@103.59.74.60> has joined #yocto | 03:02 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 240 seconds) | 03:04 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto | 03:09 | |
| *** kevinrowland <kevinrowland!~kevinrowl@104.129.199.51> has quit IRC (Quit: Client closed) | 03:17 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 256 seconds) | 03:20 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto | 03:26 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 256 seconds) | 03:32 | |
| *** gmalysa <gmalysa!~gjm@2603-6080-2d05-14c8-d413-41ff-fead-6ef1.res6.spectrum.com> has quit IRC (Quit: Client closed) | 03:35 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto | 03:38 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 256 seconds) | 03:46 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto | 03:52 | |
| *** jclsn71 <jclsn71!~jclsn@95.163.173.57.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto | 03:57 | |
| *** pgowda_ <pgowda_!uid516182@id-516182.ilkley.irccloud.com> has joined #yocto | 03:58 | |
| *** jclsn7 <jclsn7!~jclsn@84.46.23.188.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 272 seconds) | 04:00 | |
| *** jclsn71 is now known as jclsn7 | 04:00 | |
| *** jclsn7 <jclsn7!~jclsn@95.163.173.57.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 256 seconds) | 04:05 | |
| *** jclsn7 <jclsn7!~jclsn@95.163.173.57.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto | 04:11 | |
| *** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.) | 04:57 | |
| *** gmalysa <gmalysa!~gmalysa@2603-6080-2d05-14c8-d413-41ff-fead-6ef1.res6.spectrum.com> has joined #yocto | 05:23 | |
| *** rfs613 <rfs613!~rfs613@rfs.netwinder.org> has quit IRC (Quit: restart) | 05:45 | |
| *** rfs613 <rfs613!~rfs613@rfs.netwinder.org> has joined #yocto | 05:45 | |
| *** fitzsim <fitzsim!~user@69-165-165-189.dsl.teksavvy.com> has quit IRC (Read error: Connection reset by peer) | 06:07 | |
| *** gmalysa <gmalysa!~gmalysa@2603-6080-2d05-14c8-d413-41ff-fead-6ef1.res6.spectrum.com> has quit IRC (Quit: Client closed) | 06:18 | |
| *** mrnuke <mrnuke!~mrnuke@c-98-195-139-126.hsd1.tx.comcast.net> has quit IRC (Read error: Connection reset by peer) | 06:34 | |
| *** mrnuke <mrnuke!~mrnuke@2601:2c1:8501:182d::c66> has joined #yocto | 06:34 | |
| *** dmoseley <dmoseley!~dmoseley@24.96.56.90> has quit IRC (Ping timeout: 240 seconds) | 06:41 | |
| *** dmoseley <dmoseley!~dmoseley@24.96.56.90> has joined #yocto | 06:42 | |
| *** rob_w <rob_w!~rob@2001:a61:6050:d201:e45d:6190:f58a:6c8c> has joined #yocto | 06:59 | |
| *** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has joined #yocto | 07:01 | |
| *** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has quit IRC (Read error: Connection reset by peer) | 07:09 | |
| *** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has joined #yocto | 07:10 | |
| *** goliath <goliath!~goliath@user/goliath> has joined #yocto | 07:16 | |
| *** mvlad <mvlad!~mvlad@2a02:2f08:4b12:b100:24d7:51ff:fed6:906d> has joined #yocto | 07:19 | |
| *** mrnuke <mrnuke!~mrnuke@2601:2c1:8501:182d::c66> has quit IRC (Ping timeout: 250 seconds) | 07:32 | |
| *** osama3 <osama3!~osama@ipbcc2935c.dynamic.kabel-deutschland.de> has joined #yocto | 07:37 | |
| *** Etheryon <Etheryon!~textual@79.113.77.204> has joined #yocto | 07:38 | |
| *** osama4 <osama4!~osama@eth1-fw1-nbg6.eb.noris.de> has joined #yocto | 07:38 | |
| *** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection) | 07:39 | |
| *** mckoan|away is now known as mckoan | 07:41 | |
| *** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto | 07:41 | |
| *** osama3 <osama3!~osama@ipbcc2935c.dynamic.kabel-deutschland.de> has quit IRC (Ping timeout: 240 seconds) | 07:42 | |
| *** osama4 <osama4!~osama@eth1-fw1-nbg6.eb.noris.de> has quit IRC (Ping timeout: 272 seconds) | 07:43 | |
| *** frieder <frieder!~frieder@i59F4BC00.versanet.de> has joined #yocto | 07:44 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 07:46 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Client Quit) | 07:46 | |
| *** chbae <chbae!~chbae@pr-svc-em1-115.emea.corpinter.net> has joined #yocto | 07:50 | |
| *** tre <tre!~tre@ip5f5886dd.dynamic.kabel-deutschland.de> has joined #yocto | 08:02 | |
| *** oobitots <oobitots!~oobitots@aer01-mda1-dmz-wsa-3.cisco.com> has joined #yocto | 08:04 | |
| jclsn[m] | I am getting a lot of errors when using cog. Am I missing some flags?... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/575ea7fc93450262133291c6dbaefb09649c44d9) | 08:06 |
| jclsn[m] | The UI is also not shown | 08:06 |
| jclsn[m] | * I am getting a lot of errors when using cog. Am I missing some flags?... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/6017f47b46596aa50d0318fde4c31d9ef9f01401) | 08:11 |
| jclsn[m] | * I am getting some errors when using cog. Am I missing some flags?... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/6f400175662ba16fa0fb0ee4b2d7e681470ba263) | 08:11 |
| *** mrnuke <mrnuke!~mrnuke@2601:2c1:8501:182d::c66> has joined #yocto | 08:14 | |
| *** oobitots <oobitots!~oobitots@aer01-mda1-dmz-wsa-3.cisco.com> has quit IRC (Quit: Client closed) | 08:20 | |
| *** chbae <chbae!~chbae@pr-svc-em1-115.emea.corpinter.net> has quit IRC (Quit: Client closed) | 08:22 | |
| *** Austriker <Austriker!~Austriker@2a01cb040a70ef0001037a9bc4d02f26.ipv6.abo.wanadoo.fr> has joined #yocto | 08:26 | |
| *** ilunev <ilunev!~koolkhel@2a00:8740:2c:5ca1:30bf:76d:19db:2a98> has quit IRC (Ping timeout: 256 seconds) | 08:27 | |
| *** thekappe <thekappe!~thekappe@198.90.66.177> has joined #yocto | 08:29 | |
| jclsn[m] | There is no documentation | 08:29 |
| jclsn[m] | Seems like a very immature application | 08:29 |
| *** JaMa <JaMa!~martin@78.80.214.103> has quit IRC (Ping timeout: 256 seconds) | 08:34 | |
| *** ilunev <ilunev!~koolkhel@2a00:8740:2c:5ca1:f04f:a7fc:f3f:f7a4> has joined #yocto | 08:34 | |
| *** ilunev <ilunev!~koolkhel@2a00:8740:2c:5ca1:f04f:a7fc:f3f:f7a4> has quit IRC (Ping timeout: 240 seconds) | 08:39 | |
| thekappe | Hello guys !! I'm trying to bitbake this recipe: https://github.com/sartura/meta-sysrepo/blob/master/recipes-sysrepo/libyang/libyang_git.bb | 08:39 |
| *** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has joined #yocto | 08:40 | |
| thekappe | due to some errors I've already added "glibc" to "DEPENDS" and inherit autotools bash-completion pkgconfig | 08:41 |
| thekappe | Now I'm getting the following error: Exception: FileNotFoundError: [Errno 2] No such file or directory: '/home/user/yocto/build/tmp/sysroots-components/aarch64/gcc-runtime/sysroot-providers/gcc-runtime | 08:42 |
| thekappe | Does anyone has an idea on how to fix it ? | 08:42 |
| *** JaMa <JaMa!~martin@78.80.214.103> has joined #yocto | 08:42 | |
| *** ilunev <ilunev!~koolkhel@95.174.114.239> has joined #yocto | 08:51 | |
| *** ilunev <ilunev!~koolkhel@95.174.114.239> has quit IRC (Read error: Connection reset by peer) | 08:53 | |
| *** asconcepcion[m] <asconcepcion[m]!~asconcepc@2001:470:69fc:105::1:73ea> has quit IRC (Quit: You have been kicked for being idle) | 09:00 | |
| *** ilunev <ilunev!~koolkhel@95.174.114.211> has joined #yocto | 09:09 | |
| *** ilunev <ilunev!~koolkhel@95.174.114.211> has quit IRC (Client Quit) | 09:10 | |
| *** Austriker <Austriker!~Austriker@2a01cb040a70ef0001037a9bc4d02f26.ipv6.abo.wanadoo.fr> has quit IRC (Ping timeout: 256 seconds) | 09:11 | |
| *** osama4 <osama4!~osama@eth1-fw1-nbg6.eb.noris.de> has joined #yocto | 09:12 | |
| *** osama4 <osama4!~osama@eth1-fw1-nbg6.eb.noris.de> has quit IRC (Read error: Connection reset by peer) | 09:17 | |
| qschulz | RP: michaelo: halstead: I'm not sure this is actually an issue? The make flags are -W (https://www.sphinx-doc.org/en/master/man/sphinx-build.html#cmdoption-sphinx-build-w) and --keep-going (https://www.sphinx-doc.org/en/master/man/sphinx-build.html#cmdoption-sphinx-build-keep-going) the build should continue and just exit with non-zero code | 09:19 |
| *** behanw <behanw!uid110099@id-110099.uxbridge.irccloud.com> has quit IRC (Quit: Connection closed for inactivity) | 09:19 | |
| qschulz | FWIW, I tested locally, and the index page is generated and I can access it | 09:20 |
| *** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@94.31.103.247> has quit IRC (Ping timeout: 256 seconds) | 09:37 | |
| *** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@94.31.103.247> has joined #yocto | 09:39 | |
| *** osama4 <osama4!~osama@eth1-fw1-nbg6.eb.noris.de> has joined #yocto | 09:42 | |
| *** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Quit: ZZZzzz…) | 09:47 | |
| *** oobitots <oobitots!~oobitots@aer01-mda2-dmz-wsa-4.cisco.com> has joined #yocto | 09:47 | |
| *** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto | 09:48 | |
| RP | qschulz: something isn't working as for example 3.4.1 is missing | 09:56 |
| qschulz | can we add `set -eu` to this script so we have an idea if an issue arises and stop the script from running? | 09:57 |
| RP | qschulz: probably, I don't know if that will cause any other issues but we could try | 09:57 |
| qschulz | RP: e.g. could simply be some rsync issue? I seem to recall reading somewhere there are intermittent network issues? | 09:57 |
| RP | qschulz: we see clear errors about things being missing before that so whilst that could occasionally be an issue, I'm not convinced | 09:58 |
| *** otavio <otavio!~otavio@201-3-135-79.paemt705.dsl.brasiltelecom.net.br> has quit IRC (Read error: Connection reset by peer) | 10:02 | |
| *** otavio <otavio!~otavio@201-3-135-79.user3p.brasiltelecom.net.br> has joined #yocto | 10:06 | |
| *** Dracos-Carazza_ <Dracos-Carazza_!~Dracos-Ca@94.31.103.247> has joined #yocto | 10:10 | |
| *** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@94.31.103.247> has quit IRC (Ping timeout: 272 seconds) | 10:12 | |
| *** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto | 10:13 | |
| mcfrisk | is the some QA check in poky for images to e.g. check that /usr/include doesn't exist, maybe one that can be configured for forbidden content to avoid developers doing silly things | 10:17 |
| *** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV) | 10:18 | |
| *** JaMa <JaMa!~martin@78.80.214.103> has quit IRC (Killed (tantalum.libera.chat (Nickname regained by services))) | 10:23 | |
| *** Guest2142 is now known as JaMa | 10:23 | |
| *** JaMa is now known as Guest6741 | 10:23 | |
| *** Guest6741 <Guest6741!~martin@109.238.218.228> has quit IRC (Killed (zirconium.libera.chat (Nickname regained by services))) | 10:23 | |
| *** JaMa <JaMa!~martin@78.80.214.103> has joined #yocto | 10:23 | |
| *** JaMa is now known as Guest6151 | 10:23 | |
| *** Guest6151 <Guest6151!~martin@78.80.214.103> has quit IRC (Killed (silver.libera.chat (Nickname regained by services))) | 10:23 | |
| *** JaMa <JaMa!~martin@ip-109-238-218-228.aim-net.cz> has joined #yocto | 10:23 | |
| Saur[m] | mcfisk. There is, kind of (in master, and once 3.4.2 is released it will work in Honister as well). The check QA check is called "empty-dirs" and is used to validate that a directory is empty. The variable QA_EMPTY_DIRS is used to define the list of directories that are expected to be empty (see insane.bbclass). | 10:25 |
| RP | mcfrisk: no, it could be something we could add though | 10:27 |
| Saur[m] | It can typically be used to make sure that files are not installed into directories that will be used as mount points, or to make sure that files are not being installed into the wrong directories. | 10:27 |
| RP | mcfrisk: I like Saur[m]'s approach | 10:28 |
| *** JaMa is now known as Guest7223 | 10:28 | |
| *** JaMa <JaMa!~martin@78.80.214.103> has joined #yocto | 10:28 | |
| Saur[m] | It also allows to define a message per directory that will be shown in case a file is installed in the directory, so one can give an informative message as to what one should do instead. See QA_EMPTY_DIRS_RECOMMENDATION in insane.bbclass. | 10:31 |
| *** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 256 seconds) | 10:34 | |
| mcfrisk | thanks Saur[m] RP, I'll have a look and possibly cherry-pick to my dunfell tree | 10:34 |
| *** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto | 10:36 | |
| qschulz | RP: I'm even tempted to set -x in the script | 10:55 |
| Perceval[m] | Hello all, on my yocto distrib I Have the following error regularly | 10:56 |
| Perceval[m] | systemd-journald[3073]: Forwarding to syslog missed 28 messages. | 10:56 |
| Perceval[m] | do you have an idea on where it could come from? | 10:56 |
| Perceval[m] | I know that it is the forwarding from systemd logging system to syslog, but I don't know what service or soft could cause such error | 10:57 |
| *** Thorn <Thorn!~Thorn@user/thorn> has quit IRC (Ping timeout: 256 seconds) | 10:59 | |
| RP | qschulz: I was wondering to. We could try a patch? | 11:02 |
| *** Thorn <Thorn!~Thorn@user/thorn> has joined #yocto | 11:02 | |
| qschulz | RP: preparing something yes, will send soon | 11:03 |
| LetoThe2nd | yo dudX | 11:07 |
| *** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto | 11:08 | |
| *** goliath <goliath!~goliath@user/goliath> has joined #yocto | 11:11 | |
| *** lucaceresoli <lucaceresoli!~ceresoli@host-79-2-93-196.business.telecomitalia.it> has joined #yocto | 11:18 | |
| qschulz | RP: mmm set -e isn't a great idea since old branches of the docs might throw warnings and then fail | 11:25 |
| qschulz | I'll send it anyway, so we can start discussing this stuff | 11:25 |
| *** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has quit IRC (Quit: Client closed) | 11:25 | |
| *** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has joined #yocto | 11:33 | |
| *** JaMa is now known as Guest889 | 11:36 | |
| *** Guest7223 is now known as JaMa | 11:36 | |
| *** Guest889 <Guest889!~martin@78.80.214.103> has quit IRC (Remote host closed the connection) | 11:36 | |
| *** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 272 seconds) | 11:43 | |
| *** mauro_anjo <mauro_anjo!~quassel@191.13.251.42> has joined #yocto | 11:45 | |
| *** tre <tre!~tre@ip5f5886dd.dynamic.kabel-deutschland.de> has quit IRC (Ping timeout: 272 seconds) | 11:51 | |
| *** thekappe <thekappe!~thekappe@198.90.66.177> has quit IRC (Ping timeout: 256 seconds) | 12:02 | |
| *** tre <tre!~tre@ip5f5886dd.dynamic.kabel-deutschland.de> has joined #yocto | 12:03 | |
| *** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has quit IRC (Quit: Client closed) | 12:06 | |
| *** fitzsim <fitzsim!~user@69-165-165-189.dsl.teksavvy.com> has joined #yocto | 12:11 | |
| *** thekappe <thekappe!~thekappe@198.90.66.177> has joined #yocto | 12:16 | |
| *** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto | 12:16 | |
| thekappe | hello guys, I have to build the A recipe that RDPENDS from the B recipe. The point is that B must be compiled with unicode support (--enable-utf --enable-unicode-properties) there is a way to instruct bitbake to compile B with the proper flag while bitbaking A ? | 12:16 |
| RP | michaelo: I'm thinking we should apply qschulz's changes quickly? | 12:32 |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 12:32 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Remote host closed the connection) | 12:33 | |
| RP | kanavin_: your changing TARGET_ARCH in the cross recipes is worrying me | 12:36 |
| RP | kanavin_: The intent, at least for cross canadian was to have one arch compiler which targeted all the different SYS pieces | 12:37 |
| RP | cross is a little bit less clear but in theory the same mapping could apply | 12:37 |
| kanavin_ | RP: gcc-cross-arm-none-eabi needs to be configured differently to gcc-cross-arm-poky-linux: "--with-sysroot= --with-headers=no --disable-gcov --disable-threads --enable-multilib --with-multilib-list=rmprofile,aprofile" | 12:40 |
| kanavin_ | RP: even then, I wouldn't necessarily trust that --target=arm-poky-linux would produce the same output as --target=arm-none-eabi | 12:41 |
| kanavin_ | RP: that said, I reverted that change locally, as I knew it would be tough sell, and I was right ;) | 12:41 |
| RP | kanavin_: why does it need to be configured differently? | 12:43 |
| kanavin_ | RP: because it needs to build libgcc pieces in absence of libc | 12:43 |
| RP | kanavin_: libgcc needs to be configured differently, sure | 12:44 |
| RP | we build gcc-cross and libgcc in separate recipes | 12:44 |
| kanavin_ | RP: the way we build libgcc is 'copy preconfigured gcc build tree into $S, run make in libgcc subdir'. | 12:45 |
| kanavin_ | there is no separate configuration step for libgcc | 12:45 |
| RP | kanavin_: well, there probably should be as these things aren't that tied together (and aren't in cross-canadian) | 12:46 |
| kanavin_ | RP: right, I am now checking how this is done in cross-canadian sdk builds | 12:46 |
| RP | like a lot of things, I've tried to clean up and separate out the pieces over time but it only gets so far | 12:46 |
| kanavin_ | makes one wish for multi-target toolchains like rust ;) | 12:47 |
| RP | kanavin_: cross-canadian doesn't need it's own libgcc so in that sense it can cheat and use the target one we have already | 12:47 |
| RP | kanavin_: but the fact that cross-canadian works with that shows gcc-cross isn't sys specific if you pass the right params in | 12:47 |
| RP | kanavin_: there is no good reason gcc can't be multi target, it just can't do multi arch | 12:48 |
| kanavin_ | RP: gcc-cross isn't but libgcc is, and the params you need to pass for libgcc are passed via gcc-cross | 12:48 |
| kanavin_ | (see above) | 12:50 |
| RP | kanavin_: Right, I agree that is a problem today :( | 12:50 |
| RP | I was just trying to share the direction I was trying to move things in | 12:50 |
| RP | gcc-cross is meant to only rebuild per arch. Obviously it doesn't quite work right today :( | 12:51 |
| kanavin_ | it also shouldn't require target libc to build, but alas, it does | 12:51 |
| kanavin_ | for libgcc | 12:52 |
| kanavin_ | unless you suppress that with a bunch of not-obvious options | 12:52 |
| RP | kanavin_: it depends. musl doesn't have that issue, glibc does | 12:52 |
| RP | the dependencies are tweaked accordingly but you'll find it uses the same gcc-cross for both | 12:53 |
| RP | despite them being different _SYS | 12:53 |
| kanavin_ | RP: I wish gcc upstream would better separate the pieces, and not control everything through a top level configure | 12:54 |
| RP | kanavin_: well, yes | 12:55 |
| kanavin_ | I understood just enough of it to do what the customer wants, but the whole thing is just short of collapsing under its own complexity | 12:55 |
| RP | kanavin_: I have tried to improve things on several occasions, I keep chipping away at it | 12:55 |
| RP | which is why I felt I should warn you that patch didn't look quite right to me | 12:56 |
| RP | but if you want to tell me I'm wrong, whatever, I have a large queue of problems today :( | 12:56 |
| kanavin_ | RP: the patch is already reverted locally | 12:57 |
| kanavin_ | I found a way to build additional gcc-cross without changing the confuguration for the main one, but I didn't find a way to decouple libgcc from gcc-cross | 12:58 |
| RP | kanavin_: I would have to go and look at the code again to be able to give useful feedback :( | 12:59 |
| kanavin_ | RP: you also would need to look at https://github.com/kanavin/meta-cross-toolchain which is also work in progress and missing latest tweaks | 13:00 |
| kanavin_ | RP: maybe it's best to wait until I'm happy with it, and ready to submit for review :) | 13:00 |
| kanavin_ | and yes I'm abusing mcextend on a grand scale there, I love how I can avoid writing extra recipes with it :) | 13:01 |
| RP | kanavin_: I'm just worried about you spending a ton of time on something which isn't a direction I'm comfortable with, that was the reason I mention it | 13:02 |
| RP | kanavin_: that was probably more what the standard class extensions were for rather than mcextend :/ | 13:02 |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto | 13:05 | |
| RP | qschulz: "we probably want to use virtualenv with specific Sphinx versions" - this fills me with dread making this work over all the distros on the autobuilder :( | 13:05 |
| michaelo | RP, qschulz: I agree. This way we know what happens. | 13:05 |
| kanavin_ | RP: thanks for the tip, if the standard class extension works, that'd be easy to adjust - much easier than sorting the multi-cross issue | 13:06 |
| RP | michaelo: I was meaning the docs list fix for basehash | 13:06 |
| RP | the script changes in helper I'm worried about making work well :/ | 13:06 |
| RP | we probably want the script to run all the different pieces, collect up the exit code and skip the rsync if anything fails? | 13:06 |
| *** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 240 seconds) | 13:08 | |
| RP | then the build will fail, the docs website would be ok but we have a list of all the failures | 13:08 |
| kanavin_ | RP: if that helps with the worry, I warned the customer there is no certainty in upstreaming the needed tweaks in the time scale they agreed to pay for. It's a problem that might become important in the future as people would want to build things using one part of the target system that is capable of builds for the other part of the system that is too constrained to host a compiler for itself | 13:09 |
| *** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto | 13:18 | |
| *** diesUndDas <diesUndDas!~diesUndDa@p54abbba5.dip0.t-ipconnect.de> has joined #yocto | 13:19 | |
| diesUndDas | Hello guys, I am confused. | 13:20 |
| diesUndDas | I would like to create a symlink to a library, in this case it is libsdl2.So I have created a bbappend and set FILE_${PN} to /usr/lib/libSDL2.so | 13:20 |
| diesUndDas | But it get's removed by do_populate_sysroot :( | 13:21 |
| rburton | what does your bbappend actually contain? | 13:23 |
| diesUndDas | Just two lines: | 13:24 |
| diesUndDas | FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" | 13:24 |
| diesUndDas | FILES_${PN} += "/usr/lib/libSDL2.so" | 13:24 |
| diesUndDas | I have created the bbappend file with the recipetool | 13:25 |
| rburton | you don't need to set FILESEXTRAPATHS if you're not adding patches | 13:27 |
| rburton | I presume this is a libsdl2.bbappend? | 13:27 |
| michaelo | RP: now I understand you're talking about qschulz' doc changes, not his changes to run-docs-build. I'm merging them into master-next and preparing a pull-request. | 13:28 |
| diesUndDas | rburton: okay, I am going to remove it then. Almost, it is a libsdl2_%.bbappend | 13:30 |
| rburton | diesUndDas: so packaging happens in the order of packages in the PACKAGES variable. PN-dev is before PN, and that contains ${libdir}/*.so, because those symlinks are only needed at build time | 13:31 |
| rburton | diesUndDas: so if you've something that is dlopen()ing libsdl.so, then it's broken | 13:31 |
| diesUndDas | rburton: Why is it going to be broken? Isn't it referencing the actual libsdl2 shared library anymore? :S | 13:34 |
| rburton | no distribution will ship the .so on its own unless it also ships the headers and stuff | 13:34 |
| *** vladest1 <vladest1!~Thunderbi@2001:1715:9d9c:c530:5c77:7106:6f60:1b41> has joined #yocto | 13:35 | |
| diesUndDas | :( | 13:35 |
| diesUndDas | And how can I tell the buildsystem to create one? | 13:35 |
| rburton | step back: why do you need libSDL2.so to exist | 13:35 |
| rburton | https://packages.debian.org/search?searchon=contents&keywords=libSDL2.so&mode=path&suite=stable&arch=any <-- for example, on debian libSDL2.so is only packaged in libsdl2-dev | 13:36 |
| *** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:f83a:7917:7f6a:ff7> has quit IRC (Ping timeout: 250 seconds) | 13:37 | |
| *** vladest1 is now known as vladest | 13:37 | |
| diesUndDas | rburton: because an application tries to load the library as "libSDL2.so". I assume that's not how it should be done? :D | 13:38 |
| rburton | does it dlopen() at runtime? | 13:38 |
| *** ecdhe_ <ecdhe_!~ecdhe@user/ecdhe> has quit IRC (Ping timeout: 260 seconds) | 13:39 | |
| rburton | if so, yes, that's wrong. | 13:40 |
| rburton | if you *really* need to do this you can remove the .so from FILES:PN-dev so they end up in PN. but the application is the problem. | 13:40 |
| qschulz | RP: sorry was away.. What are the issues you're foreseeing with virtualenv for the docs? | 13:48 |
| qschulz | michaelo: RP: also re the docs, we probably want to update the renamed variables too. Didn't have the time now but I guess a good starting point is convert-variable-renames script? | 13:49 |
| *** ldericher <ldericher!~LDer@pantalaimon.yavook.de> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in) | 13:57 | |
| RP | qschulz: trying to get that to work reliably on all the different distros/workers on the autobuilder? | 13:58 |
| qschulz | RP: you mean without virtualenv? | 13:59 |
| qschulz | because virtualenv is supposed to fix this issue? or maybe I'm overestimating the benefit of using virtualenv over its cost? | 13:59 |
| RP | qschulz: I'm sure it is supposed to fix it but I also somehow doubt it will behave on all the different distros/python versions the same way | 14:00 |
| *** olani <olani!~olani@h87-96-160-54.cust.a3fiber.se> has joined #yocto | 14:02 | |
| diesUndDas | rburton: The problem lies in dotnet 6 :( | 14:04 |
| diesUndDas | If I say "LD_DEBUG=libs dotnet SDL2-Example" on the target, I get: | 14:04 |
| diesUndDas | 1029: find library=libSDL2.so [0]; searching | 14:05 |
| diesUndDas | 1029: search cache=/etc/ld.so.cache | 14:05 |
| diesUndDas | 1029: search path=/lib:/usr/lib (system search path) | 14:05 |
| diesUndDas | 1029: trying file=/lib/libSDL2.so | 14:05 |
| diesUndDas | 1029: trying file=/usr/lib/libSDL2.so | 14:05 |
| diesUndDas | 1029: | 14:05 |
| diesUndDas | 1029: find library=SDL2 [0]; searching | 14:05 |
| diesUndDas | 1029: search cache=/etc/ld.so.cache | 14:05 |
| diesUndDas | 1029: search path=/lib:/usr/lib (system search path) | 14:05 |
| diesUndDas | 1029: trying file=/lib/SDL2 | 14:05 |
| diesUndDas | 1029: trying file=/usr/lib/SDL2 | 14:05 |
| diesUndDas | 1029: | 14:05 |
| diesUndDas | 1029: find library=libSDL2 [0]; searching | 14:05 |
| diesUndDas | 1029: search cache=/etc/ld.so.cache | 14:05 |
| diesUndDas | 1029: search path=/lib:/usr/lib (system search path) 1029: trying file=/lib/libSDL2 | 14:05 |
| diesUndDas | 1029: trying file=/usr/lib/libSDL2 | 14:05 |
| rburton | yeah dotnet is dumb for exactly the same reason | 14:05 |
| diesUndDas | Oh man, ... | 14:05 |
| *** ldericher <ldericher!~LDer@pantalaimon.yavook.de> has joined #yocto | 14:06 | |
| diesUndDas | So my only option is to do it the wrong way then? | 14:06 |
| diesUndDas | rburton: and how should an application ideally load a shared library? :D | 14:07 |
| rburton | ideally, with the full name | 14:07 |
| diesUndDas | rburton: okay, thank you :) | 14:08 |
| *** amitk_ <amitk_!~amit@103.59.74.130> has joined #yocto | 14:09 | |
| qschulz | RP: ok I think I've found the issue with the docs. Do we have automated tests of the docs? | 14:11 |
| jclsn[m] | <diesUndDas> "Oh man, ..." <- dütt un datt! | 14:12 |
| jclsn[m] | diesdasananas | 14:12 |
| *** amitk <amitk!~amit@103.59.74.60> has quit IRC (Ping timeout: 256 seconds) | 14:13 | |
| RP | qschulz: no, we just build them | 14:13 |
| RP | rburton: with cve check, what happens if you have two builds in parallel with the same DL_DIR doing a cve_check fetch? | 14:16 |
| *** pasherring <pasherring!~pasherrin@2001:8a0:ec55:b200:27fc:a530:7097:2c60> has joined #yocto | 14:16 | |
| *** diesUndDas <diesUndDas!~diesUndDa@p54abbba5.dip0.t-ipconnect.de> has quit IRC (Quit: Client closed) | 14:17 | |
| RP | I thought we had a shared lock task flag but we don't, I think there is an sstate specific one | 14:18 |
| *** mihai <mihai!~mihai@user/mihai> has joined #yocto | 14:19 | |
| jclsn[m] | God you really need a 2TB drive when you want to build for multiple boards | 14:20 |
| qschulz | jclsn[m]: INHERIT += "rm_work" is a good friend usually :) | 14:20 |
| jclsn[m] | What does it do? | 14:21 |
| jclsn[m] | qschulz: Will it increase build time? | 14:23 |
| mihai | reusing downloads and sstate directories should also help | 14:23 |
| rburton | RP: they race on the file i guess | 14:23 |
| jclsn[m] | mihai: That I already do | 14:24 |
| rburton | RP: well, the lockfile is a filesystem lock right? so if they lock properly, it should work? | 14:24 |
| qschulz | jclsn[m]: I guess it could since it's going to remove files, so it's an additional command during the build | 14:24 |
| RP | rburton: I'm worried that one could be updating the DB whilst another accesses it. The question is whether than level of locking works over NFS | 14:25 |
| qschulz | jclsn[m]: https://docs.yoctoproject.org/ref-manual/classes.html#rm-work-bbclass | 14:25 |
| rburton | RP: same question but for two build trees doing a git fetch i guess | 14:25 |
| RP | rburton: yes. Except that bitbake does handle locking on DL_DIR for fetches/unpacks | 14:26 |
| *** codavi <codavi!~akiCA@user/akica> has joined #yocto | 14:28 | |
| jclsn[m] | qschulz: Thanks | 14:28 |
| *** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto | 14:29 | |
| *** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 250 seconds) | 14:33 | |
| *** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto | 14:34 | |
| *** ar__ <ar__!~akiCA@user/akica> has joined #yocto | 14:36 | |
| jclsn[m] | Where is the switch to use a fixed chromium version btw? | 14:36 |
| *** thekappe <thekappe!~thekappe@198.90.66.177> has quit IRC (Ping timeout: 256 seconds) | 14:36 | |
| jclsn[m] | It rebuilds frequently and it takes ages | 14:36 |
| jclsn[m] | Can't find it in the recipe. Should be PV | 14:36 |
| *** ldericher <ldericher!~LDer@pantalaimon.yavook.de> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in) | 14:36 | |
| *** ldericher <ldericher!~LDer@pantalaimon.yavook.de> has joined #yocto | 14:37 | |
| *** codavi <codavi!~akiCA@user/akica> has quit IRC (Ping timeout: 240 seconds) | 14:39 | |
| qschulz | jclsn[m]: if any dependency of Chromium gets rebuilt, Chromium will get rebuilt, there's no going around that unfortunately | 14:43 |
| *** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has quit IRC (Quit: Leaving) | 14:43 | |
| jclsn[m] | qschulz: Okay, I will ask my boss to reconsider that Threadripper then | 14:43 |
| *** TundraMan is now known as marka | 14:44 | |
| *** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:5c77:7106:6f60:1b41> has quit IRC (Quit: vladest) | 14:46 | |
| qschulz | RP: michaelo: halstead: pretty sure I fixed the most occurring issue with sphinx docs with the patch I just sent for the autobuilder | 14:47 |
| *** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:527b:127a:2d5a:c3c8> has joined #yocto | 14:47 | |
| qschulz | RP: I don't know what you think about that but I think it makes sense to set -eux -o pipefail and re-use the same Sphinx version for all doc sbuilding and the day we have an incompatibility we'll rethink about this pipenv/virtualenv stuff? | 14:49 |
| qschulz | RP: michaelo: halstead: don't know about the rsync delete_file permission denied though, c.f. https://autobuilder.yoctoproject.org/typhoon/#/builders/114/builds/350/steps/5/logs/stdio | 14:53 |
| *** ecdhe <ecdhe!~ecdhe@user/ecdhe> has joined #yocto | 15:01 | |
| RP | qschulz: I'm happy to set those and worry about the sphinx version later | 15:02 |
| RP | qschulz: We'll need mhalstead later for the rsync issue or I can try and poke at it | 15:02 |
| *** pgowda_ <pgowda_!uid516182@id-516182.ilkley.irccloud.com> has quit IRC (Quit: Connection closed for inactivity) | 15:08 | |
| RP | moto-timo: I have some changes which may help, still debugging issues though. I've spent the day on this :/ | 15:21 |
| rfs613 | qschulz, rburton, RP: morning gents, I have a bit more info about the cve-check issue. | 15:23 |
| rfs613 | I had noticed it ran slower locally with the lock, but in our CI it was far worse - build that ususally takes 1-2 hours is taking 24 to 48. | 15:23 |
| rburton | rfs613: i sent a patch this morning you can try | 15:24 |
| rfs613 | The lock is in $DL_DIR subdir, and in the case of CI this is shared via NFS (I think) | 15:24 |
| rfs613 | rburton: i' | 15:24 |
| rfs613 | ll check the list i a moment; I tried a patch yesterday that seemed to help FWIW | 15:24 |
| rfs613 | s/i a/in a/ | 15:25 |
| rburton | yeah i don't want to merge a patch which involves copying the database for every recipe | 15:25 |
| RP | rburton: could we just copy into TMPDIR once after updating and do that copy under a DL_DIR lock? | 15:26 |
| rburton | i'd hope we can avoid copying entirely | 15:28 |
| rfs613 | rburton: okay, I see the patch on list, makes sense not to copy, will test it here shortly. | 15:28 |
| rburton | the only thing that writes is the cve-update-db recipe, which is a dependent of the reading tasks, so it will happen once early | 15:28 |
| RP | rburton: but not with builds in parallel which worries me :/ | 15:29 |
| rfs613 | what happens if we run multiple concurrent builds? | 15:29 |
| zyga[m] | rburton: I ran into that issue in oniro | 15:30 |
| zyga[m] | our builds run on top of a shared nfs disk | 15:30 |
| zyga[m] | we ended up moving the database to local storage to avoid long lock waits | 15:30 |
| zyga[m] | otherwise builds would stall as the database lock was held by one task | 15:30 |
| zyga[m] | things worked but were terribly sequential | 15:30 |
| rfs613 | we were seeing "NFS reclaim lock" errors, not 100% certain if they are related, but seems likely. | 15:32 |
| rburton | right,my patch removes the lock | 15:32 |
| rburton | rfs613: are you running concurrent builds across the same DL_DIR? can you verify with timestamps that the problem is caused by multiple builds writing to the same sqlite database? | 15:33 |
| zyga[m] | at oniro we use the same DL_DIR and SSTATE_DIR across all builds | 15:34 |
| rfs613 | rburton: yes, we share DL_DIR and sstate across builds. Debugging is difficult because I have no shell access, all I can do is add "ls <whatever>" commands to the build recipes, and hope they show up in the logs. | 15:34 |
| rfs613 | Also the build runs in container which is destroyed after build... | 15:34 |
| rburton | you can look at the build logs and see if the times of cve-update-db-native correlates to failures in other runs | 15:35 |
| rfs613 | (but obviously DL_DIR and sstate are outside, via NFS apparently) | 15:35 |
| michaelo | qschulz: great catch! Many thanks | 15:35 |
| qschulz | michaelo: still, I think the bitbake rsync needs to be modified | 15:36 |
| rfs613 | rburton: yep, I can try checking timestamps, but let me get a new build running first, then I'll have time for log grepping | 15:36 |
| qschulz | michaelo: still, I think the bitbake rsync needs to be modified. I assume | 15:37 |
| qschulz | rsync -irlp --checksum --ignore-times --delete bitbake docs@docs.yoctoproject.org:docs/ | 15:37 |
| qschulz | will actually delete everything under the docs directory on docs.yoctoproject.org | 15:37 |
| *** pasherring <pasherring!~pasherrin@2001:8a0:ec55:b200:27fc:a530:7097:2c60> has quit IRC (Remote host closed the connection) | 15:38 | |
| qschulz | so if the yp-docs fail to build and does not reach its own rsync, then the yp-docs won't be available on the website, though bitbake's will | 15:38 |
| qschulz | so I **guess** rsync -irlp --checksum --ignore-times --delete bitbake/* docs@docs.yoctoproject.org:docs/bitbake/ | 15:38 |
| qschulz | might be a good replacement but I had so many issues with the few rsync scripts I wrote that I don't know if this does anything I want :) | 15:39 |
| *** pasherring <pasherring!~pasherrin@2001:8a0:ec55:b200:27fc:a530:7097:2c60> has joined #yocto | 15:39 | |
| *** pasherring <pasherring!~pasherrin@2001:8a0:ec55:b200:27fc:a530:7097:2c60> has quit IRC (Remote host closed the connection) | 15:40 | |
| rburton | RP: again i think bitbake needs shared lock support | 15:40 |
| rburton | a solid fix would be to let the reading tasks shared lock the database | 15:40 |
| rburton | i guess the tasks can do that lock manually | 15:41 |
| RP | rburton: happy to add it, shouldn't be hard | 15:42 |
| RP | rburton: internally the lock functions already do | 15:42 |
| rburton | yeah | 15:42 |
| RP | rburton: I think the sstate code uses it already | 15:43 |
| RP | rburton: I still think for efficiency you'd want a tmpdir local copy of that database | 15:43 |
| rburton | i really don't think its needed | 15:43 |
| rburton | writing is rare | 15:43 |
| RP | rburton: the writer tasks would likely stall out under pressure from cbe check tasks though :/ | 15:44 |
| rburton | there won't be lots of writer tasks | 15:44 |
| RP | rburton: I was surprised we didn't have shared task locks to be honest | 15:44 |
| rburton | if the mtime of the database is less than an hour, it doesn't update it | 15:44 |
| michaelo | qschulz: why not directly rsync -irlp --checksum --ignore-times --delete bitbake/ docs@docs.yoctoproject.org:docs/bitbake/ (without the "*")? | 15:45 |
| michaelo | it's true I'm not comfortable with the previous command :-| | 15:47 |
| qschulz | michaelo: whatever works by deleting only what's in docs/bitbake and not docs/ :) | 15:47 |
| rfs613 | rburton: tested your two patches locally, seems fine (no slowdown) | 15:47 |
| qschulz | but now that I'm reading the last rsync,it's probably just fine? otherwise we'd also be missing the bitbake docs | 15:47 |
| qschulz | s/also/always/ | 15:48 |
| qschulz | michaelo: never mind, seems like the manpage tells us the rsync commands are just fine. So I can we can "safely" enable set -eu -o pipefail. The side effect being that if nobody monitors the builds, the docs will stay out of date since rsync won't be running if anything fails before | 15:51 |
| RP | qschulz: swat does monitor failures | 15:54 |
| michaelo | qschulz: it sounds right. However, the first rsync command doesn't always do what it's supposed. That's probably safer to submit the change you proposed. I would do that if I were you... | 15:56 |
| qschulz | RP: so the question right now is... do we disable the warning-to-error to pass most builds (and don't see the error about non-existing BB_HASHBASE_WHITELIST variable for example) | 15:56 |
| RP | qschulz: can we get to a point where we're warning free again easily? | 15:56 |
| qschulz | RP: no warning from master + my two patches, didn't check the other branches | 15:57 |
| qschulz | but if it's what we aim for, then I can check. I would rather keep the fail-on-warning in Sphinx and enable set -eu -o pipefail so that we don't miss stuff | 15:58 |
| qschulz | (note that they aren't exclusive, it's just that set -eu -o pipefail is a bit less useful if you disable the warning-to-error in sphinx builds :) ) | 15:59 |
| michaelo | I agree to keep the warnings too | 16:00 |
| RP | qschulz: looks like transition, dunfell and yocto-3.4.1 still fail :( | 16:00 |
| qschulz | RP: transition is because of missing make target, can be easily fixed (since it's a branch) | 16:02 |
| *** tre <tre!~tre@ip5f5886dd.dynamic.kabel-deutschland.de> has quit IRC (Remote host closed the connection) | 16:03 | |
| rfs613 | hmm, so it seems I cannot .bbappend for a bbclass, correct? | 16:04 |
| smurray | rfs613: yep | 16:05 |
| rfs613 | right, that makes it tricky to test rburton cve-fixes in our CI setup, since I cannot modify poky there. | 16:06 |
| rfs613 | any clever ideas for me? | 16:07 |
| *** pasherring <pasherring!~pasherrin@2001:8a0:ec55:b200:27fc:a530:7097:2c60> has joined #yocto | 16:07 | |
| rfs613 | i guess I could have the build script do "git revert d55fbf47794" which would at least get the build times back down to a few hours... | 16:09 |
| smurray | rfs613: the typical approach is to just drop the new version of the bbclass in a layer to override | 16:09 |
| smurray | rfs613: which isn't great for maintainability, but it does work | 16:10 |
| *** oobitots <oobitots!~oobitots@aer01-mda2-dmz-wsa-4.cisco.com> has quit IRC (Quit: Client closed) | 16:10 | |
| *** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV) | 16:10 | |
| qschulz | RP: yocto-3.3.x and yocto-3.4.x need a patch to use the correct bitbake version for the object.inv from bitbake, but I don't see any specific error in the autobuilder for dunfell branch though? Also, the issue of -W messing up the build only exists since honister branch fro the docs (it was not part of the flags before) | 16:10 |
| mckoan | Generating an image with 'dunfell' results in the creation of timestamped images which are not deleted but continue to be added in deploy/images. Has anyone had the same problem recently? | 16:15 |
| michaelo | qschulz, RP: will we have to fix 3.4.1 too? I wish we could only generate the docs for each release branch, not for all each individual release :| | 16:15 |
| rburton | rfs613: we use kas which lets you drop patches onto other layers as part of the setup | 16:16 |
| *** osama4 <osama4!~osama@eth1-fw1-nbg6.eb.noris.de> has quit IRC (Ping timeout: 256 seconds) | 16:16 | |
| qschulz | michaelo: fcb24deb8b3abb8a77a12baa2cdd5ba5aa976f01 is missing for all tags/branches | 16:17 |
| qschulz | branches can be fixed, tags needs to be patched | 16:17 |
| smurray | mckoan: specifically dunfell HEAD? I don't see that with 3.1.14 in AGL here, can rig up a test with HEAD in a bit | 16:19 |
| michaelo | qschulz: right. That's why I'm asking whether we could only generate the docs for each branch, not for each release. What would we miss? | 16:19 |
| *** user95 <user95!~user95@user/user95> has joined #yocto | 16:21 | |
| RP | michaelo: the idea was to be able to select the docs for each release version in the version selector | 16:22 |
| michaelo | qschulz, RP: by the way https://docs.yoctoproject.org/_static/switchers.js is out of date (check the Dunfell release, 3.1.12 instead of 3.1.14). It seems the run-docs-build script is not replicating switchers.js from master but from the latest tag that was processed. | 16:23 |
| mckoan | smurray: thanks. No it is an intermediate version. However the configuration involves some 3rd party laters therefore I am not sure whu's guilty. It's very difficult do figure out where is it and I wanted any useful hint. | 16:24 |
| mckoan | s/laters/layers | 16:24 |
| mckoan | s/whu/who | 16:24 |
| mckoan | damn dyslexia | 16:25 |
| tgamblin | zeddii: What is the cutoff date for M3 contributions to the kernel (assuming some might need to be made)? | 16:25 |
| moto-timo | RP: do you think the sysconfigdata is what is breaking meson in sdk? | 16:25 |
| smurray | mckoan: maybe look in 'bitbake -e' for oddness wrt changes to the image variables? | 16:25 |
| zeddii | I'll do bugfix and -stable updates up until release, so no real cutoff. i have some queued changes now, that I'll be sending this week. | 16:25 |
| mckoan | smurray: thx | 16:26 |
| moto-timo | RP: and thank you for figuring out the pip mangling patch | 16:26 |
| tgamblin | zeddii: Alright, thanks | 16:26 |
| RP | qschulz: I merged your changes so now we have https://autobuilder.yoctoproject.org/typhoon/#/builders/114/builds/352 | 16:26 |
| michaelo | RP: yes, I understand, but why can't we use the 3.4.2 docs when we're using 3.4.1 (for example)? Shouldn't the latest docs for each branch be always sufficient? Do you expect a case when the docs of 3.x.n+y are incompatible with the 3.x.n release? Just hoping to simplify things if possible... | 16:27 |
| *** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto | 16:27 | |
| RP | michaelo: we replicated what went before and didn't want to "hide" history from users. | 16:28 |
| RP | the docs shouldn't be determining the development process | 16:28 |
| rfs613 | smurray, rburton: don't trust myself to mess with the BBLAYERs, so I've kludged a "git revert" into my build script... not ideal but we should know in an hour or two if it works. | 16:29 |
| michaelo | RP: this makes perfect sense. What's making perhaps less sense is always regenerating the stuff that was generated successfuly. | 16:31 |
| RP | michaelo: how else will the deprecation warnings/headers get added and the menus updated? | 16:31 |
| michaelo | RP: oh right, you win :-) | 16:32 |
| RP | moto-timo: I think nativesdk is being cross compiled so probably needs that | 16:33 |
| RP | moto-timo: it was meaning my pip mangling patch wasn't working for mason-nativesdk and I thought it should | 16:34 |
| *** AKN <AKN!~AKN@2409:4072:689:68ab:4cf:b1bc:6e1d:c58> has joined #yocto | 16:34 | |
| moto-timo | RP: agreed. Trying to wake up and catch up. | 16:34 |
| RP | moto-timo: I've stuffed my hacks into master-next and run a build, we'll see what happens | 16:35 |
| *** Tokamak <Tokamak!~Tokamak@172.58.188.134> has quit IRC (Ping timeout: 250 seconds) | 16:35 | |
| *** Etheryon <Etheryon!~textual@79.113.77.204> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…) | 16:35 | |
| RP | moto-timo: I know some of the fixes helped e.g. python3-pip to build | 16:35 |
| michaelo | qschulz, RP: I can propose a patch to add "make clean" to the "transition" branch. | 16:35 |
| RP | moto-timo: the wheel install thing is because it tests "python3 -m pip" and then decides it is already installed and tries to remove it | 16:35 |
| RP | moto-timo: so rather than force-reinstall, we want ignore installed | 16:36 |
| RP | michaelo: please | 16:36 |
| RP | michaelo: I think we just have to work through the issues | 16:36 |
| *** Tokamak <Tokamak!~Tokamak@172.58.188.134> has joined #yocto | 16:36 | |
| *** user95 <user95!~user95@user/user95> has quit IRC (Ping timeout: 256 seconds) | 16:38 | |
| *** Tokamak <Tokamak!~Tokamak@172.58.188.134> has quit IRC (Read error: Connection reset by peer) | 16:41 | |
| qschulz | RP: michaelo: yup, needs a clean makefile target for the transition build is required | 16:41 |
| qschulz | then fcb24deb8b3abb8a77a12baa2cdd5ba5aa976f01 or similar for honister branches/tags | 16:42 |
| qschulz | michaelo: we already patch 3.3 and 3.4 tags so you can hook up a new patch to the logic without too muhc hassle I think | 16:42 |
| qschulz | From what I saw from the logs, this should probably be enough to pass the build | 16:43 |
| *** Tokamak <Tokamak!~Tokamak@172.58.188.134> has joined #yocto | 16:44 | |
| qschulz | but there are fixes required for other branches/tags too which aren't failing the build (warnings only, and since they weren't turned into errors before honister, the build succeeds) | 16:44 |
| qschulz | I cannot have a look at it today, only tmrw, so if michaelo you have time before ~10am tmrw, please do. Oitherwise we can sync tmrw | 16:44 |
| rfs613 | rburton: I searched through previous build logs, but don't have any cve-check "read only database" in the last few weeks. Older builds get pruned... So cannot confirm or deny if timestamps align... | 16:46 |
| moto-timo | RP: I was on the fence about ignore-installed. Makes sense I think | 16:47 |
| michaelo | RP: done (https://lists.yoctoproject.org/g/docs/message/2499). I'll be happy to see what's next :) | 16:49 |
| *** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 256 seconds) | 16:52 | |
| *** Tokamak <Tokamak!~Tokamak@172.58.188.134> has quit IRC (Ping timeout: 250 seconds) | 16:56 | |
| RP | michaelo: pushed | 16:59 |
| *** Tokamak_ <Tokamak_!~Tokamak@107.116.82.98> has joined #yocto | 16:59 | |
| *** Minvera <Minvera!~Minvera@user/Minvera> has joined #yocto | 16:59 | |
| *** lucaceresoli <lucaceresoli!~ceresoli@host-79-2-93-196.business.telecomitalia.it> has quit IRC (Remote host closed the connection) | 17:00 | |
| *** oobitots <oobitots!~oobitots@aer01-mda1-dmz-wsa-7.cisco.com> has joined #yocto | 17:01 | |
| *** mckoan is now known as mckoan|away | 17:03 | |
| moto-timo | RP: I think that's the first time buildtools job passed? | 17:04 |
| moto-timo | RP: oh nevermind | 17:04 |
| *** AKN <AKN!~AKN@2409:4072:689:68ab:4cf:b1bc:6e1d:c58> has quit IRC (Ping timeout: 240 seconds) | 17:05 | |
| michaelo | qschulz: 3.4.1 conf.py looks good to me. It's just that 3.4.2 conf.py sets the current version to 3.4.1 instead of 3.4.2. Shall we patch this if we don't want to move the tag? | 17:09 |
| *** kevinrowland <kevinrowland!~kevinrowl@104.129.199.51> has joined #yocto | 17:11 | |
| *** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto | 17:14 | |
| *** oobitots <oobitots!~oobitots@aer01-mda1-dmz-wsa-7.cisco.com> has quit IRC (Quit: Client closed) | 17:17 | |
| *** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 240 seconds) | 17:20 | |
| *** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat) | 17:21 | |
| RP | moto-timo: key test is the epoxy sdk test. Looks like build-appliance has an issue though. The pip calls there were always dubious | 17:23 |
| RP | moto-timo: pip3-native isn't installing pip3 anylonger | 17:24 |
| moto-timo | RP: yeah... pip3 not found... is that native? My naïve bootstrapping only unzips the wheel... time to fix the ${bindir} installs | 17:24 |
| RP | moto-timo: yes, that calls pip3 native | 17:25 |
| kergoth | Anyone around that's building container images with bitbake? Wondering about self-hosting in-container oe builds | 17:25 |
| moto-timo | RP: another workaround would be to patch it to call "nativepython3 -m pip" but the right thing is to install to ${bindir} anyway | 17:26 |
| moto-timo | RP: let me hack at the boostrapping | 17:26 |
| RP | moto-timo: we may just need to inject the right magic file in there as it is probably generated | 17:35 |
| moto-timo | RP: I'm pretty sure we just need to mv ${D}${PYTHON_SITEPACKAGES_DIR}/bin/* ${D}${bindir}/ | 17:36 |
| moto-timo | RP: might also need to do that for ${datadir} or ${mandir} | 17:36 |
| moto-timo | hacking ${bindir} now | 17:36 |
| moto-timo | ERROR: Variable BB_ENV_EXTRAWHITE has been renamed to BB_ENV_PASSTHROUGH_ADDITIONS | 17:37 |
| moto-timo | do i just need to blow away tmp? | 17:37 |
| RP | moto-timo: no, rebuild your environment most likely | 17:37 |
| moto-timo | RP: ok, thanks | 17:37 |
| RP | moto-timo: mandir will be irrelevant for -native | 17:37 |
| RP | moto-timo: good news is testsdk is working this time | 17:42 |
| moto-timo | \o/ | 17:42 |
| moto-timo | RP: good point | 17:43 |
| *** Tokamak_ <Tokamak_!~Tokamak@107.116.82.98> has quit IRC (Ping timeout: 256 seconds) | 17:53 | |
| *** frieder <frieder!~frieder@i59F4BC00.versanet.de> has quit IRC (Remote host closed the connection) | 17:55 | |
| *** Tokamak <Tokamak!~Tokamak@107.116.82.98> has joined #yocto | 17:57 | |
| RP | michaelo, qschulz: the rsync issue was a protection against breaking the site until the scripts were fixed. That shouldn't be there now so just waiting on a free worker to run another docs build | 17:58 |
| *** Tokamak_ <Tokamak_!~Tokamak@172.58.188.134> has joined #yocto | 18:01 | |
| *** gsalazar <gsalazar!~gsalazar@194.38.148.130> has quit IRC (Ping timeout: 245 seconds) | 18:01 | |
| *** Tokamak <Tokamak!~Tokamak@107.116.82.98> has quit IRC (Ping timeout: 256 seconds) | 18:02 | |
| moto-timo | RP: well that was wishful thinking... as you suspected it is generated... still working on it | 18:07 |
| moto-timo | RP: we could also use host pip to install, but that feels wrong | 18:09 |
| RP | moto-timo: I suspect it is just a few lines so maybe just handcode it in? | 18:13 |
| moto-timo | RP: exactly | 18:13 |
| *** Tokamak_ <Tokamak_!~Tokamak@172.58.188.134> has quit IRC (Ping timeout: 256 seconds) | 18:18 | |
| *** gsalazar <gsalazar!~gsalazar@161.230.168.194> has joined #yocto | 18:18 | |
| *** goliath <goliath!~goliath@user/goliath> has joined #yocto | 18:20 | |
| *** Tokamak <Tokamak!~Tokamak@166.205.152.113> has joined #yocto | 18:21 | |
| *** gsalazar <gsalazar!~gsalazar@161.230.168.194> has quit IRC (Ping timeout: 240 seconds) | 18:23 | |
| kergoth | RP: Would it be possible to put something together about what you and other Yocto tech decision makers would like to see out of the project members? Where would resources best be used/allocated? What's the best way we can help you? Allocate dev time to work on yocto project dev tasks? Etc | 18:36 |
| *** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Ping timeout: 250 seconds) | 18:37 | |
| michaelo | RP, qschulz: happy to see that the docs are apparently getting generated correctly again. | 18:39 |
| michaelo | and the switchers.js is correct everywhere too! | 18:40 |
| *** florian_kc <florian_kc!~florian@dynamic-093-135-085-051.93.135.pool.telefonica.de> has joined #yocto | 18:40 | |
| michaelo | Thanks to this, the out-of-date version warnings are gone too. | 18:42 |
| *** kevinrowland <kevinrowland!~kevinrowl@104.129.199.51> has quit IRC (Quit: Client closed) | 18:45 | |
| *** kevinrowland <kevinrowland!~kevinrowl@104.129.199.51> has joined #yocto | 18:45 | |
| kanavin_ | rburton, I got the meta-arm-none-eabi gcc to the point where it builds and runs https://github.com/kanavin/meta-cross-toolchain | 18:48 |
| kanavin_ | rburton, it requires a few patches to oe-core though, and RP mentioned how some things should be improved https://git.yoctoproject.org/poky-contrib/log/?h=akanavin/gcc-arm-none-eabi | 18:49 |
| kanavin_ | (the reverted patch is not coming back, I only kept it until I stash it elsewhere for history) | 18:50 |
| kergoth | huh, like cross-canadian, but to run on MACHINE rather than SDKMACHINE? | 18:52 |
| kanavin_ | kergoth, YES | 18:58 |
| moto-timo | RP: also fixing the selftest failures like python3-scons-native in maintainers.inc and python3-flit-core not having HOMEPAGE | 18:59 |
| *** Tokamak_ <Tokamak_!~Tokamak@166.205.152.113> has joined #yocto | 18:59 | |
| *** Tokamak <Tokamak!~Tokamak@166.205.152.113> has quit IRC (Ping timeout: 240 seconds) | 19:02 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 19:02 | |
| fray | kanavin_ what are you doing w/ the gcc-arm-none-eabi? Baremetal stuff? | 19:03 |
| kanavin_ | fray, I hand it over to a client who's paying for Linutronix providing the toolchain :) | 19:03 |
| fray | but what is it for? Linux, baremetal, another OS? With the 'none', I'm assuming baremetal targeting | 19:04 |
| fray | I would like to see a 'baremetal' or 'baremetal-newlib' distro defined in standard Yocto Project.. since I'm seeing a lot of need for this kind of stuff | 19:05 |
| kanavin_ | fray, setting up its actual usage is on them, I'm not sure I'm even going to see how they use it, but let me check. | 19:05 |
| fray | being able to generate toolchains with meta-toolchain for baremetal is something I do regularly.. targeting newlib (with a request for 'newlib-nano' on the r5), for a9, aarch64 (various), r5 and microblaze | 19:06 |
| kanavin_ | fray, I checked, they seem to be using ecos+newlib | 19:10 |
| *** GillesM <GillesM!~gilles@233.95.127.78.rev.sfr.net> has joined #yocto | 19:11 | |
| fray | ok.. so effectively newlib based baremetal | 19:11 |
| kanavin_ | fray, they say, just give us the toolchain, we'll take care of the sysroot | 19:12 |
| khem | ecos uses libgloss + newlib yes | 19:12 |
| fray | took me a long time to understand this, but there is two parts of newlib.. newlib (the c library) and libgloss [or an alternative] that provide the OS/hardware itnerfaces) | 19:12 |
| khem | right | 19:12 |
| fray | So a proper baremetal + newlib distro would use newlib, libgloss (while allowed alternative providers for libgloss) | 19:12 |
| khem | you can classify baremetal as semihosted and purely baremetal | 19:13 |
| kanavin_ | fray, I briefly looked into building cross-canadian newlib in the context of poky, but as the customer didn't ask for it, I didn't push further. | 19:13 |
| fray | it's pretty easy to configure, but would be better if we had a more standard YP configuration to use for this, IMHO | 19:13 |
| fray | with outbuilding it, you need to provide the binaries the customer wants or gcc (libgcc) is incomplete | 19:13 |
| khem | its gcc's muddled build architecture, with llvm/clang its quite easy, you build one compiler for all. then you can build rumtimes as a normal target package | 19:14 |
| kanavin_ | yes, you can't compile anything useful without libc | 19:14 |
| kanavin_ | khem, ack. it's an awful mess of autoconf, and our recipes reflect that :( | 19:15 |
| kanavin_ | GSOC proposal: rewrite gcc build system in meson, split the pieces into independent parts! | 19:16 |
| khem | heh yeah, it will be like taking GCCs identify away 🙂 but good idea | 19:17 |
| khem | IMO the build is one part of it, but s/w arch of gcc is also due to overhaul | 19:18 |
| kanavin_ | khem, I once suggested meson to GNU gettext maintainer | 19:18 |
| kanavin_ | their answer? 'autotools have been around since I was young, meson is only a fad' | 19:18 |
| khem | yes, I am not surprised :). | 19:19 |
| kanavin_ | and so we're still stuck with 5 minutes of configure and two minutes of install for something that should take seconds | 19:19 |
| khem | yeah but to be fair I think OE does something unusual too where it runs autoreconf which is mainainer mode operation generally | 19:21 |
| kanavin_ | khem, autoreconf is not where the time goes in gettext | 19:21 |
| kanavin_ | khem, it's drowned into recursive ./configure, each of which tests everything under the sun | 19:21 |
| khem | yes but it just makes a bad problem worse | 19:21 |
| kanavin_ | ... serially | 19:22 |
| RP | kergoth: I can try but it is hard to give a very specific list. It is really a question of how the project can cover basic core needs. Recent examples - inclusive language or more specifically, bitbake variable rename support, or the python changes to adopt to packaging changes upstream, or the changes coming to CVE format, or help getting patchtest back online, or.... etc | 19:22 |
| rburton | gettext is my pathological test for autotools, autoreconf is slow but its the execution which takes FOREVER as alex says | 19:22 |
| rburton | amazingly it does already re-use a config cache between the runs | 19:23 |
| rburton | imagine how much slower it would be if it didn't! | 19:23 |
| khem | electricfense guys did a build analysis of cross builds using yocto and I think do_configure averages around 25% of build time | 19:23 |
| fray | this is the reason we generate and store the site.conf files | 19:24 |
| RP | kergoth: I did try and create the "big ticket" item list with the future directions topics | 19:24 |
| khem | and in do_compile 30% of time was spent in preprocessor | 19:24 |
| fray | without that it takes a lot more time for do_configure steps.. it was always intended to add more to the site cache, but nobody ever expanded it | 19:24 |
| kanavin_ | rburton, and for what? a target-independent library and some utilities for UI translation? | 19:25 |
| rburton | there was an attempt at a minimal gettext clone | 19:25 |
| rburton | i wonder if that's finished | 19:25 |
| khem | BSDs do the caching stuff for some packages, it needs proper care and feeding otherwise it becomes stale | 19:25 |
| kanavin_ | fray, nowadays autotools is pretty much abandoned by everyone except GNU | 19:26 |
| rburton | khem: as gettext is five nested configures the first one sets a cache that the others can re-use, so that's safe at least | 19:26 |
| kanavin_ | freedesktop and gnome moved to meson, and never looked back | 19:26 |
| fray | kanavin_: people keep saying that, yet everytime someone asked me to integrate something new -- it seems to be autoconf based unless its python based | 19:26 |
| kanavin_ | something legacy you mean ;) | 19:27 |
| fray | it all depends on the part of the system you work with. core-os components still use autoconf a ton.. higher up in the stack (graphics) meson is used more and more | 19:27 |
| rburton | our firmware is all moving to cmake which i'm in a mixed mood about | 19:27 |
| rburton | i mean, it's better than bare makefiles of doom | 19:27 |
| fray | I work on base OS integration. System services, firmware loaders, etc etc.. | 19:27 |
| fray | cmake is used a lot at (former) xilinx, I'm not a fan.. it's horribly complex to do simple things | 19:28 |
| moto-timo | cmake is just another tool to allow folks to write bad things | 19:28 |
| fray | yup | 19:28 |
| rfs613 | and building cmake itself takes forever | 19:28 |
| kanavin_ | cmake is something c++ crowd likes a lot for some unknown reason | 19:28 |
| moto-timo | "works for me on this one machine that I have in the basement" | 19:28 |
| fray | cmake also makes it 'even easier' for people to ignore cross compiling as well.. | 19:28 |
| JaMa | and setting CMake policies to keep ti as much backwards compatible -> more complexity | 19:28 |
| fray | the number of times in the last 2 years I've had to convince people to NOT hard code a magic cross-compiler into their cmake files is mind boggling to me.. | 19:29 |
| khem | gn + ninja is best when it comes to speed and use of system resources optimally but it has mind of its own | 19:29 |
| fray | with GNU make, I have the same argument to make -- but it seems to be "easier" to just fix.. | 19:29 |
| moto-timo | RP: flit_core has an update from 3.6.0 to 3.7.1 but I think I am going to hold off on that until we get the current mess sorted | 19:29 |
| rburton | khem: gn is the worst of all! | 19:30 |
| JaMa | after bazel.. :) | 19:30 |
| rburton | khem: entirely because the distribution model appears to be 'your source ships a binary of gn' | 19:30 |
| rburton | JaMa: oh, of course :) | 19:30 |
| rburton | khem: whilst you're here, https://github.com/kraj/meta-clang/pull/582 :) | 19:31 |
| moto-timo | bazel is truly a piece of work | 19:31 |
| khem | rburton: look at immense research chromium team has done on existing solutions | 19:31 |
| * moto-timo wonders if all wheels have _ and never - in the PN | 19:32 | |
| rburton | are you suggesting that chromium is easy to build? | 19:32 |
| JaMa | it builds with python3native now, finally some nails in meta-python2 coffin | 19:33 |
| moto-timo | that's a GoodThingTM | 19:34 |
| *** amitk_ <amitk_!~amit@103.59.74.130> has quit IRC (Ping timeout: 240 seconds) | 19:38 | |
| *** rob_w <rob_w!~rob@2001:a61:6050:d201:e45d:6190:f58a:6c8c> has quit IRC (Quit: Leaving) | 19:41 | |
| khem | rburton: the change looks good | 19:41 |
| *** florian_kc <florian_kc!~florian@dynamic-093-135-085-051.93.135.pool.telefonica.de> has quit IRC (Ping timeout: 250 seconds) | 19:42 | |
| khem | rburton: re chromium, its not at all easy and that was not the point, it was about building complex s/w without much overhead, | 19:42 |
| khem | fray: for small projects make is ok, ninja really shines with large projects | 19:43 |
| *** pasherring <pasherring!~pasherrin@2001:8a0:ec55:b200:27fc:a530:7097:2c60> has quit IRC (Read error: Connection reset by peer) | 19:53 | |
| *** pasherring <pasherring!~pasherrin@2001:8a0:ec55:b200:27fc:a530:7097:2c60> has joined #yocto | 19:54 | |
| RP | moto-timo: you're handling the selftest maintainer issues? so I can sort out my tweaks in -next and post them and between us we should be good for a better test run? | 20:01 |
| moto-timo | RP: exactly | 20:01 |
| *** pasherring <pasherring!~pasherrin@2001:8a0:ec55:b200:27fc:a530:7097:2c60> has quit IRC (Remote host closed the connection) | 20:02 | |
| moto-timo | RP: at this point I am creating patches on top of master-next (just waiting for build-appliance-image to finish) | 20:02 |
| *** pasherring <pasherring!~pasherrin@2001:8a0:ec55:b200:27fc:a530:7097:2c60> has joined #yocto | 20:02 | |
| moto-timo | RP: I can send the patches now... I'm not clear if the shebang in pip-native should be #!/usr/bin/env python3 or nativepython3. | 20:03 |
| RP | moto-timo: the later I think | 20:04 |
| moto-timo | RP: ok... I think I am starting to get it | 20:04 |
| RP | michaelo: qschulz: happy to see the docs did build cleanly again :) | 20:08 |
| moto-timo | \o/ | 20:08 |
| RP | moto-timo: the way to think about it is that the tool needs to use the right python without having the pythonnative inherit | 20:18 |
| moto-timo | RP: and if it is -native that means nativepython3 | 20:19 |
| RP | moto-timo: yes, and tools would normally be natives | 20:19 |
| RP | moto-timo: I only realise this having spent the day arguing with it :) | 20:20 |
| moto-timo | RP: sadly my brain shut down on me yesterday and I'm barely recovering | 20:25 |
| moto-timo | too many hours in too few days | 20:25 |
| moto-timo | not that I was being efficient | 20:25 |
| kanavin_ | khem: I do not think running specific sub-gcc configure scripts, e.g. gcc-source/libgcc/configure, gcc-source/gcc-runtime/configure etc. is correct anymore. If you check the logs, you'll see they all complain about a ton of bogus options that only work with the top level configure. It's a wonder we made it this far :-/ I'll look into using the top level gcc configure in all cases. | 20:30 |
| kanavin_ | and because we do cd {B}/libgcc first, these aren't picked up by insane :( | 20:31 |
| kanavin_ | (insane looks only at ${B}/config.log | 20:31 |
| RP | kanavin_: that insane check was always a best effort, not built to handle the complex cases | 20:31 |
| kanavin_ | RP: for gcc-arm-none-eabi I went back to how it used to be many years ago: let gcc-cross build and install libgcc as well, then change libgcc to handle only the packaging for the target | 20:32 |
| kanavin_ | RP: https://github.com/kanavin/meta-cross-toolchain/blob/master/recipes-devtools/gcc/gcc-cross_%25.bbappend | 20:33 |
| RP | kanavin_: yes, the work put in to stop rebuilding gcc-cross all the time was pretty pointless so it would make sense to rip it out and go back to that | 20:33 |
| khem | the independent configures are done because gcc has successfully made them build independent | 20:34 |
| RP | kanavin_: if we're not calling the sub configures correct, we should probably look at getting the options to those correctly | 20:35 |
| khem | if you use top level configure, it will take us back to monolithic intertwined checks and catch-22 situations that we did away with 3 phased gcc builds in past, but if you find it works better all ears for it | 20:35 |
| kanavin_ | khem, except it hasn't - if you check https://github.com/kanavin/meta-cross-toolchain/blob/master/recipes-devtools/gcc/gcc-cross_%25.bbappend you'll see I have to pass some options to top level configure for the sake of building libgcc correctly, that libgcc-specific configure is not recognizing :-/ | 20:36 |
| kanavin_ | RP: sub-configures are all receiving what is defined here: https://git.yoctoproject.org/poky-contrib/tree/meta/recipes-devtools/gcc/gcc-configure-common.inc?h=akanavin/gcc-arm-none-eabi#n22 | 20:38 |
| khem | I guess it will be fine to take a bit of hit to accomodate them if they dont have side effects | 20:38 |
| kanavin_ | those are for the top level configure only | 20:39 |
| RP | kanavin_: So great, you found a bug. It is susprising it works but it hasn't seemed to do too badly over the last few years | 20:39 |
| RP | kanavin_: I understand the problem but I'm going to get annoyed if you keep just telling me how broken it all is. You have no idea the work it was to actually get some of this stuff to this point where it does work for most of the current use cases | 20:40 |
| RP | I'd actually love to get back and continue to improve that but instead I get to do other things | 20:43 |
| *** rsalveti <rsalveti!uid117878@id-117878.uxbridge.irccloud.com> has quit IRC (Quit: Connection closed for inactivity) | 20:43 | |
| khem | 🙂 | 20:47 |
| RP | kanavin_: and just to be clear, it isn't actually the same configure options that are passed to top level gcc-cross build, they are different since one is a cross recipe and one is a target recipe. I agree there are some extra options which are passed and which are ignored | 20:47 |
| RP | kanavin_: passing target flags in a cross recipe is actually a big problem and shouldn't be done | 20:48 |
| RP | but you'll probably find that out later :/ | 20:48 |
| *** florian_kc <florian_kc!~florian@dynamic-093-135-085-051.93.135.pool.telefonica.de> has joined #yocto | 20:55 | |
| *** bluelightning <bluelightning!~paul@2406:e003:151f:d701:25db:74c9:2689:f07d> has joined #yocto | 20:55 | |
| *** kevinrowland <kevinrowland!~kevinrowl@104.129.199.51> has quit IRC (Quit: Client closed) | 21:02 | |
| *** osama4 <osama4!~osama@ipbcc2935c.dynamic.kabel-deutschland.de> has joined #yocto | 21:02 | |
| bluelightning | JPEW: could you please take a look at https://patchwork.yoctoproject.org/project/oe-core/patch/20220126181648.20864-1-abeltran@linux.microsoft.com/ ? let us know if there's anything further we should do | 21:03 |
| *** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto | 21:03 | |
| *** osama <osama!~osama@eth1-fw1-nbg6.eb.noris.de> has joined #yocto | 21:04 | |
| *** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Ping timeout: 240 seconds) | 21:05 | |
| *** florian_kc <florian_kc!~florian@dynamic-093-135-085-051.93.135.pool.telefonica.de> has quit IRC (Ping timeout: 272 seconds) | 21:07 | |
| *** osama4 <osama4!~osama@ipbcc2935c.dynamic.kabel-deutschland.de> has quit IRC (Ping timeout: 272 seconds) | 21:07 | |
| JPEW | bluelightning: ya. AFK right now, will look later | 21:17 |
| *** GillesM <GillesM!~gilles@233.95.127.78.rev.sfr.net> has quit IRC (Quit: Leaving) | 21:36 | |
| *** mauro_anjo <mauro_anjo!~quassel@191.13.251.42> has quit IRC (Ping timeout: 272 seconds) | 21:39 | |
| *** kevinrowland <kevinrowland!~kevinrowl@104.129.199.51> has joined #yocto | 21:47 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto | 21:59 | |
| *** Minvera <Minvera!~Minvera@user/Minvera> has quit IRC (Remote host closed the connection) | 22:00 | |
| *** lucaceresoli <lucaceresoli!~lucaceres@77.244.183.192> has joined #yocto | 22:00 | |
| *** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto | 22:03 | |
| RP | moto-timo: if you have those patches I think it might be good to get them into next | 22:04 |
| moto-timo | RP: I just fixed the syntax... | 22:05 |
| *** ecdhe_ <ecdhe_!~ecdhe@user/ecdhe> has joined #yocto | 22:06 | |
| moto-timo | RP: sent... this is assuming on top of master-next | 22:09 |
| *** wooosaiii <wooosaiii!~wooo@89-212-21-243.static.t-2.net> has joined #yocto | 22:09 | |
| *** ecdhe <ecdhe!~ecdhe@user/ecdhe> has quit IRC (Ping timeout: 272 seconds) | 22:09 | |
| *** wooosaiiii <wooosaiiii!~wooo@89-212-21-243.static.t-2.net> has quit IRC (Ping timeout: 256 seconds) | 22:10 | |
| *** wooosaii <wooosaii!~wooo@89-212-21-243.static.t-2.net> has quit IRC (Ping timeout: 256 seconds) | 22:10 | |
| *** wooosaiiii <wooosaiiii!~wooo@89-212-21-243.static.t-2.net> has joined #yocto | 22:10 | |
| *** rsalveti <rsalveti!uid117878@id-117878.uxbridge.irccloud.com> has joined #yocto | 22:16 | |
| moto-timo | RP: so your --ignore-installed needs to be there | 22:18 |
| *** osama1 <osama1!~osama@eth1-fw1-nbg6.eb.noris.de> has joined #yocto | 22:19 | |
| *** osama <osama!~osama@eth1-fw1-nbg6.eb.noris.de> has quit IRC (Read error: Connection reset by peer) | 22:19 | |
| *** dvorkindmitry <dvorkindmitry!~dv@5.167.98.73> has joined #yocto | 22:28 | |
| RP | moto-timo: thanks | 22:29 |
| moto-timo | RP: let me know if there are any problems in merging... I hope it's ok | 22:29 |
| RP | moto-timo: you copied that crazy exec header for pip :) | 22:29 |
| * moto-timo might be a bit tired still | 22:29 | |
| moto-timo | RP: thats what I was seeing so... yep | 22:30 |
| dvorkindmitry | how can I build all qt5 libs as DEPENDS for image for later installation from my repo? | 22:30 |
| moto-timo | https://github.com/meta-qt5/meta-qt5 | 22:31 |
| moto-timo | RP: I decided to just pretend I was pip | 22:31 |
| dvorkindmitry | is there a line I can write in my img.bb file? | 22:32 |
| RP | moto-timo: fair enough. I've started a build | 22:33 |
| dvorkindmitry | i know about meta-qt5, it looks like I have to write all qt modules one by one in DEPENDS += ""... | 22:35 |
| moto-timo | you could probably leverage bitbake-layers show-recipes -l meta-qt5 somehow to script that generation into a packagegroup | 22:44 |
| dvorkindmitry | there are packagegroup with all modules enumerated in qt layer, but they are listed in RDEPEND_ variable | 22:47 |
| dvorkindmitry | how can I make it "DEPEND" with only one line? | 22:48 |
| JaMa | the list of recipes won't probably change for dead-end meta-qt5, so just list them in DEPENDS manually | 22:48 |
| moto-timo | unfortunately, meta-qt6 doesn't follow oe branch naming so it is not in layer index | 22:50 |
| JaMa | not sure what is worse, with meta-qt5 I was following the naming and lucklily the release cadence of OE and QT matches, so there is separate branch for each Qt release, but then people are mixing different branches due to that (e.g. using 5.12 from meta-qt5/warrior with dunfell build and so on) | 22:53 |
| *** osama1 <osama1!~osama@eth1-fw1-nbg6.eb.noris.de> has quit IRC (Ping timeout: 240 seconds) | 22:53 | |
| JaMa | now with incompatible metadata changes it gets a lot worse from this perspective (so I have jansa/warrior-overrides branch as well to be usable with honister and newer) | 22:54 |
| JaMa | but not going to support every sensible combination of Qt version / yocto release | 22:54 |
| RP | I am worried about how this renaming will work out | 22:56 |
| JaMa | luckily I'm no longer maintaining meta-ros :) | 23:01 |
| JaMa | but compared to overrides syntax, it's at least relatively limited at least in layers I care about | 23:01 |
| JaMa | but with meta-qt6 e.g. 6.2 branch I was able to get overrides syntax change merged (and support for zeus dropped) while with variable renames they would probably need to add some 6.2-kirkstone branch (and who knows how well they will keep it in sync with 6.2) | 23:04 |
| JaMa | or not as only https://github.com/shr-project/meta-qt6/commit/99effdcb7e2accd77355be6b976e755fe85523aa + LAYERSERIES_COMPAT was needed to build it with kirkstone | 23:05 |
| JaMa | but if not-spdx license identifiers are turned to warning soon (even after kirkstone is released) than maybe we should backport all necessary mappings to dunfell (iirc something was missing when I run the conversion script on dunfell branch) | 23:08 |
| *** lucaceresoli <lucaceresoli!~lucaceres@77.244.183.192> has quit IRC (Quit: Leaving) | 23:09 | |
| *** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Ping timeout: 240 seconds) | 23:11 | |
| RP | JaMa: I think those changes might not be easily backported to dunfell as it was the "+" handling | 23:13 |
| RP | (vs -or-later) | 23:14 |
| *** mvlad <mvlad!~mvlad@2a02:2f08:4b12:b100:24d7:51ff:fed6:906d> has quit IRC (Remote host closed the connection) | 23:16 | |
| khem | kirkstone would mean new ports mostly, its how it is turning out for RDK, | 23:16 |
| khem | scripts are helping but people have done some really innovative stuff internally | 23:17 |
| *** lettucepunch[m] <lettucepunch[m]!~lettucepu@2001:470:69fc:105::1:c900> has joined #yocto | 23:17 | |
| khem | 🙂 | 23:17 |
| RP | khem: I dread to think :) | 23:17 |
| *** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto | 23:23 | |
| JaMa | RP: ah :/ | 23:25 |
| *** ar__ <ar__!~akiCA@user/akica> has quit IRC (Ping timeout: 272 seconds) | 23:29 | |
| *** florian_kc <florian_kc!~florian@dynamic-093-135-085-051.93.135.pool.telefonica.de> has joined #yocto | 23:36 | |
| *** goliath <goliath!~goliath@user/goliath> has quit IRC (Remote host closed the connection) | 23:36 | |
| *** ldericher <ldericher!~LDer@pantalaimon.yavook.de> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in) | 23:41 | |
| *** ldericher <ldericher!~LDer@pantalaimon.yavook.de> has joined #yocto | 23:43 | |
| RP | There is a downside to the renames where once renamed, new bitbake is happy but the older layers can silently break if you still claim compatibility with them | 23:47 |
| RP | i.e. we don't detect the new names in the old bitbake | 23:48 |
| *** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Quit: Leaving) | 23:55 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!