Friday, 2020-12-18

kiwi_29what is the standard practice in this case, is it ok to have two bbappend in repo and expect the developer to put BB_DANGLINGAPPENDS_WARNONLY = "1" in his/her repo?00:00
*** rcw <rcw!~rcwoolley@> has quit IRC00:02
*** rcw <rcw!~rcwoolley@> has joined #yocto00:02
*** oberstet <oberstet!~oberstet@> has quit IRC00:03
*** B0ned1ger <B0ned1ger!> has joined #yocto00:09
*** B0ned1ger <B0ned1ger!> has quit IRC00:13
*** goliath <goliath!> has quit IRC00:35
*** kiwi_29 <kiwi_29!> has quit IRC00:40
*** kiwi_29 <kiwi_29!> has joined #yocto00:43
*** B0ned1ger <B0ned1ger!> has joined #yocto00:48
*** B0ned1ger <B0ned1ger!> has quit IRC00:53
*** kiwi_29 <kiwi_29!> has quit IRC00:55
*** gtucker <gtucker!gtucker@nat/collabora/x-ptfvlkivmhjrnlyy> has quit IRC00:57
*** gtucker <gtucker!gtucker@nat/collabora/x-yuaisvjkdtcyvopu> has joined #yocto00:58
*** kiwi_29 <kiwi_29!> has joined #yocto01:02
*** moto-timo <moto-timo!~ttorling@fsf/member/moto-timo> has quit IRC01:12
*** moto-timo <moto-timo!> has joined #yocto01:24
*** moto-timo <moto-timo!~ttorling@fsf/member/moto-timo> has joined #yocto01:24
moto-timothis system's power button is just a wee bit too close to the USB ports and ... yeah... I totally meant to reboot...01:33
moto-timoI suppose there was probably a kernel update waiting anyway...01:33
* moto-timo looks at the bright side01:33
*** vineela <vineela!vtummala@nat/intel/x-mzcdelpibkyqztjj> has quit IRC01:37
*** kiwi_29 <kiwi_29!> has quit IRC01:53
tlwoernermoto-timo: there are no other sides01:56
*** kiwi_29 <kiwi_29!> has joined #yocto01:58
*** kiwi_29 <kiwi_29!> has quit IRC02:01
*** kiwi_29 <kiwi_29!> has joined #yocto02:02
*** kaspter <kaspter!~Instantbi@> has joined #yocto02:05
*** kiwi_29 <kiwi_29!> has quit IRC02:07
*** kiwi_29 <kiwi_29!> has joined #yocto02:07
*** rcw <rcw!~rcwoolley@> has quit IRC02:13
*** kiwi_29 <kiwi_29!> has quit IRC02:13
*** kiwi_29 <kiwi_29!> has joined #yocto02:14
kergothkiwi_29: best practice is to have separate branches that align with upstream without having to use danglingappends_warnonly. and naturally make sure that all the layres you're using have matching branches checked out02:43
*** ericch <ericch!> has quit IRC02:44
*** B0ned1ger <B0ned1ger!> has joined #yocto02:49
*** roussinm <roussinm!> has quit IRC02:49
*** B0ned1ger <B0ned1ger!> has quit IRC02:53
*** sakoman <sakoman!> has quit IRC03:05
*** sakoman <sakoman!> has joined #yocto03:26
*** sakoman <sakoman!> has quit IRC03:29
*** kaspter <kaspter!~Instantbi@> has quit IRC03:47
*** kaspter <kaspter!~Instantbi@> has joined #yocto03:47
*** kiwi_29 <kiwi_29!> has quit IRC04:13
*** Ad0 <Ad0!~Ad0@> has quit IRC04:42
*** armpit <armpit!~armpit@2601:202:4180:a5c0:340d:313d:cd08:87ee> has quit IRC04:48
*** Ad0 <Ad0!~Ad0@> has joined #yocto04:48
*** B0ned1ger <B0ned1ger!> has joined #yocto04:50
*** B0ned1ger <B0ned1ger!> has quit IRC04:54
*** armpit <armpit!~armpit@2601:202:4180:a5c0:6c0e:4e8:e4b3:302f> has joined #yocto05:00
*** kaspter <kaspter!~Instantbi@> has quit IRC05:08
*** kaspter <kaspter!~Instantbi@> has joined #yocto05:08
*** Emantor <Emantor!> has quit IRC05:32
*** georgem_home <georgem_home!uid210681@gateway/web/> has quit IRC05:33
*** Emantor <Emantor!> has joined #yocto05:34
*** jobroe <jobroe!> has joined #yocto06:12
*** kiwi_29 <kiwi_29!> has joined #yocto06:13
*** kaspter <kaspter!~Instantbi@> has quit IRC06:14
*** kaspter <kaspter!~Instantbi@> has joined #yocto06:14
*** kiwi_29 <kiwi_29!> has quit IRC06:19
*** thomas_dee <thomas_dee!91fdde45@> has joined #yocto06:26
thomas_deeHi everyone, I'd like to include mkimage into my built image. Does anyone know what recipe to use for that?06:27
*** alessioigor <alessioigor!> has joined #yocto06:30
*** AndersD <AndersD!> has joined #yocto06:39
*** AndersD_ <AndersD_!> has joined #yocto06:41
*** jobroe_ <jobroe_!> has joined #yocto06:42
*** jobroe <jobroe!> has quit IRC06:43
*** AndersD <AndersD!> has quit IRC06:44
*** beneth <beneth!> has joined #yocto06:45
*** B0ned1ger <B0ned1ger!> has joined #yocto06:51
*** B0ned1ger <B0ned1ger!> has joined #yocto06:52
*** minimaxwell <minimaxwell!> has joined #yocto06:55
*** minimaxw1ll <minimaxw1ll!> has joined #yocto06:55
*** minimaxwell <minimaxwell!> has quit IRC06:55
*** minimaxwell <minimaxwell!> has joined #yocto06:56
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has joined #yocto07:04
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto07:09
*** ssajal <ssajal!> has quit IRC07:15
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has joined #yocto07:16
*** zyga <zyga!> has quit IRC07:20
thomas_deeHi everyone, I'd like to include mkimage into my built image. Does anyone know what recipe to use for that?07:21
*** zyga <zyga!> has joined #yocto07:21
*** amitk <amitk!~amit@unaffiliated/amitk> has joined #yocto07:27
LetoThe2ndthomas_dee: probably someting u-boot-ish07:30
LetoThe2ndthomas_dee: but, pardon the remark - wanting to have that sounds strange ar least. care to elaborate why you want that?07:30
*** Shikadi <Shikadi!> has quit IRC07:31
*** frwol <frwol!> has joined #yocto07:32
*** mckoan|away is now known as mckoan07:43
mckoangood morning07:43
*** zyga <zyga!> has quit IRC07:44
*** zyga <zyga!> has joined #yocto07:45
*** zyga <zyga!> has quit IRC07:46
*** zyga <zyga!> has joined #yocto07:49
*** gsalazar <gsalazar!955a6fad@gateway/web/cgi-irc/> has joined #yocto07:51
thomas_deeLetoThe2nd Thanks for hint. We are just thinking about our options for controlling the boot process. So we'd like to create a boot.scr on the fly. And for that we obviously need mkimage07:51
LetoThe2ndthat sounds extremely problematic. to say the least.07:54
LetoThe2ndi would strongly suggest to rather try and find a way where a standard boot script can react to the situation and fall back to a sensible default.07:55
*** alessioigor <alessioigor!> has quit IRC07:55
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto08:01
*** wz <wz!> has joined #yocto08:02
*** mbulut <mbulut!> has joined #yocto08:45
*** creich <creich!> has quit IRC09:12
*** creich <creich!> has joined #yocto09:12
*** creich <creich!> has quit IRC09:17
*** creich <creich!> has joined #yocto09:17
*** crawler <crawler!> has quit IRC09:19
*** crawler <crawler!> has joined #yocto09:20
*** amitk_ <amitk_!~amit@unaffiliated/amitk> has joined #yocto09:37
*** xtron <xtron!~xtron@> has joined #yocto09:37
*** tnovotny <tnovotny!> has joined #yocto09:40
*** amitk <amitk!~amit@unaffiliated/amitk> has quit IRC09:40
qschulzthomas_dee: don't know about scr scripts but one way to achieve controlling the boot process is having your scenarios in different u-boot env variables and execute one depending on another variable in the u-boot env09:41
qschulzthis variable can be imported from the same env or another (look up `env import` command). The environment can be modified from Linux with fw_setenv available in libubootenv IIRC (u-boot-fw-utils previously IIRC)09:42
*** fl0v0 <fl0v0!> has joined #yocto09:50
LetoThe2ndyeah. another option is to outright use a patched u-boot that has board/device specific commands to get information.09:55
qschulzdoes not work well for upgrade scenarios (A/B or recovery), but yes, possible too09:56
qschulzLetoThe2nd: 3rd Yocto chant: "It dependsTM"09:57
LetoThe2ndqschulz: exactly.09:57
RPdsueiro: Just looking at that u-boot /boot change, I'm wondering if we're going to confuse users by having both the deploy dir and the sysroot...09:59
qschulzRP: I'm not sure it's the right move honestly10:03
qschulzthough I'm having a hard time understanding what should be available in SYSROOT_DIRS and what should be available in DEPLOYDIR10:04
RPqschulz: I can see the need. sysroot was supposed to be for "inter-recipe" sharing and deploy for the final result10:05
RPthen recipes learnt to go fishing in deploy10:05
qschulzand then "we" "recommend" it?10:05
RPwell, there wasn't really an alternative for some things10:05
RPif you want an image for example, we never put those in sysroots10:06
qschulzI mean, I always applied that "non-lib, non-header fies should be shared through DEPLOYDIR" but don't know if it's a good rule though10:06
qschulzRP: true... let's not tell people that you can have DEPENDS in image recipes though :p10:06
RPMy own metric is more about whether the end user would consume it...10:06
RPqschulz: there is a long list of things I don't make widely known :)10:07
qschulzyet it seems my company is very good at finding those :p10:07
RPqschulz: hard to tell when I don't talk about them ;-)10:08
qschulzRP: keep your secrets then10:09
qschulz(meme reference)10:10
*** ebail <ebail!> has joined #yocto10:28
ebailHi guys. I am wondering if someone already tried to package Cuda for a x86_64 target with NVidia GPU (the meta-tegra should not be suitable)10:30
*** frwol <frwol!> has quit IRC10:34
*** frwol <frwol!> has joined #yocto10:35
*** xtron <xtron!~xtron@> has quit IRC10:36
*** xtron <xtron!~xtron@> has joined #yocto10:37
LetoThe2ndebail: i would start out with meta-tegra anyways and start beating it into shape.10:38
*** oberstet <oberstet!~oberstet@> has joined #yocto10:42
*** dreyna <dreyna!~dreyna@2601:646:4201:e280:2c20:b041:c753:abd> has quit IRC10:43
ebailYep LetoThe2nd, I think so. I would need to tune COMPATIBLE_MACHINE. I am wondering why meta-tegra was not split into several layers to make SW packaging HW-independant.10:44
LetoThe2ndebail: just ask matt, he's a nice  guy :)10:45
ebailLetoThe2nd: sure. is he on #yocto ?10:46
LetoThe2ndebail: not sure. and if, then probably not until US daytimes.10:48
ebailok LetoThe2nd I will contact him on GH. Thanks for your help10:48
LetoThe2ndhave fun!10:49
qschulzebail: technically you could also add one of tegra's machine into your machine's MACHINEOVERRIDES if it makes sense10:51
qschulzat least that's a good way to start without too many bbappends at once (great to get started, and might even make sense in some cases)10:51
*** xtron <xtron!~xtron@> has quit IRC10:52
ebailyes qschulz that's a good way to test it.10:53
*** goliath <goliath!> has joined #yocto11:06
*** thomas_dee <thomas_dee!91fdde45@> has quit IRC11:19
*** ebail <ebail!> has quit IRC11:38
*** lxc <lxc!> has joined #yocto11:41
*** pbb <pbb!> has quit IRC11:42
*** pbb <pbb!> has joined #yocto11:43
*** ebail <ebail!> has joined #yocto11:51
*** alephan <alephan!andreicubi@gateway/shell/> has joined #yocto11:56
*** guest1231231 <guest1231231!b9b04ce0@> has joined #yocto11:58
alephanHi guys. Long time no IRC.12:00
*** mbulut <mbulut!> has quit IRC12:01
qschulzhello there12:02
alephanfray: I have a question for you. You took care of the shared downloads (sources mirror) strategy in WRS. Can you give me a short overview on how you designed that process? I'm taking this from the traceability and regression point of view so I'm wondering if you were also doing freezing of the mirror per release (not only the build metadata).12:06
*** guest1231231 <guest1231231!b9b04ce0@> has quit IRC12:07
lxcAnyone that have success in using nativesdk-gcc? When I include this in the SDK the sysroot does not get correct when the linker is invoked.12:18
*** hipr_c <hipr_c!> has joined #yocto12:24
madisoxebail: The CUDA support could be split out from meta-tegra and extended to handle x86 targets.  There was some discussion of it a few years ago.12:25
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC12:29
ebailmadisox: good point. I will check this out12:31
*** madisox <madisox!sid453692@gateway/web/> has quit IRC12:34
*** madisox <madisox!sid453692@gateway/web/> has joined #yocto12:34
*** kaspter <kaspter!~Instantbi@> has quit IRC12:35
*** mbulut <mbulut!> has joined #yocto12:55
ebailmadisox: I read your GH link. So I guess it is not recommended to start from meta-nvidia which seems outdated. The best would be to split meta-tegra, right ?13:07
ebailmadisox: did you also have some experience using meta-tegra with PREEMPT_RT full ?13:08
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC13:09
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto13:10
*** agrue <agrue!> has quit IRC13:13
*** sno <sno!> has quit IRC13:15
*** marka <marka!> has quit IRC13:31
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC13:32
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto13:34
*** marka <marka!> has joined #yocto13:36
*** radsquirrel <radsquirrel!~radsquirr@> has quit IRC13:42
*** radsquirrel <radsquirrel!~radsquirr@2603:3015:e15:5bf2:d0b3:d9ff:fede:b022> has joined #yocto13:46
*** andersonJ <andersonJ!> has joined #yocto13:49
*** amitk_ is now known as amitk13:50
*** georgem_home <georgem_home!uid210681@gateway/web/> has joined #yocto13:52
*** sakoman <sakoman!> has joined #yocto13:54
*** hpsy <hpsy!~hpsy@> has joined #yocto13:59
*** radsquirrel <radsquirrel!~radsquirr@2603:3015:e15:5bf2:d0b3:d9ff:fede:b022> has quit IRC14:03
*** radsquirrel <radsquirrel!~radsquirr@> has joined #yocto14:05
*** jobroe_ <jobroe_!> has quit IRC14:06
*** mace_ <mace_!> has joined #yocto14:12
*** hpsy <hpsy!~hpsy@> has quit IRC14:20
RPkanavin_home: I've sent a patch to bitbake-devel for that os-release issue14:26
*** andersonJ <andersonJ!> has quit IRC14:29
*** Anarky <Anarky!> has joined #yocto14:32
AnarkyHello, I have an issue where the RDEPENDS files of a recipe are not inside the sysroot that DEPENDS on this recipe14:33
AnarkyI have created a post on stackoverflow earlier to better explain things:
qschulzAnarky: you cannot RDEPENDS on a native recipe, that does not make sense14:37
qschulza native recipe is for the host, where you build stuff. You want a target package (without -native) for packages installed in your rootfs14:37
qschulzthat's one issue, reading your post more carefully now14:38
Anarkyqschulz: the "composer" recipe is not supposed to go on my system14:39
qschulzAnarky: which version of Yocto are you using?14:39
*** mace_ <mace_!> has quit IRC14:40
qschulzRDEPENDS for native packages have only been recently added14:40
Anarkybut to build "myserver", which will go on my target, I need to run "php composer.phar composer.lock" on my system14:40
Anarkyright now I'm stuck on thud14:40
qschulzalso... not sure RDEPENDS for native packages is correct14:40
qschulzok, so RDEPENDS in your composer-native won't work14:40
qschulzjust put DEPENDS = "php-native" instead14:41
Anarkyqschulz: on the last version, RDEPENDS is more correct right?14:46
qschulzAnarky: I do not know. Because technically, you're pulling composer-native with DEPENDS and not RDEPENDS14:49
qschulzI don't have much experience with native RDEPENDS, specifically because I'm using thud like you and it isn't supported14:50
qschulzRDEPENDS on native packages*14:50
Anarkyqschulz: the issue is the same with a DEPENDS on composer-native14:51
Anarkyeven after a cleanall, when I build "myserver" it can't find "usr/bin/php" during the compile14:52
Anarkyoh wait :/14:52
Anarkyqschulz: you're right, it works perfectly now, thanks!14:54
Anarkydo you know which version adds the RDEPENDS support for native package? I might be able to update in the future14:55
qschulzAnarky: still I'm not sure it is supposed to work the way you intend to14:56
kanavin_homeRP: thanks! it's crucial for keeping AUH running and not falling behind on version updates :)14:56
RPkanavin_home: if you could confirm it helps, that would be useful14:57
kanavin_homeRP: I guess once it merges, I can re-start AUH builder?14:59
kanavin_homeor is there a way to run AUH against master-next maybe?14:59
RPkanavin_home: I think you could just set the branch to master-next one I add it there?15:00
kanavin_homeRP: yes I can15:05
smurrayAnarky qschulz: if a tool is needed at build time, it should be in DEPENDS as -native.  RDEPENDS on -native packages should really only be needed by other native recipes15:07
*** ericch <ericch!> has joined #yocto15:11
Anarkysmurray: so it's a normal behaviour the problem I had?15:11
qschulzsmurray: the question is when RDEPENDS on native packages make sense? in image recipes?15:17
smurrayqschulz: when something that is native needs another native tool to run, if you grep in oe-core / poky, you'll see there are not many instances15:19
smurrayAnarky: yes15:19
*** kanavin_home <kanavin_home!~ak@2a02:2450:1011:4f7:596d:bf31:3950:5bda> has quit IRC15:25
qschulzAh, like a native recipe which is a bash script calling another binary I guess, no need at build time obviously15:30
Anarkysmurray: but in my case, php-native was needed at runtime for composer-native, so why I couldn't use php during the compile task on my recipe that DEPENDS on composer-native?15:32
*** ssajal <ssajal!> has joined #yocto15:34
smurrayAnarky: if composer-native needs php-native, then adding the RDEPENDS_${PN}_class-native = "php-native" to the composer recipe would perhaps make sense15:34
smurrayAnarky: that is the usecase I mentioned ("RDEPENDS on -native packages should really only be needed by other native recipes")15:35
zeddiiRP: a few warnings (fixed), and of course stap failure on 5.10 run v1. I guess I'll end up doing that uprev after all ;)15:37
smurrayAnarky: though that depends a bit on your composer recipe, if it's intended for both target and native, it should just have RDEPENDS_${PN} = "php" and I think wouldn't need anything else if it uses BBCLASSEXTEND = "native"15:39
RPzeddii: I guess it could be worse!15:39
zeddiiindeed. or just the obvious ones could be worse. We'll see how more runtime tests behave.15:40
*** roussinm <roussinm!> has joined #yocto15:40
Anarkysmurray: composer is only native, to build the target recipe "myserver"15:41
Anarkysmurray: right now it's called "" with "inherit native" inside15:41
*** armpit <armpit!~armpit@2601:202:4180:a5c0:6c0e:4e8:e4b3:302f> has quit IRC15:41
smurrayAnarky: okay, likely you want RDEPENDS_${PN}_class-native = "php-native"15:41
Anarkysmurray: thanks I try right now15:42
*** armpit <armpit!~armpit@2601:202:4180:a5c0:6c0e:4e8:e4b3:302f> has joined #yocto15:42
*** B0ned1ger <B0ned1ger!> has quit IRC15:43
qschulzsmurray: why the class-native override? it's a native only recipe, so it shouldn't be needed right?15:44
*** amitk_ <amitk_!~amit@unaffiliated/amitk> has joined #yocto15:44
*** kanavin_home <kanavin_home!~ak@2a02:2450:1011:4f7:596d:bf31:3950:5bda> has joined #yocto15:44
smurrayqschulz: yeah, I'm not 100% sure, it might be okay w/o it when using native.bbclass15:44
Anarkysmurray: it doesn't work, is it because it's only "inherit native" instead of BBCLASSEXTEND?15:45
smurrayAnarky: looking at native.bbclass, I think you can just use RDEPENDS there15:47
*** amitk <amitk!~amit@unaffiliated/amitk> has quit IRC15:47
smurrayAnarky: if that doesn't result in php-native getting pulled in, I think you'll need to stick with explicitly putting it in DEPENDS15:48
Anarkysmurray: it's what I had on the first place:
qschulzsmurray: also, Anarky is on thud and RDEPENDS on native packages is *NOT* supported in thud15:53
smurrayqschulz: ah15:54
smurrayAnarky: I think you're likely stuck with the explicit DEPENDS, but it's entirely possible I'm missing something15:55
qschulzAnarky: warrior has support according to the release note15:55
*** AndersD_ <AndersD_!> has quit IRC15:55
*** mihai <mihai!~mihai@unaffiliated/mihai> has joined #yocto16:06
*** Konsgn <Konsgn!> has joined #yocto16:14
*** Konsgn <Konsgn!~Konsgnx3@unafiliated/joyseph> has joined #yocto16:14
*** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@> has joined #yocto16:14
*** dakhouya <dakhouya!> has joined #yocto16:25
*** mbulut <mbulut!> has quit IRC16:28
*** sno <sno!> has joined #yocto16:34
*** gsalazar <gsalazar!955a6fad@gateway/web/cgi-irc/> has quit IRC16:35
*** ByteLawd <ByteLawd!extor@unaffiliated/extor> has quit IRC16:37
*** ByteLawd <ByteLawd!extor@unaffiliated/extor> has joined #yocto16:37
khemzeddii:  I am seeing selftest build failures with 5.8 and also with -dev ( 5.10 ) version its same error
khemzeddii:  any ideas ? before I dig16:49
*** pharaon2502 <pharaon2502!> has quit IRC16:51
*** ebail <ebail!> has quit IRC16:51
*** pharaon2502 <pharaon2502!> has joined #yocto16:51
*** ebail <ebail!> has joined #yocto16:52
*** ebail <ebail!> has joined #yocto16:52
zeddiihmm. 5.8 is static in versions, since it is EOL, or I would have suspected my recent version bumps.  I don't have any config changes for 5.8 either. 5.10, could just be the new kernel, I just started running the full uprev through the AB, so I haven't seen all the issues yet.16:52
hipr_cWhile trying to use meta-st-stmp32 BSP layer I'm encountering "/path/ has circular dependency on /path/". Any pointers for a beginner on how to resolve this?16:55
*** frwol <frwol!> has quit IRC17:01
*** ebail <ebail!> has quit IRC17:12
*** fl0v0 <fl0v0!> has quit IRC17:15
*** JaBen <JaBen!~Thunderbi@2a02:8109:86c0:1c58:bd52:f0ef:80f0:e69e> has joined #yocto17:19
*** Shikadi` <Shikadi`!> has joined #yocto17:19
v0nhow can I remove -MACHINE from the image file names?17:31
*** dreyna <dreyna!> has joined #yocto17:32
v0nIt seems redundant since images are already in a deploy/images/MACHINE/ folder and having just core-image-minimal.wic for example would simplify the documentation (especially when multiple machine are involved)17:32
*** falk0n <falk0n!> has quit IRC17:32
*** rcrudo <rcrudo!~rcrudo@2001:16b8:c2f4:c300:9e7c:d8df:f37:e6cb> has joined #yocto17:33
*** falk0n <falk0n!> has joined #yocto17:33
*** vineela <vineela!~vtummala@> has joined #yocto17:34
v0nI mean the link core-image-minimal.wic for example, not the ${IMAGE_BASENAME}-${MACHINE}-${DATETIME}.wic file it points to.17:35
AnarkyAnother question, how can I enable the openssl extension when I use the native php binary?17:38
*** dakhouya <dakhouya!> has quit IRC17:44
*** mckoan is now known as mckoan|away17:52
v0nI would like build/tmp/deploy/images/MACHINE/core-image-minimal.wic -> core-image-minimal-MACHINE-20201217202436.rootfs.wic (instead of core-image-minimal-MACHINE.wic)17:55
*** minimaxwell <minimaxwell!> has quit IRC17:56
*** zyga <zyga!> has quit IRC18:04
*** falk0n_ <falk0n_!> has joined #yocto18:05
zeddiiRP: I have a fix for the systemtap uprev, and for it on 5.10, but the damn thin oom's on my qemux86-64 run on the default setting (systemd init). So we may start running into memory limits again.18:06
kergothv0n: you can set any of those in your recipe or distro or whatever18:07
*** falk0n <falk0n!> has quit IRC18:08
v0nkergoth: thanks! I was unfortunately looking at (which has no occurrence of IMAGE_LINK_NAME) instead of
*** agrue <agrue!> has joined #yocto18:12
* v0n updates his new best friend helper to: yvar () { for var; do firefox "$var"; done; exec swaymsg -q '[urgent="newest"] focus' ; }18:14
*** zyga <zyga!> has joined #yocto18:16
*** agrue <agrue!> has quit IRC18:17
*** vineela <vineela!~vtummala@> has quit IRC18:18
RPzeddii: that sounds like fun :(18:18
zeddiibooting with qemuparams="-m 2048" fixes it up.18:18
zeddiiI'll put the fix for stap on my test branch and see if the AB runs see the oom.18:19
RPzeddii: an init system needs 2GB of memory though? :(18:25
zeddiiI'll try some lower values, that's my goto bump when things oom :D18:26
*** tnovotny <tnovotny!> has quit IRC18:26
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has quit IRC18:27
*** JaMa <JaMa!> has quit IRC18:40
*** agrue <agrue!> has joined #yocto18:46
v0nkergoth: works beautifully, thanks18:55
*** zkrx <zkrx!> has quit IRC18:58
*** Shikadi` <Shikadi`!> has quit IRC18:59
*** zkrx <zkrx!> has joined #yocto19:08
*** amitk_ <amitk_!~amit@unaffiliated/amitk> has quit IRC19:10
*** vineela <vineela!~vtummala@> has joined #yocto19:11
*** zkrx <zkrx!> has quit IRC19:14
khemzeddii: systemd now has oom daemon, are you enabling it ?19:17
*** agrue <agrue!> has quit IRC19:17
*** zkrx <zkrx!> has joined #yocto19:18
zeddiikhem: I'm just taking the defaults of current master, so probably not.19:20
*** zkrx <zkrx!> has quit IRC19:25
*** zkrx <zkrx!> has joined #yocto19:29
*** zkrx <zkrx!> has quit IRC19:31
*** zkrx <zkrx!> has joined #yocto19:37
*** wz <wz!> has quit IRC19:50
*** zkrx <zkrx!> has quit IRC19:53
*** Bunio_FH <Bunio_FH!> has quit IRC20:06
*** zkrx <zkrx!> has joined #yocto20:19
*** Bunio_FH <Bunio_FH!> has joined #yocto20:21
*** zkrx <zkrx!> has quit IRC20:22
*** zkrx <zkrx!> has joined #yocto20:26
*** zkrx <zkrx!> has quit IRC20:27
*** Bunio_FH <Bunio_FH!> has quit IRC20:36
*** zkrx <zkrx!> has joined #yocto20:39
JPEWtlwoerner: Hmm, I have to enable a few kernel configs for the Rock Pi X, which probably means it should have it's own machine. Any suggestions for where it should live?20:41
*** hipr_c <hipr_c!> has quit IRC20:45
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC20:48
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto20:49
*** zkrx <zkrx!> has quit IRC20:50
*** zkrx <zkrx!> has joined #yocto20:55
*** Bunio_FH <Bunio_FH!> has joined #yocto20:59
tlwoernerJPEW: not in meta-rockchip :-)21:00
tlwoernerisn't the X an x86-based MACHINE?21:00
tlwoernerJPEW: if they're generic enough maybe they could be added to ?21:03
*** georgem_home <georgem_home!uid210681@gateway/web/> has quit IRC21:03
*** vineela <vineela!~vtummala@> has quit IRC21:04
tlwoernermaybe bsp/intel-x86 or bsp/intel-common21:04
tlwoerneror bsp/rock-pi-x21:05
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has quit IRC21:11
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has joined #yocto21:22
*** pharaon2502 <pharaon2502!> has quit IRC21:22
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has quit IRC21:28
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has quit IRC21:44
*** vineela <vineela!~vtummala@> has joined #yocto21:56
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has joined #yocto21:57
*** Konsgn <Konsgn!~Konsgnx3@unafiliated/joyseph> has quit IRC21:59
*** Hauke <Hauke!~weechat@2a01:4f8:c0c:80d9::1> has quit IRC22:02
*** Hauke <Hauke!~weechat@2a01:4f8:c0c:80d9::1> has joined #yocto22:04
v0nwhen creating your own distribution, is it better to stick to core-image-* if possible?22:07
*** bernardoaraujo <bernardoaraujo!uid179602@gateway/web/> has joined #yocto22:11
v0nI think meta-raspberrypi got rid of their custom images in favor of core-image-*22:14
paulgwell, that is kind of useless.  The mailing list archiver obscures e-mail addresses in body text, even if they are a part of an URL....22:17
paulgso all links to anything to do with any list on official archiver "lore" get turned into garbage.22:18
paulglink is truncated because it looks like an e-mail addy.22:18
paulgShould be:
paulgnot sure how one would fix that, but trashing any and all links to the millions of posts archived on lore is...  well, rather "not good".22:20
paulgAt least it seems like the copy that list subscribers got directly was not mangled.22:23
v0nso is it fine for a distro to append IMAGE_INSTALL or CORE_IMAGE_EXTRA_INSTALL or should it define its own <distro>-image-*?22:23
v0nI'm struggling to understand weither it's ok or not to extend the standard image22:24
*** xicopitz[m] <xicopitz[m]!xicopitzma@gateway/shell/> has joined #yocto22:26
RPv0n: defining new images is pretty inexpensive. As a distro you can redefine the core it you need/want too22:28
RPpaulg: I'd mention that to halstead22:29
halsteadpaulg: that certainly seems to be an undesired side effect. I'll raise a bug22:31
paulghalstead, awesome - thanks!22:33
*** falk0n_ <falk0n_!> has quit IRC22:35
*** falk0n <falk0n!> has joined #yocto22:35
v0nRP: in other words, if you fetch a distro layer, do you expect to build core-image-minimal and flash it on your board or do you expect custom distro images?22:42
v0nlike if I want the "dev" image to have u-boot configured to tftpboot my kernel+initramfs, should I create a custom image recipe or should I extend core-image-minimal-dev or core-image-initramfs for example?22:44
JPEWv0n: Create a new image most likely22:44
*** vineela <vineela!~vtummala@> has quit IRC22:46
*** vineela <vineela!~vtummala@> has joined #yocto22:47
v0nok I think I get it. For BSP layer, you expect "core-image-*" to boot and just work.22:52
v0nFor distro layers, you certainly expect custom image targets since distro have their own flavors, packages and stuffs and thus "core-image-*" don't make much sense here I guess.22:53
RPright, I'd agree with that22:53
v0nwell Poky isn't a good example of this but it is a reference distro after all22:58
v0nlike if there was a meta-ubuntu distro layer, the instructions would be "bitbake ubuntu" or "bitbake ubuntu-dev" I imagine.22:59
RPv0n: that is true!23:09
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC23:16
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto23:18
*** leon-anavi <leon-anavi!~Leon@> has quit IRC23:25
RPzeddii: there was a warning with your latest patchset on poky-tiny:
RP(that is with master-next)23:27
*** sakoman <sakoman!> has quit IRC23:29
*** falk0n <falk0n!> has quit IRC23:34
halsteadThe bug is files thanks you paulg :)23:36
*** wz <wz!> has joined #yocto23:37
*** falk0n <falk0n!> has joined #yocto23:45

Generated by 2.17.2 by Marius Gedminas - find it at!