Wednesday, 2024-06-05

*** xmn <xmn!~xmn@2600:4040:9398:a200:54c4:5748:1682:3016> has quit IRC (Quit: ZZZzzz…)00:05
*** MrCryo <MrCryo!~MrCryo@user/MrCryo> has joined #yocto00:10
*** MrCryo <MrCryo!~MrCryo@user/MrCryo> has quit IRC (Remote host closed the connection)00:12
*** MrCryo <MrCryo!~MrCryo@user/MrCryo> has joined #yocto00:12
sotaoverridecan someone explain why this bitbake command just gets stuck? bitbake-layers add-layer ../meta-openembedded/meta-oe00:19
sotaoverrideNOTE: Starting bitbake server...00:19
*** qschulz <qschulz!~weechat@ns326003.ip-37-187-106.eu> has quit IRC (Remote host closed the connection)00:32
*** qschulz <qschulz!~weechat@ns326003.ip-37-187-106.eu> has joined #yocto00:34
*** davidinux <davidinux!~davidinux@45.11.82.48> has quit IRC (Ping timeout: 246 seconds)01:03
*** davidinux <davidinux!~davidinux@45.11.82.48> has joined #yocto01:05
*** ablu <ablu!~m-bfyrfh@user/Ablu> has quit IRC (Ping timeout: 272 seconds)01:11
*** MrCryo <MrCryo!~MrCryo@user/MrCryo> has quit IRC (Remote host closed the connection)01:23
*** ablu <ablu!~m-bfyrfh@user/Ablu> has joined #yocto01:27
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto01:31
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Client Quit)01:32
*** lexano <lexano!~lexano@pool-174-119-69-134.cpe.net.cable.rogers.com> has quit IRC (Ping timeout: 268 seconds)01:34
*** sgw <sgw!~swold@user/sgw> has joined #yocto01:34
*** ablu <ablu!~m-bfyrfh@user/Ablu> has quit IRC (Ping timeout: 268 seconds)01:37
*** stgl <stgl!~stgl@2a03:b0c0:3:d0::cad:a001> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)01:42
*** stgl <stgl!~stgl@2a03:b0c0:3:d0::cad:a001> has joined #yocto01:42
*** Jones42_ <Jones42_!~Jones42@user/Jones42> has joined #yocto01:44
*** xmn <xmn!~xmn@2600:4040:9398:a200:54c4:5748:1682:3016> has joined #yocto01:45
*** Jones42__ <Jones42__!~Jones42@user/Jones42> has quit IRC (Ping timeout: 240 seconds)01:47
*** ablu <ablu!~m-bfyrfh@user/Ablu> has joined #yocto01:48
*** ablu <ablu!~m-bfyrfh@user/Ablu> has quit IRC (Ping timeout: 255 seconds)01:53
*** ablu <ablu!~m-bfyrfh@user/Ablu> has joined #yocto01:58
*** Saur_Home5 <Saur_Home5!~Saur_Home@94-137-113-31.customers.ownit.se> has quit IRC (Quit: Client closed)02:00
*** jclsn <jclsn!~jclsn@2a04:4540:650f:fe00:2ce:39ff:fecf:efcd> has quit IRC (Ping timeout: 268 seconds)02:00
*** Saur_Home5 <Saur_Home5!~Saur_Home@94-137-113-31.customers.ownit.se> has joined #yocto02:00
*** jclsn <jclsn!~jclsn@2a04:4540:6539:1a00:2ce:39ff:fecf:efcd> has joined #yocto02:01
*** Piraty <Piraty!~irc@user/piraty> has quit IRC (Remote host closed the connection)02:21
*** Piraty <Piraty!~irc@user/piraty> has joined #yocto02:22
*** ablu <ablu!~m-bfyrfh@user/Ablu> has quit IRC (Ping timeout: 255 seconds)02:31
*** ablu <ablu!~m-bfyrfh@user/Ablu> has joined #yocto02:34
*** ablu <ablu!~m-bfyrfh@user/Ablu> has quit IRC (Read error: Connection reset by peer)02:46
*** ablu <ablu!~m-bfyrfh@user/Ablu> has joined #yocto02:54
*** sgw <sgw!~swold@user/sgw> has quit IRC (Ping timeout: 264 seconds)03:00
*** sgw <sgw!~swold@user/sgw> has joined #yocto03:01
*** sgw <sgw!~swold@user/sgw> has quit IRC (Quit: Leaving.)03:10
*** ablu <ablu!~m-bfyrfh@user/Ablu> has quit IRC (Ping timeout: 240 seconds)04:09
*** roussinm <roussinm!~mroussin@142.115.196.7> has quit IRC (Ping timeout: 268 seconds)04:19
*** ablu <ablu!~m-bfyrfh@user/Ablu> has joined #yocto04:27
*** Saur_Home5 <Saur_Home5!~Saur_Home@94-137-113-31.customers.ownit.se> has quit IRC (Quit: Client closed)04:41
*** Saur_Home5 <Saur_Home5!~Saur_Home@94-137-113-31.customers.ownit.se> has joined #yocto04:41
*** jmd <jmd!~user@2001:a61:2b57:a201:4b92:15ba:c66d:13b9> has joined #yocto04:48
*** Jones42_ <Jones42_!~Jones42@user/Jones42> has quit IRC (Ping timeout: 246 seconds)04:51
*** Jookia <Jookia!~jookia@LuminaSensum/founder/Jookia> has joined #yocto04:53
Jookiadoes yocto sign its git tags/releases with a key?04:54
khemqschulz: https://snips.sh/f/7pebax45CB04:58
khemqschulz: it seems when we add meta-clang and let clang fill in for all llvm needs this is what I see04:58
*** sotaoverride <sotaoverride!~aatir@ool-4578fe22.dyn.optonline.net> has quit IRC (Ping timeout: 240 seconds)05:03
*** sotaoverride <sotaoverride!~aatir@ool-4578fe22.dyn.optonline.net> has joined #yocto05:18
*** jmd <jmd!~user@2001:a61:2b57:a201:4b92:15ba:c66d:13b9> has quit IRC (Remote host closed the connection)05:28
*** MrCryo <MrCryo!~MrCryo@user/MrCryo> has joined #yocto05:29
*** MrCryo <MrCryo!~MrCryo@user/MrCryo> has quit IRC (Remote host closed the connection)05:35
*** sng <sng!~quassel@217.140.105.54> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)05:42
*** sng <sng!~quassel@217.140.105.54> has joined #yocto05:43
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto05:47
*** rfuentess <rfuentess!~rfuentess@154.45.232.215> has joined #yocto05:52
*** ehussain <ehussain!~Thunderbi@2400:adc5:122:ef00:d9e1:7ebb:7a1:d44c> has joined #yocto06:03
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.104> has joined #yocto06:04
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.10> has joined #yocto06:04
*** ahussain <ahussain!~Thunderbi@2404:3100:1897:9bd1:8fa5:ceae:35be:147> has joined #yocto06:06
*** ehussain <ehussain!~Thunderbi@2400:adc5:122:ef00:d9e1:7ebb:7a1:d44c> has quit IRC (Ping timeout: 268 seconds)06:07
*** ahussain is now known as ehussain06:07
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has joined #yocto06:13
*** BhsTalel <BhsTalel!~BhsTalel@147.161.164.95> has joined #yocto06:25
*** Kubu_work <Kubu_work!~kubu@lfbn-nan-1-335-137.w82-120.abo.wanadoo.fr> has joined #yocto06:27
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has joined #yocto06:29
*** alessioigor <alessioigor!~alessioig@185.178.95.238> has joined #yocto06:34
*** alperak <alperak!uid641238@id-641238.ilkley.irccloud.com> has joined #yocto06:42
*** mckoan|away is now known as mckoan06:43
jclsnMorning guys06:46
Xogiumjclsn: hi06:47
*** Jookia <Jookia!~jookia@LuminaSensum/founder/Jookia> has quit IRC (Ping timeout: 264 seconds)06:47
jclsnSo this oelint-adv tool is telling me to place FILES before RDEPENDS. My colleague is complaining about this. I don't see anything about this in the OE Styleguide. Does anyone know where the oelint-dev gets this from?06:47
jclsnOh it actually is there https://docs.yoctoproject.org/dev/contributor-guide/recipe-style-guide.html06:49
*** Jookia <Jookia!~jookia@115.68.233.220.static.exetel.com.au> has joined #yocto06:49
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has quit IRC (Ping timeout: 240 seconds)06:50
mckoangood morning06:52
*** enok <enok!~Thunderbi@94.191.152.247> has joined #yocto06:56
jclsnBtw now that I got your attention06:58
*** zpfvo <zpfvo!~fvo@i59F5CDE4.versanet.de> has joined #yocto06:58
jclsnHow is Qualcomm support looking in general? Is it a good idea to use one of their SoCs? The BSPs seem closed-source to me, since I can't find much about them06:59
jclsnThere is also not much in here https://github.com/Linaro/meta-qcom06:59
*** goliath <goliath!~goliath@user/goliath> has joined #yocto07:00
*** ehussain <ehussain!~Thunderbi@2404:3100:1897:9bd1:8fa5:ceae:35be:147> has quit IRC (Remote host closed the connection)07:02
*** ehussain <ehussain!~Thunderbi@2404:3100:1897:9bd1:8fa5:ceae:35be:147> has joined #yocto07:02
*** crazy_imp <crazy_imp!~mj@user/crazy-imp/x-1371519> has joined #yocto07:04
crazy_imphi, is there a way to get the targets (kernel) page size during compile time of userland applications?07:05
mckoanjclsn: my past experiences with Qualcomm were not good07:11
jclsnmckoan: Can you elaborate?07:12
mckoanjclsn: no, I can't sorry. All depends on your real need on QC system. Maybe you can describe your scenario07:14
*** enok <enok!~Thunderbi@94.191.152.247> has quit IRC (Ping timeout: 240 seconds)07:15
jclsnWe are developing a system for a highly-regulated industry. We already have an NXP-based solution, but are looking for more performance and a more modern SoC than the i.MX8. So we would need to port our existing system to a Qcom SoC. I don't see it used much in the industry. It is more of an Android SoC for imo. That is why I am asking.07:17
jclsnI would think of other performant SoCs like the RK3588, but I doubt anyone would accept an SoC from a Chinese manufacturer in our industry.07:18
*** ehussain <ehussain!~Thunderbi@2404:3100:1897:9bd1:8fa5:ceae:35be:147> has quit IRC (Ping timeout: 268 seconds)07:19
*** xmn <xmn!~xmn@2600:4040:9398:a200:54c4:5748:1682:3016> has quit IRC (Ping timeout: 246 seconds)07:26
*** altru <altru!~altru@static-css-ccs-204145.business.bouyguestelecom.com> has joined #yocto07:26
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has joined #yocto07:27
*** alessioigor <alessioigor!~alessioig@185.178.95.238> has quit IRC (Quit: Client closed)07:27
jclsnI also see an issue with our DRM setup. This is currently based on NXP's OP-TEE. We would probably have to change a lot here07:30
Xogiumwell if you switch vendor pretty much everything in the boot chain will change for sure07:34
*** alessioigor <alessioigor!~alessioig@185.178.95.238> has joined #yocto07:34
mckoanjclsn: usong QC expect weird and non-YP-ortodox software implementations :-(07:35
jclsnXogium: Sure, I am just asking about how well the Yocto support is. I wouldn't want to write half the BSP myself or be completely dependent of official Qcom support07:36
BhsTalelmckoan I confirm.07:36
jclsnmckoan: Isn't NXP weird in this regard already?07:36
jclsnI guess Qcom is such a big player in the Android market, that they don't care about Yocto much07:37
*** florian <florian!~florian@dynamic-002-243-218-083.2.243.pool.telefonica.de> has joined #yocto07:38
*** mvlad <mvlad!~mvlad@2a02:2f05:821a:fb00:e88e:21ff:fe65:be18> has joined #yocto07:40
*** Jones42 <Jones42!~Jones42@user/Jones42> has joined #yocto07:40
*** Jones42_ <Jones42_!~Jones42@user/Jones42> has joined #yocto07:43
*** Jones42 <Jones42!~Jones42@user/Jones42> has quit IRC (Ping timeout: 246 seconds)07:46
*** florian <florian!~florian@dynamic-002-243-218-083.2.243.pool.telefonica.de> has quit IRC (Ping timeout: 272 seconds)07:57
*** mbulut <mbulut!~mbulut@ip1f128e48.dynamic.kabel-deutschland.de> has joined #yocto08:00
*** Jones42__ <Jones42__!~Jones42@user/Jones42> has joined #yocto08:06
*** Jones42_ <Jones42_!~Jones42@user/Jones42> has quit IRC (Ping timeout: 256 seconds)08:09
rburtoncrazy_imp: no, because you're not running inside the kernel08:10
qschulzkhem: I know, I'm trying to work this issue out but it's **really** difficult right now08:15
qschulzkhem: so, iris gallium driver is now requiring lbclc08:15
qschulzhttps://gitlab.freedesktop.org/mesa/mesa/-/commit/5438b1910464e4b17fe0248a96a6ed98f0280a2008:16
qschulzhowever, if I add libclc to DEPENDS of PACKAGECONFIG[gallium] when iris is part of GALLIUMDRIVERS, I get a conflict in sysroot of mesa-native because llvm and clang both install the same static library08:17
qschulzthis is because gallium-llvm is forced in PACKAGECONFIG for the native recipe08:17
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has quit IRC (Ping timeout: 240 seconds)08:18
qschulzso it can either be gallium-llvm or gallium for now (or I move iris gallium to gallium-llvm, something I'll try today)08:18
qschulzjclsn: if that can help, i'll personally never work on any product based on Qcom, that's bad enough to make me quit my job if i'm forced to work on SoCs from that vendor08:19
qschulzI know people who worked on Qcom products and they basically said never again08:20
qschulzon SW side08:20
crazy_imprburton: yes i know. hoped there's some variable inside the build system exposing it :|. even within the kernel it's kinda messy because for x86_64 there's no config parameter declaring tha page size while for arm64, there's CONFIG_ARM64_4K_PAGES08:20
qschulzon HW side, i only know one person who had some experience with them and it wasn't a good experience as well, with the same conclusion: no product on Qcom08:20
qschulzjclsn: this may have changed though, since Linaro is working a lot with upstream on Qcom products but this may be aiming only the very high performance SoCs (the ones you find in PCs or flagship smartphones)08:21
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto08:24
Xogiumqschulz: which vendors are you ok with, out of curiosity ?08:24
qschulzXogium: I've worked on Amlogic, Allwinner, Mediatek, NXP and Rockchip for now. Amlogic has virtually no documentation and their BSP is really meh, Baylibre did upstream a few SoCs but I was told they weren't given any more documentation than I had.08:26
qschulzXogium: Allwinner, it was ten years ago when it was in cheap tablets/phones. Doc a bit better than Amlogic, I never had a BSP with DT support (I worked on a 4.9 but they did some very weird thing with the DT)08:27
qschulzMediatek was not great, didn't get access to docs IIRC, and the kernel was really not great. But Baylibre has been working a lot on Mtk SoCs as well with upstream, so maybe that has improved as well08:28
qschulzRockchip is quite OK on the doc side, much better than the other mentioned Chinese vendors but you still have some incorrect info or IPs entirely not mentioned08:28
qschulzThe kernel is... not great but it feels a bit better than the other CHinese vendors08:28
qschulzThe best experience I had was with NXP08:28
qschulzAmazing doc, really nice support the only time I needed it (an issue in assembly code when entering suspend to RAM I could have never found by myself)08:29
qschulzthey sometimes upstream stuff themselves, but they also keep updating their downstream repos often08:29
Xogiuminteresting !08:30
qschulztheir doc is so good (or at least used to be, have been a couple of years I have worked on those) that this is actually used to understand how the same IP in SoCs from other vendors work08:30
qschulzIn the end, you pay for what you get (in both directions)08:31
Xogiumindeed08:31
qschulzThe only surprise is Qcom, which I think isn't that affordable, and the quality of the BSP we received was abysmal08:31
Xogiumdamn08:31
Xogiumthat does sound very bad indeed08:32
qschulzFor Qcom stuff, you can ask Linaro and specifically caleb, they have done a lot of awesome work on products from that vendor, so they would know much more than I do what the current state is08:33
BhsTalelI had good experience also with NXP, their documentation is very good, and even for free support they did help me on a MIPI DSI kernel driver for a panel that is not theirs, their support is also good.08:33
XogiumI've not yet done lots of bsp, mostly because I'm quite comfortable with st so far... And I'll admit, outside of bsp things, I only did allwinner and amlogic, and they were both absolutely awful. Here, catch ! It's a patch for your board to make it work better ! ... thanks, sochip. That's not a patch. It's a binary file I have no idea what it is used for, where to even put it, what to even do with it in the08:34
Xogiumfirst place08:34
Xogiumthey sent me this when the SoC we were using at the time got EOL... They replaced it with a supposedly compatible pin-to-pin version that is low power08:35
Xogiumneedless to say I wasn't impressed08:36
BhsTalelXogium I noticed that lot of companies are switching to ST SoCs specially the MP1 processor, and they offer well detailed documents and good support.08:36
XogiumBhsTalel: yeah I definitely agree on doc and support, they're very nice. They even helped us with a board that wasn't of their own design in understanding why we had problem with the i2c controller from the dev board08:38
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto08:38
Xogiumtheir bsp isn't, like, the worst, probably. It's just very very weird and doing of things it shouldn't be doing08:38
Xogium*lots of things08:39
BhsTalelST invest alot in support, we have ST here and they have like an entire departement just for handling support and forum questions08:39
Xogiumcarrying bbappend for pulseaudio, mesa, systemd, etc.08:39
BhsTalelWhat I only hate about ST is that they over engineer alot when its coming to BSP and Yocto, cyou can compare meta-st-stm32mp and meta-nxp and see the difference, but they did a pretty good job on Yocto side08:40
Xogiumyeah they really overdone stuff08:40
Xogiumbut I'm sure there's far worse out there08:41
*** enok <enok!~Thunderbi@94.191.152.60.mobile.tre.se> has joined #yocto08:41
XogiumI actually had plans of starting my own proper bsp for st to have only what a bsp should do in there... Hardware support and bringup, nothing more08:41
Xogiumbut well, something called real life got in my way for the moment08:42
BhsTalelI am working with a company that designed a custom board based on MP1 and since they know ST has overdone their Yocto BSP layer, the company created a wrapper layers with simpler variables and explaination for their clients08:43
Xogiumthat said I'm very interested to see how the stm32mp2 sries will be like08:43
Xogiumoooh wow that is nice !08:43
Xogiumis that bsp kept private ? Probably is but... If not, I'd sure like to check it out and see how they've done things08:44
BhsTalelI remember once I tried to simplify the env setup of ST layers with KAS yaml files and they rejected the pull request saying that the internal team did not agree on this LOL https://github.com/STMicroelectronics/meta-st-stm32mp/pull/6208:45
qschulzBhsTalel: it's a third party tool not part of Yocto/OE, so I wouldn't throw them under the bus for this choice08:46
BhsTalelYeah, I totally understand that08:47
Xogiumshame though it would have made the setup quite a bit easier08:48
Xogiumbecause their scripts are SO BAD08:48
qschulzwe have some bitbake tool now to setup layers and whatnot, so maybe there's something to do there08:49
Xogiumlike the one that generates sd card images from a flashlayout file for example. Oh my. It's full of hardcoded things, and full of shellcheck warnings and errors :D08:49
BhsTalelTheir tools are very specific to their boards, I think there is someone there that wants everything to be very tight to ST.08:51
BhsTalelqschulz Good contribution diea08:51
BhsTalelidea*08:51
BhsTalelI am still working on a Rust tool that will be an alternative for KAS, I hope it will be ready before the next 2024.11 Summit08:53
*** Saur_Home5 <Saur_Home5!~Saur_Home@94-137-113-31.customers.ownit.se> has quit IRC (Quit: Client closed)08:58
*** Saur_Home5 <Saur_Home5!~Saur_Home@94-137-113-31.customers.ownit.se> has joined #yocto08:58
*** enok <enok!~Thunderbi@94.191.152.60.mobile.tre.se> has quit IRC (Ping timeout: 240 seconds)09:06
rburtonBhsTalel: does it offer anything beyond kas/repo/tuxbake/bitbake-setup apart from being written in a different language?09:10
*** Jones42__ is now known as Jones4209:12
*** BhsTalel <BhsTalel!~BhsTalel@147.161.164.95> has quit IRC (Quit: Client closed)09:35
*** Saur_Home5 <Saur_Home5!~Saur_Home@94-137-113-31.customers.ownit.se> has quit IRC (Quit: Client closed)09:38
*** Saur_Home5 <Saur_Home5!~Saur_Home@94-137-113-31.customers.ownit.se> has joined #yocto09:38
*** BhsTalel <BhsTalel!~BhsTalel@147.161.164.95> has joined #yocto09:46
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 268 seconds)09:47
*** alessioigor <alessioigor!~alessioig@185.178.95.238> has quit IRC (Quit: Client closed)09:52
BhsTalelrburton It does the same needed job ofc which is setting up layers and build environment, but what I tried to add is the following features:09:52
BhsTalel- Support different types of input files (thanks to serde crate): YAML, JSON, TOML and RON are supported09:52
BhsTalel- Reverse: generate a build configuration based of an existing build environment09:52
BhsTalel- Repo: this is like google repo09:52
BhsTalel- Theme: which has lot of themes config files like ROS2 and RPI for example, if you type: easyocto theme -t rpi --setup , then it will setup a build environment automatically based on a predefiend rpi theme config, ... (BTW, its called easyocto)09:53
BhsTalel- Also, I have included what I called core and third party layers config files, so in the config file you don't need to specify every layer again like in KAS, for example you can specify directly the layer name.09:53
BhsTalel- Also, meta, meta-poky are automatically selected as they are required, so with just: easyocto build , with no config input, you can get a setup ready09:53
BhsTalel- Also, I started a CLI support to edit and create a config file, because it s quite complicated.09:53
BhsTalel- Also, Git2 crate is used and not a system git command09:53
BhsTalelNOTE: I started this for me as a big project to learn Rust.09:53
BhsTalelit could be usefull somehow, we will see09:53
BhsTalelI am going for lunch, I will check with you if you sent something I didnt received09:53
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto09:54
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat)09:57
*** alessioigor <alessioigor!~alessioig@185.178.95.238> has joined #yocto09:58
*** alessioigor <alessioigor!~alessioig@185.178.95.238> has quit IRC (Client Quit)10:02
*** alessioigor <alessioigor!~alessioig@185.178.95.238> has joined #yocto10:12
*** BhsTalel <BhsTalel!~BhsTalel@147.161.164.95> has quit IRC (Quit: Client closed)10:30
*** BhsTalel <BhsTalel!~BhsTalel@147.161.164.95> has joined #yocto10:38
BhsTalelrburton I got disconnected, did you reply on my message ?10:38
XogiumBhsTalel: they didn't10:41
BhsTalelXogium BTW, what do you think about it ?10:42
XogiumBhsTalel: that sounds like it definitely could be useful, from what you've described. Kas here just broke so I can't actually use it, and so I resorted to manually setting up everything currently10:44
*** florian <florian!~florian@dynamic-002-243-218-083.2.243.pool.telefonica.de> has joined #yocto10:45
qschulzBhsTalel: meta-poky is for sure not required :)10:58
qschulzBhsTalel: also, we have an archive of this IRC chat so you can check it on https://libera.irclog.whitequark.org/yocto10:59
*** BhsTalel <BhsTalel!~BhsTalel@147.161.164.95> has quit IRC (Quit: Client closed)11:06
*** BhsTalel <BhsTalel!~BhsTalel@147.161.164.95> has joined #yocto11:07
*** sotaoverride is now known as Guest723611:09
*** Guest7236 <Guest7236!~aatir@ool-4578fe22.dyn.optonline.net> has quit IRC (Killed (iridium.libera.chat (Nickname regained by services)))11:09
*** ctraven is now known as sotaoverride11:09
*** sotaover1ide <sotaover1ide!~aatir@ool-4578fe22.dyn.optonline.net> has joined #yocto11:09
*** mbulut <mbulut!~mbulut@ip1f128e48.dynamic.kabel-deutschland.de> has quit IRC (Ping timeout: 256 seconds)11:09
BhsTalelqschulz the poky distro is in meta-poky, so why it is not required ? am I missing something here ?11:10
qschulzBhsTalel: yes, poky is a reference distro, technically nobody should use it11:10
qschulzBhsTalel: and, bitbake+oe-core is the minimal setup11:11
BhsTalelqschulz I should take that into consideration only for default build, then meta-poky is required for poky distro, otherwise it is not.11:12
qschulzBhsTalel: if you don't include meta-poky, poky distro won't be found anyway, so I would suggest to not be smart about it11:13
*** lexano <lexano!~lexano@pool-174-119-69-134.cpe.net.cable.rogers.com> has joined #yocto11:13
qschulzthe smarter you want your tool to be, the more corner cases you'll have and the more difficult it'll get to maintain or refactor code11:13
BhsTalelqschulz yeah, that's why keeping default bblayers template file the choice.11:14
BhsTalelMy tool checks if default config is set for local.conf and bblayers.conf, if it is the case (which is the default) it sets up the templates from meta-poky.11:14
*** altru <altru!~altru@static-css-ccs-204145.business.bouyguestelecom.com> has quit IRC (Quit: Client closed)11:38
*** dkc <dkc!~dan@user/dkc> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)11:42
*** dkc <dkc!~dan@user/dkc> has joined #yocto11:45
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.10> has quit IRC (Quit: Client closed)11:51
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Quit: jmiehe)11:56
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has joined #yocto12:01
*** BhsTalel <BhsTalel!~BhsTalel@147.161.164.95> has quit IRC (Ping timeout: 250 seconds)12:05
*** BhsTalel <BhsTalel!~BhsTalel@147.161.164.95> has joined #yocto12:07
*** altru <altru!~altru@static-css-ccs-204145.business.bouyguestelecom.com> has joined #yocto12:16
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has quit IRC (Quit: enok)12:25
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has joined #yocto12:25
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has quit IRC (Ping timeout: 240 seconds)12:41
*** roussinm <roussinm!~mroussin@142.115.196.7> has joined #yocto12:42
jclsnqschulz: Well, guess I will have to make my own experiences here. If our architects decide to use this SoC, I won't be able to do much about it12:43
*** ablu <ablu!~m-bfyrfh@user/Ablu> has quit IRC (Ping timeout: 260 seconds)12:44
*** ablu <ablu!~m-bfyrfh@user/Ablu> has joined #yocto12:45
qschulzjclsn: hardware people and marketing people sometimes do not realize that the SW cost of a choice can be vastly different12:48
qschulzif someone tells them before they make the choice, they cannot complain afterwards they didn't know :)12:49
*** sgw <sgw!~swold@user/sgw> has joined #yocto12:51
*** ablu <ablu!~m-bfyrfh@user/Ablu> has quit IRC (Ping timeout: 260 seconds)13:06
jclsnSure, I also forwarded what I heard13:08
jclsnI just think it would be interesting to work with a Qcom SoC13:08
jclsnTheir chips are super efficient. It would make our product ready for years to come13:09
jclsnSo it may be worth the effort. NXP does not have an SoC that can compete unfortunately13:09
*** ablu <ablu!~m-bfyrfh@user/Ablu> has joined #yocto13:10
*** xmn <xmn!~xmn@2600:4040:9398:a200:e120:fd4a:df2c:3db8> has joined #yocto13:10
mckoanjclsn: however our company offer support even for YP projects based on Qcom ;-)13:10
jclsnmckoan: We are already working with Linaro anyway. So it is convenient that they maintain the layer13:11
qschulzjclsn: if it takes you years to have parity with your NXP SoC... :)13:12
*** Jones42_ <Jones42_!~Jones42@user/Jones42> has joined #yocto13:25
*** Jones42 <Jones42!~Jones42@user/Jones42> has quit IRC (Ping timeout: 268 seconds)13:29
*** Jones42_ <Jones42_!~Jones42@user/Jones42> has quit IRC (Ping timeout: 240 seconds)13:30
smurrayjclsn: in my experience, for product Qualcomm will want you to use one of their SDKs, which includes a massive repo of stuff.  They don't provide a separate BSP layer for most of their chips, their model is you work in their environment13:34
jclsnsmurray: That is disgusting13:34
jclsnMaybe Linaro can do that part for us :D13:36
smurrayjclsn: it's not fun, that's for sure.  In theory you could pick stuff apart out of their SDK, I'm not sure if anyone does, I imagine it would lead to troublesome support discussions13:37
*** altru <altru!~altru@static-css-ccs-204145.business.bouyguestelecom.com> has quit IRC (Quit: Client closed)13:37
smurrayjclsn: afaik the Linaro work is pretty much only for SoCs that go into stuff like Chromebooks or potentially now the new Windows ARM PCs.  I'll admit I've not looked at meta-qcom that recently, though13:38
jclsnAlright, thanks for the input guys13:40
jclsnNothing is set in stone yet anyway13:40
qschulzI concur, I've looked at their Yocto SDK for about an hour and I had to take a two-week holidays to try to forget about it13:42
qschulzIIRC, they replaced the base bbclass13:42
qschulzIt's probably more fair to say it's a Bitbake SDK than a Yocto SDK at that point honestly13:42
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has quit IRC (Quit: Leaving)13:42
jclsnqschulz: Don't be so dramatique13:50
*** MrCryo <MrCryo!~MrCryo@user/MrCryo> has joined #yocto13:50
*** Guest68 <Guest68!~Guest90@176.33.64.59> has joined #yocto13:50
jclsnBut yeah it is quite bad :D13:50
*** schtobia <schtobia!~quassel@schmidl.dev> has quit IRC (Quit: Bye!)13:51
*** Guest68 <Guest68!~Guest90@176.33.64.59> has quit IRC (Client Quit)13:53
*** schtobia <schtobia!~quassel@schmidl.dev> has joined #yocto13:53
*** alessioigor <alessioigor!~alessioig@185.178.95.238> has quit IRC (Quit: Client closed)14:05
*** rfuentess <rfuentess!~rfuentess@154.45.232.215> has quit IRC (Remote host closed the connection)14:09
*** alessioigor <alessioigor!~alessioig@185.178.95.238> has joined #yocto14:09
*** ehussain <ehussain!~Thunderbi@2400:adc5:122:ef00:6e68:6010:2a2f:d235> has joined #yocto14:14
*** ehussain <ehussain!~Thunderbi@2400:adc5:122:ef00:6e68:6010:2a2f:d235> has quit IRC (Client Quit)14:15
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has joined #yocto14:18
JPEWRP: you can drop the image.bbclass hooks patch. I did it better per the call yesterday14:20
zeddiigettext isn't building for me this morning after an update. anyone else seeing that ?14:23
zeddiia libtool version mismatch in a header.14:24
*** BhsTalel <BhsTalel!~BhsTalel@147.161.164.95> has quit IRC (Quit: Client closed)14:24
zeddiiclearly I can blame RP, since he's the main contributor to libtool now! ;)14:24
*** alessioigor <alessioigor!~alessioig@185.178.95.238> has quit IRC (Quit: Client closed)14:26
*** alessioigor <alessioigor!~alessioig@185.178.95.238> has joined #yocto14:28
*** sgw <sgw!~swold@user/sgw> has quit IRC (Quit: Leaving.)14:30
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has quit IRC (Ping timeout: 240 seconds)14:40
*** Saur_Home5 <Saur_Home5!~Saur_Home@94-137-113-31.customers.ownit.se> has quit IRC (Quit: Client closed)14:53
*** Saur_Home5 <Saur_Home5!~Saur_Home@94-137-113-31.customers.ownit.se> has joined #yocto14:53
khemqschulz: is it just one library of a set of libs which are conflicting ?15:01
*** alessioigor <alessioigor!~alessioig@185.178.95.238> has quit IRC (Quit: Client closed)15:02
*** alessioigor <alessioigor!~alessioig@185.178.95.238> has joined #yocto15:02
*** alessioigor <alessioigor!~alessioig@185.178.95.238> has quit IRC (Quit: Client closed)15:09
*** alessioigor <alessioigor!~alessioig@185.178.95.238> has joined #yocto15:14
*** vthor <vthor!~thor@user/vthor> has joined #yocto15:25
qschulzkhem: only have this error message, maybe it would complain for more if we resolve this one?15:25
RPzeddii: clean it and it will build fine. autotools is a bit dense at times15:33
RPzeddii: I did see it myself but assumed I'd corrupted something when testing15:33
zeddiiI tried cleansstate and cleanall still blowing up, but I went away from it for a bit and will try again.15:34
* zeddii tries just -c clean15:34
zeddiiRP: I assume yours was like this: https://pastebin.com/HdtjhF2r15:36
zeddiimaybe I need to force libtool to rebuild15:36
JaMa-c clean worked for me (in couple different builds today)15:38
zeddiimine is persisting. I'm obviously just picking up some old files.15:39
* zeddii ponders15:40
*** Saur_Home5 <Saur_Home5!~Saur_Home@94-137-113-31.customers.ownit.se> has quit IRC (Quit: Client closed)15:40
*** Saur_Home5 <Saur_Home5!~Saur_Home@94-137-113-31.customers.ownit.se> has joined #yocto15:40
qschulzkhem: https://paste.ack.tf/f4244e15:43
*** MrCryo <MrCryo!~MrCryo@user/MrCryo> has quit IRC (Remote host closed the connection)15:43
qschulzall duplicates (find in sysroot-components + sorted + uniq -d with the merge sorted output for clang-native and llvm-native)15:43
RPzeddii: "gettext-native -c clean" should have been enough15:48
RPobviously a bitbake in there15:49
RPzeddii: was it gettext or gettext-native?15:49
zeddiiyah. it was that I was doing gettext, and not gettext-native, I scanned it too quickly.15:49
zeddiiit's building more now15:50
RPkhem: the python3 patch seems to cause: https://valkyrie.yoctoproject.org/#/builders/6/builds/39 ?15:58
RP(and https://valkyrie.yoctoproject.org/#/builders/6/builds/39 )15:58
*** vthor <vthor!~thor@user/vthor> has quit IRC (Ping timeout: 256 seconds)16:10
*** BhsTalel <BhsTalel!~BhsTalel@147.161.255.87> has joined #yocto16:12
*** mjm_ <mjm_!~mjm@user/mjm> has joined #yocto16:16
*** mjm_ <mjm_!~mjm@user/mjm> has quit IRC (Client Quit)16:17
*** mjm_ <mjm_!~mjm@user/mjm> has joined #yocto16:17
*** jmd <jmd!~user@2001:a61:2b57:a201:4b92:15ba:c66d:13b9> has joined #yocto16:18
*** mjm <mjm!~mjm@user/mjm> has quit IRC (Ping timeout: 255 seconds)16:18
*** mjm_ is now known as mjm16:18
*** zpfvo <zpfvo!~fvo@i59F5CDE4.versanet.de> has quit IRC (Remote host closed the connection)16:27
*** mbulut <mbulut!~mbulut@31.18.142.72> has joined #yocto16:35
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has joined #yocto16:39
*** BhsTalel <BhsTalel!~BhsTalel@147.161.255.87> has quit IRC (Quit: Client closed)16:42
*** Guest3753 <Guest3753!~Guest37@199.59.102.58> has joined #yocto16:50
*** nerdboy <nerdboy!~nerdboy@gentoo/developer/nerdboy> has quit IRC (Ping timeout: 252 seconds)16:56
*** npk32 <npk32!~npk32@107.159.218.121> has joined #yocto17:00
*** npk32 <npk32!~npk32@107.159.218.121> has left #yocto17:02
*** Saur_Home5 <Saur_Home5!~Saur_Home@94-137-113-31.customers.ownit.se> has quit IRC (Quit: Client closed)17:04
*** Saur_Home5 <Saur_Home5!~Saur_Home@94-137-113-31.customers.ownit.se> has joined #yocto17:04
*** npk <npk!~npk32@user/npk> has joined #yocto17:05
*** nerdboy <nerdboy!~nerdboy@47.143.129.166> has joined #yocto17:08
*** Guest3753 <Guest3753!~Guest37@199.59.102.58> has quit IRC (Quit: Connection closed)17:18
*** florian <florian!~florian@dynamic-002-243-218-083.2.243.pool.telefonica.de> has quit IRC (Ping timeout: 264 seconds)17:27
*** vthor <vthor!~thor@187.148.151.84> has joined #yocto17:29
*** npk <npk!~npk32@user/npk> has quit IRC (Quit: Client closed)17:34
*** mattsm <mattsm!~mattsm@104-189-170-210.lightspeed.austtx.sbcglobal.net> has joined #yocto17:35
mattsmwhat is the preferred way of doing local fast kernel builds these days? ideally bypassing the fetch + full recompile if a commit is made or even just using the local changes to iterate quickly.17:36
*** florian <florian!~florian@dynamic-002-243-218-083.2.243.pool.telefonica.de> has joined #yocto17:39
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Quit: Leaving)17:44
khemRP: is that only happening on musl targets ?17:46
khemthats a LTO fat object, so I am guessing we never generated it with musl before perhaps or its now in different path is expected17:47
khem   FILES:libpython3-staticdev += "${libdir}/python${PYTHON_MAJMIN}/config-${PYTHON_MAJMIN}-*/libpython${PYTHON_MAJMIN}.a"17:49
RPkhem: seems so17:50
RPkhem: I thought we had static libs disabled17:51
*** mattsm <mattsm!~mattsm@104-189-170-210.lightspeed.austtx.sbcglobal.net> has quit IRC (Quit: Client closed)17:53
*** mattsm <mattsm!~mattsm@104-189-170-210.lightspeed.austtx.sbcglobal.net> has joined #yocto17:53
khemI think it works ok on x86_64 qemu here - /usr/lib/python3.12/config-3.12-x86_64-linux-musl/libpython3.12.a17:53
khembut your build is for 32bit x86 so let me see17:54
khemif I can reproduce it17:55
RPkhem: it failed on both 32 and 64 bit17:56
khemoh hmm17:56
khemsomehow OSABI is probably not being used in your case for config-3.12 case17:58
khemis it happening on different build hosts ?17:59
khemthis is ubu22.04 which you pasted above17:59
*** florian_kc <florian_kc!~florian@dynamic-002-243-218-083.2.243.pool.telefonica.de> has joined #yocto18:01
khemx86_64 builds seem to be on rocky918:01
RPkhem: it triggered failures in selftest too18:03
RPhttps://valkyrie.yoctoproject.org/#/builders/76/builds/47/steps/14/logs/stdio - the multiconfig one is from this18:03
RPhttps://valkyrie.yoctoproject.org/#/builders/76/builds/47/steps/14/logs/stdio18:03
*** florian <florian!~florian@dynamic-002-243-218-083.2.243.pool.telefonica.de> has quit IRC (Ping timeout: 252 seconds)18:04
RPhttps://valkyrie.yoctoproject.org/#/builders/54/builds/49/steps/14/logs/stdio18:04
RPkhem: doesn't seem host specific?18:04
khemyeah18:06
khembut I wonder why it works ok here18:07
*** npk32 <npk32!~npk32@107.159.218.121> has joined #yocto18:15
paulghttps://bugzilla.yoctoproject.org/show_bug.cgi?id=1550118:22
paulgA rather inventive spam.18:22
* tgamblin marks it for high priority18:30
*** mattsm <mattsm!~mattsm@104-189-170-210.lightspeed.austtx.sbcglobal.net> has quit IRC (Quit: Client closed)18:39
khemRP: you dropped bunch of stuff from master-next, I wonder if it was causing the issue ?18:46
khemRP: I will run yoe/mut through existing AB and see if we see the same issue there too18:47
Jookiahow do i verify the yocto source code?18:48
khemverify source code of metadata ?18:52
Jookiaverify the bitbake and openembedded-core source code's authenticity (ie it hasn't been tampered with)18:54
*** ablu <ablu!~m-bfyrfh@user/Ablu> has quit IRC (Ping timeout: 272 seconds)18:54
Jookiado i just trust the git servers are uncompromised18:54
*** vthor <vthor!~thor@user/vthor> has quit IRC (Ping timeout: 260 seconds)18:57
*** ablu <ablu!~m-bfyrfh@user/Ablu> has joined #yocto19:00
*** sgw <sgw!~swold@user/sgw> has joined #yocto19:05
*** ablu <ablu!~m-bfyrfh@user/Ablu> has quit IRC (Ping timeout: 255 seconds)19:07
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has quit IRC (Ping timeout: 240 seconds)19:08
khemI think pick the tarballs from download server19:13
RPkhem: I did drop some things but I'm not sure they'd be related19:13
khemJookia:https://downloads.yoctoproject.org/releases/yocto/yocto-5.0/19:13
khemthere are sha256 checksums published there as well. you can match them before using the tarballs19:14
Jookiakhem: are these verifiable?19:14
khemRP: OK, I am building locally as well as on AB lets see, I hope that it breaks on AB19:14
khemJookia: these are releases made by yocto project so I would think yes19:15
Jookiaok, so the solution is to trust the server19:15
khemI can hand you Thumb drive physically if that helps :)19:16
Jookiasure!19:17
Jookiai would appreciate something easier though, like signed releases19:17
rburtonJookia: what like https://git.yoctoproject.org/poky/tag/?h=yocto-5.0.119:17
Jookiayes, but with a verifiable key19:17
rburtonthat is a verifiable key19:17
Jookiawhere is it listed?19:17
Jookiai did searching for it using google or reading the online docs and it's not listed anywhere19:19
rburtonthat key in particular is signed by the release engineer19:19
Jookiawho are they? do they list the key anywhere?19:20
rburtonpersonally i'd reading the release announcement https://lists.yoctoproject.org/g/yocto-announce/topic/announcement_yocto_project/106279511 which lists the SHAs19:20
rburtonsame sha means same source19:21
Jookiaok, so i'll trust the website then and ignore signing19:21
rburtonyou could even use a non-yocto archive such as https://lore.kernel.org/yocto/IA1PR11MB8098359D776B39471093371EB9F52@IA1PR11MB8098.namprd11.prod.outlook.com/ to verify that the list archive wasn't compromised at the same time as the git repo19:22
Jookiai was hoping not to have to do that19:23
rburtondepends how paranoid you're being.  the tags are signed by the release engineer, so we should document those key ids somewhere19:24
Jookiamy requirements are that things are signed by a key that is publicly listed in at least two locations19:24
Jookiathe release key is listed in no locations19:24
rburtonJookia: file a bug please19:24
Jookiai'll put it on my list19:26
Jookiawhat category would it be under?19:27
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has joined #yocto19:29
Jookiaand what should i write in it?19:31
Jookiajust a general idea would help19:31
*** Guest3738 <Guest3738!~Guest37@199.59.102.58> has joined #yocto19:36
*** bgreen <bgreen!~quassel@2600:1010:a11c:fba4:1ac0:4dff:fe33:40b8> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)19:37
Guest3738does anybody if for the cargo class in poky, if the cargo fetch has been tried in do_fetch?19:39
*** ablu <ablu!~m-bfyrfh@user/Ablu> has joined #yocto19:39
Guest3738(for rust)19:39
*** ablu <ablu!~m-bfyrfh@user/Ablu> has quit IRC (Ping timeout: 246 seconds)19:47
*** ablu <ablu!~m-bfyrfh@user/Ablu> has joined #yocto19:52
khemGuest3738:we translate the toml files into SRC_URI entries19:53
khemwe then use bitbake -c update_crates <recipe> to update this e.g. see https://git.openembedded.org/meta-openembedded/tree/meta-python/recipes-devtools/python/python3-pydantic-core-crates.inc19:55
khemand https://git.openembedded.org/meta-openembedded/tree/meta-python/recipes-devtools/python/python3-pydantic-core_2.16.3.bb19:55
*** sgw <sgw!~swold@user/sgw> has quit IRC (Ping timeout: 268 seconds)19:56
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has quit IRC (Ping timeout: 240 seconds)20:09
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has joined #yocto20:10
*** sgw <sgw!~swold@user/sgw> has joined #yocto20:11
Guest3738khem: ah that helps a lot20:12
*** florian_kc <florian_kc!~florian@dynamic-002-243-218-083.2.243.pool.telefonica.de> has quit IRC (Ping timeout: 264 seconds)20:13
*** Haxxa <Haxxa!~Haxxa@116.255.4.123> has quit IRC (Quit: Haxxa flies away.)20:15
*** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@94.31.104.192> has quit IRC (Quit: ZNC 1.9.0 - https://znc.in)20:15
Guest3738anybody use git depencencies in a rust project instead of crates.io dependencies?20:15
*** Haxxa <Haxxa!~Haxxa@116.255.4.123> has joined #yocto20:17
*** alessioigor <alessioigor!~alessioig@185.178.95.238> has quit IRC (Quit: Client closed)20:17
*** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@94.31.104.192> has joined #yocto20:22
*** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@94.31.104.192> has quit IRC (Client Quit)20:23
*** florian_kc <florian_kc!~florian@dynamic-002-243-218-083.2.243.pool.telefonica.de> has joined #yocto20:25
*** Ad0 <Ad0!~Ad0@93.124.245.194> has quit IRC (Ping timeout: 268 seconds)20:28
Guest3738oh it looks like rust git dependencies need a tweak to allow workspace git dependencies20:29
*** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@94.31.104.192> has joined #yocto20:32
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has quit IRC (Ping timeout: 240 seconds)20:56
*** Ad0 <Ad0!~Ad0@93.124.245.194> has joined #yocto21:01
khemRP: I am locally getting the python bits installed right - packages-split/libpython3-staticdev/usr/lib/python3.12/config-3.12-x86_64-linux-musl/libpython3.12.a21:06
khemseems to fail in same way on AB too https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/909821:09
*** npk32 <npk32!~npk32@107.159.218.121> has quit IRC (Quit: Client closed)21:22
khemRP: I think the issue is that the test that upstream added to compute PLATFORM_TRIPLET is working with clang but not with gcc21:25
khemthe build-renamed/ dir on AB has the workdir for python3 but I could not run the compiler inside it. perhaps some issues when the dirs are renamed21:26
*** mvlad <mvlad!~mvlad@2a02:2f05:821a:fb00:e88e:21ff:fe65:be18> has quit IRC (Remote host closed the connection)21:29
Guest3738where do i need to submit patches for poky?21:31
*** mbulut <mbulut!~mbulut@31.18.142.72> has quit IRC (Ping timeout: 255 seconds)21:40
*** mbulut <mbulut!~mbulut@31.18.142.72> has joined #yocto21:47
khemGuest3738: usually if you are chaning things under meta/ then send to openembedded-core list21:49
khemthings under meta-poky go to poky ml and under bitbake/ dir go to bitbake list21:50
*** Saur_Home5 <Saur_Home5!~Saur_Home@94-137-113-31.customers.ownit.se> has quit IRC (Quit: Client closed)21:50
khemsince poky is composed of multiple git repositories21:50
*** Saur_Home5 <Saur_Home5!~Saur_Home@94-137-113-31.customers.ownit.se> has joined #yocto21:50
Jookiai submitted a bug: https://bugzilla.yoctoproject.org/show_bug.cgi?id=1550421:51
khemRP: I can see the problem, its actually the platform test is failing for musl+gcc and works for musl+clang and the reason is a compiler issue where for musl it should look into sysroot for std headers before it looks into compiler headers dirs, I have fixed clang for that few years ago but not gcc21:52
khemfor glibc order is reverse21:52
khemwhich is gcc's default too so it works21:53
khemon glibc systems21:53
RPkhem: glad you at least understand the problem21:57
Guest3738how do i build an image for an image type specifying CONVERSION_CMD ?21:59
*** alperak <alperak!uid641238@id-641238.ilkley.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)22:01
*** florian_kc <florian_kc!~florian@dynamic-002-243-218-083.2.243.pool.telefonica.de> has quit IRC (Ping timeout: 264 seconds)22:02
rburtonGuest3738: IMAGE_TYPES="ext4.gz" would be a gzip-compressed ext4 image22:05
Guest3738rburton: ok that what i thought, im just seeing a problem where .enc for swupdate isnt recognized even though i did inherit swupdate-enc22:05
*** mbulut <mbulut!~mbulut@31.18.142.72> has quit IRC (Ping timeout: 246 seconds)22:14
Guest3738bitbake -e (my-image-name-here) | grep CONVERSION_CMD shows that enc is an entry for CONVERSION_CMD as expected22:18
*** Saur_Home5 <Saur_Home5!~Saur_Home@94-137-113-31.customers.ownit.se> has quit IRC (Quit: Client closed)22:37
*** Saur_Home5 <Saur_Home5!~Saur_Home@94-137-113-31.customers.ownit.se> has joined #yocto22:37
*** vthor <vthor!~thor@2806:10a6:6:1b6e:acbd:297a:3efd:467e> has joined #yocto22:45
*** vthor <vthor!~thor@user/vthor> has quit IRC (Client Quit)22:49
*** xmn <xmn!~xmn@2600:4040:9398:a200:e120:fd4a:df2c:3db8> has quit IRC (Ping timeout: 256 seconds)22:55
*** xmn <xmn!~xmn@2600:4040:9398:a200:b43a:e1c1:4cb5:736d> has joined #yocto23:14
*** Kubu_work <Kubu_work!~kubu@lfbn-nan-1-335-137.w82-120.abo.wanadoo.fr> has quit IRC (Quit: Leaving.)23:18

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