Tuesday, 2021-02-23

*** imcleod_ <imcleod_!~imcleod@2601:249:8200:1ba1:af65:6e6f:10d:e757> has joined #yocto00:00
*** ByteLawd <ByteLawd!extor@unaffiliated/extor> has quit IRC00:00
*** ByteLawd <ByteLawd!extor@unaffiliated/extor> has joined #yocto00:00
*** RzR <RzR!~rzr@78.197.125.113> has joined #yocto00:01
*** Shikadi` <Shikadi`!~Shikadi@136-27-89-140.cab.webpass.net> has joined #yocto00:07
*** linums <linums!~linums@84.198.214.27> has quit IRC00:11
*** linums <linums!~linums@apn-94-44-114-128.vodafone.hu> has joined #yocto00:12
*** linums <linums!~linums@apn-94-44-114-128.vodafone.hu> has quit IRC00:23
paulgnever underestimate the magic of "nuke and pave".00:23
*** blauskaerm <blauskaerm!blauskaerm@gateway/vpn/mullvad/blauskaerm> has quit IRC00:24
*** camus <camus!~Instantbi@58.246.136.202> has joined #yocto00:24
*** kaspter <kaspter!~Instantbi@58.246.136.202> has quit IRC00:25
*** camus is now known as kaspter00:25
*** blauskaerm <blauskaerm!blauskaerm@gateway/vpn/mullvad/blauskaerm> has joined #yocto00:25
*** linums <linums!~linums@apn-94-44-99-170.vodafone.hu> has joined #yocto00:25
*** OnkelUlla <OnkelUlla!~uol@ptx.hi.pengutronix.de> has quit IRC00:33
*** shoragan <shoragan!~shoragan@debian/developer/shoragan> has quit IRC00:33
*** mrpelotazo <mrpelotazo!~mrpelotaz@HSI-KBW-109-192-067-084.hsi6.kabel-badenwuerttemberg.de> has joined #yocto00:35
*** kvpnet <kvpnet!ccf6a226@204.246.162.38> has joined #yocto00:37
*** linums <linums!~linums@apn-94-44-99-170.vodafone.hu> has quit IRC00:38
*** linums <linums!~linums@84.198.214.27> has joined #yocto00:38
kvpnetI have a 5.4 kernel where I applied a patch from 5.6 which brings in dmabuf heaps. The patch exports a uapi header include/uapi/linux/dma-heap.h. I am trying to write an application that uses dmabuf. It is able to find #include<linux/dma-buf.h> but not #include<linux/dma-heap.h> (this file is introduced in the patch)00:41
*** NiniC0c0 <NiniC0c0!56ee833f@lfbn-idf2-1-900-63.w86-238.abo.wanadoo.fr> has quit IRC00:41
*** shoragan <shoragan!~shoragan@debian/developer/shoragan> has joined #yocto00:42
*** gonkulator <gonkulator!~brandon@75.71.150.20> has joined #yocto00:44
*** OnkelUlla <OnkelUlla!~uol@ptx.hi.pengutronix.de> has joined #yocto00:45
yatesdoes anyone know how Freescale built their BSP for the i.MX6?01:06
yatesis it based on linaro?01:06
yatesJPEW, kergoth?01:08
*** Anarky_ <Anarky_!~Anarky@2a01:cb14:585:6700:baac:6fff:fea4:58b5> has joined #yocto01:33
*** Anarky <Anarky!~Anarky@lfbn-lyo-1-1731-121.w90-65.abo.wanadoo.fr> has quit IRC01:33
*** linums <linums!~linums@84.198.214.27> has quit IRC01:44
*** linums <linums!~linums@apn-94-44-101-155.vodafone.hu> has joined #yocto01:44
*** mrpelotazo <mrpelotazo!~mrpelotaz@HSI-KBW-109-192-067-084.hsi6.kabel-badenwuerttemberg.de> has quit IRC01:54
*** linums <linums!~linums@apn-94-44-101-155.vodafone.hu> has quit IRC01:57
*** linums <linums!~linums@84.198.214.27> has joined #yocto01:58
*** Kyubi_ <Kyubi_!~Kyubi@2601:647:4080:f10:7916:53ac:39bb:e34c> has joined #yocto02:00
*** Kyubi <Kyubi!~Kyubi@149.199.62.128> has quit IRC02:00
*** linums <linums!~linums@84.198.214.27> has quit IRC02:09
*** RzR <RzR!~rzr@78.197.125.113> has quit IRC02:09
*** RzR <RzR!~rzr@unaffiliated/rzr> has joined #yocto02:09
*** linums <linums!~linums@apn-94-44-101-155.vodafone.hu> has joined #yocto02:09
*** mrpelotazo <mrpelotazo!~mrpelotaz@HSI-KBW-109-192-067-084.hsi6.kabel-badenwuerttemberg.de> has joined #yocto02:11
*** linums <linums!~linums@apn-94-44-101-155.vodafone.hu> has quit IRC02:28
*** TalleyHo <TalleyHo!c71b740f@199.27.116.15> has quit IRC02:28
*** linums <linums!~linums@84.198.214.27> has joined #yocto02:28
*** kvpnet <kvpnet!ccf6a226@204.246.162.38> has quit IRC02:45
smurrayyates: AFAIK for at least the last couple of years they've based their meta-fsl-bsp-release and now meta-imx based BSP releases on top of meta-freescale02:45
yatessmurray: i see02:57
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has quit IRC02:59
yatesisn't there a git repo of the yocto layers03:00
yates(btw, that might be nice to have in the topic)03:00
yatesthat url, i.e.03:00
*** ahadi <ahadi!~ahadi@89.244.122.210> has quit IRC03:05
*** ahadi <ahadi!~ahadi@88.130.218.68> has joined #yocto03:07
*** Shikadi_ <Shikadi_!~Shikadi@136-27-89-140.cab.webpass.net> has joined #yocto03:12
*** oberstet_ <oberstet_!~oberstet@213.170.219.39> has joined #yocto03:12
*** Shikadi` <Shikadi`!~Shikadi@136-27-89-140.cab.webpass.net> has quit IRC03:13
*** oberstet <oberstet!~oberstet@213.170.219.39> has quit IRC03:13
*** camus <camus!~Instantbi@180.168.140.162> has joined #yocto03:48
*** kaspter <kaspter!~Instantbi@58.246.136.202> has quit IRC03:49
*** camus is now known as kaspter03:49
*** imcleod_ <imcleod_!~imcleod@2601:249:8200:1ba1:af65:6e6f:10d:e757> has quit IRC03:55
*** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has quit IRC04:02
*** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has joined #yocto04:02
yatesyocto is advertised as a system for building linux distributions, but is there anything to prevent it from being used for building a system based on (e.g.) freertos? has it ever been used for a non-linux build?04:06
*** Kyubi_ <Kyubi_!~Kyubi@2601:647:4080:f10:7916:53ac:39bb:e34c> has quit IRC04:09
*** camus <camus!~Instantbi@58.246.136.202> has joined #yocto04:10
*** kaspter <kaspter!~Instantbi@180.168.140.162> has quit IRC04:11
*** camus is now known as kaspter04:11
*** oberstet_ <oberstet_!~oberstet@213.170.219.39> has quit IRC04:11
*** Kyubi <Kyubi!~Kyubi@149.199.62.130> has joined #yocto04:15
*** Wouter01000 <Wouter01000!~Wouter010@84-80-174-188.fixed.kpn.net> has quit IRC04:23
*** Wouter01000 <Wouter01000!~Wouter010@84-80-174-188.fixed.kpn.net> has joined #yocto04:23
*** Shikadi_ <Shikadi_!~Shikadi@136-27-89-140.cab.webpass.net> has quit IRC04:24
*** stacktru1t <stacktru1t!~stacktrus@cpe-68-174-158-185.nyc.res.rr.com> has quit IRC04:38
*** mranostaj <mranostaj!~mranostaj@pdpc/supporter/active/mranostay> has joined #yocto04:40
*** stacktru1t <stacktru1t!~stacktrus@cpe-68-174-158-185.nyc.res.rr.com> has joined #yocto04:40
*** risca <risca!~quassel@212.85.71.156> has quit IRC05:12
*** vineela <vineela!~vtummala@134.134.139.72> has quit IRC05:13
*** risca <risca!~quassel@212.85.71.156> has joined #yocto05:14
*** pcglue <pcglue!~kvirc@cpe-104-175-108-43.socal.res.rr.com> has joined #yocto05:45
*** alessioigor <alessioigor!~alessioig@93-47-228-8.ip115.fastwebnet.it> has joined #yocto05:54
*** camus <camus!~Instantbi@58.246.136.202> has joined #yocto05:56
*** kaspter <kaspter!~Instantbi@58.246.136.202> has quit IRC05:56
*** camus is now known as kaspter05:56
*** alessioigor <alessioigor!~alessioig@93-47-228-8.ip115.fastwebnet.it> has quit IRC05:58
*** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-ctuqobmsihlahsah> has quit IRC06:05
*** jobroe <jobroe!~manjaro-u@p579eb4d8.dip0.t-ipconnect.de> has joined #yocto06:06
*** risca <risca!~quassel@212.85.71.156> has quit IRC06:16
*** risca <risca!~quassel@212.85.71.156> has joined #yocto06:18
*** kaspter <kaspter!~Instantbi@58.246.136.202> has quit IRC06:32
*** kaspter <kaspter!~Instantbi@58.246.136.202> has joined #yocto06:32
*** rcoote <rcoote!~rcoote@2a02:908:692:81c0:8805:3dc7:cafe:a5d5> has joined #yocto06:36
*** minimaxwell <minimaxwell!~minimaxwe@atoulouse-258-1-35-192.w90-55.abo.wanadoo.fr> has joined #yocto06:36
*** AndersD <AndersD!~AndersD@h83-209-96-136.cust.a3fiber.se> has joined #yocto06:39
*** AndersD_ <AndersD_!~AndersD@h83-209-96-136.cust.a3fiber.se> has joined #yocto06:43
*** mattsm <mattsm!~mattsm@104-181-154-57.lightspeed.austtx.sbcglobal.net> has quit IRC06:44
*** AndersD <AndersD!~AndersD@h83-209-96-136.cust.a3fiber.se> has quit IRC06:46
*** mattsm <mattsm!~mattsm@104-181-154-57.lightspeed.austtx.sbcglobal.net> has joined #yocto06:52
*** agust <agust!~agust@p508b685a.dip0.t-ipconnect.de> has joined #yocto07:01
*** linums <linums!~linums@84.198.214.27> has quit IRC07:12
*** linums <linums!~linums@84.198.214.27> has joined #yocto07:13
*** rubdos <rubdos!~rubdos@2a02:578:859d:700:dddd::1> has joined #yocto07:37
*** mckoan|away is now known as mckoan07:38
mckoangood morning07:39
*** kaspter <kaspter!~Instantbi@58.246.136.202> has quit IRC07:49
*** kaspter <kaspter!~Instantbi@58.246.136.202> has joined #yocto07:49
*** rubdos <rubdos!~rubdos@2a02:578:859d:700:dddd::1> has quit IRC07:50
*** gsalazar <gsalazar!955a6fad@gateway/web/cgi-irc/kiwiirc.com/ip.149.90.111.173> has joined #yocto07:50
*** fl0v0 <fl0v0!~fvo@i59F44D7E.versanet.de> has joined #yocto07:53
*** rubdos <rubdos!~rubdos@77.109.115.119> has joined #yocto07:59
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/irccloud.com/x-hiegmyxsblxtijgo> has joined #yocto08:00
*** medaliyou <medaliyou!c4b3dd32@196.179.221.50> has joined #yocto08:09
medaliyouHey guys08:09
medaliyouhaving hard time with this error08:09
medaliyou  File "/home/user/yocto-colibri-imx7/layers/openembedded-core/bitbake/lib/bb/codeparser.py", line 308, in parse_python08:09
medaliyou    code = compile(check_indent(str(node)), filename, "exec",08:09
medaliyou  File "autogenerated", line 308:09
medaliyou    rm -f ${S}/package-lock.json08:09
medaliyou          ^08:09
medaliyouSyntaxError: invalid syntax08:09
medaliyoui m sure identations are pretty good08:10
medaliyou4 spaces08:10
*** Yumasi <Yumasi!~guillaume@2a01:e0a:5cb:4430:7a61:84e4:c5cd:f119> has joined #yocto08:10
medaliyouwhen i remove the functions it passes ? idk what to do ?08:10
medaliyoudo_configure_append() {08:10
medaliyou    rm -f ${S}/package-lock.json08:10
medaliyou    rm -f ${S}/backend/static/app*08:10
medaliyou}08:10
*** yannholo <yannholo!~yannholo@fs-141-0-205-41.fullsave.info> has joined #yocto08:18
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto08:27
mckoanmedaliyou: pleade use pastebin instead of pasting code here08:29
mckoanmedaliyou: are you modifying inside openembedded-core ?08:30
LetoThe2ndi guess its python versus shell, but hey.08:31
rburtonmedaliyou: sounds like you've written a class that appends do_configure but assumes that do_configure is always shell, which might not be the case08:33
rburtonspecifically the do_configure provided by npm.bbclass is python08:34
rburtonso you can't just slap shell code on the end08:34
*** linums <linums!~linums@84.198.214.27> has quit IRC08:34
rburtonmedaliyou: am I right so far?08:34
medaliyoulet me check , i will assume you re right yeah08:34
rburtonas LetoThe2nd said, more context is essential08:35
*** linums <linums!~linums@apn-94-44-109-143.vodafone.hu> has joined #yocto08:35
medaliyouhow can i see the content of do configure of the reciepe  ?08:35
LetoThe2ndrburton: to put that into proper context, i actually wrote, not said it.08:35
rburtonLetoThe2nd: pedant!08:36
rburtonmedaliyou: well, does your recipe inherit npm08:36
medaliyoubitbake -b PATH_TO_RECIPE -e ?08:36
LetoThe2ndrburton: and proud of it!08:36
medaliyouyeahhh inherit npm systemd08:36
medaliyouboth08:36
rburtonso the do_configure in npm is python08:36
medaliyouahin ,08:37
medaliyougot it08:37
rburtonif you want to do some shell then use a do_configure[postfuncs] instead.  append *literally* puts what you tell it at the end so you're just putting some shell after a block of python.08:37
medaliyouso in recipes we ve two approches either writing inSHELL or pure python , right ?08:37
rburtonall functions can be shell or python08:37
medaliyoui got u08:38
medaliyouso now i replace the do_configure__append() { /****/ } with08:38
medaliyoudo_configure[postfuncs] ?08:38
medaliyouright ?08:38
LetoThe2ndrburton: you know what my main problem these days is? whenever i read "i got u", then my brain autocompletes: ", babe". and thats extremely un-metal!08:39
rburtonrofl08:40
rburtonmedaliyou: look up postfuncs in the docs (or just grep poky), but you basically get to write self-contained functions that run as part of the task08:40
medaliyouthank you man08:47
medaliyoui apperciate it08:47
*** mbulut <mbulut!~nameclash@ip1f121f26.dynamic.kabel-deutschland.de> has joined #yocto08:49
*** frsc <frsc!~frsc@p50937620.dip0.t-ipconnect.de> has joined #yocto08:50
*** mbulut <mbulut!~nameclash@ip1f121f26.dynamic.kabel-deutschland.de> has quit IRC08:52
*** mbulut <mbulut!~nameclash@ip1f121f26.dynamic.kabel-deutschland.de> has joined #yocto08:52
*** minimaxwell <minimaxwell!~minimaxwe@atoulouse-258-1-35-192.w90-55.abo.wanadoo.fr> has quit IRC08:59
*** minimaxwell <minimaxwell!~minimaxwe@61.46.205.77.rev.sfr.net> has joined #yocto09:01
*** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has joined #yocto09:02
*** manuel1985 <manuel1985!~manuel198@62.99.131.178> has joined #yocto09:05
Ad0is there a way to change kernel module load order for modules that are with the kernel (not out of tree modules)09:10
Ad0does KERNEL_MODULE_AUTOLOAD apply here too09:10
*** __ad <__ad!~prefetch@mail.kernel-space.org> has joined #yocto09:13
*** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto09:13
*** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC09:18
*** linums <linums!~linums@apn-94-44-109-143.vodafone.hu> has quit IRC09:18
*** linums <linums!~linums@84.198.214.27> has joined #yocto09:19
*** thekappe <thekappe!c65a42b1@198.90.66.177> has joined #yocto09:19
*** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto09:22
*** HatsyRei <HatsyRei!cabe12ca@202.190.18.202> has joined #yocto09:24
*** mbulut <mbulut!~nameclash@ip1f121f26.dynamic.kabel-deutschland.de> has quit IRC09:25
*** mbulut <mbulut!~nameclash@ip1f121f26.dynamic.kabel-deutschland.de> has joined #yocto09:25
*** dleppich <dleppich!~Thunderbi@81.20.119.6> has quit IRC09:26
*** dleppich <dleppich!~Thunderbi@81.20.119.6> has joined #yocto09:26
*** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@94.31.98.91> has quit IRC09:26
*** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@94.31.98.91> has joined #yocto09:27
*** dev1990 <dev1990!~dev@dynamic-78-8-42-145.ssp.dialog.net.pl> has quit IRC09:27
*** dev1990 <dev1990!~dev@dynamic-78-8-42-145.ssp.dialog.net.pl> has joined #yocto09:27
*** HatsyRei <HatsyRei!cabe12ca@202.190.18.202> has left #yocto09:40
*** jbaxter <jbaxter!~jbaxter@host81-132-126-225.range81-132.btcentralplus.com> has joined #yocto09:44
*** __ad <__ad!~prefetch@mail.kernel-space.org> has quit IRC09:47
*** linums <linums!~linums@84.198.214.27> has quit IRC09:47
*** linums <linums!~linums@84.198.214.27> has joined #yocto09:47
*** __ad <__ad!~prefetch@2a01:4f8:c2c:5a84::1> has joined #yocto09:48
*** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has quit IRC09:55
*** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has joined #yocto09:57
*** __ad <__ad!~prefetch@2a01:4f8:c2c:5a84::1> has quit IRC09:59
*** __ad <__ad!~prefetch@2a01:4f8:c2c:5a84::1> has joined #yocto10:00
*** __ad <__ad!~prefetch@2a01:4f8:c2c:5a84::1> has quit IRC10:15
*** otavio <otavio!~otavio@static.203.17.243.136.clients.your-server.de> has quit IRC10:16
*** __ad <__ad!~prefetch@mail.kernel-space.org> has joined #yocto10:19
*** __ad <__ad!~prefetch@mail.kernel-space.org> has quit IRC10:26
*** __ad <__ad!~prefetch@2a01:4f8:c2c:5a84::1> has joined #yocto10:26
*** minimaxwell <minimaxwell!~minimaxwe@61.46.205.77.rev.sfr.net> has quit IRC10:41
*** hpsy <hpsy!~hpsy@197.37.213.245> has joined #yocto10:44
*** Yatekii <Yatekii!~yatekii@huesser.dev> has quit IRC10:46
*** Yatekii <Yatekii!~yatekii@huesser.dev> has joined #yocto10:47
*** jbaxter <jbaxter!~jbaxter@host81-132-126-225.range81-132.btcentralplus.com> has quit IRC10:47
*** sno <sno!~sno@p4fe93db3.dip0.t-ipconnect.de> has quit IRC10:48
*** jbaxter <jbaxter!~jbaxter@nat-ies.mentorg.com> has joined #yocto10:48
*** Net147_ <Net147_!~Net147@unaffiliated/net147> has quit IRC10:57
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto10:57
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC11:00
*** __ad <__ad!~prefetch@2a01:4f8:c2c:5a84::1> has quit IRC11:01
*** __ad <__ad!~prefetch@mail.kernel-space.org> has joined #yocto11:01
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto11:01
medaliyouany idea on how to pass do_configure of npm.bbclass without having package-lock.json nor npm-shrinkwrap.json11:14
*** leon-anavi <leon-anavi!~Leon@78.130.197.211> has joined #yocto11:18
medaliyouException: FileNotFoundError: [Errno 2] No such file or directory: src/npm-shrinkwrap.json, on the do_configure()11:18
medaliyoui ve tried the patch on github11:19
medaliyouhttps://github.com/openembedded/openembedded-core/commit/47760b0d7d66b2b68ee197d359f0b7b17374d74211:19
medaliyoubut throws more errors11:19
medaliyouhow does the new npm.bbclass works ? should i do npm i and generate the package-lock.json nd npm_modules folder and generate the npm-shrinkwrap.json11:22
medaliyouin order to successfully integrate my app ?11:23
*** mckoan is now known as mckoan|away11:28
*** la_croix_ <la_croix_!~la_croix@cpc139740-walt24-2-0-cust196.13-2.cable.virginm.net> has quit IRC11:32
*** otavio <otavio!~otavio@static.203.17.243.136.clients.your-server.de> has joined #yocto11:42
yatesyocto is advertised as a system for building linux distributions, but is there anything to prevent it from being used for building a system based on (e.g.) freertos? has it ever been used for a non-linux build?11:51
Ad0it's very integrated / intertwined with linux11:54
Ad0that's how I read it at least :)11:54
yatesAd0: so basically, no?11:55
qschulzyates: https://elinux.org/images/9/9f/ELC_Europe_2019_Presentation_AlejandroHernandez_FreeRTOS_ToUpload.pdf11:58
yatesqschulz: very good!11:59
yateshow does yocto build a cross toolchain? what if the processor is custom?12:06
RPyates: it can be used to build pretty much anything, linux is just the default12:08
*** imcleod_ <imcleod_!~imcleod@2601:249:8200:1ba1:af65:6e6f:10d:e757> has joined #yocto12:08
yatesRP: +112:08
RPyates: grep for baremetal. If you want to use gcc, your target will need gcc support. You can use other compilers too if you wanted12:08
yatesok12:09
RPyates: I've personally done avr microcontroller work with YP toolchains12:09
yatesRP: you mean using yocto?12:09
RPyates: yes12:09
yatesgood to know it has been done - thank you12:10
yatesour product is something like a microship sama512:11
*** imcleod_ <imcleod_!~imcleod@2601:249:8200:1ba1:af65:6e6f:10d:e757> has quit IRC12:13
*** kanavin_ <kanavin_!~Srain@2a02:2450:1011:512:45a5:1b3d:84d2:e7fc> has joined #yocto12:18
*** kanavin <kanavin!~Srain@2a02:2450:1011:512:45a5:1b3d:84d2:e7fc> has quit IRC12:21
*** kanavin_ is now known as kanavin12:21
*** oberstet <oberstet!~oberstet@213.170.219.39> has joined #yocto12:22
*** imcleod_ <imcleod_!~imcleod@2601:249:8200:1ba1:af65:6e6f:10d:e757> has joined #yocto12:32
*** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-lqwqmllkswsapglo> has joined #yocto12:38
*** linums <linums!~linums@84.198.214.27> has quit IRC12:39
*** stwcx <stwcx!~stwcx@2604:880:a:6::c9c> has quit IRC12:42
Ad0very cool12:43
*** stwcx <stwcx!~stwcx@172.110.7.206> has joined #yocto12:51
*** minimaxwell <minimaxwell!~minimaxwe@29.46.205.77.rev.sfr.net> has joined #yocto12:57
*** rcoote <rcoote!~rcoote@2a02:908:692:81c0:8805:3dc7:cafe:a5d5> has quit IRC13:02
*** yannholo <yannholo!~yannholo@fs-141-0-205-41.fullsave.info> has quit IRC13:10
*** yannholo <yannholo!~yannholo@80.215.107.93> has joined #yocto13:10
*** frsc <frsc!~frsc@p50937620.dip0.t-ipconnect.de> has quit IRC13:15
*** frsc <frsc!~frsc@p50937620.dip0.t-ipconnect.de> has joined #yocto13:17
*** linums <linums!~linums@84.198.214.27> has joined #yocto13:20
*** yannholo <yannholo!~yannholo@80.215.107.93> has quit IRC13:24
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC13:24
*** yannholo <yannholo!~yannholo@fs-141-0-205-41.fullsave.info> has joined #yocto13:25
*** berton <berton!~user@200-180-244-11.user3p.brasiltelecom.net.br> has joined #yocto13:26
*** frsc <frsc!~frsc@p50937620.dip0.t-ipconnect.de> has quit IRC13:29
*** berton <berton!~user@200-180-244-11.user3p.brasiltelecom.net.br> has quit IRC13:32
*** yannholo <yannholo!~yannholo@fs-141-0-205-41.fullsave.info> has quit IRC13:33
*** berton <berton!~user@200-180-244-11.user3p.brasiltelecom.net.br> has joined #yocto13:34
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has joined #yocto13:37
RPJPEW: somehow diffoscope-native is now having issues finding the magic file code. The python3-magic upgrade is suspect but it reproduces on the AB without that13:40
*** zkrx <zkrx!~slimshady@adsl-89-217-237-59.adslplus.ch> has quit IRC13:42
*** frsc <frsc!~frsc@p50937620.dip0.t-ipconnect.de> has joined #yocto13:44
RPJPEW: there is also a diffoscope upgrade 166 -> 167 but I'm not convinced its that either13:45
*** Konsgn <Konsgn!~Konsgnx3@66-109-34-138.static.firstlight.net> has joined #yocto13:51
*** Konsgn <Konsgn!~Konsgnx3@unafiliated/joyseph> has joined #yocto13:51
*** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC13:51
*** yannholo <yannholo!~yannholo@fs-141-0-205-41.fullsave.info> has joined #yocto13:54
*** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto13:55
*** zkrx <zkrx!~slimshady@adsl-89-217-237-59.adslplus.ch> has joined #yocto13:57
*** stacktru1t <stacktru1t!~stacktrus@cpe-68-174-158-185.nyc.res.rr.com> has quit IRC14:03
*** stacktru1t <stacktru1t!~stacktrus@cpe-68-174-158-185.nyc.res.rr.com> has joined #yocto14:05
*** hpsy <hpsy!~hpsy@197.37.213.245> has quit IRC14:10
*** abelal <abelal!~quassel@110.93.212.98> has quit IRC14:19
*** abelal <abelal!~quassel@110.93.212.98> has joined #yocto14:20
RPsakoman: now purple builds? :/14:20
RPsakoman: looks like one of the workers has something using a lot of memory14:21
*** Anarky_ <Anarky_!~Anarky@2a01:cb14:585:6700:baac:6fff:fea4:58b5> has quit IRC14:22
sakomanRP: I stopped the build14:22
*** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has quit IRC14:23
bantuHello everyone. I am somewhat confused. How do I add systemd-journal-upload to my image?14:23
*** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has joined #yocto14:23
RPsakoman: pause debian8 and it should be ok14:24
sakomanRP: yes looks like debian8-ty-1 has memory issues14:24
sakomanOK, will do14:24
RPsakoman: it seems to have things running on it that should be there14:26
RPas in old stale builds14:26
JPEWRP: Hmm, is it possible to run the diffoscope selftest on diffoscope-native?14:28
KonsgnHmmm, if I want to make a custom machine file in my layer, should i rename the machine conf name when copying it into my custom layer or not? Will a bitbake search local layer first for a named machine? If the former, do I also need to copy and rename a kernel folder into my layers conf?,14:32
qschulzKonsgn: if you need to modify the machine conf, change its name14:33
qschulzyou can leverage the MACHINEOVERRIDES variable in your machine conf to "impersonate" the original machine if need be14:34
Konsgnthanks, but in that case its not finding a named defconf, do i haveto also rename the kernel folder?14:34
Konsgninteresting as in, beaglebone-custom can call a kernel named beaglebone?14:35
Konsgn*defconfig in kernel folder14:35
qschulzKonsgn: we don't have access to your layers so we cannot help with the info you're giving us :/14:36
Konsgnhttps://github.com/jumpnow/meta-bbb is what i am trying to modify so that uboot is loading from spi flash14:36
Konsgnseem to need to modify the UBOOT_MACHINE = "am335x_evm_spiboot_config"14:37
JPEWKonsgn: You should be able to update the upstream machine to deal with that14:37
KonsgnI dont want to change anything in the meta-bbb folder if thats what you mean14:38
KonsgnI want all modifications to be local to my layer, Isn't that the principal of yocto or am i misunderstanding14:38
JPEWKonsgn: for the specific case of booting from spi, you *should* be able to make the upstream support that in addition to the normal boot process14:39
JPEWWhich might prevent you from needing to fork the machine14:39
* JPEW looks for something14:39
*** __ad <__ad!~prefetch@mail.kernel-space.org> has quit IRC14:39
*** __ad <__ad!~prefetch@unaffiliated/ad/x-0785363> has joined #yocto14:39
KonsgnAhh, as in make a pull request adding that as a seperate machine name in that layer?14:39
JPEWKonsgn: You can do it with the same machine.... j/s14:40
JPEWKonsgn: https://docs.yoctoproject.org/ref-manual/variables.html#term-UBOOT_CONFIG14:41
JPEWYou can use that variable to allow you to have different u-boot configs and you can select which one you want in e.g. local.conf14:41
*** tasslehoff <tasslehoff!~Tasslehof@193.69.214.126> has joined #yocto14:42
*** kyanres <kyanres!~kyanres@ecascr.ecatou.fr> has quit IRC14:42
*** kyanres <kyanres!~kyanres@ecascr.ecatou.fr> has joined #yocto14:42
*** kyanres <kyanres!~kyanres@ecascr.ecatou.fr> has quit IRC14:42
*** kyanres <kyanres!~kyanres@ecascr.ecatou.fr> has joined #yocto14:42
Konsgnstill this would be a pull request to add that selection block in the upstream layer right? or can i use a UBOOT_CONFIG declaration and expect it to override the upstreams UBOOT_MACHINE definition?14:43
*** kaspter <kaspter!~Instantbi@58.246.136.202> has quit IRC14:43
*** kaspter <kaspter!~Instantbi@58.246.136.202> has joined #yocto14:43
JPEWKonsgn: Ya, you'd want to make a PR to the upstream (the advantage being that you could use the upstream machine instead of having to fork it)14:44
Konsgneventually i will need to make kernel modifications though... should i just fork it anyway? are there ways of overridding the defconfig?14:46
*** tasslehoff <tasslehoff!~Tasslehof@193.69.214.126> has quit IRC14:48
JPEWUh oh: Getting this on my CI: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.ss [bit 27]14:50
JPEWKonsgn: Ah, ya. In that case you might have to fork the machine. I'd probably give the machine a new name. If you are still including the meta-bbb layer, you can have it "require" the other one  and then override the variables you want to change14:52
*** Anarky <Anarky!~Anarky@2a01:cb14:585:6700:baac:6fff:fea4:58b5> has joined #yocto14:53
*** marc1 <marc1!~marc@ipagstaticip-ad9375f2-382c-b511-8ac1-9541f69fe50f.sdsl.bell.ca> has joined #yocto14:53
JaMaJPEW: have you tried to change the -cpu? Nehalem is the best :)14:56
JaMaJPEW: https://www.openembedded.org/pipermail/openembedded-core/2018-April/268608.html14:57
qschulzKonsgn: MACHINEOVERRIDES will do the trick for your defconfig14:57
JPEWJaMa: Ah, excellent. I checked and it looks like my builds that passed also gave the same warning, so perhaps it's always been there and I didn't notice14:59
JPEWJaMa: But I will change my CPU14:59
JaMawhat CPU do you have on host? I've finally replaced my aging Bulldozer last year :)15:00
JPEWJaMa: This is on the used servers I purchased: Xeon X567015:00
*** jobroe <jobroe!~manjaro-u@p579eb4d8.dip0.t-ipconnect.de> has quit IRC15:02
RPJPEW: hmm, not sure how we'd do that15:03
*** beneth` <beneth`!~beneth@irc.beneth.fr> has left #yocto15:03
JPEWRP: Ok. We could write and run a ptest on target to try it out, I was just wondering if it was possible to test native since that's what we actually use15:06
RPsakoman: debian8 seems fairly clear now. Not sure what was up with it15:08
bantuIt looks like one has to combine IMAGE_INSTALL_append = " systemd-journal-upload" and PACKAGECONFIG_append = "journal-upload". This is highly confusing15:09
JaMaJPEW: interesting, E5-2680 is only 2 years younger and seems to support ss, https://ark.intel.com/content/www/us/en/ark/products/64583/intel-xeon-processor-e5-2680-20m-cache-2-70-ghz-8-00-gt-s-intel-qpi.html I was just suprised that people still used something like that, but for used serer makes sense (as long as your electricity is relatively cheap :))15:10
RPdl9pf, JPEW: My attempt to clear that SDE warning didn't work either, didn't invalidate the sstate, or hashequiv has already broken it15:10
*** Kyubi <Kyubi!~Kyubi@149.199.62.130> has quit IRC15:14
RPThe AB workers look totally overloaded :/15:15
dl9pfRP ok, got my builder back up, will build and check master-next15:17
alephankhem: What is the status of systemd with musl? I see there is a warning in the core recipe when using musl.15:23
RPalephan: use at your own risk, there is functionality missing15:24
alephanDo you have a short context on the missing functionality - known issues?15:24
RPalephan: look at what the musl patches do to systemd, its fairly bad in places15:24
alephanCool. We will take a look.15:25
RPalephan: for some contexts it may be ok, for others it may be a big problem15:25
alephanSure. But are we aware of known cases where it fails for sure?15:26
JPEWJaMa: Ya, not sure... this all running in Kubernetes + Tekton + KubeVirt. I wonder if KubeVirt is not passing the flags? I'll have to look into it more. Either way, it doesn't appear to be the real reason my test failed15:26
JPEWRP: Hmm15:26
JPEWRP: The SDE processing is.... tricky.15:26
JaMaJPEW: it's possible that it wasn't supported there (/proc/cpuinfo can tell - I haven't found it in ark.intel.com)15:27
*** medaliyou <medaliyou!c4b3dd32@196.179.221.50> has quit IRC15:27
*** marc1 <marc1!~marc@ipagstaticip-ad9375f2-382c-b511-8ac1-9541f69fe50f.sdsl.bell.ca> has quit IRC15:27
Konsgn.. hmm, is there a way to check if my UBOOT_MACHINE_an-override = "am335x_evm_spiboot_config" line took effect from local.conf?15:29
qschulzKonsgn: you should really define a new machine15:31
qschulzbut to answer your question, bitbake <some-recipe> -e | grep -e "^UBOOT_MACHINE="15:32
KonsgnAlright, will do, but thanks for that.15:32
* JPEW looks at the SDE handling15:36
stefan-schmidt[mJPEW: i have a question on one of your patches RP did not take. https://lists.openembedded.org/g/openembedded-core/topic/79714162#14685915:44
stefan-schmidt[mLooking at it it seems the part that refers to the yocto bug was really only the first line of the append. The network file removal came in the commit that introduced the file to systemd-conf15:45
*** yates <yates!~user@fv-nc-f7af8b91e1-234237-1.tingfiber.com> has quit IRC15:45
stefan-schmidt[mThat commit does not say why it is not suited for qemu though :-)15:45
stefan-schmidt[mDid you follow up with RP on this? Maybe he just saw the bug ref and thought the network file is also part of it15:46
RPJPEW: I was able to strace it, its trying to access /home/pokybuild/yocto-worker/reproducible-ubuntu/build/build-st-31077/tmp/work/x86_64-linux/file-native/5.39-r0/recipe-sysroot-native/usr/share/misc/magic.mgc15:48
JPEWstefan-schmidt[m: I think I was trying to get systemd to bring up the network interfaces just like actual hardware; I didn't follow up because it turned out I had other problems with network testing on QEMU15:49
JPEWRP: Ah, another missing RDEPENDS perhaps?15:49
RPJPEW: well, file-native's sysroot definitely isn't the right path for something in diffoscope-native15:50
JPEWRP: Ah, right15:50
*** mbulut <mbulut!~nameclash@ip1f121f26.dynamic.kabel-deutschland.de> has quit IRC15:51
JPEWRP: Which explains why it's sporadic.... it *does* work if file-native was built locally, but not from sstate15:52
stefan-schmidt[mJPEW: fair enough, I will have another look here if it works for us and if that is the case raise the discussion again on your patch15:52
JPEWstefan-schmidt[m: Cool, thanks15:52
*** Yumasi <Yumasi!~guillaume@2a01:e0a:5cb:4430:7a61:84e4:c5cd:f119> has quit IRC15:53
*** Yumasi <Yumasi!~guillaume@2a01:e0a:5cb:4430:47c4:89ec:8e68:7431> has joined #yocto15:54
*** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC15:55
JPEWRP: It must be a path encoded in libmagic?15:58
*** rcoote <rcoote!~rcoote@2a02:908:692:81c0:3872:4b9d:3a2d:30d3> has joined #yocto16:01
JPEWRP: Yep, it's a path encoded in libmagic16:01
RPJPEW: specifying the path with MAGIC= solves it16:01
RPJPEW: probably have to wrap diffoscope16:01
JPEWRP: Ah, OK.16:02
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC16:02
*** minimaxwell <minimaxwell!~minimaxwe@29.46.205.77.rev.sfr.net> has quit IRC16:03
vdlRP: I've sent a patch named "[openembedded-core][PATCH] systemd: fix importd requirements" to the wrong mailing list (poky). Did it get lost and do you want me to resend it?16:04
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto16:04
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC16:07
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto16:09
*** dmoseley <dmoseley!~dmoseley@24.96.56.90> has quit IRC16:12
kanavinRP: I am working through the list of failed AUH updates, and those will be run through a-full by myself before I submit them16:13
*** dmoseley <dmoseley!~dmoseley@24.96.56.90> has joined #yocto16:15
*** manuel1985 <manuel1985!~manuel198@62.99.131.178> has quit IRC16:19
Konsgnif i copy in the recipes-kernel folder into my layer, do i need to rename it?16:33
*** AndersD_ <AndersD_!~AndersD@h83-209-96-136.cust.a3fiber.se> has quit IRC16:34
*** frsc <frsc!~frsc@p50937620.dip0.t-ipconnect.de> has quit IRC16:35
qschulzKonsgn: what are you doing?16:40
Konsgnhahaha i have no idea16:40
Konsgnstill trying to get a modified uboot made with bitbake16:41
qschulzand what has the recipes-kernel to do with that?16:41
KonsgnI've been copying the relevant recipes-kernel subfolder into my build/recipes-kernel folder of my layer16:41
qschulzwhy are you copying them?16:41
qschulzit seems to be a XY problem16:42
qschulzwhat exactly do you want to do?16:42
KonsgnThey were not found to have been compatible with my renamed machine16:42
qschulzKonsgn: what was the error?16:42
Konsgnnot in COMPATIBLE_MACHINE16:42
Konsgnlinux-stable PROVIDES virtual/kernel but was skipped: incompatible with machine16:43
qschulzKonsgn: because you didn't add the appropriate MACHINEOVERRIDES for your new machine configuration file16:43
qschulzKonsgn: MACHINEOVERRIDES =. "beaglebone:" IIRC in your machine configuration file. Check the order is right with bitbake some-recipe -e | grep -e "^MACHINEOVERRIDES=", leftmost to rightmost = least to most important16:44
qschulzthe order is counterintuitive so you might need a few tries but it's definitely a prepend you want, it just depends when you need to add it (before the includes in your machine configruation file IIRC)16:45
Konsgnalright, lemme try that. I must say I don't understand its function based on the ref manual. seems to imply that all upstream layers haveto lookout for the named overrides16:46
*** dreyna <dreyna!~dreyna@2601:646:4201:e280:cc0b:cf31:a49c:b4df> has joined #yocto16:48
*** gsalazar <gsalazar!955a6fad@gateway/web/cgi-irc/kiwiirc.com/ip.149.90.111.173> has quit IRC16:48
qschulzKonsgn: anything in OVERRIDES (MACHINEOVERRIDES is in it) can be used as _override in recipes16:48
qschulzit can also be used in COMPATIBLE_MACHINE16:48
KonsgnIs it that you have a custom machine name and in overrides you reference the machine it's based on?16:48
qschulzsee MACHINEOVERRIDES as machine families16:48
qschulzif we didn't have such mechanism, we would have to explicit all machines in COMPATIBLE_MACHINE16:49
qschulzinstead, you can define a machine family and use that one in COMPATIBLE_MACHINE16:49
Konsgnhmm, earlier I was trying to UBOOT_MACHINE_an-override but it didn't seem to be taking16:49
qschulzKonsgn: where did you put it and what exactly the line was?16:49
Konsgninto my local.conf at the end iirc16:50
Konsgnrn I'm trying your recommendation and is baking16:50
qschulzKonsgn: have you created a new machine configuration file?16:51
qschulzin which directory? did you change the MACHINE variable appropriately in local.conf?16:51
Konsgnfor this run yes, for the attempt with an-override: no.16:51
vdlis wic part's --ondisk option host or target specific?16:52
qschulzok, it's anyway something you want to go with :)16:52
qschulzwith/for/16:52
yannhow is KERNEL_IMAGETYPE_FOR_MAKE suppose to work ?  the code says "KERNEL_IMAGETYPES may contain a mixture of image types supported directly by the kernel build system and types which are created by post-processing the output of the kernel build system", but it still unconditionally copies everything from KERNEL_IMAGETYPES.  And to remove anything from there, KERNEL_IMAGETYPE_FOR_MAKE_remove is not usable, we have to filter anything out manually with a python16:53
yannsnippet ?  I can't help thinking I must have missed something, but what ?16:53
Konsgndamnit, am335x_evm_spiboot_defconfig doesn't seem to exist17:05
qschulzKonsgn: there's a qspiboot_defconfig one17:10
qschulzcheck if it would suit you17:10
qschulzKonsgn: sorry, wasn't looking at the right line17:11
*** fl0v0 <fl0v0!~fvo@i59F44D7E.versanet.de> has quit IRC17:12
qschulzKonsgn: the defconfig you mention is very new17:12
qschulzwas only added in 2021.0117:12
qschulzyou could try to backport it yourself, maybe there weren't too many changes involved17:12
Konsgnwierd, with am3358 being around so long i wouldave expected more people putting uboot onto spiflash..will do.17:13
*** linums <linums!~linums@84.198.214.27> has quit IRC17:22
*** linums <linums!~linums@apn-94-44-102-151.vodafone.hu> has joined #yocto17:22
*** linums <linums!~linums@apn-94-44-102-151.vodafone.hu> has quit IRC17:23
*** linums <linums!~linums@84.198.214.27> has joined #yocto17:24
moto-timopaulbarker: exaple of go issue I mentioned k9s/0.24.2+gitAUTOINC+f929114ae4-r0/build/pkg/mod/k8s.io/apiextensions-apiserver@v0.18.0/pkg/cmd/server/options/options.go': Permission denied17:28
moto-timopaulbarker: there are pages and pages of those kind of errors...17:28
paulbarkermoto-timo: Have a look at the `-modcacherw` flag17:29
paulbarkerhttps://go-review.googlesource.com/c/go/+/202563/17:29
paulbarkerhttps://github.com/golang/go/issues/3148117:29
moto-timopaulbarker: thank you. I epically failed to search for that flag.17:30
paulbarkerI remember the discussion on the github issue17:30
*** ssajal <ssajal!~ssajal@bras-base-otwaon1146w-grc-08-142-114-156-131.dsl.bell.ca> has quit IRC17:31
*** linums <linums!~linums@84.198.214.27> has quit IRC17:40
*** vineela <vineela!~vtummala@134.134.137.73> has joined #yocto17:41
*** linums <linums!~linums@apn-94-44-102-151.vodafone.hu> has joined #yocto17:42
vdlsilly question: is there a way to override the file extension in the IMAGE_LINK_NAME so that I can name the link "sdcard.img" instead of "sdcard.img.wic"?17:53
smurrayRP: it just occurred to me, would moving fetched source out of WORKDIR imply that the pretty common S = "${WORKDIR}/git" in recipes would need to change?17:56
smurrayRP: seems like it would?17:56
*** aleblanc <aleblanc!~textual@192-222-183-114.qc.cable.ebox.net> has quit IRC18:02
RPsmurray: no, since we'd symlink S into place18:04
smurrayRP: ah, I wasn't sure I caught that right on the call.  All the files in the new ${WORKDIR}/src get symlinked into ${WORKDIR}, is that the plan?18:05
RPsmurray: no, only the one that S would point at18:06
RPsmurray: that would catch most of the common usage except for the larger SRC_URIs with non-patches18:07
*** aleblanc <aleblanc!~textual@192-222-183-114.qc.cable.ebox.net> has joined #yocto18:07
smurrayRP: okay18:07
RPsmurray: this is my theory anyway.18:07
rburtonRP: cough http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-m/trusted-firmware-m_1.2.0.bb#n1818:07
RPrburton: should be ok as S wouldn't change18:08
RPrburton: that recipe probably deserves to get broken mind ;-)18:09
moto-timopaulbarker: go-mod.bbclass already sets -modcacherw18:12
fraylol I just went downstairs and double checked my measurements.. :)18:14
*** yates <yates!~user@fv-nc-f7af8b91e1-234237-1.tingfiber.com> has joined #yocto18:14
*** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto18:17
*** linums <linums!~linums@apn-94-44-102-151.vodafone.hu> has quit IRC18:17
*** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC18:17
*** linums <linums!~linums@natx-145.kulnet.kuleuven.be> has joined #yocto18:17
RPrburton: I guess it does make the case that we'd have to symlink in advance18:19
*** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto18:20
*** yannholo <yannholo!~yannholo@fs-141-0-205-41.fullsave.info> has quit IRC18:23
*** leon-anavi <leon-anavi!~Leon@78.130.197.211> has quit IRC18:25
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/irccloud.com/x-hiegmyxsblxtijgo> has quit IRC18:26
*** ssajal <ssajal!~ssajal@bras-base-otwaon1146w-grc-08-142-114-156-131.dsl.bell.ca> has joined #yocto18:32
*** ByteLawd <ByteLawd!extor@unaffiliated/extor> has quit IRC18:32
*** ByteLawd <ByteLawd!extor@unaffiliated/extor> has joined #yocto18:32
dl9pfdoh, hitting the magic file bug18:35
moto-timopaulbarker: well, no wonder, the Makefile is not flexible https://github.com/derailed/k9s/blob/master/Makefile#L1918:36
RPdl9pf: I'm trying to reproduce locally to test a patch but it doesn't want to do it on demand!18:40
opellohi, is there a "canonical" way to get around the package_rpm.bbclass wrap_uninstall behavior for prerm/postrm?  it seems ldconfig on rpm downgrade leaves library symlinks in an ultimately bad state (pointing to the newer file)18:42
*** linums <linums!~linums@natx-145.kulnet.kuleuven.be> has quit IRC18:45
RPvmeson: http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/t222&id=bbc4753fcc7d933f11c44961fda2bb09b3891613 was the patch I wondered about18:45
*** linums <linums!~linums@apn-94-44-111-203.vodafone.hu> has joined #yocto18:45
RPdl9pf: http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=0d47b2256c3df7d45cd85417e0a104485ddb5430 - fix for diffoscope magic18:45
RPjonmason, rburton: https://autobuilder.yoctoproject.org/typhoon/#/builders/97/builds/2422 - 19 hours - do you want to investigate ?18:46
dl9pfRP: heh ... pulling18:47
jonmasonRP: I'll let rburton handle that one ;-)18:47
*** dmoseley <dmoseley!~dmoseley@24.96.56.90> has quit IRC18:52
RPjonmason: trouble is its blocking other builds :(18:52
yateswhat does a BSP provide?18:54
yatesis this accurate: https://en.wikipedia.org/wiki/Board_support_package#:~:text=In%20embedded%20systems%2C%20a%20board,or%20CPU%20card)%2C%20integrated%20with18:55
*** dmoseley <dmoseley!~dmoseley@24.96.56.90> has joined #yocto18:59
*** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC19:02
*** ByteLawd <ByteLawd!extor@unaffiliated/extor> has quit IRC19:05
*** ByteLawd <ByteLawd!extor@unaffiliated/extor> has joined #yocto19:05
vdlyates: a BSP usually provides all necessary low level software to boot a device. In the Yocto world, a BSP layer usually contains the machine definition including its architecture, the preferred bootloader and kernel, eventually kernel patches, etc. Then with the BSP layer for your board (e.g. meta-raspberrypi), you should be able to have a working environment by building a combination of e.g. the19:07
vdl"raspberrypi" machine, the "core-image-minimal" image and any distro (e.g. "poky").19:07
*** linums <linums!~linums@apn-94-44-111-203.vodafone.hu> has quit IRC19:09
*** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has quit IRC19:09
*** linums <linums!~linums@natx-145.kulnet.kuleuven.be> has joined #yocto19:09
*** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has joined #yocto19:10
*** beneth` <beneth`!~beneth@irc.beneth.fr> has joined #yocto19:10
khemAndrei:  systemd will work with musl in OE, but its not tested and upstream systemd does not support anything other than glibc, we keep it working to a certain extent, dont expect to work it same as glibc19:15
Konsgnhow can i find the source of the used u-boot? as in where the repository resides from my images -e output19:16
khemKonsgn: from recipe you can not sure from image  bitbake -e virtual/bootloader | grep -e "^S="19:17
Konsgnyea, grepping didn't find any info about it. how else can I see it then?19:19
RPload average isn't a good metric for autobuilder stress. There is one 650+ but no IO wait and it is responsive. The issue appears to be high io wait times but caused by what...19:20
vdlRP: did you see my message regarding the openembedded-core patch sent to poky@?19:21
*** mr_science <mr_science!~sarnold@47.143.129.77> has joined #yocto19:22
RPvdl: please do send it to the right list. Sorry its gotten lost19:22
vdlno problem, will do.19:22
*** beneth` <beneth`!~beneth@irc.beneth.fr> has left #yocto19:23
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC19:24
*** oberstet <oberstet!~oberstet@213.170.219.39> has quit IRC19:28
*** f3ddischson <f3ddischson!~feddischs@HSI-KBW-095-208-248-106.hsi5.kabel-badenwuerttemberg.de> has joined #yocto19:31
*** mr_science <mr_science!~sarnold@47.143.129.77> has quit IRC19:33
yatesvdl: thanks much. that is a great explanation19:33
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto19:33
*** beneth` <beneth`!~beneth@irc.beneth.fr> has joined #yocto19:34
yatesuboot is part of the bsp? i think someone said this yesterday - just double checking19:34
Konsgnyup just found it with bitbake-layers show-recipes > recipelist.txt | grep -n uboot. points to "meta"19:36
smurrayyates: it's a bootloader, so part of the BSP if a board needs it to boot19:37
vdlyates: the default u-boot recipe is in the "core" layer (found in openembedded-core/meta/recipes-bsp/u-boot). But if you take the example of the Beaglebone board, its machine definition is found in the "meta-ti" BSP layer, providing their own uboot-ti-staging recipe. They define their bootloader by default (obviously, that is the one they officially support), but you can decide to switch to another19:38
vdlbootloader if you wish.19:38
*** jpnurmi <jpnurmi!jpnurmi@qt/jpnurmi> has quit IRC19:38
*** jpnurmi <jpnurmi!jpnurmi@qt/jpnurmi> has joined #yocto19:39
*** rcoote <rcoote!~rcoote@2a02:908:692:81c0:3872:4b9d:3a2d:30d3> has quit IRC19:40
vdlsmurray: btw I didn't fix the "container" IMAGE_FSTYPES yet, I have minimal working examples, but I fail to find the faulty config in my setup (which now fails to parse the _unused_ core-image-rt-sdk.bb recipe...)19:40
*** mcfrisk <mcfrisk!mcfrisk@kapsi.fi> has quit IRC19:40
*** mcfrisk <mcfrisk!mcfrisk@kapsi.fi> has joined #yocto19:40
yatessmurray: what processor doesn't have to boot?!? sorta like a write-only memory...19:49
smurrayyates: there are other bootloaders19:50
yatessorry, i misread19:50
vdlyates: the kernel is able to self boot on x86 for example, no bootloader needed.19:50
yatesvdl: how is that possible? the cpu has startup code internally (like an internal bootrom), but still at some point it has, at a minimum, to get the boot command from somewhere.19:54
yatesdid it used to be (in prehistoric days) that the "boot" code wold reside on track 0 of the drive?19:56
yatesdidn't19:56
yatesor the first sector19:57
yatesperhaps the bios acts as a sort of boot loader?19:58
yatesor am i being stupid?19:59
*** linums <linums!~linums@natx-145.kulnet.kuleuven.be> has quit IRC20:00
vdlyes, EFI firmware can boot a kernel image directly for example.20:00
*** linums <linums!~linums@apn-94-44-101-135.vodafone.hu> has joined #yocto20:01
*** linums <linums!~linums@apn-94-44-101-135.vodafone.hu> has quit IRC20:01
*** linums <linums!~linums@natx-145.kulnet.kuleuven.be> has joined #yocto20:02
vdland if I'm not mistaken you could directly write the kernel image on first sector with some old architectures, but I don't remember the details20:02
vdlanyway, this is all part of the BSP configuration ;-)20:02
*** linums <linums!~linums@natx-145.kulnet.kuleuven.be> has quit IRC20:18
*** linums <linums!~linums@natx-145.kulnet.kuleuven.be> has joined #yocto20:18
*** xtron <xtron!~xtron@103.113.103.49> has joined #yocto20:20
*** linums <linums!~linums@natx-145.kulnet.kuleuven.be> has quit IRC20:23
*** linums <linums!~linums@natx-145.kulnet.kuleuven.be> has joined #yocto20:24
alephankhem: I looked into the patches (and also we looked as a team) and look fine to us. I was looking for known broken issues. And it's strange that we have a warning for something that we suspect it might break. But nobody really had issues with. If that is how we flag possible issues, I have a feeling we would flag many other warnings in the build system. I'm wondering what do you think of making that warning optional.20:25
alephanBasically, having a variable that signifies the fact that the user acknowledges the "risk".20:25
*** ahadi <ahadi!~ahadi@88.130.218.68> has quit IRC20:26
*** ahadi <ahadi!~ahadi@88.130.218.68> has joined #yocto20:27
*** linums <linums!~linums@natx-145.kulnet.kuleuven.be> has quit IRC20:29
*** linums <linums!~linums@apn-94-44-101-135.vodafone.hu> has joined #yocto20:29
*** linums <linums!~linums@apn-94-44-101-135.vodafone.hu> has quit IRC20:30
*** linums <linums!~linums@natx-145.kulnet.kuleuven.be> has joined #yocto20:30
*** __ad is now known as angelo__20:39
RPalephan: I've been told by several people that what is done in there musl wise is a huge potential security hole and there were people who wanted the patches removed entirely. This was the compromise20:48
RPalephan: I wish we could get the patches cleaned up a bit :/20:48
*** linums <linums!~linums@natx-145.kulnet.kuleuven.be> has quit IRC20:50
*** linums <linums!~linums@apn-94-44-101-135.vodafone.hu> has joined #yocto20:51
*** f3ddischson <f3ddischson!~feddischs@HSI-KBW-095-208-248-106.hsi5.kabel-badenwuerttemberg.de> has quit IRC20:52
*** beneth` <beneth`!~beneth@irc.beneth.fr> has left #yocto20:57
*** armpit <armpit!~armpit@2601:202:4180:a5c0:8e1:8c0f:8c00:9696> has quit IRC21:00
alephanRP: there is indeed on patch that has such a suspicion behind. There is a bug behind it anyway. But I agree that the patch might not be ideal. We look a bit into it today but we couldn't figure the roots of it21:05
RPalephan: I have a fix for the AT_SYMLINK_NOFOLLOW one FWIW, was trying to see if musl would fix that21:06
RPkhem: I didn't see any feedback from musl on that patch?21:07
vdlany reason why wic doesn't support --fstype f2fs?21:08
RPvdl: nobody's added it? :)21:10
*** risca <risca!~quassel@212.85.71.156> has quit IRC21:11
*** risca <risca!~quassel@212.85.71.156> has joined #yocto21:12
yatesvdl: pot a toe, pot tah toe. EFI is a bootloader21:12
*** xtron <xtron!~xtron@103.113.103.49> has quit IRC21:12
vdlRP: okay I just wanted to make sure there wasn't a technical reason against it (IMAGE_FSTYPES supports f2fs anyway)21:12
*** armpit <armpit!~armpit@2601:202:4180:a5c0:8cb5:e0e1:ba5f:6619> has joined #yocto21:12
vdlyates: in the context of a BSP layer, what I meant is that you do not always need to compile a bootloader (just a EFI partition for EFI). So to complement smurray's answer, the bootloader is part of the BSP layer, if the machine requires to compile such software.21:15
*** berton <berton!~user@200-180-244-11.user3p.brasiltelecom.net.br> has quit IRC21:16
RPJPEW: around and have a minute to talk through this SDE issue? I don't understand why its breaking :(21:18
*** sbach <sbach!~sbachmatr@192.184.90.156> has quit IRC21:18
*** sbach <sbach!~sbachmatr@192.184.90.156> has joined #yocto21:19
RPI'll just write it down. https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/3087 shows three warnings, they're from lib32-wic-tools saying SDE==0. This build has http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=b625705bb710ebbd57f2e8b6d56cf8203aa8ebc5 in it21:22
RPIn that master-next patch, I modify create_source_date_epoch_stamp which causes do_unpack to rerun. I've checked, its in do_unpacks sigdata for lib32-wic-tools.21:22
KonsgnWhere could one find where the uboot sources are linked in from?21:23
KonsgnI cant seem to find the SRC_URI21:24
Konsgnscratch that, found it...21:24
RPThe only thing I can think is happening is hashequiv somehow mixes up and links the SDE=0 and SDE=real values accidentally21:25
*** beneth` <beneth`!~beneth@irc.beneth.fr> has joined #yocto21:25
RPin which case do we really have to bump the hash equiv version? :/21:25
RPI'm tempted just to empty the autobuilders hashequiv server21:26
*** linums <linums!~linums@apn-94-44-101-135.vodafone.hu> has quit IRC21:34
*** linums <linums!~linums@natx-145.kulnet.kuleuven.be> has joined #yocto21:35
khemRP:  Rich rejected the musl/systemd patch I think he cced you too21:35
*** om26er <om26er!6e260b11@ubuntu/member/om26er> has quit IRC21:35
khemhttps://www.openwall.com/lists/musl/2021/02/16/221:36
khemAndrei:  I think if there are more users for musl/systemd combo we could have more hands maintaining it. I can only support so much21:39
*** caio <caio!~caio@92-108-245-63.cable.dynamic.v4.ziggo.nl> has joined #yocto21:47
*** caio is now known as Guest1622921:47
RPkhem: ah, don't think I was cc'd21:51
khemoh I see21:52
RPkhem: thanks. I think the leftover flags argument from the old call confused me21:52
khemI think Rich has a good point, but who will tell this to systemd folks :)21:52
RPkhem: I guess glibc must me emulating this21:53
khemyes glibc does sadly21:54
khemI checked it afterwards21:54
RPkhem: the systemd people will just say they only care about latest kernel and faccessat221:58
*** Konsgn <Konsgn!~Konsgnx3@unafiliated/joyseph> has quit IRC21:59
RPkhem: ah well, thanks for the help22:01
khemyeah :(22:02
*** thekappe <thekappe!c65a42b1@198.90.66.177> has quit IRC22:02
*** linums <linums!~linums@natx-145.kulnet.kuleuven.be> has quit IRC22:11
*** linums <linums!~linums@apn-94-44-101-135.vodafone.hu> has joined #yocto22:13
*** linums <linums!~linums@apn-94-44-101-135.vodafone.hu> has quit IRC22:14
RPkhem: with go 1.16 are we going to see test failures, did I read your email correctly?22:14
*** linums <linums!~linums@natx-145.kulnet.kuleuven.be> has joined #yocto22:14
khemyes, there are few changes which need adjustments to go.bbclass22:16
khemgo community is pushing for go modules move22:17
khemthe way we build go packages does not use it, hold onto these patches I am working on fixing it22:18
RPkhem: ok, fair enough, thanks. Just wanted to check I was doing the right thing!22:18
khemI think the go patches as such are ok but the infra/go.bbclass need to adopt22:20
RPkhem: right. one step at a time! :)22:20
* RP notes diffoscope is still taking 30 mins to diff 2 rpms on the autobuilder :(22:21
RPhttps://autobuilder.yoctoproject.org/typhoon/#/builders/116/builds/34/steps/12/logs/stdio22:21
alephankhem: We made the switch ourselves to musl as the default libc provider. So you can expect some help on our side (but currently we are focusing on dunfell).22:21
RPsorry, 4 in that case22:21
khemAndrei: good deal22:21
alephanNevertheless, anything we fact in dunfell we will try to go through master first if it's relevant.22:22
alephanfind*22:22
*** linums <linums!~linums@natx-145.kulnet.kuleuven.be> has quit IRC22:25
*** linums <linums!~linums@apn-94-44-101-135.vodafone.hu> has joined #yocto22:26
*** linums <linums!~linums@natx-145.kulnet.kuleuven.be> has joined #yocto22:26
*** emBG <emBG!~em@134.249.102.199> has joined #yocto22:33
emBG/!\ this chat has moved to irc.crimeircd.net #0 /!\22:33
*** emBG <emBG!~em@134.249.102.199> has quit IRC22:33
*** manuel1985 <manuel1985!~manuel198@089144217195.atnat0026.highway.a1.net> has joined #yocto22:35
*** vquicksilver <vquicksilver!~nobody@gentoo/contributor/vquicksilver> has quit IRC22:46
*** alinucs <alinucs!~abo@215.ip-51-38-235.eu> has quit IRC22:46
*** vquicksilver <vquicksilver!~nobody@gentoo/contributor/vquicksilver> has joined #yocto22:48
*** alinucs <alinucs!~abo@215.ip-51-38-235.eu> has joined #yocto22:48
*** CarlGel <CarlGel!~Rika-chan@unaffiliated/carlgel> has quit IRC22:49
*** agust <agust!~agust@p508b685a.dip0.t-ipconnect.de> has quit IRC22:51
*** CarlGel <CarlGel!~Rika-chan@unaffiliated/carlgel> has joined #yocto22:51
*** linums <linums!~linums@natx-145.kulnet.kuleuven.be> has quit IRC22:58
*** linums <linums!~linums@apn-94-44-110-195.vodafone.hu> has joined #yocto22:58
*** qschulz <qschulz!~weechat@ns326003.ip-37-187-106.eu> has quit IRC23:39
*** qschulz <qschulz!~weechat@ns326003.ip-37-187-106.eu> has joined #yocto23:42
JPEWRP: Sorry, I had to physically go into work today (the horror!) so I was AFK. I'll have time tomorrow23:45
khemugh23:48
*** kiwi_29 <kiwi_29!~kiwi_29@c-73-231-211-214.hsd1.ca.comcast.net> has joined #yocto23:53

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