Monday, 2024-08-12

*** jsbronder <jsbronder!jsbronder@user/jbronder> has quit IRC (Ping timeout: 252 seconds)00:16
*** jsbronder <jsbronder!~jsbronder@user/jbronder> has joined #yocto00:18
*** reatmon_ <reatmon_!~reatmon@192.91.75.29> has quit IRC (Remote host closed the connection)00:20
*** reatmon_ <reatmon_!~reatmon@192.91.75.30> has joined #yocto00:21
*** fray <fray!~fray@70.99.78.136> has quit IRC (Remote host closed the connection)00:25
*** amitk_ <amitk_!~amit@58.84.61.168> has quit IRC (Ping timeout: 248 seconds)01:14
*** jclsn <jclsn!~jclsn@2a04:4540:6506:5300:2ce:39ff:fecf:efcd> has quit IRC (Ping timeout: 272 seconds)01:43
*** jclsn <jclsn!~jclsn@2a04:4540:653d:d600:2ce:39ff:fecf:efcd> has joined #yocto01:45
*** sgw <sgw!~swold@user/sgw> has joined #yocto02:00
*** Articulus <Articulus!~Articulus@2601:642:4900:741:16ac:60ff:fed8:386b> has joined #yocto02:24
*** rber__ <rber__!~rber|res@2001:4bb8:198:a6cd:84a:db9e:33a9:6a96> has quit IRC (Ping timeout: 248 seconds)03:13
*** rber|res <rber|res!~rber|res@2001:4bb8:150:32ca:e8a0:490a:1f14:cd36> has joined #yocto03:16
*** Notgnoshi <Notgnoshi!~quassel@184-83-174-55-dynamic.midco.net> has joined #yocto03:52
*** mbulut <mbulut!~mbulut@31.18.142.72> has joined #yocto04:47
*** ablu <ablu!~m-bfyrfh@user/Ablu> has quit IRC (Ping timeout: 260 seconds)04:58
*** ablu <ablu!~m-bfyrfh@user/Ablu> has joined #yocto05:00
*** xmn <xmn!~xmn@2600:4040:9398:a200:5dfd:1104:8752:442c> has quit IRC (Quit: ZZZzzz…)05:04
*** xmn <xmn!~xmn@2600:4040:9398:a200:5dfd:1104:8752:442c> has joined #yocto05:06
*** goliath <goliath!~goliath@user/goliath> has joined #yocto05:13
*** amitk <amitk!~amit@58.84.61.168> has joined #yocto05:14
*** BenBE <BenBE!~benbe@user/benbe> has quit IRC (Ping timeout: 260 seconds)05:41
*** rfuentess <rfuentess!~rfuentess@lfbn-lyo-1-1566-5.w90-52.abo.wanadoo.fr> has joined #yocto05:57
*** eminboydak <eminboydak!~eminboyda@user/eminboydak> has joined #yocto06:00
*** ray-san3 <ray-san3!~ray-san@195.50.168.194> has joined #yocto06:01
*** xmn <xmn!~xmn@2600:4040:9398:a200:5dfd:1104:8752:442c> has quit IRC (Ping timeout: 260 seconds)06:29
*** Guest48 <Guest48!~Guest48@157.32.45.240> has joined #yocto06:31
*** BenBE <BenBE!~benbe@user/benbe> has joined #yocto06:35
*** xmn <xmn!~xmn@2600:4040:9398:a200:806f:ae0c:ce89:5920> has joined #yocto06:38
*** mvlad <mvlad!~mvlad@2a02:2f05:810e:b200:e88e:21ff:fe65:be18> has joined #yocto06:41
Guest48Hi Everyone, just wanted to ask that from a packagegroup if i want to remove a single packageso that it doesn't get built in the final image is this the correct way to do it ?06:45
Guest48RDEPENDS:packagegroup-name:remove = "package-name"06:45
Guest48i am trying to do add this from local.conf as i dont want to remove it permanently and just want rootfs to be created once without the package06:45
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.113> has quit IRC (Quit: Konversation terminated!)06:45
*** nerdboy <nerdboy!~nerdboy@gentoo/developer/nerdboy> has quit IRC (Ping timeout: 258 seconds)06:46
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.113> has joined #yocto06:46
*** xmn_ <xmn_!~xmn@2600:4040:9398:a200:f03f:5618:5ce8:deef> has joined #yocto06:51
*** Guest48 <Guest48!~Guest48@157.32.45.240> has quit IRC (Ping timeout: 256 seconds)06:52
eminboydakHello, I am using Yocto to create the rootfs and the kernel provided by the board manufacturer. Wi-Fi works on the default Debian rootfs but not on the rootfs I created with Yocto. I reached out to the company about this issue, and they provided me with a kernel module file named "bcmdhd.ko" and instructed me to enable the module in Yocto. I want06:52
eminboydakto enable the "bcmdhd" module in Yocto, but I can't find the proper solution. Is there anyone here who knows how to do this?06:52
*** xmn <xmn!~xmn@2600:4040:9398:a200:806f:ae0c:ce89:5920> has quit IRC (Ping timeout: 260 seconds)06:53
*** rynofinn____ <rynofinn____!sid362734@id-362734.lymington.irccloud.com> has quit IRC (Ping timeout: 260 seconds)06:56
*** rynofinn____ <rynofinn____!sid362734@id-362734.lymington.irccloud.com> has joined #yocto06:57
*** armpit <armpit!sid501830@id-501830.uxbridge.irccloud.com> has quit IRC (Ping timeout: 260 seconds)06:57
*** madisox_ <madisox_!sid453692@id-453692.ilkley.irccloud.com> has quit IRC (Ping timeout: 260 seconds)06:57
*** madisox_ <madisox_!sid453692@id-453692.ilkley.irccloud.com> has joined #yocto06:57
*** armpit <armpit!sid501830@id-501830.uxbridge.irccloud.com> has joined #yocto06:57
*** stgloor <stgloor!~stgl@2a03:b0c0:3:d0::cad:a001> has joined #yocto06:57
*** zpfvo <zpfvo!~fvo@118-59-142-46.pool.kielnet.net> has joined #yocto06:57
*** LetoThe2nd <LetoThe2nd!sid453638@id-453638.uxbridge.irccloud.com> has quit IRC (Ping timeout: 260 seconds)06:58
*** CosmicPenguin <CosmicPenguin!sid489106@id-489106.uxbridge.irccloud.com> has quit IRC (Ping timeout: 260 seconds)06:58
*** Crofton <Crofton!sid401373@id-401373.lymington.irccloud.com> has quit IRC (Ping timeout: 260 seconds)06:58
*** nerdboy <nerdboy!~nerdboy@47.143.129.197> has joined #yocto06:58
*** khimaros <khimaros!~khimaros@2a01:4f9:c012:6c55::1> has quit IRC (Ping timeout: 260 seconds)06:58
*** NishanthMenon <NishanthMenon!sid138049@id-138049.uxbridge.irccloud.com> has quit IRC (Ping timeout: 260 seconds)06:58
*** stgl <stgl!~stgl@2a03:b0c0:3:d0::cad:a001> has quit IRC (Ping timeout: 260 seconds)06:59
*** stgloor is now known as stgl06:59
*** LetoThe2nd <LetoThe2nd!sid453638@id-453638.uxbridge.irccloud.com> has joined #yocto07:00
*** khimaros <khimaros!~khimaros@2a01:4f9:c012:6c55::1> has joined #yocto07:00
*** NishanthMenon <NishanthMenon!sid138049@id-138049.uxbridge.irccloud.com> has joined #yocto07:00
*** Crofton <Crofton!sid401373@id-401373.lymington.irccloud.com> has joined #yocto07:00
*** CosmicPenguin <CosmicPenguin!sid489106@id-489106.uxbridge.irccloud.com> has joined #yocto07:01
*** xmn_ <xmn_!~xmn@2600:4040:9398:a200:f03f:5618:5ce8:deef> has quit IRC (Ping timeout: 252 seconds)07:02
*** Kubu_work <Kubu_work!~kubu@2a01cb05949d5800e3ef2d7a4131071f.ipv6.abo.wanadoo.fr> has joined #yocto07:16
*** wmills__ <wmills__!~wmills@pool-72-83-14-124.washdc.fios.verizon.net> has joined #yocto07:20
*** kanavin <kanavin!~Alexander@2a02:2454:2a7:1800:ea0:a5be:afd:9683> has quit IRC (Remote host closed the connection)07:21
*** wmills_ <wmills_!~wmills@pool-72-83-14-124.washdc.fios.verizon.net> has quit IRC (Ping timeout: 245 seconds)07:22
*** Thorn <Thorn!~Thorn@user/thorn> has quit IRC (Quit: If at first you don't succeed, skydiving is not for you.)07:28
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto07:31
*** frieder <frieder!~frieder@i4DF67AE6.pool.tripleplugandplay.com> has joined #yocto07:33
*** kanavin <kanavin!~Alexander@2a02:2454:2a7:1800:ea0:a5be:afd:9683> has joined #yocto07:34
*** olani <olani!~olani@wlan-gw.se.axis.com> has joined #yocto07:35
*** viric <viric!~viric@mail.viric.name> has joined #yocto07:38
viricHello07:39
viricWhy the devshell has to start inside a terminal emulator?07:39
viricCannot it just be a child shell in the same terminal?07:39
abelloniI guess you can use the OE_TERMINAL variable07:42
*** florian_kc <florian_kc!~florian@dynamic-093-131-052-209.93.131.pool.telefonica.de> has joined #yocto07:48
*** florian_kc <florian_kc!~florian@dynamic-093-131-052-209.93.131.pool.telefonica.de> has quit IRC (Ping timeout: 264 seconds)07:55
*** eminboydak <eminboydak!~eminboyda@user/eminboydak> has quit IRC (Ping timeout: 256 seconds)08:06
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto08:27
*** Haxxa <Haxxa!~Haxxa@116.255.4.123> has quit IRC (Quit: Haxxa flies away.)08:28
*** deribaucourt <deribaucourt!~ederibauc@80-15-101-118.ftth.fr.orangecustomers.net> has joined #yocto08:33
*** ederibaucourt <ederibaucourt!~ederibauc@80-15-101-118.ftth.fr.orangecustomers.net> has quit IRC (Ping timeout: 252 seconds)08:36
kanavinviric, it probably can, I suppose you can study the code that starts it and propose improvements08:42
viricabelloni: I think OE_TERMINAL doesn't support any case without a new emulator08:45
virickanavin: ok, I'll have a look.08:45
viricto me it was so evident that the easiest would be no emulator that I thought maybe I was missing something obvious08:46
kanavinviric, I suspect the issue is that the devshell has to run under pseudo (fake root environment which is a LD_PRELOAD hack)08:46
kanavinbut how that ends up needing a new terminal, I don't know08:47
viricI think that the problem is that "bitbake" keeps on printing a progress bar in the normal terminal08:48
viricand then it would print over the devshell08:48
viricthe fake root environment thing has nothing to do with a new terminal or not.08:48
viricwhen one uses a devshell, for a cmake project, "mkdir b; cd b; cmake .." fails.08:56
viricWhat else do I have to prepare, between devshell + the call to cmake?08:57
kanavinviric, I suppose do_configure?08:59
kanavinit's possible there are cmake-specific tweaks in do_configure, and devshell+bare cmake won't run them09:00
virichm but that will use the build directory from tmp/work, not any I want, right?09:00
kanavinI mean, there are no promises that it will work. Only that you're getting an environemnt that replicates what the tasks are executed in, but the tasks may need to do additional things before invoking the underlying build system09:00
*** Haxxa <Haxxa!~Haxxa@116.255.4.123> has joined #yocto09:00
viricand how can I call do_configure from the devshell?09:01
kanavinviric, and tbh, you'll be better served by devtool modify from the looks of it09:01
viricI'm using also devtool modify09:01
viricbut I wanted the build env09:01
kanavinviric, run temp/run.do_configure09:02
viricso if I used devtool modify, I should not be using devshell to build?09:02
kanavinno, you just run bitbake as usual09:03
viricoh but that's very slow09:03
kanavinwhy?09:04
kanavinit will run incremental builds from workspace09:04
viricit takes 1min to run bitbake, loading cache, init tasks,09:04
viricit's the bitbake python thing that takes ages09:04
viric1 minute is ages, compared to 1 second of a compile error by just calling "make", I mean09:04
kanavinthen you can use devshell without devtool09:05
viricexactly. Then I have to find how to make cmake find the sysroot09:05
*** Shaun <Shaun!~shaun@user/shaun> has quit IRC (Ping timeout: 252 seconds)09:05
kanavinyou can run task scripts from temp/09:05
kanavinrun.do_configure, run.do_compile etc09:06
viricyes, now that you said I remember it09:06
viricbut those are very hardcoded to the output paths & config options there set.09:06
kanavinyeah. but you should really look into why bitbake is slow for you. it shouldn't take a whole minute09:07
viricI only need cmake to find the sysroot, nothing else. I'll try to figure it out from the configure script09:07
viricInitialising tasks: 100% ... Time: 0:02:0209:07
viricThat's in "devtool build"09:07
viricAttempted 2212 tasks of which 2205 didn't need to be rerun09:07
kanavinyou don't have to use devtool build, 'bitbake recipe' is fine09:08
viricI guess it's the same thing. I mean it took 2 minutes09:08
kanavinthat is excessive09:08
viricI'm using the cache, so I'm already skipping the "parsing recipes" time09:08
kanavinbut we've tweaked a few things in bitbake master that improve task handling times. Maybe you're hitting those issues. What layers are enabled in your setup other than meta/?09:17
RPviric: the challenge with tasks is that multiple tasks can happen at once. For that reason any shell task needs to be via a terminal multiplexer09:18
RPviric: BB_SERVER_TIMEOUT = "300" may help with reload time09:19
*** ptsneves <ptsneves!~Thunderbi@public-gprs216641.centertel.pl> has joined #yocto09:20
viricRP: I tried that and it didn't seem a big improvement. Let me try.09:27
*** Jones42 <Jones42!~Jones42@user/Jones42> has joined #yocto09:32
kanavinviric, can you check if it is still slow in a plain poky environment (no other layers)?09:38
kanavinpick any cmake-based recipe in oe-core09:38
viricI was distracted but I'm checking it now09:39
viric'time bitbake recipe', twice in a row, with the server timeout 300, 1m22s each09:42
viricwould bitbake say anything about succesfully connecting to a server?09:43
viricbitbake-cookerdaemon.log reports about clients connected.09:44
viricI don't see any advantage with the 'server' being alive09:44
*** ptsneves <ptsneves!~Thunderbi@public-gprs216641.centertel.pl> has quit IRC (Ping timeout: 252 seconds)09:45
RPviric: it would depend on what was using the time, as I said, it may have helped. I'm not entirely sure why your situation is so slow :/09:48
viricof 1m30s, 1m05s are "Initialising tasks"09:49
viric1 second Loading cache, 3 seconds Parsing recipes09:49
RPlots of layers and a complex dependency chain?09:50
viricIt's 6076 tasks, none had to be rerun. Maybe it's ok for that amount of tasks?09:50
viric3325 bb files, 4947 targets09:50
viricI have always seen these times so I don't have other expectations09:51
RPI guess it depends on the machine you're running it on too. It is hard to say what is expected :/09:51
viricXeon E-2276 2.8GHz   (but peaks at ~4GHz with that turbo thing)09:52
viricE-2276M sorry09:52
viricIt sounded like you expected 3 seconds09:52
RPviric: I've have thought 30s rather than more like 9009:53
viricah, 30s vs 90s may be that you have a faster cpu09:54
viricor less tasks09:54
viricI picked the -DCMAKE_TOOLCHAIN_FILE=.. line from the do_configure and that seems enough09:56
*** enok <enok!~Thunderbi@185.102.18.74> has joined #yocto10:02
*** eminboydak <eminboydak!~eminboyda@user/eminboydak> has joined #yocto10:07
*** enok <enok!~Thunderbi@185.102.18.74> has quit IRC (Ping timeout: 248 seconds)10:09
*** Shaun <Shaun!~shaun@user/shaun> has joined #yocto10:26
*** zpfvo <zpfvo!~fvo@118-59-142-46.pool.kielnet.net> has quit IRC (Ping timeout: 252 seconds)10:57
*** pvogelaar <pvogelaar!~pvogelaar@p200300efdf19e300127b44fffe802df7.dip0.t-ipconnect.de> has joined #yocto11:01
*** Din <Din!~Din@201.20.110.242> has joined #yocto11:02
*** Din <Din!~Din@201.20.110.242> has quit IRC (Client Quit)11:02
*** zpfvo <zpfvo!~fvo@i59F5CCDD.versanet.de> has joined #yocto11:11
*** ehussain <ehussain!~Thunderbi@72.255.51.71> has joined #yocto11:16
*** Starfoxxes <Starfoxxes!~Starfoxxe@2a02:8071:65c3:7240:7a06:838d:5b3f:8daf> has joined #yocto11:26
*** adrianp <adrianp!~adrianp@ns-02.wenglor.com> has joined #yocto11:29
*** jstephan_ <jstephan_!~jstephan@build4.baylibre.com> has quit IRC (Remote host closed the connection)11:29
adrianphello, in ubuntu there is /usr/share/docs/<package-name>/copyright11:30
adrianphow can i obtain this copyright on yocto built deb package?11:30
*** michael_e <michael_e!~michael_e@user/michael-e:30278> has joined #yocto11:41
*** xmn <xmn!~xmn@2600:4040:9398:a200:fc46:3c68:63d1:9e85> has joined #yocto11:51
*** flom84 <flom84!~flom84@user/flom84> has joined #yocto11:52
*** enok <enok!~Thunderbi@185.102.18.74> has joined #yocto12:16
*** enok <enok!~Thunderbi@185.102.18.74> has quit IRC (Ping timeout: 260 seconds)12:29
*** adrianp <adrianp!~adrianp@ns-02.wenglor.com> has quit IRC (Quit: Client closed)12:31
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto12:44
*** wicki4 <wicki4!~wicki@user/wicki> has joined #yocto13:07
*** eminboydak <eminboydak!~eminboyda@user/eminboydak> has quit IRC (Quit: Client closed)13:09
*** wicki4 <wicki4!~wicki@user/wicki> has quit IRC (Client Quit)13:10
*** wicki4 <wicki4!~wicki@user/wicki> has joined #yocto13:10
*** Perflosopher1 <Perflosopher1!~perflosop@71-211-253-58.hlrn.qwest.net> has joined #yocto13:15
*** Perflosopher <Perflosopher!~perflosop@71-211-227-77.hlrn.qwest.net> has quit IRC (Ping timeout: 248 seconds)13:16
*** Perflosopher1 is now known as Perflosopher13:16
*** Minvera <Minvera!~Minvera@user/Minvera> has joined #yocto13:17
*** wicki4 <wicki4!~wicki@user/wicki> has quit IRC (Quit: The Lounge - https://thelounge.chat)13:33
*** wicki4 <wicki4!~wicki@user/wicki> has joined #yocto13:33
*** wicki4 <wicki4!~wicki@user/wicki> has quit IRC (Quit: The Lounge - https://thelounge.chat)13:40
*** xmn <xmn!~xmn@2600:4040:9398:a200:fc46:3c68:63d1:9e85> has quit IRC (Ping timeout: 260 seconds)13:52
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Quit: jmiehe)13:53
*** flom84 <flom84!~flom84@user/flom84> has quit IRC (Ping timeout: 244 seconds)13:56
*** xmn <xmn!~xmn@pool-108-46-142-76.nycmny.fios.verizon.net> has joined #yocto14:04
*** dmoseley <dmoseley!~dmoseley@129.222.254.182> has quit IRC (Quit: ZNC 1.9.1 - https://znc.in)14:06
*** michael_e <michael_e!~michael_e@user/michael-e:30278> has quit IRC (Quit: Client closed)14:09
*** dmoseley <dmoseley!~dmoseley@129.222.254.182> has joined #yocto14:10
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat)14:10
*** ehussain <ehussain!~Thunderbi@72.255.51.71> has quit IRC (Quit: ehussain)14:12
*** flom84 <flom84!~flom84@user/flom84> has joined #yocto14:21
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)14:30
*** fray <fray!~fray@70.99.78.136> has joined #yocto14:30
*** wicki4 <wicki4!~wicki@user/wicki> has joined #yocto14:48
*** BenBE <BenBE!~benbe@user/benbe> has quit IRC (Ping timeout: 248 seconds)14:49
jdiezhow do I tell bitbake to build the RDEPENDS packages in addition to its DEPENDs?14:56
*** Jones42 <Jones42!~Jones42@user/Jones42> has quit IRC (Ping timeout: 260 seconds)14:56
jdiezi.e. I want to put these packages in an index: a DEPENDS on a-build-dep, a RDEPENDS on b; `bitbake a` results in `a` and `a-build-dep` being built14:57
*** florian_kc <florian_kc!~florian@dynamic-093-131-052-209.93.131.pool.telefonica.de> has joined #yocto14:58
jdiez... but I also need `b` to be built so it can be downloaded on the target later14:58
*** florian_kc <florian_kc!~florian@dynamic-093-131-052-209.93.131.pool.telefonica.de> has quit IRC (Client Quit)15:00
jdiezmaybe `bitbake -c world a`?15:00
*** florian <florian!~florian@dynamic-093-131-052-209.93.131.pool.telefonica.de> has joined #yocto15:01
KanjiMonsterjdiez: bitbake --runall=do_package_write_ipk a15:21
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Quit: Leaving)15:25
*** tgamblin_ is now known as tgamblin15:32
*** goliath <goliath!~goliath@user/goliath> has joined #yocto15:38
*** jmd` <jmd`!~user@2001:a61:2a51:1801:edcb:9e4c:3259:2a73> has joined #yocto15:47
*** jmd` <jmd`!~user@2001:a61:2a51:1801:edcb:9e4c:3259:2a73> has quit IRC (Remote host closed the connection)15:49
vvnIf I want to create a image for my build host (x86-64) that I can use with Docker, should I write a custom image recipe which inherits container-host?15:49
vvnI'm not sure how host containers are supposed to be created with meta-virtualization15:49
*** jmd` <jmd`!~user@2001:a61:2a51:1801:edcb:9e4c:3259:2a73> has joined #yocto15:50
*** rfuentess <rfuentess!~rfuentess@lfbn-lyo-1-1566-5.w90-52.abo.wanadoo.fr> has quit IRC (Remote host closed the connection)16:20
*** Kubu_work <Kubu_work!~kubu@2a01cb05949d5800e3ef2d7a4131071f.ipv6.abo.wanadoo.fr> has quit IRC (Quit: Leaving.)16:20
*** zpfvo <zpfvo!~fvo@i59F5CCDD.versanet.de> has quit IRC (Quit: Leaving.)16:20
*** frieder <frieder!~frieder@i4DF67AE6.pool.tripleplugandplay.com> has quit IRC (Remote host closed the connection)16:26
vvnAlso is there a mechanism to set the preferred network manager? i.e. systemd-networkd, connman or networkmanager?16:42
*** BenBE <BenBE!~benbe@user/benbe> has joined #yocto16:51
flom84@vvn you can find here an example how to setup systemd-networkd: https://hub.mender.io/t/how-to-configure-networking-using-systemd-in-yocto-project/109717:09
flom84for connman or networkmanager, there are recipes in yocto that you can install and configure as you see fit17:13
flom84i dont recall if there is a "virtual" network manager variable that you can set with your preferred manager...therefore its just installing and configuring one of them17:15
*** bhstalel <bhstalel!~bhstalel@196.224.140.155> has joined #yocto17:18
vvnyep that was my point, I think setting PREFERRED_PROVIDER_virtual/networkmanager would make sense (even though they are not technically different implementation of the same API)17:21
flom84@vvn for container images...probably you want something similar to this examples from meta-virtualization: https://git.yoctoproject.org/meta-virtualization/tree/recipes-demo/images17:23
vvnI'm confused whether it is a container image intended for embedding into an embedded system, or if it is an host container image, or if it actually doesn't matter17:25
flom84containers can run anywhere...host, target17:26
flom84i dont think it matters here17:26
vvnI'm looking for a complete example for an host container, as I know it requires more config to set the machine (qemux86-64 I presume) as well as PREFERRED_PROVIDER_virtual/kernel = "linux-dummy" I guess17:26
*** florian <florian!~florian@dynamic-093-131-052-209.93.131.pool.telefonica.de> has quit IRC (Ping timeout: 244 seconds)17:27
zeddiivvn. There's no support for host containers. I actually have a feature about that, which I work on periodically, but with architecture mismatches, and kernel versions, etc, it is not easy to do generally17:27
vvnzeddii: I understand, it might not be fully portable, but it should be fairly easy to achieve and run on a relatively similar host, isn't it?17:29
zeddiisure. anything is possible, but I can't do half-support, it needs to be complete.17:30
zeddiiand not for a particular container runtime, etc, etc.17:31
vvnI understand that, it makes sense17:31
zeddiithe same way that we don't have every recipe as a -native variant.17:31
vvnIn the meantime, how can I test/contribute that?17:31
zeddiiit would be done in meta-virt, and really, there's no simple way to contribute that. it is very involved. and it is something that I've got bits and pieces done already.17:32
vvn(hum that makes me think that having the ability to build images with a -native suffix, e.g. core-image-base-native looks quite intuitive)17:32
zeddiibut it is coupled to some cross-container install parts that I need to complete for the upcoming release.17:32
vvnI see17:33
vvndo you have an upstream reference for the required pieces that I can try?17:33
vvnthe closest I guess would be a multiconfig setting MACHINE, PREFERRED_PROVIDER_virtual/kernel and the IMAGE_FSTYPES17:34
zeddiimy WIP stuff is scattered across about 4 development machines. not until I get the cross container bits pushed to meta-virt is the oci container creation flexible enough to even try a -native OCI container.17:34
vvnare you recommending to not even try this?17:35
zeddiiI mean, you can just build an OCI container from meta-virt that matches your host architecture. Head into deploy, jump into it with runc and you'll have some parts work for sure.17:36
flom84@vvn i have integrated a bunch of docker container images in a project i have worked in the past. the target architecture was x86_64. I did something similar with what is presented here: https://blog.savoirfairelinux.com/en-ca/2020/integrating-container-image-in-yocto/17:37
zeddiibut there's all sorts of host configuration, networking issues, security tweaks, different container runtimes, and integration with something that looks like "runqemu" to get the feature fully working. Which is the parts that I'm working on once summer ends and  I'm back full time.17:37
vvnI have to valid usecases for this, one is providing a light image for hardware-agnostic application stacks (so that one can run with docker on a laptop instead rather than needed a development board) and the second is providing a development environment for each middleware application, x86-64 being one of them (so that these apps can optionally cross-compile in their own CI pipelines before17:38
vvntriggering a whole yocto build)17:38
vvns/to/two/17:39
*** bhstalel <bhstalel!~bhstalel@196.224.140.155> has quit IRC (Quit: Client closed)17:39
flom84for CI pipeline...should you use yocto SDK? curious why you need an yocto image to be used for others to do develop17:40
vvnthe sdk is the default option for it indeed17:42
*** florian <florian!~florian@dynamic-093-131-052-209.93.131.pool.telefonica.de> has joined #yocto17:43
vvnzeddii: thanks I will try that. I am still confused by the container-host.bbclass. Am I supposed to use that?17:45
jdiezvvn: i also want to build container images as a base for application development. I've tried the container classes in meta-virtualization with mixed success. in theory, the only thing that is different when building a rootfs for a container is that you don't need the kernel/bootloader - and you want an extra build step where you take the rootfs and turn it into an OCI image17:47
jdiezvvn: see also this example of a build container image https://github.com/konsulko/meta-container-demo/blob/master/recipes-core/images/build-container.bb17:47
zeddiithat's for a target image running as a container-host.17:47
jdieznot necessarily17:48
zeddiijdiez, I'17:48
zeddiiI wasn't answering your question17:48
jdiezoh sorry17:48
zeddiibut if you had "mixed success" but have never mentioned it on meta-virt ...17:48
jdiezi'm assuming the mixed success is due to me doing something wrong, that's why I haven't mentioned anywhere17:49
jdiezKanjiMonster: that worked, thanks a lot!17:51
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)18:01
vvnzeddii: just to make sure I understand and don't mix the terminology here, container-host refers to what I want to implement, i.e. a container image runnable on the build host (well, "x86-64"), correct?18:11
jdiezvvn: container-host is for running container images on a target18:14
*** flom84 <flom84!~flom84@user/flom84> has quit IRC (Quit: Leaving)18:14
vvnhaaa I see, it makes more sense18:15
vvnsimilar to systemd-container in order to add support for nspawn and such18:15
*** flom84 <flom84!~flom84@user/flom84> has joined #yocto18:21
*** wak <wak!~wkenningt@2001:19f0:ac01:40f:5400:4ff:fe7c:68e6> has quit IRC (Quit: ZNC - https://znc.in)18:36
*** wak <wak!~wkenningt@2001:19f0:ac01:40f:5400:4ff:fe7c:68e6> has joined #yocto18:36
*** goliath <goliath!~goliath@user/goliath> has joined #yocto18:37
*** khem <khem!khem@2600:3c02::f03c:93ff:fe83:edf2> has quit IRC (Quit: WeeChat 4.3.5)18:54
*** amitk <amitk!~amit@58.84.61.168> has quit IRC (Ping timeout: 245 seconds)19:01
*** khem <khem!khem@2600:3c02::f03c:93ff:fe83:edf2> has joined #yocto19:11
*** florian <florian!~florian@dynamic-093-131-052-209.93.131.pool.telefonica.de> has quit IRC (Ping timeout: 248 seconds)19:16
*** mbulut <mbulut!~mbulut@31.18.142.72> has quit IRC (Ping timeout: 252 seconds)19:23
*** jmd` <jmd`!~user@2001:a61:2a51:1801:edcb:9e4c:3259:2a73> has left #yocto (ERC 5.4 (IRC client for GNU Emacs 28.2))19:25
*** Starfoxxes <Starfoxxes!~Starfoxxe@2a02:8071:65c3:7240:7a06:838d:5b3f:8daf> has quit IRC (Remote host closed the connection)19:36
*** florian <florian!~florian@dynamic-093-131-052-209.93.131.pool.telefonica.de> has joined #yocto19:42
vvnactually can systemd-networkd resides beside networkmanager, or they will conflict? (if systemd-networkd is disabled)19:42
*** mbulut <mbulut!~mbulut@ip1f128e48.dynamic.kabel-deutschland.de> has joined #yocto19:55
*** olani- <olani-!~olani@78-67-176-189-no2814.tbcn.telia.com> has joined #yocto19:57
*** vthor_ <vthor_!~thor@2806:10a6:24:d861:5ba2:9a4b:2a4d:bb72> has quit IRC (Remote host closed the connection)20:05
*** vthor_ <vthor_!~thor@2806:10a6:24:d861:323d:59b6:9347:d3f8> has joined #yocto20:06
*** flom84 <flom84!~flom84@user/flom84> has quit IRC (Quit: Leaving)20:09
*** Haxxa <Haxxa!~Haxxa@116.255.4.123> has quit IRC (Quit: Haxxa flies away.)20:15
*** Haxxa <Haxxa!~Haxxa@116.255.4.123> has joined #yocto20:17
*** BenBE <BenBE!~benbe@user/benbe> has quit IRC (Ping timeout: 258 seconds)20:24
*** flom84 <flom84!~flom84@user/flom84> has joined #yocto20:29
*** flom84 <flom84!~flom84@user/flom84> has quit IRC (Remote host closed the connection)20:30
*** mvlad <mvlad!~mvlad@2a02:2f05:810e:b200:e88e:21ff:fe65:be18> has quit IRC (Remote host closed the connection)20:30
khemthey can live together20:31
kheme.g. you can use nm to take care of wifi connection and networkd to manage ethernet20:32
Ch^WWhat is the procedure for dealing with autobuilder failures due to missing modules? Is that something that can be added to the autobuilder?20:33
khemmissing modules ? you mean python, perl ?20:36
khemusually, these are provided by some recipe so adding the relevant recipe/package to deps/rdeps of failing recipe is the way to go20:37
Ch^Wkhem: No, we pushed a serial (RS-232) testing bbclass patch to OE-Core that needs to use pexepct. The autobuilder does not seem to have pexepect installed, so the build broke when it tried to load the module.20:40
gmorelllooking at making a package out of a rust library that supports workspaces, but cargo-bitbake has a Lot of opinions. Is there a better way, or would I have to patch it to support worksapces20:42
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.113> has quit IRC (Quit: Konversation terminated!)20:51
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.113> has joined #yocto20:52
*** mbulut <mbulut!~mbulut@ip1f128e48.dynamic.kabel-deutschland.de> has quit IRC (Ping timeout: 260 seconds)20:52
khemCh^W:that should be part of HOSTTOOLS I believe then or made part of distro pre-requisites or perhaps bbclass should add a dependency on expect-native20:52
Ch^Wkhem: Oh, as in DEPENDS += "expect-native"?20:53
Ch^WI thought about that, but testing happens after the build, so I was sort of scratching my head as to where something like that would actually go.20:54
khemsee meta/lib/oeqa/selftest/cases/glibc.py20:54
khemI think you need to install python3-pexpect20:55
khemgmorell: cargo-bitbake is a wrapper around cargo nothing more. What do you expect out of the this21:00
gmorellI meant the the ol bitbake update_crates, regardless they do the same thing but don't parse the toml correctly with the upgraded workspace decls21:02
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)21:07
Ch^Wkhem: Ah, nice thanks. I wish I had thought to grep for that. Cheers.21:13
*** brrm <brrm!~brrm@2a02:8071:b700::1c89> has quit IRC (Ping timeout: 248 seconds)21:52
*** florian <florian!~florian@dynamic-093-131-052-209.93.131.pool.telefonica.de> has quit IRC (Ping timeout: 248 seconds)22:45
*** mk3890 <mk3890!~mk3890@75-60-131-157.lightspeed.stlsmo.sbcglobal.net> has quit IRC (Remote host closed the connection)22:48
*** olani- <olani-!~olani@78-67-176-189-no2814.tbcn.telia.com> has quit IRC (Ping timeout: 258 seconds)23:19
*** cabazon76 <cabazon76!~cabazon@136.226.78.193> has joined #yocto23:34
cabazon76Hey, I have a custom license file, LICENSE.my. How do I add it to meta-my layer? I read about SPDXLICENSEMAP variable but I'm not sure whether I can use that variable within meta-my layer23:35
*** cabazon76 <cabazon76!~cabazon@136.226.78.193> has quit IRC (Quit: Client closed)23:52

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