Thursday, 2022-01-13

*** florian <florian!> has joined #yocto00:02
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)00:11
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto00:27
*** sakoman <sakoman!> has quit IRC (Ping timeout: 240 seconds)00:36
*** florian <florian!> has quit IRC (Ping timeout: 250 seconds)00:42
*** sakoman <sakoman!> has joined #yocto00:50
*** dev1990 <dev1990!~dev@> has quit IRC (Quit: Konversation terminated!)00:57
*** BCMM <BCMM!~BCMM@user/bcmm> has quit IRC (Quit: Konversation terminated!)01:09
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Ping timeout: 240 seconds)01:24
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto01:27
*** goliath <goliath!~goliath@user/goliath> has joined #yocto01:48
*** geoffhp <geoffhp!> has joined #yocto01:52
*** sakoman <sakoman!> has quit IRC (Quit: Leaving.)02:13
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Ping timeout: 250 seconds)02:14
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto02:15
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Read error: Connection reset by peer)02:22
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto02:23
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Ping timeout: 240 seconds)02:31
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto02:34
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Read error: Connection reset by peer)02:34
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto02:35
*** sakoman <sakoman!> has joined #yocto02:38
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)03:22
*** sakoman <sakoman!> has quit IRC (Quit: Leaving.)04:23
*** amitk <amitk!~amit@> has joined #yocto04:28
*** jmiehe1 <jmiehe1!~Thunderbi@user/jmiehe> has joined #yocto04:29
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Ping timeout: 268 seconds)04:30
*** jmiehe1 is now known as jmiehe04:30
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)04:33
*** mariusz1 <mariusz1!~mariusz@> has joined #yocto06:10
*** goliath <goliath!~goliath@user/goliath> has joined #yocto06:24
*** Wouter0100 <Wouter0100!> has quit IRC (Remote host closed the connection)06:26
*** Wouter0100 <Wouter0100!> has joined #yocto06:26
*** yocti <yocti!> has joined #yocto06:31
*** alessioigor <alessioigor!~alessioig@> has joined #yocto06:35
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Remote host closed the connection)06:35
*** alessioigor <alessioigor!~alessioig@> has joined #yocto06:35
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Client Quit)06:36
*** alessioigor <alessioigor!~alessioig@> has joined #yocto06:36
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Client Quit)06:36
*** xmn <xmn!> has quit IRC (Read error: Connection reset by peer)06:52
*** xmn_ <xmn_!> has joined #yocto06:53
*** xmn_ <xmn_!> has quit IRC (Quit: xmn_)07:02
*** Guest03 <Guest03!> has joined #yocto07:16
*** Guest0 <Guest0!> has quit IRC (Ping timeout: 256 seconds)07:16
*** tolszak <tolszak!~tolszak@> has joined #yocto07:29
*** mckoan|away is now known as mckoan07:34
*** Guest03 <Guest03!> has quit IRC (Quit: Client closed)07:35
*** frieder <frieder!> has joined #yocto07:51
*** tolszak <tolszak!~tolszak@> has quit IRC (Remote host closed the connection)07:56
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto07:57
*** zpfvo <zpfvo!~fvo@> has joined #yocto07:59
*** Guest0 <Guest0!> has joined #yocto08:05
*** lucaceresoli <lucaceresoli!~lucaceres@> has joined #yocto08:06
*** mvlad <mvlad!~mvlad@2a02:2f08:4e02:5400:24d7:51ff:fed6:906d> has joined #yocto08:07
*** ziga__ <ziga__!> has joined #yocto08:13
*** huseyinkozan <huseyinkozan!~hk@> has joined #yocto08:18
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto08:32
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 252 seconds)08:33
*** zpfvo <zpfvo!~fvo@> has joined #yocto08:34
*** dev1990 <dev1990!~dev@> has joined #yocto08:38
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 245 seconds)08:38
*** zpfvo <zpfvo!~fvo@> has joined #yocto08:39
*** amitk_ <amitk_!~amit@> has joined #yocto08:40
*** amitk <amitk!~amit@> has quit IRC (Ping timeout: 256 seconds)08:43
*** Guest0 <Guest0!> has quit IRC (Quit: Client closed)08:50
*** prabhakarlad <prabhakarlad!> has joined #yocto08:51
*** Schlumpf <Schlumpf!~Schlumpf@> has joined #yocto08:53
*** huseyinkozan <huseyinkozan!~hk@> has quit IRC (Ping timeout: 250 seconds)09:00
*** sveinse <sveinse!~sveinse@2a01:799:55e:1000:c23f:d5ff:fe69:c6fb> has joined #yocto09:07
*** kanavin <kanavin!~Alexander@2a02:2454:29b:3b00:d35d:e3cf:58b5:748b> has quit IRC (Remote host closed the connection)09:07
*** camus1 <camus1!~Instantbi@> has joined #yocto09:10
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 256 seconds)09:10
*** camus1 is now known as camus09:10
sveinseI have a problem with my honister build re-trigging all tasks when I rerun bitbake. What is the current way to debug and track down changes in recipes/sigs? Is it still diffsig as per this page:
*** kroon <kroon!> has joined #yocto09:12
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 256 seconds)09:12
*** zpfvo <zpfvo!~fvo@> has joined #yocto09:13
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 245 seconds)09:17
*** florian <florian!> has joined #yocto09:17
*** zpfvo <zpfvo!~fvo@> has joined #yocto09:17
RPsveinse: yes, you need to find which task hashes change09:24
RPrburton: two stap failures in one build now. There is a qemuarm64 on that failed in 30s so this may be something different but it was on an arm host with kvm so may just happen faster09:27
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)09:34
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 250 seconds)09:42
*** zpfvo <zpfvo!~fvo@> has joined #yocto09:43
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 256 seconds)09:49
*** zpfvo <zpfvo!~fvo@> has joined #yocto09:49
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 268 seconds)09:58
*** zpfvo <zpfvo!~fvo@> has joined #yocto09:59
coldspark29[m]Can someone tell me what imx-boot is needed for? I am currently trying to bump our Yocto version to hardknott and when packaging the .wic, bitbake is missing imx-boot. The NXP user guide says it is SPL + U-Boot etc. so I guess it is the bootloader image. We are building our own bootloader though. Can't find a way to turn this off as dependency.10:00
dacavHi.  As mentioned a few days ago, I've got problems in building the SDK (due to a broken third party).  I've been suggested to work with `bitbake -c devshell ...`, which effectively gives me a way out.  I'm unfortunately missing a few tools.  For example, gdb is present, but has wrong prefix (aarch64-none-elf-gdb).  On the other hand, gcc exists with the correct prefix.10:04
dacavDoing `bitbake-layers show-recipes` presents only `gdb-cross-aarch64`, which I executed, with no success.  Any suggestion?10:04
*** salutfdp <salutfdp!~salutfdp@> has joined #yocto10:05
qschulzcoldspark29[m]: hardknott is soon EOL, I'd suggest starting to work on master so that once kirkstone is out you're ready10:07
qschulzor dunfell10:07
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 268 seconds)10:07
coldspark29[m]qschulz: What about honister?10:08
*** zpfvo <zpfvo!~fvo@> has joined #yocto10:08
coldspark29[m]The NXP document doesn't even mention honister yet.10:08
qschulzcoldspark29[m]: honister is EOL in May10:09
qschulzcoldspark29[m]: whata re you upgrading from?10:09
*** salutfdp is now known as salutlesbg10:10
qschulzcoldspark29[m]: hardknott is EOL in March10:10
coldspark29[m]And here hardknott is the latest version10:10
qschulzkirkstone (current master) is an LTS10:10
qschulzcoldspark29[m]: what do you use from NXP?10:10
qschulzit seems you don't use their bootloader10:10
coldspark29[m]Some NXP layers don't even have an honister branch yet10:10
qschulzcoldspark29[m]: you don't necessarily need vendor BSP layers is all I'm saying10:11
qschulzit depends what your needs are10:11
coldspark29[m]meta-freescale, meta-freescale-3rdparty and meta-freescale-distro10:11
coldspark29[m]Not sure if I need all of them though10:12
coldspark29[m]qschulz: But I need the NXP kernel I guess10:14
qschulzcoldspark29[m]: it's a simple recipe so you can just copy that recipe (or create one that is heavily stripped down from theirs, if bloated) in your meta layer10:16
qschulzI've always tried to not use vendor BSP layers if possible10:17
qschulztaking only what I need10:17
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 268 seconds)10:18
agherzanRP:  we have a kirckstone next branch. Is it fair to assume that it will follow master branch for a good while until we branch off for the release?10:18
coldspark29[m]qschulz: I don't think that I am experienced enough to do that10:18
*** zpfvo <zpfvo!~fvo@> has joined #yocto10:18
*** tnovotny <tnovotny!> has joined #yocto10:19
coldspark29[m]We have our custom board based on an imx8mm chip10:19
coldspark29[m]I probably should create our own custom layer, but for now we just use the NXP layers and throw out what we don't need10:20
dacav`devtool build-image` -> how does it know what image to build?  I usually have to tell it explicitly to bitbake (e.g. `bitbake my-image`)10:20
landgrafdacav: config.get('SDK', 'sdk_targets', '').split()[0]10:25
landgrafdacav: or you will see "Unable to determine image to build, please specify one" :)10:26
dacavthanks landgraf.  Then I'll confidently try it.10:28
dacavlandgraf: is config.get referring to the local.conf or...?10:29
dacavI'm guessing I've to set up this:
*** Guest97 <Guest97!~Guest97@> has joined #yocto10:34
landgrafdacav: looks so: config.set('SDK', 'sdk_targets', d.getVar('SDK_TARGETS')).  give it a try :)10:35
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:9d0b:91ea:5b33:7005> has joined #yocto10:38
coldspark29[m]qschulz: Why is it bad if a Yocto branch is EOL? Isn't just the buildsystem?10:38
coldspark29[m]In the end I am more dependent on the BSP releases from my chip manufacturer, am I not?10:39
dacavlandgraf: where should I write that (python?) line?10:41
dacavalso, a colleague mentioned to me that `devtool build-image` allows for an argument with the image name.  This is not mentioned in the inline help ...but it seems to work.10:43
dacavbut still, where should I put this kind of lines?10:43
*** mariusz1 <mariusz1!~mariusz@> has quit IRC (Ping timeout: 250 seconds)10:46
*** mariusz1 <mariusz1!~mariusz@> has joined #yocto10:47
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 268 seconds)10:48
*** zpfvo <zpfvo!~fvo@> has joined #yocto10:48
coldspark29[m]@qschulz: I tried with master now and now all layers are not compatible10:51
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 245 seconds)10:52
landgrafdacav: you should not. this is the way how it's set. What are you trying to achieve?10:53
*** zpfvo <zpfvo!~fvo@> has joined #yocto10:53
qschulzcoldspark29[m]: no security fixes once the release is EOL10:54
coldspark29[m]Really weird. Bitbake says... (full message at
coldspark29[m]s///, s/eppendorf/custom/10:55
qschulzcoldspark29[m]: you're dependent of your vendor currently because of their vendor BSP layers, hence why I suggested to not use vendor BSP layers but take only what you need. Which takes more time in the beginning for sure, but frees you from your vendor10:55
qschulzit's not always easy nor fast, especially when you need GPU/VPU/IPU/whatever custom weird IP they use10:56
coldspark29[m]qschulz: Do you think that is doable for a newbie? I am new to the company and need to provide some results10:57
coldspark29[m]I haven't come much further than booting the old configuration10:58
coldspark29[m]Is there any guide you can recommend to do that?10:58
qschulzcoldspark29[m]: it's the age old question of immediate results but more difficult maintenance and taking time now for easier maintenance long term10:59
qschulzyou can see already that you have a vendor lockin for now10:59
*** goliath <goliath!~goliath@user/goliath> has joined #yocto10:59
qschulzIt might be just as easy as copying the recipes you need in your layer11:00
qschulzyou'll learn a few things while debugging stuff as well11:00
coldspark29[m]qschulz: I see that point and I am definitely with your there11:00
coldspark29[m]qschulz: But would I not have to do that for every release again? NXP changed quite a lot from gatesgarth to harknott already. I would have to copy the recipes every time. Else I would duplicate all the work NXP does in their layer. I don't see how that will save me work.11:03
coldspark29[m]* harknott already and I coudn't even figure out how to port that yet. I11:04
dacavlandgraf: I'm following the documentation for kernel development ( ), since I need to troubleshoot something that is happening in kernelspace11:05
coldspark29[m]I mean you are super experienced and all of this seems easy to you, but I am quite overwhelmed11:05
* rburton glares at moto-timo for making his CI explode11:05
rburtonLuckily the meta-oe fixes went in promptly so I can just re-run it :)11:06
qschulzcoldspark29[m]: ideally no, you'd just need to bump the version in the recipes you're using to target whatever their latest branch is.11:07
qschulzFor me, the BSP components boil down to: ATF/TF-A, bootloader (U-Boot usually), Linux kernel11:08
qschulzthat's three recipes11:08
qschulzcompared to the miriad of recipes you have in vendor BSPs11:08
coldspark29[m]@qschulz Is there any guide to help me start? Josef doesn't cover that in his tutorials11:08
*** Guest97 <Guest97!~Guest97@> has quit IRC (Ping timeout: 250 seconds)11:08
qschulzcoldspark29[m]: meta-freescale seems to have support for honister?
qschulzso what exactly are you using?11:09
coldspark29[m]You suggested that11:10
qschulzkirkstone is master11:10
qschulzsorry, let me put more ocntext in my message11:10
coldspark29[m]I am super confused now11:10
qschulzYou said you had an issue upgrading to more recent version of Yocto because of meta-freescale layers11:10
qschulzbut meta-freescale seems to be supporting whatever11:11
qschulzsame for meta-freescale-3rdparty and meta-freescale-distro11:12
qschulzor did I miss some messages and got confused?11:12
*** kanavin <kanavin!~Alexander@2a02:2454:29b:3b00:d35d:e3cf:58b5:748b> has joined #yocto11:12
coldspark29[m]No that is basically it.11:12
qschulzaaah this imx-boot stuff I remember, my bad11:13
coldspark29[m]What I am doing atm is checking out the freescale stuff and then copy some things over to my custom layer if they need adjustment11:13
coldspark29[m]That is already hard enough11:13
coldspark29[m]But you are telling me to write my own layer somehow11:13
qschulzthere's almost no way you don't need a layer11:14
coldspark29[m]I am not able to create BSP layers myself yet11:14
qschulzbe it for an image recipe11:14
coldspark29[m]I am quite discouraged now11:15
qschulzI kinda made it hard and confused you so no worries11:15
qschulzSo.. the initial issue was "my vendor BSP layer is not supporting hardknott" (or more recent)11:16
qschulzbut it seems that the three layers you mentioned all have their own hardknott branch11:16
qschulzand there's an imx-boot recipe in meta-freescale11:16
coldspark29[m]Well the freescale-ml doesn't, but we don't need that actually11:16
qschulz(also, as far as I remember, meta-freescale is community maintained, not a vendor BSP layer per se)11:17
qschulzmeta-imx is the vendor BSP layer I think. Anyway :)11:17
coldspark29[m]Freescale is NXP11:17
qschulzyes that I know11:17
coldspark29[m]NXP took them over11:17
qschulzmeta-rockchip is community maintained11:17
coldspark29[m]So what do you mean by vendor bsp now? I am even more confused now11:18
qschulzbasically... My point being. There is a difference between vendor BSP layer and just BSP layer11:18
qschulzBSP layer is usually fine11:18
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 256 seconds)11:18
qschulzvendor BSP layer, not so much (and they might not allow external contribution either)11:18
qschulzso, try to make meta-freescale work as is, if it does nto, you can always ask question/support on the mailing list (or here?) and we can help. We don't really provide help for vendor BSP layer though11:19
qschulzanyway.. I kinda messed up my answers to you and made it more difficult to understand than it should have been11:20
*** rperier <rperier!> has quit IRC (Quit: - Chat comfortably. Anywhere.)11:20
qschulzso.. let's work on fixing this meta-freescale thingy11:20
*** rperier <rperier!> has joined #yocto11:20
qschulzso let's start from the beginning and forget the last 30min :D11:21
*** zpfvo <zpfvo!~fvo@> has joined #yocto11:21
coldspark29[m]I already deleted all of my hardknott progress because you told me it was EOL11:21
qschulz1) did you make sure all of your layers are on the same branch (seems to be hardknott for you, though it'll be EOL soon but the process is the same for other branches)11:21
qschulz2) what is the exact error you're having?11:22
coldspark29[m]qschulz: Sure, I only need to fix my custom layer11:22
coldspark29[m]But if hardknott is so old, I might as well go honister. Especially for the syntax change. That was my initial plan, but then my colleague said I should go with the NXP documents.11:23
coldspark29[m]Being this one
coldspark29[m]And they don't mention honister yet11:23
coldspark29[m]So I was assuming their honister branches are not complete or whatever11:23
qschulzcoldspark29[m]: NXP does not maintain meta-freescale11:24
coldspark29[m]qschulz: The do_image_wic was missing imx-boot while packaging11:24
coldspark29[m]qschulz: Who maintains it then?11:25
qschulzcoldspark29[m]: the community11:25
qschulzin short.. people :D11:26
coldspark29[m]Okay, I did not know that11:26
qschulzwhen I worked on imx8mm we started with meta-imx first which is maintained by NXP11:26
coldspark29[m]No we don't use meta-imx11:27
coldspark29[m]So I am checking out the honister branches of all layers now11:28
qschulzcoldspark29[m]: that's what I had
coldspark29[m]So that is the vendor BSP?11:30
coldspark29[m]meta-rust also doesn't have an honister branch11:30
qschulzcoldspark29[m]: rust is a first citizen since recently11:31
qschulzso not sure you need meta-rust anymore11:31
coldspark29[m]So it is included in poky?11:31
qschulzoe-core even11:31
coldspark29[m]or meta-openembedded?11:31
qschulzno, opembedded-core11:32
qschulz(openembedded-core is "embedded" in poky FYI)11:33
coldspark29[m]So I don't need meta-openembedded if I already have poky?11:34
qschulzno, different things11:34
qschulzmeta-openembedded is NOT openembedded-core11:34
coldspark29[m]I want to verify that rust is still there11:36
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 250 seconds)11:36
*** zpfvo <zpfvo!~fvo@> has joined #yocto11:37
qschulzif you have something that depends on rust, you'll know soon enough if it's not there11:37
rburtonRP: so yeah running the stap test case by hand has resulted in a hang11:37
coldspark29[m]Okay it is in ./poky/meta/recipes-devtools/rust11:38
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 250 seconds)11:41
*** zpfvo <zpfvo!~fvo@> has joined #yocto11:43
RPrburton: at least you can reproduce I guess :)11:46
coldspark29[m]qschulz: So far we have our own meta-custom layer and our own custom machine type in there, because we have our own board based on an imx8mm chip. Then I copy all the required files over from meta-freescale and make our changes. Is that good practice or not?11:48
coldspark29[m]If not, now is the time to do it differently. I want to use the best habits from the start11:49
*** risca <risca!> has quit IRC (Quit: No Ping reply in 180 seconds.)11:56
*** risca <risca!> has joined #yocto11:57
qschulzkeep meta-freescale11:58
qschulzif something's wrong you can contribute to it or get support from the community11:59
coldspark29[m]Sure, but I need to create my own machine configuration I guess11:59
qschulzyes, in your own layer12:00
coldspark29[m]And then I start off with the imx8mm-lpddr4-evk.conf and the corresponding kernel and make my changes12:00
coldspark29[m]I will see how far I get and the write you again12:01
qschulzcoldspark29[m]: you can have your own machine conf file which requires imx8mm-lpddr4-evk.conf in it12:03
qschulzso you don't need to duplicate everything12:03
qschulz(if it makes sense, I didn't check)12:03
*** leon-anavi <leon-anavi!~Leon@> has quit IRC (Ping timeout: 256 seconds)12:09
*** Schlumpf <Schlumpf!~Schlumpf@> has quit IRC (Ping timeout: 256 seconds)12:10
salutlesbghas anyone ever tried to use meta-linaro? can't build anything using the official tags (morty, sumo, warrior, zeus...)12:18
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto12:23
rburtonyou've listed a lot of very old releases12:24
rburtonwhat are you building, for what versions, and what is the error?12:24
rburtonsalutlesbg: ^12:35
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 256 seconds)12:38
salutlesbgi'm trying to build  for armhf, using arm gcc 8.312:39
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 268 seconds)12:39
salutlesbglooks like zeus is the version i look for12:39
*** zpfvo <zpfvo!~fvo@> has joined #yocto12:39
rburtonzeus is very old, and we recommend you upgrade12:40
salutlesbgwhich version would you recommend?12:40
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto12:40
rburtonthe latest :)12:40
rburtondunfell is the LTS release12:40
rburtondepends what you own release cycle is12:41
rburtonthere are biannual LTS releases, or six monthly releases, with different support durations12:41
salutlesbgdunfell sounds good, i'll try12:42
rburton(next LTS coming this spring too)12:42
salutlesbgi'm using yocto for personal use so no release cycle defined12:42
rburtonah in that case the six monthly releases mean you get latest stuff quicker12:43
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 240 seconds)12:45
salutlesbgalright thanks12:50
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto12:50
salutlesbgrburton: im still getting errors even on dunfell13:08
rburtonimpossible to help if you don't say what the errors are13:08
salutlesbgFetcher failure: Unable to find revision 0cf25829896330dcf8f95d8484c5f0eae6923f4f in branch linux-linaro even from upstream13:08
salutlesbg-SRC_URI_append = " git://;protocol=http;branch=linux-linaro;name=kernel "13:09
salutlesbg+SRC_URI_append = " git://;protocol=http;name=kernel;nobranch=1 "13:09
salutlesbgdid the trick13:09
rburtonwhat hardware are you building for?13:09
RPrburton: qemuarm64-alt is working at least :)13:10
rburtonsalutlesbg: that's not hardware :). if youre running in qemu, qemuarm is good13:10
rburtonRP: phew13:11
*** kroon <kroon!> has quit IRC (Quit: Leaving)13:15
*** alessioigor <alessioigor!~alessioig@> has joined #yocto13:20
salutlesbgrburton: wym? target cpu is a ARM Cortex A8 CPU 32bit13:21
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Client Quit)13:21
salutlesbgi'm trying to build a SDK to be able to cross-compile my apps for this target13:21
coldspark29[m]qschulz: I am getting a ERROR: ParseError in configuration INHERITs: Could not inherit file classes/image-mklibs.bbclass now. Seems to be here, so I wonder why it is not included in any of my meta-layers13:40
qschulzcoldspark29[m]: inherit image-mklibs13:42
qschulzinherit works on classes only so .bbclass is implied as extension13:42
qschulzinherit works with bbclasses only and they all appear in specified directories (via BBPATH IIRC) so there's no need to give the path either13:42
coldspark29[m]It is in my local.conf, because I was adjusting it to look like the NXP setup with Repo etc13:44
coldspark29[m]USER_CLASSES ?= "buildstats image-mklibs image-prelink"13:44
coldspark29[m]But in none of my layers13:45
coldspark29[m]I ripgrepped all layers13:46
zeddiithe class was removed from core. your local.conf is just needs to be udpated.13:47
coldspark29[m]Updated how? When I remove it I get another error13:50
zeddiijust remove it fro the USER_CLASSES, whatever error you have next, I can't say .. but you defnitely have to remove it from that variable if you are in a branch where it has been removed (It was removed ~may 2021)13:51
*** salutlesbg <salutlesbg!~salutfdp@> has quit IRC (Quit: Connection closed)13:51
* coldspark29[m] sent a code block:
coldspark29[m]Guess the local config layout has changed in honister?13:53
*** sakoman <sakoman!> has joined #yocto13:55
coldspark29[m]Any idea why bitbake is complaining about the old override syntax here?
coldspark29[m]It is inside poky so no idea why that happens14:08
qschulzcoldspark29[m]: can we get the error message maybe?14:08
coldspark29[m]ERROR: /home/user/Workspace/Yocto-Workspace/vti2/sources/poky/meta/recipes-graphics/wayland/ Variable do_install_append_mx6 contains an operation using the old override syntax. Please convert this layer/metadata before attempting to use with a newer bitbake.0:4114:09
coldspark29[m]ERROR: Failed to parse recipe: /home/user/Workspace/Yocto-Workspace/vti2/sources/poky/meta/recipes-graphics/wayland/weston-init.bb14:09
coldspark29[m]There is no do_install_append_mx6 in that recipe14:10
qschulzcoldspark29[m]: did you checkout ALL your layers to a honister branch?14:10
qschulzpoky included?14:11
qschulzdid you check your bblayers.conf points to those up-to-date layers?14:11
coldspark29[m]Think it was my custom layer14:12
coldspark29[m]I ried to change the override syntaxes manually14:12
coldspark29[m]I ran the script over it and now it works14:12
coldspark29[m]Should have done that in the first place...14:12
qschulzit's alright don't worry :)14:12
coldspark29[m]Yeah but I want to work independently actually14:13
coldspark29[m]My colleague also says that I should look at the code rather than asking people, but Yocto is just a special kind of beast14:14
coldspark29[m]Compling now tumbs crossed14:14
qschulzcoldspark29[m]: everybody starts one day, I still ask plenty of questions14:14
coldspark29[m]Who do you ask? You are the most active person here14:15
qschulzwe know Yocto has a steep learning curve, you'll get there eventually. I was very lost at the beginning too, I'm doing better now :)14:15
coldspark29[m]Yeah but you know that bosses don't care14:15
qschulzcoldspark29[m]: I read the code now more than I ask questions but I started like you14:15
coldspark29[m]They don't want to hear why or how it works or doesn't14:15
coldspark29[m]They want results14:16
qschulzyour bosses didn't tell you to not ask the community :)14:16
qschulzWe all struggled and still struggle to find the right balance between immediate results and learning things/doing them properly14:17
coldspark29[m]Well I have one colleague who knows more than me. He has been the sole base system guy of this company for years and has done everything by himself. He is just approaching stuff differently14:17
coldspark29[m]qschulz: Yeah and doing things properly is important. I am a big fan of that. I don't like to advance if I don't know what I am doing.14:18
coldspark29[m]But then I am slow...14:18
coldspark29[m]It was like this job I had as a sysadmin once. There were two of us and we were supposed to activate SSL for our servers. The other guy created the certificate online while I was working on certbot. He was done faster than me and my boss asked me why. Just stupid...14:20
qschulzI'm afraid to say this feeling of being slow hasn't disappeared yet, even if I'm more skilled than I was years ago. I don't have a recipe for feeling better unfortunately :/14:20
coldspark29[m]His approach would have to be repeated every year and mine was a one-time solution.14:20
coldspark29[m]s/one/long/, s/time/term/14:21
coldspark29[m]qschulz: Just act like it's French mentality or something. Should work in Austria ;)14:22
*** xmn <xmn!> has joined #yocto14:23
qschulzjust to be clear, I was saying I still feel slow today. No complaint from bosses. Just wanted to say that sometimes we feel/think things that aren't objectively true (and what is *slow* anyway?)14:24
coldspark29[m]Then that is just a character trait I guess. I am quite hard on myself as well. It also has advantages though.14:24
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 256 seconds)14:25
qschulzTherapy helped me already with self expectations but yeah, it's hard to find a healthy balance14:25
coldspark29[m]I think most people are like it though ;)14:26
qschulzthen it says more about our society than yourself :)14:26
qschulzanyways, I think our not-so-private conversation has spammed enough the chan :)14:27
coldspark29[m]qschulz: Well, you shouldn't see it as a defect. I have friends who think they are doing great, but their achievements fade in comparison.14:28
coldspark29[m]qschulz: Alright alright14:28
coldspark29[m]You can always PM me :)14:28
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 252 seconds)14:32
*** zpfvo <zpfvo!~fvo@> has joined #yocto14:33
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto14:35
*** radsquirrel <radsquirrel!~radsquirr@> has joined #yocto14:36
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 268 seconds)14:38
*** zpfvo <zpfvo!~fvo@> has joined #yocto14:39
*** salutlesbg <salutlesbg!> has joined #yocto14:39
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 250 seconds)14:39
*** rob_w <rob_w!> has joined #yocto14:44
RPcoldspark29[m]: remember that the problem Yocto Project solves is complex. Would your bosses expect you to perform brain surgery tomorrow with no prior experience? Probably not. Some software problems are similar - skills take time to learn14:45
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto14:47
coldspark29[m]RP: Yes you are right. I guess I just have the same character trait as Quentin ;)14:49
*** radsquirrel <radsquirrel!~radsquirr@> has quit IRC (Quit: radsquirrel)14:54
*** radsquirrel <radsquirrel!~bradleyb@> has joined #yocto14:55
LetoThe2ndyo dudX15:03
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)15:05
*** TundraMan is now known as marka15:14
*** rob_w <rob_w!> has quit IRC (Quit: Leaving)15:19
radsquirrelhi all.  I'm trying to use mkimage/openssl/libp11/p11-kit in native context.15:20
*** Schlumpf <Schlumpf!~Schlumpf@> has joined #yocto15:22
radsquirrelThe issue I face is that when mkimage runs and I tell it to use the pkcs11 engine, it looks for that in the openssl sysroot rather than the libp11 sysroot.  I suspect that if I get past this issue, I'll run into it again when libp11 (provided by libp11) looks for the p11 kit proxy library (provided by p11-kit).15:23
radsquirrelAm I breaking new ground here or is this a solved problem?15:23
rburtonthere's only one sysroot when you actually run something15:24
rburtoneach recipe contributes a piece15:24
rburtonif something is hard-coding a path to the build sysroot then that needs to be fixed up when the sysroot is used15:24
rburtontypically, environment variables are used15:25
radsquirrelrburton:thanks...I'm still processing what you said :-)15:26
radsquirrelso I guess openssl should provide an env var for its search path for engine plugins?15:27
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 268 seconds)15:27
radsquirrelperhaps it alread does.15:27
*** zpfvo <zpfvo!~fvo@> has joined #yocto15:28
radsquirrelor is the problem with mkimage15:28
radsquirrelI straced my mkimage invocation and this is where its looking for libp1115:29
radsquirrelare you saying that's wrong?  and it should be looking for it in some "shared" location?15:29
rburtonhow are you running mkimage and from what recipe?15:30
radsquirrelI made my own recipe15:31
radsquirrelI'm just running it from do_compile15:32
radsquirrellet me make a paste15:32
rburtonyou might have found a new edge case that doesn't get relocated15:34
rburtontheres most likely a variable that openssl uses to know where to look for engines, and you just need to set that15:35
rburtonif you grep for create_wrapper you'll find lots of wrapper scripts that are generated to do that15:35
radsquirrelrburton: good stuff, thanks for those hints.15:36
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 256 seconds)15:37
*** zpfvo <zpfvo!~fvo@> has joined #yocto15:38
*** mariusz1 <mariusz1!~mariusz@> has quit IRC (Ping timeout: 256 seconds)15:39
*** florian <florian!> has quit IRC (Quit: Ex-Chat)15:49
rburtonthe basic problem is that some libraries hardcode their search paths15:52
rburtonwhich doesn't work too well when you take those libraries and build a new sysroot with them15:52
*** lucaceresoli <lucaceresoli!~lucaceres@> has quit IRC (Quit: Leaving)15:54
radsquirrelrburton that was exactly the hint I needed, thanks.  if I wrap mkimage and specify OPENSSL_ENGINES I'm off to the races.15:56
radsquirrelI'll send a patch...15:58
*** hpsy[m] <hpsy[m]!~hpsymatri@2001:470:69fc:105::f822> has quit IRC (Quit: You have been kicked for being idle)16:00
*** akiCA <akiCA!~akiCA@user/akica> has joined #yocto16:04
*** codavi <codavi!~akiCA@user/akica> has joined #yocto16:05
*** akiCA <akiCA!~akiCA@user/akica> has quit IRC (Ping timeout: 250 seconds)16:09
JPEWRP: For Yocto #14685, do you want a targeted "add a dependency on zstd" or a more general solution like we discussed eariler?16:19
*** ctxnop <ctxnop!~ctxnop@2a02:2788:864:1cf:a411:2d43:4e7d:fd04> has joined #yocto16:29
moto-timomichaelo: I'm also hoping to get to finishing the kernel-lab docs this week16:31
moto-timomichaelo: that takes a special "attention to detail" mindset to do it right16:31
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Read error: Connection reset by peer)16:32
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto16:34
*** ctxnop <ctxnop!~ctxnop@2a02:2788:864:1cf:a411:2d43:4e7d:fd04> has quit IRC (Quit: Client closed)16:35
*** goliath <goliath!~goliath@user/goliath> has joined #yocto16:42
*** zpfvo <zpfvo!~fvo@> has quit IRC (Quit: Leaving.)16:47
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)16:52
*** Schlumpf <Schlumpf!~Schlumpf@> has quit IRC (Quit: Client closed)17:01
RPJPEW: I think we'll need a general solution17:16
RPJPEW: this issue is just a symptom17:16
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto17:22
*** mckoan is now known as mckoan|away17:24
*** tnovotny <tnovotny!> has quit IRC (Quit: Leaving)17:31
JPEWRP: I was trying to think if it was possible (or wise) to try and "roll down" the dependencies into the final task instead of having each intermediate change it's output based on dependencies... basically automate the process of making do_package_write_rpm depend on zstd instead of making rpm do it17:37
RPJPEW: I wondered about that but I think rolling them into the outhash is going to be the practical approach17:40
JPEWRP: K, I'll give that a go17:50
JPEWThat doesn't somehow defeat hashequiv in some way I can't comprehend, does it?17:50
JPEWI don't *think* it would....17:50
*** gsalazar_ <gsalazar_!~gsalazar@> has quit IRC (Ping timeout: 240 seconds)17:51
*** JaMa <JaMa!> has joined #yocto17:52
JPEWI guess it's no different that if the dependency does actually change a recipe (e.g. header change or whatever), you'r just forcing it17:53
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 240 seconds)17:59
ad__hi, i am in dunfell, getting a "multiple versions are due to be built" error, but i am setting the PREFERRED_VERSION, anyway, still getting the error. What can be wrong ?18:25
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Quit: jmiehe)18:44
*** mariusz1 <mariusz1!~mariusz@> has joined #yocto18:55
*** frieder <frieder!> has quit IRC (Remote host closed the connection)18:56
RPJPEW: I don't think so, it just adds a constraint (which we want)19:18
JPEWOK, I'll draft something up for that19:20
*** mariusz1 <mariusz1!~mariusz@> has quit IRC (Ping timeout: 250 seconds)19:23
*** wooosaii <wooosaii!> has joined #yocto19:27
*** leonanavi <leonanavi!~Leon@> has joined #yocto19:27
*** ziga_ <ziga_!> has joined #yocto19:29
*** leon-anavi <leon-anavi!~Leon@> has quit IRC (Ping timeout: 256 seconds)19:29
*** ziga__ <ziga__!> has quit IRC (Ping timeout: 256 seconds)19:29
*** wooosaiii <wooosaiii!> has quit IRC (Ping timeout: 256 seconds)19:29
*** sakoman <sakoman!> has quit IRC (Ping timeout: 256 seconds)19:34
*** sakoman <sakoman!> has joined #yocto19:34
*** salutlesbg <salutlesbg!> has quit IRC (Quit: Client closed)19:52
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:9d0b:91ea:5b33:7005> has quit IRC (Remote host closed the connection)19:54
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto19:54
*** florian <florian!> has joined #yocto20:00
vmesontgamblin: and vmeson are a bit flummox about cmake-native not building on a ubu-18.04.6 system whereas it works on 18.04.320:12
zeddiispeaking in the 3rd person, and using flummox .. two crimes, one statement20:13
vmesonsymptom is: Error when bootstrapping CMake:  Problem while running initial CMake   in cmake-native do_configure in case anyone else is having similar issues.20:13
vmesonzeddii: you aren't flummoxed by stap still ?20:14
* vmeson runs20:14
vmesonanyway, if anyone else sees this let us know.20:14
*** davidinux <davidinux!~davidinux@> has quit IRC (Ping timeout: 256 seconds)20:28
vd_which package provides sfdisk?20:39
*** florian <florian!> has quit IRC (Ping timeout: 250 seconds)20:40
*** mauro_anjo <mauro_anjo!~AdminUser@> has joined #yocto20:48
vd_thank you20:50
*** mauro_anjo <mauro_anjo!~AdminUser@> has quit IRC (Client Quit)20:51
*** mauro_anjo <mauro_anjo!~quassel@> has joined #yocto20:51
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)20:56
*** mauro_anjo <mauro_anjo!~quassel@> has quit IRC (Ping timeout: 256 seconds)21:11
*** ziga_ <ziga_!> has quit IRC (Ping timeout: 250 seconds)21:16
RPOr TUNEABI for that matter21:20
RPvmeson: could you check if WR use these anywhere?21:20
vmesonRP I just did! There's no sign of it in our layers on master.21:21
RPvmeson: cool. It was seebs who added these but I know of no use of them anywhere so I think we'll just remove them21:21
*** mvlad <mvlad!~mvlad@2a02:2f08:4e02:5400:24d7:51ff:fed6:906d> has quit IRC (Remote host closed the connection)21:22
vmesonRP, makes sense I suppose, I did see seebs using it in email from many years ago.21:23
RPvmeson: If people need them, they can implement this in their layer now ;-)21:24
vmesonNothing since 2015!21:24
* RP sends a nice deletion patch21:27
rburtonRP: good news: systemtap upstream are fixing some issues i've found in debugging the problem21:28
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto21:30
*** florian <florian!> has joined #yocto21:37
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Read error: Connection reset by peer)21:44
RPrburton: that is very cool :)21:44
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto21:45
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Read error: Connection reset by peer)21:51
*** florian <florian!> has quit IRC (Ping timeout: 250 seconds)21:51
*** Tokamak_ <Tokamak_!~Tokamak@> has joined #yocto21:52
*** Tokamak_ <Tokamak_!~Tokamak@> has quit IRC (Read error: Connection reset by peer)21:54
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto21:54
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Read error: Connection reset by peer)21:57
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto22:03
*** wCPO <wCPO!> has quit IRC (Quit: The Lounge -
*** Tokamak_ <Tokamak_!~Tokamak@> has joined #yocto22:08
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Read error: Connection reset by peer)22:08
*** wCPO <wCPO!> has joined #yocto22:10
*** florian <florian!> has joined #yocto22:25
*** ecdhe_ is now known as ecdhe22:36
abellonidid anyone try to build poky on macos?22:37
fraythe pseudo part is dificult to do under recent MacOS..22:37
frayMacOS security software restricts what/how you can intercept things, while Linux makes it pretty easy via LD_PRELOAD22:38
kergothIf you don't have issue with docker desktop licensing that works great for it, but I've een doing my builds in lima lately (wraps qemu)22:39
kergothlimactl start debian; fire up vscode and connect to it over ssh and open my workspace, kick off a build22:39
kergothits like wsl for mac basically, just with qemu under it instead of a vm. can run contianers under it also, though that has some limitations right now22:44
*** amitk_ <amitk_!~amit@> has quit IRC (Ping timeout: 256 seconds)22:44
*** Tokamak_ <Tokamak_!~Tokamak@> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)22:48
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto22:50
*** florian <florian!> has quit IRC (Ping timeout: 250 seconds)22:58
*** dmoseley <dmoseley!~dmoseley@> has quit IRC (Ping timeout: 256 seconds)23:06
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)23:18
* RP suspects we're seeing on the autobuilder :(23:25
*** dmoseley <dmoseley!~dmoseley@> has joined #yocto23:26
*** leonanavi <leonanavi!~Leon@> has quit IRC (Quit: Leaving)23:29

Generated by 2.17.2 by Marius Gedminas - find it at!