Wednesday, 2022-05-11

*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 246 seconds)00:28
*** nemik <nemik!> has joined #yocto00:29
*** qschulz <qschulz!> has quit IRC (Remote host closed the connection)00:32
*** nemik <nemik!> has quit IRC (Ping timeout: 240 seconds)00:33
*** nemik <nemik!~nemik@> has joined #yocto00:34
*** qschulz <qschulz!> has joined #yocto00:35
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 240 seconds)01:13
*** nemik <nemik!> has joined #yocto01:14
*** wkawka <wkawka!> has quit IRC (Ping timeout: 252 seconds)01:14
*** nemik <nemik!> has quit IRC (Ping timeout: 252 seconds)01:18
*** nemik <nemik!~nemik@> has joined #yocto01:18
*** starblue <starblue!> has quit IRC (Ping timeout: 276 seconds)01:29
*** starblue <starblue!~juergen@> has joined #yocto01:30
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving)02:04
*** sakoman <sakoman!> has quit IRC (Quit: Leaving.)02:11
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 256 seconds)02:14
*** nemik <nemik!> has joined #yocto02:14
*** nemik <nemik!> has quit IRC (Ping timeout: 252 seconds)02:18
*** nemik <nemik!~nemik@> has joined #yocto02:19
*** sakoman <sakoman!> has joined #yocto02:26
*** _whitelogger <_whitelogger!> has quit IRC (Remote host closed the connection)02:27
*** _whitelogger <_whitelogger!> has joined #yocto02:30
vvnwhatever I do, qtwebengine recompile every times. It's now compiling qtdeclarative-5.15.3+gitAUTOINC+32b37e20f7-r0 for example. Am I doing something wrong?02:33
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Read error: Connection reset by peer)02:33
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto02:40
*** Tokamak_ <Tokamak_!~Tokamak@> has joined #yocto02:43
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Ping timeout: 256 seconds)02:45
*** thomas_ <thomas_!> has joined #yocto04:24
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has joined #yocto04:27
*** vvn <vvn!> has quit IRC (Quit: WeeChat 3.5)04:38
*** vvn <vvn!> has joined #yocto04:41
*** Polo <Polo!~textual@user/polo> has joined #yocto04:42
*** vvn <vvn!> has quit IRC (Client Quit)04:43
*** vvn <vvn!> has joined #yocto04:45
*** sakoman <sakoman!> has quit IRC (Quit: Leaving.)04:47
*** Polo <Polo!~textual@user/polo> has quit IRC (Quit: Textual IRC Client:
*** money <money!~textual@user/polo> has joined #yocto04:50
*** money is now known as Gambino04:51
*** Gambino <Gambino!~textual@user/polo> has quit IRC (Client Quit)04:52
*** vvn <vvn!> has quit IRC (Ping timeout: 240 seconds)05:10
*** vvn <vvn!> has joined #yocto05:12
*** olani <olani!~olani@> has quit IRC (Ping timeout: 256 seconds)05:14
*** vvn <vvn!> has quit IRC (Client Quit)05:17
*** vvn <vvn!> has joined #yocto05:18
*** vvn <vvn!> has quit IRC (Client Quit)05:18
*** vvn <vvn!> has joined #yocto05:19
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 256 seconds)05:29
*** nemik <nemik!> has joined #yocto05:29
*** nemik <nemik!> has quit IRC (Ping timeout: 276 seconds)05:34
*** nemik <nemik!~nemik@> has joined #yocto05:34
*** rob_w <rob_w!> has joined #yocto05:51
*** Guest8962 <Guest8962!> has joined #yocto05:53
*** Guest8962 <Guest8962!> has quit IRC (Read error: Connection reset by peer)05:57
*** dev1990 <dev1990!> has joined #yocto06:17
*** adrian__ <adrian__!~F_Adrian@> has joined #yocto06:18
*** OnkelUlla <OnkelUlla!> has joined #yocto06:29
*** goliath <goliath!~goliath@user/goliath> has joined #yocto06:34
*** bps <bps!~bps@user/bps> has joined #yocto06:34
*** mckoan|away is now known as mckoan06:41
mckoangood morning06:41
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto06:42
*** frieder <frieder!> has joined #yocto06:43
*** bps <bps!~bps@user/bps> has quit IRC (Ping timeout: 240 seconds)07:02
*** cmd <cmd!~cmd@user/cmd> has quit IRC (Remote host closed the connection)07:04
*** pbergin <pbergin!~pbergin@> has joined #yocto07:07
*** florian_kc <florian_kc!> has joined #yocto07:13
*** Rolle79 <Rolle79!~Rolle79@> has joined #yocto07:22
*** olani <olani!> has joined #yocto07:23
Rolle79I am cross-compiling a toolchain for arm. I have specified TARGET_OS=linux-gnueabi and TCLIBC=glibc, but still the SDK ends up with a musl and a musl-eabi toolchain in addition to the linux-gnueabi. How can I disable this?07:24
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 246 seconds)07:35
*** thomas__ <thomas__!> has joined #yocto07:37
*** thomas_ <thomas_!> has quit IRC (Ping timeout: 240 seconds)07:39
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 256 seconds)07:39
*** nemik <nemik!~nemik@> has joined #yocto07:40
*** Schiller <Schiller!> has joined #yocto07:47
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto07:48
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 276 seconds)07:59
*** Guest0815 <Guest0815!~Guest0815@> has joined #yocto07:59
*** Bardon_ <Bardon_!~Bardon@user/Bardon> has joined #yocto08:00
*** Bardon <Bardon!~Bardon@user/Bardon> has quit IRC (Ping timeout: 276 seconds)08:00
*** bps <bps!~bps@> has joined #yocto08:01
Guest0815Hello, I noticed a call of bitbake does not use all cores for compiling in parallel, instead it seems it's only a single-core compiling. As my PC is quadcore, bitbake would be much more faster with parallel compiling. Is there a bitbake option for that?08:01
Guest0815(release is honister)08:02
landgrafGuest0815: THere's bitbake option for that. However default value is to use parallel compiling08:07
landgrafGuest0815: BB_NUMBER_THREADS and PARALLEL_MAKE08:07
*** mrnuke <mrnuke!> has quit IRC (Ping timeout: 246 seconds)08:10
*** mrnuke <mrnuke!> has joined #yocto08:11
Guest0815Okay. Thank you08:12
*** Guest0815 <Guest0815!~Guest0815@> has quit IRC (Quit: Guest0815)08:12
qschulzlandgraf: please point to :)08:16
*** Nate20 <Nate20!~Nate@2406:5a00:b440:4600:b0de:c5ca:b548:77d8> has quit IRC (Quit: Client closed)08:18
landgrafqschulz: it was google, not me :) I've taken link from here08:18
landgrafqschulz: but point taken, thanks08:18
*** davidinux <davidinux!~davidinux@> has joined #yocto08:30
*** davidinux <davidinux!~davidinux@> has quit IRC (Ping timeout: 246 seconds)08:35
*** Bardon_ <Bardon_!~Bardon@user/Bardon> has quit IRC (Ping timeout: 252 seconds)08:36
*** davidinux <davidinux!~davidinux@> has joined #yocto08:37
*** Bardon_ <Bardon_!~Bardon@user/Bardon> has joined #yocto08:39
*** Starfoxxes <Starfoxxes!~Starfoxxe@2a02:8070:5390:d00:12bf:48ff:feb8:38c8> has quit IRC (Ping timeout: 260 seconds)08:44
*** amahnui1 <amahnui1!> has joined #yocto08:53
*** Starfoxxes <Starfoxxes!~Starfoxxe@2a02:8070:5390:d00:12bf:48ff:feb8:38c8> has joined #yocto08:56
*** Starfoxxes <Starfoxxes!~Starfoxxe@2a02:8070:5390:d00:12bf:48ff:feb8:38c8> has quit IRC (Ping timeout: 248 seconds)09:04
*** tnovotny <tnovotny!> has joined #yocto09:05
*** PaowZ <PaowZ!> has quit IRC (Ping timeout: 240 seconds)09:07
*** PaowZ <PaowZ!> has joined #yocto09:08
*** Starfoxxes <Starfoxxes!~Starfoxxe@2a02:8070:5390:d00:12bf:48ff:feb8:38c8> has joined #yocto09:08
kayterina[m]hello.When does devtool creates a folder with this revision? "1.0+git999-r0/"09:10
rburtonlandgraf: check what google gives you. the 1.4 docs are *very* old09:11
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 256 seconds)09:12
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto09:15
*** pgowda_ <pgowda_!> has joined #yocto09:26
*** prabhakarlad <prabhakarlad!> has joined #yocto09:28
LetoThe2ndyo dudX09:30
*** davidinux <davidinux!~davidinux@> has quit IRC (Ping timeout: 256 seconds)09:38
*** florian_kc <florian_kc!> has joined #yocto09:46
*** Wouter0100 <Wouter0100!> has quit IRC (Remote host closed the connection)09:50
*** Wouter0100 <Wouter0100!> has joined #yocto09:50
*** ptsneves <ptsneves!> has joined #yocto10:08
derRichardis it only me or is downloading always super slow?10:10
derRichardi get a most 500kb/s here ;-\10:10
rburtonhalstead: ^10:11
qschulzderRichard: it was an issue a few weeks ago, don't know if we did anything since?10:11
qschulzderRichard: you should setup your own mirror on your premises anyway (not that it fixes the actual issue :) )10:12
derRichardqschulz: i have a shared download dir...10:12
derRichardbut this is the very first build which needs that file10:12
qschulzhalstead: I have 200KBps here (Austria) if that helps pinpointing the issue?10:14
qschulzderRichard: halstead is in the US (don't remember which coast), so probably will need to wait a few hours :)10:15
derRichard0: binutils-native-2.38-r0 do_fetch - 1h0m5s (pid 17535)  62% |######################################################################################################                                                                | 134K/s10:15
derRichardalso austria here10:15
*** starblue <starblue!~juergen@> has quit IRC (Ping timeout: 252 seconds)10:16
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 240 seconds)10:18
*** starblue <starblue!> has joined #yocto10:18
*** nemik <nemik!> has joined #yocto10:19
*** mvlad <mvlad!~mvlad@2a02:2f08:4114:c500:24d7:51ff:fed6:906d> has joined #yocto10:19
florianderRichard: I had a similar issue a few days ago... (from germany).10:20
*** wkawka <wkawka!> has joined #yocto10:21
*** nemik <nemik!> has quit IRC (Ping timeout: 252 seconds)10:24
*** nemik <nemik!~nemik@> has joined #yocto10:24
*** kroon <kroon!> has joined #yocto10:27
*** wkawka <wkawka!> has quit IRC (Quit: Client closed)10:27
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 248 seconds)10:28
*** xmn <xmn!> has quit IRC (Quit: ZZZzzz…)10:52
kayterina[m]pyinstaller has a COPYING.txt which was added by devtool in the recipe. It says that pyinstaller is GPLv2+ , so I also add LICENSE = "GPLv2+" ?10:54
kayterina[m]changed Uknown to GPLv2+ is ok?10:56
*** kroon <kroon!> has quit IRC (Quit: Leaving)10:56
qschulzkayterina[m]: not sure to follow what you mean by "COPYING.txt which was added by devtool"10:59
kayterina[m]devtool add found a copying text and added that to the recipe with th ecomment I should check the licenses11:00
kayterina[m]the text is from the package11:00
*** R0b0t1 <R0b0t1!> has joined #yocto11:00
R0b0t1How do I use bitbake-layers to add an existing openembed layer to my project?11:00
R0b0t1I'm trying to modify the distro files from stmicro11:01
qschulzkayterina[m]: unfortunately, it is not GPL-2.0 :/11:01
qschulzkayterina[m]: look at the meta section11:01
kayterina[m]a,ok. So I keep their license file copying.txt in the recipe and it is ok?11:02
qschulzkayterina[m]: I would actually set it to GPL-2.0-or-later-with-bootloader-exception and then use NO_GENERIC_LICENSE to add the COPYING.txt to the license files11:02
qschulzkayterina[m]: yup, that's usually what should be done11:03
qschulzyou always point to in-tree (in the sources) files for the license11:03
*** davidinux <davidinux!~davidinux@> has joined #yocto11:03
qschulzif it's not a common license, I think you need to play with NO_GENERIC_LICENSE or BitBake might complain11:03
qschulzR0b0t1: bitbake-layers --help ? :)11:10
R0b0t1yes but open questions for that command are what do I name the directory, why, and what do I put in it11:10
R0b0t1I did find that meta-openembedded was already in the project with all contents, including meta-networking; I need to edit the recipes to include pppd, how do I do that?11:11
R0b0t1I don't mind reading the docs but finding what exactly I need to read and why is proving to be a big issue11:13
*** amahnui1 <amahnui1!> has quit IRC (Quit: Connection closed for inactivity)11:13
qschulzR0b0t1: you need to clone the git repo for meta-openembedded manually in one directory11:14
qschulzthen bitbake-layers add-layer $SOMEPATH/meta-openembedded/meta-networking should do it?11:14
R0b0t1ok, good, that is what I came up with before I noticed the project included meta-openembedded11:15
R0b0t1last part hmm11:15
R0b0t1how do I select which things in a layer I want11:15
R0b0t1the entirety of meta-networking is pretty big11:15
kayterina[m]does this point to in-tree files?11:15
kayterina[m]LIC_FILES_CHKSUM = "file://COPYING.txt;md5=752110777ecd9e72b16df0e59c1e0019"11:15
qschulzkayterina[m]: it should yes11:16
R0b0t1looks like meta-networking is already added from show-layers but pppd is not selected11:16
qschulzif it does not, bitbake will complain it cannot find the file11:16
qschulzR0b0t1: you shouldn't need to import only a selection of recipes from a layer11:16
qschulzR0b0t1: note that including a layer does not mean building the recipes11:17
qschulzit means the recipes will be parsed and are available if they need to be built11:17
qschulzif you need to add something to your image11:17
qschulzyou need: 1) a recipe (probably already aailable in some layer youi need to add), 2) add it to your image one way or the other (usually via IMAGE_INSTALL in your image recipe)11:18
R0b0t1so where do I specy it's install? add my own layer, and that layer pulls it in?11:18
R0b0t1still a little confused11:18
*** davidinux <davidinux!~davidinux@> has quit IRC (Ping timeout: 260 seconds)11:19
qschulzR0b0t1: should probably help you get started and understand the concepts used by yocto11:20
R0b0t1I build the image I use right now with `bitbake st-image-weston` but I'm finding no link between that name and what is actually on disk11:20
qschulzR0b0t1: what do you mean? what's the issue?11:20
R0b0t1I do pretty poorly with videos qschulz, which part of the docs should I be looing at?11:20
*** davidinux <davidinux!~davidinux@> has joined #yocto11:21
R0b0t1well I don't know how to specify a specific recipe should be installed11:21
qschulzyou should have a recipe named somewhere, this is your iamge recipe11:21
R0b0t1I know the default build target in the current yocto config I've been provided from vendor but not much else11:21
qschulz for the concetps11:21
rburton is the image recipe11:22
qschulz could also help11:22
rburtonargh another copy of the optee recipes in there11:22
*** Sukru <Sukru!~Sukru@> has joined #yocto11:23
R0b0t1thinkg I got it qschulz, thanks11:24
R0b0t1yeah the st provided docs are... weird, for reasons I can't quite figure out, and don't track perfectly with project docs11:26
*** tnovotny <tnovotny!> has quit IRC (Quit: Leaving)11:55
*** cmd <cmd!~cmd@user/cmd> has joined #yocto12:02
*** wkawka <wkawka!> has joined #yocto12:05
*** dvorkindmitry <dvorkindmitry!~dv@> has quit IRC (Quit: KVIrc 5.0.0 Aria
*** dvorkindmitry <dvorkindmitry!~dv@> has joined #yocto12:08
wkawkaHi, I'm trying to integrate previously builded u-boot image with builded kernel version. Both of them are working if they are alone, but when I simply copy u-boot on card, system cannot boot throwing: libfdt fdt_check_header(): FDT_ERR_BADMAGIC. I have to discover how can I rebuild either of those to get them work together.12:09
wkawkaWhen I'm trying to boot it manually, using booti command I'm getting : Bad Linux ARM64 Image magic!12:11
wkawkaI'm new to Yocto and I am getting confused, it is so much to learn there.12:12
*** davidinux <davidinux!~davidinux@> has quit IRC (Ping timeout: 252 seconds)12:22
*** JPEW <JPEW!> has quit IRC (Read error: Connection reset by peer)12:26
*** JPEW <JPEW!> has joined #yocto12:26
*** Ch^W <Ch^W!~mouser@> has quit IRC (Ping timeout: 240 seconds)12:28
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 252 seconds)12:28
*** nemik <nemik!> has joined #yocto12:29
*** Ch^W <Ch^W!~mouser@> has joined #yocto12:29
*** nemik <nemik!> has quit IRC (Ping timeout: 240 seconds)12:33
*** nemik <nemik!~nemik@> has joined #yocto12:34
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 240 seconds)13:03
*** nemik <nemik!> has joined #yocto13:03
*** nemik <nemik!> has quit IRC (Ping timeout: 246 seconds)13:08
*** nemik <nemik!~nemik@> has joined #yocto13:08
*** GillesM <GillesM!> has joined #yocto13:11
*** GillesM <GillesM!> has quit IRC (Client Quit)13:11
*** seninha <seninha!~seninha@user/seninha> has joined #yocto13:12
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Remote host closed the connection)13:13
*** seninha <seninha!~seninha@user/seninha> has joined #yocto13:13
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 256 seconds)13:14
*** nemik <nemik!> has joined #yocto13:14
*** nemik <nemik!> has quit IRC (Ping timeout: 240 seconds)13:18
*** nemik <nemik!~nemik@> has joined #yocto13:19
*** vvn <vvn!> has quit IRC (Quit: WeeChat 3.5)13:19
*** vvn <vvn!> has joined #yocto13:20
*** thomas__ <thomas__!> has quit IRC (Ping timeout: 256 seconds)13:21
dvorkindmitryI have public GIT repo at github. What is 100% correct syntax to use in SRC_URI? I've got error on fetch with SRC_URI="git://;protocol=https;branch=master". Github says something about port that should not be used13:30
qschulzdvorkindmitry: can you actually git clone with https protocol outside of yocto?13:32
dvorkindmitryqschulz, what url should I use for clone to do exactly like Yocto does?13:33
qschulzgit clone I assume13:34
dvorkindmitryno, It says, I need to use publickey13:35
qschulzdvorkindmitry: then you probably need to enable https access on your github repo for this to work13:35
qschulzotherwise, you could use protocol=ssh but you'll likely need to handle different ssh pubkeys and whatnot, usually not the best13:36
qschulzespecially when it's a public git repo13:36
dvorkindmitryqschulz, oh! I made a mistake. When U was clonning like this:13:37
*** xmn <xmn!> has joined #yocto13:37
dvorkindmitrygit clone https://github... it cloned correctly.13:38
dvorkindmitrybut when I try "git clone" It said about the key.13:38
qschulzyeah that's normal13:38
qschulzmaybe bitbake -DDDDDD my-recipe -c fetch -f could give you the exact command that is run13:39
qschulzso you can do it again on your PC locally and check if it works13:40
dvorkindmitrybut my SRC_URI is git://;protocol=https;branch=master; and it looks like it really use the git:// method13:40
rburtonwhat does bitbake actually say?13:40
rburtonguessing the problem from an error we can't see is tricky13:40
*** rob_w <rob_w!> has quit IRC (Quit: Leaving)13:41
dvorkindmitryrburton, give me 5 mins...13:41
Schillerdoes anyone have experience with customizing the from the yocto-controller?13:41
*** leon-anavi <leon-anavi!~Leon@> has quit IRC (Quit: Leaving)13:50
*** otavio <otavio!> has quit IRC (Quit: leaving)13:53
*** otavio <otavio!> has joined #yocto13:53
*** sakoman <sakoman!> has joined #yocto13:55
*** Sukru <Sukru!~Sukru@> has quit IRC (Ping timeout: 252 seconds)13:56
*** pbergin <pbergin!~pbergin@> has quit IRC (Quit: Leaving)13:58
Schillerbasically i just want to add a REVISION to the <branchdefaults> List in the Can't find the right syntax.13:59
*** florian_kc <florian_kc!> has joined #yocto14:00
*** amahnui1 <amahnui1!> has joined #yocto14:11
*** Tyaku <Tyaku!> has joined #yocto14:12
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving)14:14
kayterina[m]I have built three recipes, pyinstaller, altgrapch and pyinstaller-hooks-contrib. There is a pyinstaller executable in WORKDIR/image/usr/bin/pyinstaller . How can I use it in
qschulzkayterina[m]: you need to DEPENDS on pyinstaller-native in my-recipe14:17
qschulzthen simply use pyinstaller directly14:17
*** Schiller <Schiller!> has quit IRC (Ping timeout: 252 seconds)14:17
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 248 seconds)14:18
*** nemik <nemik!> has joined #yocto14:18
*** nemik <nemik!> has quit IRC (Ping timeout: 240 seconds)14:23
*** nemik <nemik!~nemik@> has joined #yocto14:23
*** ptsneves <ptsneves!> has quit IRC (Ping timeout: 252 seconds)14:25
kayterina[m]pyinstaller-native is the one that I made a recipe for,? Because I named it just "pyinstaller" and DEPENDS = "pyinstaller" gives the same error.14:27
dvorkindmitryrburton, Fetcher accessed the network with the command LANG=C git -c core.fsyncobjectfiles=0 clone --bare --mirror "
qschulzkayterina[m]: if you need to run something at build time, it needs to be compiled for the host. That is a native recipe.14:32
qschulzIf you don't need pyinstaller on the target, ever. You can just name your recipe and have an inherit native in there14:32
rburtondvorkindmitry: that's not the whole log, or the real src_uri14:33
dvorkindmitryrburton, yes. Trying to generate good log for you. It is not easy, case I have multiconfig and several recipes that uses private repos with key at ~/.ssh/. If I drop the key from ~/.ssh/, some other recipes stop my build before fetch is done for the target recipe...14:37
*** davidinux <davidinux!~davidinux@> has joined #yocto14:38
qschulzdvorkindmitry: bitbake my-recipe -c fetch -f bypasses all this14:39
dvorkindmitryqschulz, I do like this: bitbake -DDDDDD -c fetch -f mc::myrecipe. (:myarch: is set to default in local.conf) Is it wrong?14:41
dvorkindmitryit try to refetch another recipes, that have no dependency to the target one. and fails case I dropped ssh KEY14:42
*** fitzsim <fitzsim!> has quit IRC (Ping timeout: 240 seconds)14:43
kayterina[m]if I understand correctly,  an inherit native in the recipe does not need a BBCLASSEXTEND = "native"14:44
rburtonkayterina[m]: feel free to share the recipe so we can check it makes sense14:44
rburtonpersonally i'd say use bbclassextend as it's more generic. someone might want a nativesdk version, or a target version.14:45
*** davidinux <davidinux!~davidinux@> has quit IRC (Ping timeout: 248 seconds)14:46
*** davidinux <davidinux!~davidinux@> has joined #yocto14:48
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 252 seconds)14:59
*** nemik <nemik!> has joined #yocto14:59
*** nemik <nemik!> has quit IRC (Ping timeout: 246 seconds)15:03
*** nemik <nemik!~nemik@> has joined #yocto15:04
*** ilunev <ilunev!~koolkhel@> has joined #yocto15:09
ilunevHello! I'm trying to run "devtool modify linux-yocto" in a setup where there's 2 bbappends to the recipe. For some reason, devtool tries to find odroid-kmeta/bsp/odroid-h2/bsp/common-pc-64/common-pc-64-cpu.cfg , all after odroid-h2 being garbage, I think, from generic x86_64 config. Why does it look for kmeta stuff in a recipe folder and why it even attempts to do so? There are 2 kmeta in SRC_URI, machine is odroid-c4.15:11
ilunevah. odroid-h2.scc contains "include bsp/common-pc-64/common-pc-64.scc" but I think it wants to read it from generic linux-yocto kmeta, but there isn't such a file in meta-odroid.15:12
ilunevI guess "MACHINE" is wrong15:13
*** Tyaku <Tyaku!> has quit IRC (Quit: Lost terminal)15:19
*** davidinux <davidinux!~davidinux@> has quit IRC (Ping timeout: 248 seconds)15:21
*** ahs3[m] <ahs3[m]!~ahs3@user/ahs3> has joined #yocto15:21
*** davidinux <davidinux!~davidinux@> has joined #yocto15:23
frayIs there a way to dump the hash equivalency data for a few recipes/tasks?  We're trying to do some valiation that two different builds produced the same contents and this seems to be th eeasiest way for us15:25
*** pgowda_ <pgowda_!> has quit IRC (Quit: Connection closed for inactivity)15:25
dvorkindmitryIf I drop the key from ~/.ssh/ I can't build my target recipe althrough it has no dependency for another private recipes that is used in the image. What would you recommend?15:27
sveinseAre there any ways to restrict/shape the resources for particular recipe when building? E.g. reduce the number of parallell jobs? I have problems building nodejs which is by far the biggest package in my setup, and the linux oom kills the build from time to time requiring me to start over.15:40
rburtonyou can use overrides in local.conf to set PARALLEL_MAKE per-recipe15:42
rburtonor use -l instead of -j, which looks at the load15:42
rburtonassuming gnu make, that is.15:42
rburtonit would be great if all the build tools supported a common way of saying 'spawn up to N threads whilst the system load is less than L', but they don't15:45
rburtongnu make can't even agree in a single build with -j10 not to spawn 10*10 jobs15:46
sveinseyeah, i'm seeing linux loads of 40-80, which is by normal standard extremely high15:46
sveinserburton: I think maybe the issue with make is when you have make->bash->make constructs, where the outer job context isn't passed through the shell layer to the inner make andj job controls goes havok15:48
*** seninha <seninha!~seninha@user/seninha> has joined #yocto15:48
dvorkindmitryrburton, better to see this log15:49
rburtondvorkindmitry: that looks like a successful fetch log15:50
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)15:50
*** davidinux <davidinux!~davidinux@> has quit IRC (Quit: WeeChat 2.8)15:51
dvorkindmitryrburton, yes. an this is strange, case customer says, he has problem during the build:
rburtonthen they're not using the same recipe you are15:53
rburtonas they don't have protocol=https15:53
dvorkindmitryrburton, thank you!15:54
*** davidinux <davidinux!~davidinux@> has joined #yocto15:54
sveinseI normally don't experience gcc and building to be particularely memory intesive. We installed 128G ram in another build server, but linux is using most of it for fs buffering and not for compiling. It's seldom to see gcc consuming more that 1G of mem. In fact putting build/tmp inside tmpfs had a much larger effect than anything else. So even ending up with a tmp tree of 50Gb it doesn't get starved for15:55
sveinseNodejs seems to be the notable exception evidently.15:55
rburtonanything involving JS :)15:56
*** Gambino <Gambino!~textual@user/polo> has joined #yocto16:01
JaMasveinse: depends on what you're building I guess, I can easily trigger OOMK with -j 64 build of chromium; 2G per cpu core is no longer enough for some C++ code16:11
sveinseJaMa: jep. I'm building vanilla nodejs in kirkstone16:12
sveinseEven Qt isn't as heavy16:13
JaMaqtwebengine triggers OOMK as well16:13
sveinseok, that I haven't seen. But I'm building Qt a lot thou16:14
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 252 seconds)16:14
*** nemik <nemik!> has joined #yocto16:15
*** Gambino <Gambino!~textual@user/polo> has quit IRC (Quit: Textual IRC Client:
*** davidinux <davidinux!~davidinux@> has quit IRC (Ping timeout: 252 seconds)16:17
JaManow I'm lowering P_M for webruntime/qtwebengine to about 2/3 cpu threads just to avoid OOMK getting triggered16:18
sveinseHas there been any initatives to look at the parallell tasks vs parallell jobs recently?16:19
JaMait was fine with gcc-10 I think, since 11 it's worse, not sure how much worse 12 (but -j 40 still works with langdale)16:20
sveinseI directed a test a year ago for compiling yocto in azure vm, where I tried many permutations on CPU from 1 through 64 VCPUs to see what gave the most efficient result. I think we landed on that for that setup, approx 16 VCPUs seems to give the best efficiency.16:20
sveinseEfficiency = cost vs time16:21
JaMathe job server and -l was mentioned few times, but I don't remember seeing it recently, I assume it waits for you to volunteer :)16:21
JPEWsveinse: That matches my observations. We build on 16 core 32 GB RAM VMs16:21
JaMait depends highly in what you typically build (and how much sstate you reuse) in my experience16:22
sveinseThe -l can be tricky, as there are so many disparate build systems in the phlethora of different packages we build16:22
sveinseJaMa: yes, we try to maxiumize sstate sharing and reusage. But that test, specifically, were done without any sstate to compete on equal terms.16:23
*** nemik <nemik!> has quit IRC (Ping timeout: 260 seconds)16:24
JaMa16c is nice for "smaller" images, but once chromium gets rebuilt in most of your builds (for whatever reason) then icecc or higher cores really help rebuilding it 1000 times a day16:24
*** nemik <nemik!~nemik@> has joined #yocto16:25
sveinseYocto build is somewhere inbetween being CPU bound and IO bound, not heavy optimization on either doesn't really give that much benefit16:25
JaMabut I'm also biased and spoiled from having 10+, 60+core machines just for my personal builds until recently, building in cloud and paying per-core would force me to do fewer builds :)16:26
sveinseWe needed to reinvest in new server, and at the volume of builds that we're doing (handful a day), our estimates seems to indicate that it will be cheaper to use cloud computing for this rather than investing in new metal. It will have an impact on build times, but that is acceptible.16:28
*** frieder <frieder!> has quit IRC (Remote host closed the connection)16:29
*** davidinux <davidinux!~davidinux@> has joined #yocto16:30
RPsveinse: it does depend a lot on your build. Memory does help and the system is more cpu bound than IO on most systems I've looked at but it does depend on what you build16:32
*** tgamblin <tgamblin!> has joined #yocto16:33
JaMait also depends on how many engineers are blaming slow CI for not being productive :)16:34
sveinseRP: yes. As I mentioned earlier, we added 128G to a server which didn't use it all. Rather putting build/tmp on tmpfs had a much much larger impact on performance, despite the 30G-60G drainage on available memory for builds.16:34
*** davidinux <davidinux!~davidinux@> has quit IRC (Ping timeout: 240 seconds)16:36
*** mckoan is now known as mckoan|away16:37
RPsveinse: you might be able to better tune the filesystem to match the tmpfs fwiw16:37
sveinseRP: what fs do you normally use for build tmps?16:37
JaMabarrier=0 (commit=10000)16:38
*** wkawka <wkawka!> has quit IRC (Quit: Client closed)16:38
*** kevinrowland <kevinrowland!~kevinrowl@> has quit IRC (Quit: Client closed)16:39
RPsveinse: ext416:40
*** ilunev <ilunev!~koolkhel@> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)16:41
RPand noatime16:41
sveinseHow is it with journal, is that impeding performance in high fs activity?16:41
*** gsalazar <gsalazar!> has quit IRC (Ping timeout: 256 seconds)16:42
*** xmn <xmn!> has quit IRC (Ping timeout: 260 seconds)16:52
RPsveinse: I've not found it to be an issue, bigger factors are the commit time and barriers as JaMa mentions16:53
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 240 seconds)16:54
JaMathe biggest pain with long commit is that when you finish a build and then e.g. reboot, the umount takes long time and when it's writting all that data you don't plan to use after the reboot to your precious NVME drive, then tmpfs is better option (especially for builds where you don't plan to use the artifacts for anything and only want to see if it builds OK and maybe the cooker log from it)16:59
JaMaoften I hope that rm_work removed most of the useless data before it got written to actual drive, but tmpfs makes it more explicit that I don't care about that data later17:00
*** Rolle79 <Rolle79!~Rolle79@> has quit IRC (Quit: Client closed)17:05
*** florian_kc <florian_kc!> has joined #yocto17:06
*** Tokamak_ <Tokamak_!~Tokamak@> has quit IRC (Ping timeout: 246 seconds)17:13
*** Tokamak <Tokamak!> has joined #yocto17:17
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 260 seconds)17:20
*** nemik <nemik!~nemik@> has joined #yocto17:20
*** Tokamak_ <Tokamak_!> has joined #yocto17:20
*** Tokamak <Tokamak!> has quit IRC (Ping timeout: 256 seconds)17:22
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 240 seconds)17:29
*** nemik <nemik!> has joined #yocto17:29
*** goliath <goliath!~goliath@user/goliath> has joined #yocto17:35
*** starblue <starblue!> has quit IRC (Ping timeout: 246 seconds)17:36
*** starblue <starblue!> has joined #yocto17:37
*** nemik <nemik!> has quit IRC (Ping timeout: 240 seconds)17:38
*** nemik <nemik!~nemik@> has joined #yocto17:38
*** Telgareith <Telgareith!~Telgareit@user/telgareith> has joined #yocto17:43
Telgareithwhat's a good starting point for yocto for raspberry pi? The only source I can find is a 2016 book, and I imagine things are quite different than then17:44
Telgareithdoes it even have to be raspberry pi, it'd be nice to be able to throw an image into vmware and test it17:45
Telgareithalso, will there be recording of the lectures of the summit?17:49
*** Tokamak_ <Tokamak_!> has quit IRC (Ping timeout: 240 seconds)17:50
jsbronderTelgareith: Following the steps here will get you to an image you can run in qemu.
Telgareithi'm a scrub nub so I kinda need some hand holding to learn the territory, and would prefer a guide of some sort17:52
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto17:52
Telgareithnot a person guide, but tutorial, documentation, etc17:52
Telgareiththanks for the link17:53
Telgareith*embarrased* yea that's the kind of thing I'm looking for17:54
TelgareithI can replace whatever distro layer they use with (I assume) the rasbian version when I want to build my rpi image17:55
Telgareithand probably need to switch bootloader17:55
*** kevinrowland <kevinrowland!~kevinrowl@> has joined #yocto17:57
jsbronderI haven't built for an RPi myself, but once you work through that tutorial you probably will have a better foundation to start reading this one,
*** prabhakarlad <prabhakarlad!> has quit IRC (Quit: Client closed)18:01
Telgareithdream job is giving bonus points for knowing yocto... And I'll probably be the only person who knows what it is nevermind is learning how to use it (I need to learn it for another project anyway)18:05
landgrafTelgareith: you can follow this doc to run kirkstone based distro on rPi418:15
JaMatlwoerner: around?18:19
JaMatlwoerner: can you please fast-forward kirkstone branch to master? the e2fsprogs-native dependency is also needed in kirkstone because of
*** bps <bps!~bps@user/bps> has quit IRC (Ping timeout: 240 seconds)18:22
*** florian <florian!> has quit IRC (Quit: Ex-Chat)18:33
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 240 seconds)18:33
*** nemik <nemik!> has joined #yocto18:34
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 240 seconds)18:36
*** ilunev <ilunev!~koolkhel@> has joined #yocto18:36
*** nemik <nemik!> has quit IRC (Ping timeout: 252 seconds)18:38
*** nemik <nemik!~nemik@> has joined #yocto18:38
*** amahnui1 <amahnui1!> has quit IRC (Quit: Connection closed for inactivity)18:41
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Remote host closed the connection)18:41
moto-timoThis is in a console for a Digital Ocean droplet.18:59
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 276 seconds)19:00
*** nemik <nemik!~nemik@> has joined #yocto19:00
Telgareithdo yocto builds ususally consume very large amounts of ram? I'm on a 16C/32T machine and its currently using 95gb ram19:15
Telgareithrunning from inside WSL219:15
*** bps <bps!> has joined #yocto19:16
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)19:21
*** seninha <seninha!~seninha@user/seninha> has joined #yocto19:24
*** ilunev <ilunev!~koolkhel@> has quit IRC (Read error: Connection reset by peer)19:29
*** ilunev <ilunev!~koolkhel@> has joined #yocto19:34
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 240 seconds)19:39
*** nemik <nemik!> has joined #yocto19:39
*** florian_kc <florian_kc!> has joined #yocto19:40
*** nemik <nemik!> has quit IRC (Ping timeout: 260 seconds)19:44
*** nemik <nemik!~nemik@> has joined #yocto19:44
*** ilunev <ilunev!~koolkhel@> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)19:49
LetoThe2ndTelgareith: sounds about okay, if your box has that amount of ram19:53
Telgareithit does19:53
Telgareithbut the builds over and its still hovering there19:53
LetoThe2ndTelgareith: I guess you're looking at the windows process manager and see WSL2 still taking about that amount, but thats a peculiarity of the hyper-v that underlies WSL219:54
Telgareithah, it's being used by fs buffer19:55
LetoThe2ndTelgareith: once bitbake is over, "yocto" consumes exactly no ram.19:55
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 240 seconds)19:58
*** nemik <nemik!> has joined #yocto19:58
*** nemik <nemik!> has quit IRC (Ping timeout: 240 seconds)20:03
*** nemik <nemik!~nemik@> has joined #yocto20:03
denixLetoThe2nd: are you sure about that? one can never forget "yocto" and it stays in your memory forever!20:07
LetoThe2nddenix: my words were, (as always!) carefully chosen - thats why i used "ram", and not "memory". because my memory is random, but certainly not accessible in a robust way.20:08
* derRichard expected scripts/contrib/ to fix my layer and not to rape it ;-\20:12
derRichardthe script even replaced underscores in shell scripts *grrrr*20:13
LetoThe2ndyeah i've had that effect too at one occasion20:13
RPderRichard: there is a reason we couldn't do it automatically :(20:13
derRichardand it is an implicit dos2unix, it messed up all kind of new lines20:14
RPI didn't realise anyone was using dos newlines in OE metadata so that was never even tested20:14
derRichardRP: you don't work a lot with customers that develop on windows? ;-)20:15
*** florian_kc is now known as florian20:15
derRichardi fear something else broke too :-D20:18
RPderRichard: there is a patch that looks a bit like that I just merged20:18
*** goliath <goliath!~goliath@user/goliath> has joined #yocto20:20
*** fitzsim <fitzsim!> has joined #yocto20:25
JaMaI run dos2unix from time to time, just to teach my co-workers to use linux or at least configure git on windows correctly :)20:27
JaMabut it's rarely an issue with bitbake metadata, the .patch files for our internal components are much worse, e.g. when I forget to use --keep-cr with git am20:28
*** adrian__ <adrian__!~F_Adrian@> has quit IRC (Ping timeout: 252 seconds)20:36
*** guysoft42 <guysoft42!> has quit IRC (Ping timeout: 240 seconds)20:36
derRichardah, "fixed" also an src uri here ;-\20:45
derRichard-SRC_URI = "file://wf111-linux-driver_5.2.2-r1_armv7-a.tar.gz"20:45
derRichard+SRC_URI = "file://wf111-linux-driver_5.2.2-r1:armv7-a.tar.gz"20:45
derRichardand having a colon in a file name is something bitbake/lib/bb/ does not like20:45
*** mvlad <mvlad!~mvlad@2a02:2f08:4114:c500:24d7:51ff:fed6:906d> has quit IRC (Remote host closed the connection)20:45
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Remote host closed the connection)20:46
*** florian <florian!> has quit IRC (Ping timeout: 260 seconds)21:05
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 240 seconds)21:09
*** nemik <nemik!> has joined #yocto21:09
JaMaderRichard: yeah, I had quite a few cases like this as well, I undid them in separate commit so it's easy to re-run the script and then re-fix again21:09
derRichardJaMa: yep. just did so. :-)21:10
derRichardhm, commit ebfa1700f41b ("bitbake: fetch2/cooker: Fix source revision handling with floating upstreams") is also problematic. i have a recipe which uses AUTOREV, it works perfectly fine. but when i try to build it after running devtool modify, bitbake thinks i use floating upstreams21:13
derRichardbitbake foo # works21:13
derRicharddevtool modify foo # hack hack21:13
derRichardbitbake foo # fails21:13
derRichardafter running devtool reset -n foo i can build it again ;-\21:13
*** nemik <nemik!> has quit IRC (Ping timeout: 246 seconds)21:13
*** nemik <nemik!~nemik@> has joined #yocto21:14
*** seninha <seninha!~seninha@user/seninha> has joined #yocto21:36
*** bps <bps!~bps@user/bps> has quit IRC (Ping timeout: 252 seconds)21:46
kevinrowlandHere's a weird one. We've got a `do_install()` task that runs a script that runs a `git` command to find the root of the repository, but the `git` command fails with "fatal: unsafe repository ('...' is owned by someone else)".. so we added one line in `do_install()` to just call `/usr/bin/whoami` and it says `root`! Why is `do_install()` running as21:52
kevinrowlandroot? Is it in a fakeroot? TBH I don't fully understand fakeroot/pseudo21:52
RPkevinrowland: yes, it is run under pseudo which is a fakeroot environment21:53
RPkevinrowland: which release? There are some fixes queued for dunfell/kirkstone21:53
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 252 seconds)21:54
RPkevinrowland: you'll have to port the fixes from one of the other branches then21:54
*** nemik <nemik!> has joined #yocto21:54
kevinrowlandCool, thanks for responding. Seems like an intermittent issue though, I haven't been able to repro and it only reared its head on another dev's machine and only after we moved some layers around21:56
RPkevinrowland: it depends whether git has a CVE fix backported to it or is a very recent version21:58
*** nemik <nemik!> has quit IRC (Ping timeout: 246 seconds)21:58
*** nemik <nemik!~nemik@> has joined #yocto21:59
*** peoliye <peoliye!~peoliye@> has joined #yocto22:02
*** JaMa <JaMa!> has quit IRC (Ping timeout: 240 seconds)22:18
*** JaMa <JaMa!> has joined #yocto22:23
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Ping timeout: 276 seconds)22:30
*** seninha <seninha!~seninha@user/seninha> has joined #yocto22:50
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Client Quit)22:52
*** seninha <seninha!~seninha@user/seninha> has joined #yocto22:56
paulgRP, ha ha - you aren't the only one trying to suck me back in time to powerpc serial crap!
RPpaulg: nice. Still don't know what to do with ppc in yocto :/23:12
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Ping timeout: 246 seconds)23:23
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto23:31
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)23:43
*** Starfoxxes <Starfoxxes!~Starfoxxe@2a02:8070:5390:d00:12bf:48ff:feb8:38c8> has quit IRC (Ping timeout: 248 seconds)23:52
*** Starfoxxes <Starfoxxes!~Starfoxxe@2a02:8070:5390:d00:12bf:48ff:feb8:38c8> has joined #yocto23:53
denixkevinrowland: hitting this?

Generated by 2.17.2 by Marius Gedminas - find it at!