Thursday, 2023-05-11

*** PobodysNerfect <PobodysNerfect!~PobodysNe@84.214.105.47> has joined #yocto00:26
*** PobodysNerfect <PobodysNerfect!~PobodysNe@84.214.105.47> has quit IRC (Ping timeout: 264 seconds)00:31
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Remote host closed the connection)00:48
*** seninha <seninha!~seninha@user/seninha> has joined #yocto00:48
*** davidinux <davidinux!~davidinux@194.147.59.155> has quit IRC (Ping timeout: 240 seconds)01:04
*** sakoman <sakoman!~steve@dhcp-72-234-106-30.hawaiiantel.net> has quit IRC (Quit: Leaving.)01:09
*** starblue <starblue!~juergen@dslb-094-220-114-137.094.220.pools.vodafone-ip.de> has quit IRC (Ping timeout: 240 seconds)01:21
*** Thorn <Thorn!~Thorn@user/thorn> has joined #yocto01:21
*** starblue <starblue!~juergen@dslb-094-221-183-040.094.221.pools.vodafone-ip.de> has joined #yocto01:23
*** Thorn <Thorn!~Thorn@user/thorn> has quit IRC (Ping timeout: 240 seconds)01:27
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)01:29
*** rber|res <rber|res!~rber|res@62-47-44-37.adsl.highway.telekom.at> has joined #yocto01:32
*** RobertBerger <RobertBerger!~rber|res@62.47.44.37> has quit IRC (Ping timeout: 240 seconds)01:34
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Remote host closed the connection)01:57
*** sakoman <sakoman!~steve@dhcp-72-234-106-30.hawaiiantel.net> has joined #yocto02:28
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)02:55
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat)03:00
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has joined #yocto03:01
*** jclsn <jclsn!~jclsn@2a04:4540:651e:ae00:2ce:39ff:fecf:efcd> has quit IRC (Ping timeout: 240 seconds)03:01
*** jclsn <jclsn!~jclsn@2a04:4540:6528:ed00:2ce:39ff:fecf:efcd> has joined #yocto03:03
*** Thorn <Thorn!~Thorn@user/thorn> has joined #yocto03:07
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 240 seconds)03:18
*** nemik <nemik!~nemik@76.74.126.42> has joined #yocto03:19
*** nemik <nemik!~nemik@76.74.126.42> has quit IRC (Ping timeout: 265 seconds)03:23
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto03:23
*** sakoman <sakoman!~steve@dhcp-72-234-106-30.hawaiiantel.net> has quit IRC (Quit: Leaving.)04:30
*** thomasd13 <thomasd13!~thomas@DSL01.212.114.255.148.ip-pool.NEFkom.net> has joined #yocto04:36
tomzy_0[m]<ecdhe> "Are sumo-era builds not supporte..." <- I think you can go back and use kas-docker (now known as kas-container, but older release) if this is an option for you, e.g. v 2.0 https://github.com/siemens/kas/blob/2.0/kas-docker or older05:10
*** RobertBerger <RobertBerger!~rber|res@089144203021.atnat0012.highway.a1.net> has joined #yocto05:17
*** rber|res <rber|res!~rber|res@62-47-44-37.adsl.highway.telekom.at> has quit IRC (Ping timeout: 264 seconds)05:19
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto05:29
*** Thorn <Thorn!~Thorn@user/thorn> has quit IRC (Ping timeout: 240 seconds)05:30
*** rob_w <rob_w!~rob@2001:a61:6012:6901:dc56:77e9:c511:6170> has joined #yocto05:36
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)05:38
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto05:39
*** Guest98 <Guest98!~Guest98@31.145.189.2> has joined #yocto05:41
*** PobodysNerfect <PobodysNerfect!~PobodysNe@84.214.105.47> has joined #yocto05:45
*** PobodysNerfect <PobodysNerfect!~PobodysNe@84.214.105.47> has quit IRC (Ping timeout: 264 seconds)05:55
*** zpfvo <zpfvo!~fvo@i59F5CECF.versanet.de> has joined #yocto06:02
*** wooosaiiii <wooosaiiii!~Thunderbi@89-212-21-243.static.t-2.net> has quit IRC (Quit: wooosaiiii)06:03
*** wooosaiiii <wooosaiiii!~Thunderbi@89-212-21-243.static.t-2.net> has joined #yocto06:03
*** davidinux <davidinux!~davidinux@194.147.59.133> has joined #yocto06:07
*** pbergin <pbergin!~pbergin@c-799071d5.44006-0-69747578.bbcust.telenor.se> has quit IRC (Ping timeout: 246 seconds)06:24
*** frieder <frieder!~frieder@i577BE786.versanet.de> has joined #yocto06:27
*** sgw <sgw!~swold@user/sgw> has quit IRC (Quit: Leaving.)06:37
*** sgw <sgw!~swold@user/sgw> has joined #yocto06:37
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has joined #yocto06:40
*** mckoan|away is now known as mckoan06:49
mckoangood morning06:49
Guest98morning06:51
*** PobodysNerfect <PobodysNerfect!~PobodysNe@84.214.105.47> has joined #yocto06:54
*** Thorn <Thorn!~Thorn@user/thorn> has joined #yocto06:57
Guest98Hi everyone, i have a question mark in my mind about 2 topic. First one about combining the 2 different Yocto Project to under a single project. Second one, how a recipe is designed in a project with more than 1 machine.06:59
Guest98Let's say i have 2 machines. One of them is RPI4 and the other is Coral Dev Board. I have Yocto build, which is in separate repos for these.06:59
Guest98The meta-layers I use:06:59
Guest98RPi4: "meta-raspberrypi", "meta-openembedded", "poky", "meta-mylayer" are all dunfell version.06:59
Guest98Coral Dev Board : "meta-freescale", "meta-freescale-3rdparty", "meta-freescale-distro", "meta-openembedded", "poky", "meta-mylayer" are all zeus version.06:59
Guest981) If I want to combine them in one project, how should i do this? Does it make sense to combine two different versions into one project?06:59
Guest982) Let's say i have a recipe called "test.bb" and it contains separate configurations for both IMX(Coral Dev Board) and RPI4. Is it more logical to separating it as "test_imx.bb" and "test_rpi.bb" or is it reasonable to set up a structure like the one below in "test.bb"? The SRC, do_configure, do_install, do_compile functions used by RPI and IMX06:59
Guest98are different.06:59
Guest98if(machine==RPI4)06:59
Guest98{06:59
Guest98    do_configure()06:59
Guest98    do_compile()06:59
Guest98    do_install()06:59
Guest98}06:59
Guest98else if(machine==CoralDevBoard)06:59
Guest98{06:59
Guest98    do_configure()06:59
Guest98    do_compile()06:59
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto07:15
mckoanGuest98: please DO NOT post code here, use pastebin07:15
mckoanGuest98: the term project is misleading in this case. What does it mean?07:18
mckoanGuest98: a reposhould be associated to a meta layer, not to a 'project'07:18
mckoanGuest98: however I'd keep the two Yocto directories separate, one for RPI and one for Coral-IMX07:19
mckoanGuest98: about the recipe, the answer is the usual: depends :-D07:20
mckoanGuest98: if is a BSP related recipe I'd keep it different as "test_imx.bb" and "test_rpi.bb", if is software and something shareable I'd put everything in a singe one if it makes sense07:21
frosteyes1Guest98: Your should properly target something like 3 layers. A pure software / distro layer. A custom BSP layer for your RPi machine and a Custom BSP layer for your Coral Dev board.07:24
frosteyes1Your custom RPi4 bsp layer depend on meta-raspberrypi, and your Custom Coral BSP layer, depend on meta-freescale, etc...07:25
frosteyes1And your bsp layers should be able to work with core-image-minimal etc. So they don't depend on your meta-mylayer, but is allowed to have bbappend in a dynamic layer..07:26
*** Guest98 <Guest98!~Guest98@31.145.189.2> has quit IRC (Quit: Client closed)07:26
*** alejandr1 <alejandr1!~alejandro@user/alejandrohs> has quit IRC (Read error: Connection reset by peer)07:30
mcfriskHas anyone else seen issues with tar and pigz in latest master branch? On aarch64 I'm sometimes seeing corrupt tar files after pigz compression07:30
*** Guest98 <Guest98!~Guest98@31.145.189.2> has joined #yocto07:33
*** alejandr1 <alejandr1!~alejandro@user/alejandrohs> has joined #yocto07:34
LetoThe2ndyo dudX07:40
mckoanLetoThe2nd: hey07:41
RPmcfrisk: not on the autobuilder07:41
mcfriskRP: good to know. I'm seeing issues on target when creating large tar files to tmpfs and then extracting fails with "crc32 mismatch". I don't see any changes to pigz, zlib, glibc, or even gcc between poky a94ca827c2066b22c and 2942c7f2c16e5b. There are kernel changes and issue is only seen on some boards, sigh.07:45
*** gsalazar <gsalazar!~gsalazar@139.0.166.178.rev.vodafone.pt> has joined #yocto07:51
*** Guest98 <Guest98!~Guest98@31.145.189.2> has quit IRC (Quit: Client closed)07:52
RPmcfrisk: the last time I saw something like that it was a bug in the minicache handling in the kernel  on a pxa processor :(07:59
mcfriskRP: yea, could be something similar this time too. I suspect the kernel update from 6.1.20 to 6.1.25. I'll try to bisect..08:01
*** camus <camus!~Instantbi@58.246.136.203> has quit IRC (Read error: Connection reset by peer)08:09
*** camus1 <camus1!~Instantbi@58.246.136.203> has joined #yocto08:09
*** bps <bps!~bps@193.89.194.60> has joined #yocto08:09
*** camus1 is now known as camus08:11
*** Thorn <Thorn!~Thorn@user/thorn> has quit IRC (Ping timeout: 240 seconds)08:32
*** PobodysNerfect_ <PobodysNerfect_!~PobodysNe@84.214.105.47> has joined #yocto08:33
*** PobodysNerfect <PobodysNerfect!~PobodysNe@84.214.105.47> has quit IRC (Ping timeout: 268 seconds)08:36
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)08:39
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto08:39
*** pbergin <pbergin!~pbergin@c-799071d5.44006-0-69747578.bbcust.telenor.se> has joined #yocto08:41
*** davidinux <davidinux!~davidinux@194.147.59.133> has quit IRC (Quit: WeeChat 3.5)08:44
*** Guest98 <Guest98!~Guest98@31.145.189.2> has joined #yocto08:44
*** camus <camus!~Instantbi@58.246.136.203> has quit IRC (Quit: camus)08:49
*** camus <camus!~Instantbi@58.246.136.203> has joined #yocto08:50
*** camus <camus!~Instantbi@58.246.136.203> has quit IRC (Client Quit)08:50
*** camus <camus!~Instantbi@58.246.136.203> has joined #yocto08:51
*** camus <camus!~Instantbi@58.246.136.203> has quit IRC (Client Quit)08:51
*** camus <camus!~Instantbi@58.246.136.203> has joined #yocto08:54
*** davidinux <davidinux!~davidinux@81.22.36.243> has joined #yocto09:04
*** Thorn <Thorn!~Thorn@user/thorn> has joined #yocto09:06
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto09:06
rburtonkhem: thanks for the cpio patch :) hooray timezones, i can moan about something and then stop working, come back and a patch is merged :)09:22
*** ptsneves <ptsneves!~Thunderbi@84.47.155.82> has joined #yocto09:24
*** shoragan <shoragan!~shoragan@user/shoragan> has quit IRC (Remote host closed the connection)09:30
*** shoragan <shoragan!~shoragan@user/shoragan> has joined #yocto09:31
LetoThe2ndrburton: I thought you we busy doing dog walking to your new fav cafe anyways?09:33
rburtonhow do you know i'm not there now?09:33
rburton(i'm not, but it's a good day for it)09:33
LetoThe2ndrburton: as a general rule, I don't know anything.09:33
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 265 seconds)09:34
*** nemik <nemik!~nemik@76.74.126.42> has joined #yocto09:34
*** Guest98 <Guest98!~Guest98@31.145.189.2> has quit IRC (Quit: Client closed)09:36
*** nemik <nemik!~nemik@76.74.126.42> has quit IRC (Ping timeout: 265 seconds)09:39
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto09:39
*** d-s-e <d-s-e!~d.s.e@muedsl-82-207-224-080.citykom.de> has joined #yocto09:48
*** yolo <yolo!~xxiao@li1120-73.members.linode.com> has quit IRC (Ping timeout: 240 seconds)09:56
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto10:00
*** yolo <yolo!~xxiao@li1120-73.members.linode.com> has joined #yocto10:02
*** kpo <kpo!~kpo@87-206-161-246.dynamic.chello.pl> has joined #yocto10:03
*** kpo <kpo!~kpo@87-206-161-246.dynamic.chello.pl> has quit IRC (Client Quit)10:04
*** kpo <kpo!~kpo@87.206.161.246> has joined #yocto10:05
*** starblue <starblue!~juergen@dslb-094-221-183-040.094.221.pools.vodafone-ip.de> has quit IRC (Ping timeout: 265 seconds)10:13
*** starblue <starblue!~juergen@dslb-094-221-183-040.094.221.pools.vodafone-ip.de> has joined #yocto10:15
*** Guest98 <Guest98!~Guest98@31.145.189.2> has joined #yocto10:23
*** sgw <sgw!~swold@user/sgw> has quit IRC (Quit: Leaving.)10:28
*** yssh <yssh!~yssh@2401:4900:1b67:9e40:d11a:92ae:3297:7d6b> has joined #yocto10:28
*** sgw <sgw!~swold@user/sgw> has joined #yocto10:28
*** goliath <goliath!~goliath@user/goliath> has joined #yocto10:29
*** seninha <seninha!~seninha@user/seninha> has joined #yocto10:49
*** Thorn <Thorn!~Thorn@user/thorn> has quit IRC (Ping timeout: 240 seconds)11:15
*** d-s-e <d-s-e!~d.s.e@muedsl-82-207-224-080.citykom.de> has quit IRC (Ping timeout: 246 seconds)11:18
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat)11:25
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has joined #yocto11:26
*** Thorn <Thorn!~Thorn@user/thorn> has joined #yocto11:36
*** kpo <kpo!~kpo@87.206.161.246> has quit IRC (Remote host closed the connection)12:13
*** yssh <yssh!~yssh@2401:4900:1b67:9e40:d11a:92ae:3297:7d6b> has quit IRC (Ping timeout: 245 seconds)12:14
*** kpo <kpo!~kpo@87-206-161-246.dynamic.chello.pl> has joined #yocto12:15
*** kpo <kpo!~kpo@87-206-161-246.dynamic.chello.pl> has quit IRC (Client Quit)12:16
*** kpo <kpo!~kpo@87-206-161-246.dynamic.chello.pl> has joined #yocto12:17
Guest98Hi everyone, I asked a question today. After asking, my internet connection was gone and i dropped from the chat. I didn't see the replies. I'm asking the question again, sorry.12:23
Guest98I have a question mark in my mind about 2 topic. First one about combining the 2 different Yocto Project to under a single project. Second one, how a recipe is designed in a project with more than 1 machine.12:23
Guest98Let's say i have 2 machines. One of them is RPI4 and the other is Coral Dev Board. I have Yocto build, which is in separate repos for these.12:23
Guest98The meta-layers I use:12:23
Guest98RPI4: "meta-raspberrypi", "meta-openembedded", "poky", "meta-mylayer"(Common with CoralDevBoard) are all dunfell version.12:23
Guest98Coral Dev Board : "meta-freescale", "meta-freescale-3rdparty", "meta-freescale-distro", "meta-openembedded", "poky", "meta-mylayer"(Common with RPI4) are all zeus version.12:23
Guest981) If I want to combine them in one project, how should i do this? Does it make sense to combine two different versions into one project?12:23
Guest982) Let's say i have a recipe called "test.bb" and it contains separate configurations for both IMX(Coral Dev Board) and RPI4. Is it more logical to separating it as "test_imx.bb" and "test_rpi.bb" or is it reasonable to set up a structure like the one below in "test.bb"? The SRC, do_configure, do_install, do_compile functions used by RPI and IMX12:23
Guest98are different.12:23
Guest98pastebin.com/Ytj5mk7w12:23
Guest98If i try to build "test.bb" for two 2 machines, what type of problem can i encounter? For example, what happens if one more machine is added?12:23
rburtonif you want a recipe to be machine-specific that's fine (the kernel is, for example), just set PACKAGE_ARCH.12:28
rburtonits your choice how to structure this really.  if the recipes are 99% identical but ship slightly different files then you can set PACKAGE_ARCH and have a single recipe12:29
rburtonif the machine differences are so vast that you're reimplementing do_compile then write two recipes (foo-rpi, foo-coral, etc), set them as compatible with the specific machine, have them RPROVIDE a name like foo, and then you can just say IMAGE_INSTALL+=foo and everything just works12:30
LetoThe2ndor have your configuration mechanism accept a target platform, which you can just pass in as EXTRA_OECONF:append = " --machine=${MACHINE" for example12:31
LetoThe2nd(add the missing "}" please)12:33
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto12:40
*** d-s-e <d-s-e!~d.s.e@muedsl-82-207-224-080.citykom.de> has joined #yocto12:41
*** davidinux <davidinux!~davidinux@81.22.36.243> has quit IRC (Quit: WeeChat 3.5)12:41
*** transrights[m] <transrights[m]!~transrigh@2001:470:69fc:105::3:57c0> has left #yocto12:42
*** Guest98 <Guest98!~Guest98@31.145.189.2> has quit IRC (Quit: Client closed)12:43
*** Guest98 <Guest98!~Guest98@31.145.189.2> has joined #yocto12:43
Guest98rburton LetoThe2nd Thank you. How can i combine 2 different version Yocto projects? I wrote the layers included in the projects above. Can you give any ideas or suggestions regarding this?12:44
LetoThe2ndGuest98: you need to be much more precise as of what a "version" means for you.12:47
Guest98im talking about yocto project releases version. i use zeus for imx, dunfell for rpi. i want to combine them.12:49
*** Guest98 <Guest98!~Guest98@31.145.189.2> has quit IRC (Quit: Client closed)12:53
*** Guest98 <Guest98!~Guest98@31.145.189.2> has joined #yocto12:55
Guest98LetoThe2nd If you answered my question, i didn't see it. I dropped from chat again. I don't understand why this happens.12:56
LetoThe2ndGuest98: ah. that is usually not directly possible, it means having two separate branches.12:57
*** kscherer <kscherer!~kscherer@bras-base-otwaon1146w-grc-33-70-53-64-242.dsl.bell.ca> has joined #yocto12:57
*** Minvera <Minvera!~Minvera@user/Minvera> has joined #yocto12:57
*** Guest98 <Guest98!~Guest98@31.145.189.2> has quit IRC (Client Quit)12:58
tomzy_0[m]Guest98: I would say it is rather not possible but definitely not recommended. You would end with e.g. 2 versions of the same recipe so probably any bbappends would not apply. I would suggest to keep them separate.12:58
tomzy_0[m]But also interested what LetoThe2nd got to say12:59
LetoThe2ndtomzy_0[m]: in a real life situation you will just end up with so many parse errors that it is factually not possible, except for trivial projects13:00
LetoThe2ndthats at least my experience, and its definitely not recommended.13:00
tomzy_0[m]yeap, so two separate projects13:01
*** Guest98 <Guest98!~Guest98@31.145.189.2> has joined #yocto13:01
LetoThe2ndyou'll usually have two branches. or better, bump the zeus one to dunfell.13:04
*** suwako[m] <suwako[m]!~suwakohot@2001:470:69fc:105::3:4c2d> has left #yocto13:12
*** Guest98 <Guest98!~Guest98@31.145.189.2> has quit IRC (Quit: Client closed)13:16
*** Guest98 <Guest98!~Guest98@31.145.189.2> has joined #yocto13:20
Guest98LetoThe2nd thank you.13:21
LetoThe2ndGuest98: have fun!13:21
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 246 seconds)13:41
*** Thorn <Thorn!~Thorn@user/thorn> has quit IRC (Quit: Easy as 3.14159265358979323846...)13:42
*** Guest98 <Guest98!~Guest98@31.145.189.2> has quit IRC (Quit: Client closed)13:49
*** davidinux <davidinux!~davidinux@81.22.36.243> has joined #yocto13:56
*** sakoman <sakoman!~steve@dhcp-72-234-106-30.hawaiiantel.net> has joined #yocto13:57
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 240 seconds)13:58
*** nemik <nemik!~nemik@76.74.126.42> has joined #yocto13:58
*** nemik <nemik!~nemik@76.74.126.42> has quit IRC (Ping timeout: 240 seconds)14:03
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto14:03
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat)14:25
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has joined #yocto14:26
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)14:34
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto14:34
*** dmoseley <dmoseley!~dmoseley@d4-50-9-187.evv.wideopenwest.com> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)14:37
*** dmoseley <dmoseley!~dmoseley@d4-50-9-187.evv.wideopenwest.com> has joined #yocto14:38
d-s-eIs there a non-GPLv3 alternative to stdbuf from coreutils available?14:51
*** embetrix <embetrix!~embetrix@2a02:3102:8c10:a0:2016:a8d1:60ed:bcb5> has joined #yocto14:55
embetrixHi, does yocto support builds for cortex-M7 ? I enabled in my machine conf : require conf/machine/include/arm/armv7m/tune-cortexm7.inc and set TCLIBC = "musl" but the build breaks for several components : libffi & openssl14:57
*** mckoan is now known as mckoan|away15:02
LetoThe2ndembetrix: it is not an officially tested and supported target.15:16
rburtonembetrix: did you see my reply to your mail?15:17
embetrixrburton no I didn't get any mail15:37
rburtonare you ayoub.zaki@googlemail.com or is that just a huge coincidence15:38
embetrixyes that's me :-)15:38
rburtoncheck your email :)15:38
rburtonhttps://lists.yoctoproject.org/g/yocto/message/5998715:38
embetrixsorry it landed in the spam folder15:39
embetrixhere is my meta-layer : https://github.com/embetrix/meta-stm32f7x/15:39
embetrixit's very simple, I don't need openssl/libffi but somehow they get trigered for the Build, if I bbmask their receipe the native tools break15:41
rburtondon't mask, as you need the native recipes15:43
rburtonSKIP_RECIPE[openssl] = "1" should just refuse to build the target recipe15:44
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Quit: Leaving)15:45
embetrixrburton thanks that's a good hint to find out the chain of the dependencies :15:52
embetrixMissing or unbuildable dependency chain was: ['busybox', 'virtual/update-alternatives', 'update-alternatives-opkg', 'python3-compression', 'libffi']15:52
embetrixERROR: Required build target 'stm32f7x-initramfs-image' has no buildable providers.15:52
embetrixMissing or unbuildable dependency chain was: ['stm32f7x-initramfs-image', 'busybox', 'virtual/update-alternatives', 'update-alternatives-opkg', 'python3-compression', 'libffi']15:52
embetrixMissing or unbuildable dependency chain was: ['busybox', 'virtual/update-alternatives', 'update-alternatives-opkg', 'python3-fcntl', 'openssl']15:52
embetrixERROR: Required build target 'stm32f7x-initramfs-image' has no buildable providers.15:52
embetrixMissing or unbuildable dependency chain was: ['stm32f7x-initramfs-image', 'busybox', 'virtual/update-alternatives', 'update-alternatives-opkg', 'python3-fcntl', 'openssl']15:52
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has quit IRC (Remote host closed the connection)15:53
rburtontry PACKAGECONFIG:pn-opkg-utils:remove = "python"15:53
rburtonerm, PACKAGECONFIG:remove:pn-opkg-utils15:53
rburtonwe should split that tool out of opkg-utils so its as lean as possible15:54
embetrixthere seems to be some hard coded dependencies :15:56
embetrixarsing recipes: 100% |##############################################################################################################################################################################| Time: 0:00:0715:56
embetrixParsing of 885 .bb files complete (0 cached, 885 parsed). 1646 targets, 204 skipped, 0 masked, 0 errors.15:56
embetrixWARNING: No bb files in default matched BBFILE_PATTERN_yoctobsp '^/home/zaki/Projects/meta-stm32f7x/build/../layers/meta-yocto-bsp/'15:56
embetrixNOTE: Resolving any missing task queue dependencies15:56
embetrixERROR: Nothing PROVIDES 'openssl' (but /home/zaki/Projects/meta-stm32f7x/build/../layers/meta/recipes-devtools/python/python3_3.10.9.bb DEPENDS on or otherwise requires it)15:56
embetrixopenssl was skipped: Recipe will be skipped because: 115:56
embetrixNOTE: Runtime target 'python3-stringold' is unbuildable, removing...15:56
embetrixMissing or unbuildable dependency chain was: ['python3-stringold', 'openssl']15:56
embetrixNOTE: Runtime target 'update-alternatives-opkg' is unbuildable, removing...15:56
embetrixMissing or unbuildable dependency chain was: ['update-alternatives-opkg', 'python3-stringold', 'openssl']15:56
embetrixNOTE: Runtime target 'busybox' is unbuildable, removing...15:56
embetrixMissing or unbuildable dependency chain was: ['busybox', 'virtual/update-alternatives', 'update-alternatives-opkg', 'python3-stringold', 'openssl']15:56
embetrixERROR: Required build target 'stm32f7x-initramfs-image' has no buildable providers.15:56
embetrixMissing or unbuildable dependency chain was: ['stm32f7x-initramfs-image', 'busybox', 'virtual/update-alternatives', 'update-alternatives-opkg', 'python3-stringold', 'openssl']15:56
embetrixthe virtual/update-alternatives' cannot be disabled ? I don't need any package management15:56
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)15:57
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto15:59
rburtonhm why does it do that15:59
rburtoncomment out the call to ua_extend_depends() in update-alternatives.bbclass15:59
rburtonthat's adding a dependency on the target u-a package for some reason16:00
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving)16:00
embetrixI set the following:16:03
embetrixdef ua_extend_depends(d):16:03
embetrix    return True16:03
embetrixin update-alternatives.bbclass16:03
embetrixit went through :-)16:03
rburtonnot sure why a build would need a _target_ u-a16:03
embetrixI get now some conflicts in do_rootfs16:03
embetrixERROR: stm32f7x-initramfs-image-1.0-r0 do_rootfs: Unable to install packages. Command '/home/zaki/Projects/meta-stm32f7x/build/tmp/work/stm32f769_disco-poky-linux-musleabi/stm32f7x-initramfs-image/1.0-r0/recipe-sysroot-native/usr/bin/opkg --volatile-cache -f16:03
embetrix/home/zaki/Projects/meta-stm32f7x/build/tmp/work/stm32f769_disco-poky-linux-musleabi/stm32f7x-initramfs-image/1.0-r0/opkg.conf -t /home/zaki/Projects/meta-stm32f7x/build/tmp/work/stm32f769_disco-poky-linux-musleabi/stm32f7x-initramfs-image/1.0-r0/temp/ipktemp/ -o16:03
embetrix/home/zaki/Projects/meta-stm32f7x/build/tmp/work/stm32f769_disco-poky-linux-musleabi/stm32f7x-initramfs-image/1.0-r0/rootfs  --force_postinstall --prefer-arch-to-version   install busybox' returned 1:16:03
embetrix * Solver encountered 1 problem(s):16:03
embetrix * Problem 1/1:16:03
embetrix *   - conflicting requests16:03
embetrix *   - nothing provides update-alternatives-opkg needed by busybox-1.35.0-r0.cortexm716:03
embetrix *16:03
embetrix * Solution 1:16:03
embetrix *   - do not ask to install a package providing busybox16:04
embetrix * opkg_finalize_intercepts: Failed to open dir /home/zaki/Projects/meta-stm32f7x/build/tmp/work/stm32f769_disco-poky-linux-musleabi/stm32f7x-initramfs-image/1.0-r0/temp/ipktemp//opkg-CGAv04/opkg-intercept-rSF6KM: No such file or directory.16:04
embetrix * rm_r: Failed to open dir /home/zaki/Projects/meta-stm32f7x/build/tmp/work/stm32f769_disco-poky-linux-musleabi/stm32f7x-initramfs-image/1.0-r0/temp/ipktemp//opkg-CGAv04/opkg-intercept-rSF6KM: No such file or directory.16:04
embetrix * rm_r: Failed to open dir /home/zaki/Projects/meta-stm32f7x/build/tmp/work/stm32f769_disco-poky-linux-musleabi/stm32f7x-initramfs-image/1.0-r0/temp/ipktemp//opkg-CGAv04: No such file or directory.16:04
embetrixERROR: Logfile of failure stored in: /home/zaki/Projects/meta-stm32f7x/build/tmp/work/stm32f769_disco-poky-linux-musleabi/stm32f7x-initramfs-image/1.0-r0/temp/log.do_rootfs.212853616:04
embetrixERROR: Task (/home/zaki/Projects/meta-stm32f7x/build/../recipes-core/images/stm32f7x-initramfs-image.bb:do_rootfs) failed with exit code '1'16:04
embetrixNOTE: Tasks Summary: Attempted 1178 tasks of which 1168 didn't need to be rerun and 1 failed.16:04
*** rob_w <rob_w!~rob@2001:a61:6012:6901:dc56:77e9:c511:6170> has quit IRC (Quit: Leaving)16:05
rburtonoh right it depends on it to ensure its built for image time16:05
rburtonbut that's workaroundable16:05
rburtonok revert that16:05
rburtonwhat branch are you using?  the packageconfig on opkg-utils should have nuked the python dependencies16:06
*** ptsneves <ptsneves!~Thunderbi@84.47.155.82> has quit IRC (Ping timeout: 264 seconds)16:06
embetrixkirkstone16:06
rburtonbrute force: remove python from PACKAGECONFIG = "python update-alternatives" in opkg-utils_0.5.0.bb16:07
embetrixThanks that did it :-)16:09
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)16:09
embetrixI will create a bbappend for that in my layer16:09
embetrixrburton : thanks for your support16:09
*** thomasd13 <thomasd13!~thomas@DSL01.212.114.255.148.ip-pool.NEFkom.net> has quit IRC (Ping timeout: 240 seconds)16:11
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)16:18
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto16:18
*** bps <bps!~bps@user/bps> has quit IRC (Ping timeout: 256 seconds)16:20
*** embetrix <embetrix!~embetrix@2a02:3102:8c10:a0:2016:a8d1:60ed:bcb5> has quit IRC (Quit: Client closed)16:24
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat)16:27
dv_suppose that there's something wrong in a BSP layer, a regression that causes serious performance problems, and some git commit introduced this (that is, an older version had no such problems). the logical choice is to use git bisect to pinpoint what exact commit in the BSP layer caused the regression.16:36
dv_however, during bisect, the git head might go back. this can then lead to errors because bitbake sees that the versions of some recipes were reverted to older ones.16:36
*** zpfvo <zpfvo!~fvo@i59F5CECF.versanet.de> has quit IRC (Quit: Leaving.)16:37
dv_are there suggestions, best practices etc. for how to do a bisect in OE layers?16:37
dv_other than to wipe the entire build directory16:37
yoctonAt minimum you can disable the QA error about the version going backward16:39
dv_but if a version goes backwards, can this cause problems in the sstate cache for example? some stale states etc.?16:39
yoctonEach version has a different sstate cache element16:40
*** embetrix <embetrix!~embetrix@2a02:3102:8c10:a0:2016:a8d1:60ed:bcb5> has joined #yocto16:40
*** embetrix <embetrix!~embetrix@2a02:3102:8c10:a0:2016:a8d1:60ed:bcb5> has quit IRC (Client Quit)16:40
yoctonI used to have a project with a recipe going forward and back for some reason. Never had a problem with sstate (it even help by speeding up build in both old/new version)16:42
*** sgw <sgw!~swold@user/sgw> has quit IRC (Quit: Leaving.)16:44
*** sgw <sgw!~swold@user/sgw> has joined #yocto16:44
*** ptsneves <ptsneves!~Thunderbi@031011128008.dynamic-3-poz-k-0-2-0.vectranet.pl> has joined #yocto16:47
*** ptsneves <ptsneves!~Thunderbi@031011128008.dynamic-3-poz-k-0-2-0.vectranet.pl> has quit IRC (Ping timeout: 246 seconds)16:52
rburtondv_: disable the version check as yocton said, but otherwise you can reuse a build tree, definitely reuse sstate16:56
rburtoni've often done bisects on builds with git, just let bitbake clean up tmp as it needs to16:56
dv_would `ERROR_QA:remove = "version-going-backwards"` in `local.conf` do it?16:58
rburtonyes16:59
rburtonalso you need to run the bisect at the top of the git tree you're bisecting, but once you've init'd the build tree with recent releases you can cd anywhere and bitbake knows where the build is17:04
*** d-s-e <d-s-e!~d.s.e@muedsl-82-207-224-080.citykom.de> has quit IRC (Quit: Konversation terminated!)17:08
*** gsalazar <gsalazar!~gsalazar@139.0.166.178.rev.vodafone.pt> has quit IRC (Ping timeout: 240 seconds)17:24
*** Net147 <Net147!~Net147@user/net147> has quit IRC (Ping timeout: 260 seconds)17:28
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 264 seconds)17:34
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto17:35
*** florian_kc <florian_kc!~florian@78.48.55.213> has joined #yocto17:44
*** Net147 <Net147!~Net147@167-179-157-192.a7b39d.syd.nbn.aussiebb.net> has joined #yocto17:49
*** florian_kc <florian_kc!~florian@78.48.55.213> has quit IRC (Ping timeout: 240 seconds)18:11
*** bps <bps!~bps@user/bps> has joined #yocto18:16
*** dmoseley <dmoseley!~dmoseley@d4-50-9-187.evv.wideopenwest.com> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)18:23
*** dmoseley <dmoseley!~dmoseley@d4-50-9-187.evv.wideopenwest.com> has joined #yocto18:24
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat)18:35
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has joined #yocto18:36
*** florian_kc <florian_kc!~florian@78.48.55.213> has joined #yocto18:59
yolois there a 'global' repo or some index that I can search all possible recipes, for example I am looking for possible klib recipe before I write one from scratch, but could not find it: https://github.com/attractivechaos/klib19:24
JaMayolo: https://layers.openembedded.org/layerindex/branch/master/recipes/19:25
yologreat, thanks!!19:31
*** bps <bps!~bps@user/bps> has quit IRC (Ping timeout: 240 seconds)19:56
*** tgamblin <tgamblin!~tgamblin@cpe64777de11593-cm64777de11590.cpe.net.cable.rogers.com> has quit IRC (Quit: Leaving)19:59
*** dmoseley <dmoseley!~dmoseley@d4-50-9-187.evv.wideopenwest.com> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)20:06
*** dmoseley <dmoseley!~dmoseley@d4-50-9-187.evv.wideopenwest.com> has joined #yocto20:07
*** wkawka <wkawka!~wkawka@2a02:a31c:8240:e900:7910:5aeb:135a:8760> has joined #yocto20:34
*** dmoseley <dmoseley!~dmoseley@d4-50-9-187.evv.wideopenwest.com> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)20:34
*** rvignesh <rvignesh!~rvignesh@p54b3cea2.dip0.t-ipconnect.de> has joined #yocto20:35
*** dmoseley <dmoseley!~dmoseley@d4-50-9-187.evv.wideopenwest.com> has joined #yocto20:35
*** rvignesh <rvignesh!~rvignesh@p54b3cea2.dip0.t-ipconnect.de> has quit IRC (Client Quit)20:37
wkawkaHi, can I add somehow do_install:append only to specific package?20:37
wkawkaI have included php in my imafe and i want to add couple of lines within do install, but only for php-fpm package, php-native keeps failing because of this lines..20:39
*** rvignesh <rvignesh!~rvignesh@p54b3cea2.dip0.t-ipconnect.de> has joined #yocto20:39
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)20:39
*** rvignesh <rvignesh!~rvignesh@p54b3cea2.dip0.t-ipconnect.de> has left #yocto20:41
JaMawkawka: that question doesn't make much sense, you can use do_install:append:class-target to do something only in target build, but there is only one do_install and various files are then packaged into specific packages based on FILES variables20:44
*** bps <bps!~bps@80.71.142.18.ipv4.parknet.dk> has joined #yocto20:51
*** Guest39 <Guest39!~Guest39@2001:420:30a:4d04:4177:9ae3:a023:c176> has joined #yocto20:52
Guest39Hi All, I am trying to build kirkstone on  a centos7 VM and hitting an issue with dbus. The error message says "ERROR: dbus: useradd command did not succeed." so I tried running bitbake dbus and it gives the same error. I tried `BBDEBUG=1 bitbake dbus` command and i dont know what I am looking at. Can some one help me ? I only know basic knowledge20:56
Guest39about yocto20:56
*** PobodysNerfect_ <PobodysNerfect_!~PobodysNe@84.214.105.47> has quit IRC (Quit: Gone to sleep. ZZZzzz…)21:02
*** wyre <wyre!~wyre@user/wyre> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)21:02
*** wyre <wyre!~wyre@user/wyre> has joined #yocto21:04
*** wkawka <wkawka!~wkawka@2a02:a31c:8240:e900:7910:5aeb:135a:8760> has quit IRC (Quit: Client closed)21:20
*** frieder <frieder!~frieder@i577BE786.versanet.de> has quit IRC (Remote host closed the connection)21:37
*** pbergin <pbergin!~pbergin@c-799071d5.44006-0-69747578.bbcust.telenor.se> has quit IRC (Quit: Leaving)21:52
*** seninha <seninha!~seninha@user/seninha> has joined #yocto21:55
*** wkawka <wkawka!~wkawka@2a02:a31c:8240:e900:7910:5aeb:135a:8760> has joined #yocto22:04
*** wyre <wyre!~wyre@user/wyre> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)22:04
*** wyre <wyre!~wyre@user/wyre> has joined #yocto22:05
*** wyre <wyre!~wyre@user/wyre> has quit IRC (Read error: Connection reset by peer)22:06
*** wyre <wyre!~wyre@user/wyre> has joined #yocto22:07
*** pbsds <pbsds!~pbsds@84.20.102.95> has quit IRC (Ping timeout: 240 seconds)22:08
*** pbsds <pbsds!~pbsds@84.20.102.95> has joined #yocto22:09
*** wyre <wyre!~wyre@user/wyre> has quit IRC (Read error: Connection reset by peer)22:11
*** wyre <wyre!~wyre@user/wyre> has joined #yocto22:11
*** wyre <wyre!~wyre@user/wyre> has quit IRC (Remote host closed the connection)22:12
*** wyre <wyre!~wyre@user/wyre> has joined #yocto22:13
*** dmoseley <dmoseley!~dmoseley@d4-50-9-187.evv.wideopenwest.com> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)22:54
*** dmoseley <dmoseley!~dmoseley@d4-50-9-187.evv.wideopenwest.com> has joined #yocto22:55
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Ping timeout: 240 seconds)23:00
*** Guest39 <Guest39!~Guest39@2001:420:30a:4d04:4177:9ae3:a023:c176> has quit IRC (Ping timeout: 245 seconds)23:01
*** wkawka <wkawka!~wkawka@2a02:a31c:8240:e900:7910:5aeb:135a:8760> has quit IRC (Quit: Client closed)23:23
*** bps <bps!~bps@user/bps> has quit IRC (Ping timeout: 246 seconds)23:51
*** florian_kc <florian_kc!~florian@78.48.55.213> has quit IRC (Ping timeout: 240 seconds)23:52

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