Thursday, 2022-03-31

*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto00:17
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Client Quit)00:20
*** jclsn1007 <jclsn1007!~jclsn@46.59.216.93.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 246 seconds)00:23
*** jclsn1007 <jclsn1007!~jclsn@46.59.216.93.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto00:23
*** jclsn1007 <jclsn1007!~jclsn@46.59.216.93.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 246 seconds)00:34
*** jclsn1007 <jclsn1007!~jclsn@46.59.216.93.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto00:40
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)00:50
*** jclsn1007 <jclsn1007!~jclsn@46.59.216.93.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 246 seconds)01:01
*** BCMM <BCMM!~BCMM@user/bcmm> has quit IRC (Quit: Konversation terminated!)01:06
*** jclsn1007 <jclsn1007!~jclsn@46.59.216.93.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto01:07
*** dev1990 <dev1990!~dev@dynamic-78-8-240-254.ssp.dialog.net.pl> has quit IRC (Quit: Konversation terminated!)01:08
*** jclsn1007 <jclsn1007!~jclsn@46.59.216.93.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 260 seconds)01:12
*** bonalais <bonalais!uid502939@id-502939.tinside.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)01:13
*** otavio <otavio!~otavio@201-3-135-79.user3p.brasiltelecom.net.br> has quit IRC (Remote host closed the connection)01:14
tlwoernerRP: good! an go ahead and remove recipes-core/initscripts/initscripts-1.0/GPLv2.patch and recipes-kernel/modutils-initscripts/files/PD.patch too ;-)01:16
*** jclsn1007 <jclsn1007!~jclsn@46.59.216.93.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto01:17
*** otavio <otavio!~otavio@201-3-135-79.user3p.brasiltelecom.net.br> has joined #yocto01:17
*** lowfi <lowfi!~lowfi@user/lowfi> has joined #yocto01:19
*** ecdhe <ecdhe!~ecdhe@user/ecdhe> has quit IRC (Read error: Connection reset by peer)01:24
*** ecdhe <ecdhe!~ecdhe@user/ecdhe> has joined #yocto01:24
*** neverpanic <neverpanic!~clemens@towel.neverpanic.de> has quit IRC (Quit: reboot)01:26
*** neverpanic <neverpanic!~clemens@towel.neverpanic.de> has joined #yocto01:27
*** jclsn1007 <jclsn1007!~jclsn@46.59.216.93.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 260 seconds)01:28
*** jclsn1007 <jclsn1007!~jclsn@46.59.216.93.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto01:33
*** jclsn1007 <jclsn1007!~jclsn@46.59.216.93.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 272 seconds)01:40
*** geoff_ <geoff_!~geoff@207.154.79.70> has quit IRC (Ping timeout: 246 seconds)01:42
*** jsbronder <jsbronder!jsbronder@user/jbronder> has quit IRC (Quit: WeeChat 3.3)01:45
*** jclsn1007 <jclsn1007!~jclsn@46.59.216.93.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto01:45
*** camus <camus!~Instantbi@183.192.143.37> has joined #yocto01:46
*** jsbronder <jsbronder!jsbronder@user/jbronder> has joined #yocto01:55
*** jclsn1007 <jclsn1007!~jclsn@46.59.216.93.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 240 seconds)01:55
*** jclsn1007 <jclsn1007!~jclsn@46.59.216.93.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto02:01
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)02:04
*** jclsn1007 <jclsn1007!~jclsn@46.59.216.93.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 272 seconds)02:06
*** jclsn1007 <jclsn1007!~jclsn@46.59.216.93.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto02:11
*** jclsn1007 <jclsn1007!~jclsn@46.59.216.93.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 246 seconds)02:19
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto02:22
*** jclsn1007 <jclsn1007!~jclsn@213.21.33.208.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto02:27
*** jclsn1007 <jclsn1007!~jclsn@213.21.33.208.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 240 seconds)02:34
*** jclsn1007 <jclsn1007!~jclsn@213.21.33.208.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto02:40
*** jclsn1007 <jclsn1007!~jclsn@213.21.33.208.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 246 seconds)02:57
*** jclsn1007 <jclsn1007!~jclsn@213.21.33.208.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto03:03
*** bonalais <bonalais!uid502939@id-502939.tinside.irccloud.com> has joined #yocto03:49
*** lowfi <lowfi!~lowfi@user/lowfi> has quit IRC (Quit: Leaving)03:51
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)04:27
*** lowfi <lowfi!~lowfi@user/lowfi> has joined #yocto04:36
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Ping timeout: 256 seconds)05:16
*** amitk <amitk!~amit@103.208.69.6> has joined #yocto05:33
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto05:50
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Client Quit)05:51
*** kroon <kroon!~kroon@89-253-118-72.customers.ownit.se> has joined #yocto05:52
*** Circuitsoft <Circuitsoft!uid393878@id-393878.lymington.irccloud.com> has joined #yocto06:03
*** lowfi <lowfi!~lowfi@user/lowfi> has quit IRC (Quit: Leaving)06:08
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto06:51
*** mckoan|away is now known as mckoan06:52
*** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has joined #yocto06:57
*** bonalais <bonalais!uid502939@id-502939.tinside.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)06:58
*** mvlad <mvlad!~mvlad@2a02:2f08:4114:c500:24d7:51ff:fed6:906d> has joined #yocto07:02
*** tnovotny <tnovotny!~tnovotny@ip4-83-240-26-162.cust.nbox.cz> has joined #yocto07:07
*** Wouter0100 <Wouter0100!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Read error: Connection reset by peer)07:11
*** Wouter0100 <Wouter0100!~Wouter010@entry.nbg.netvos.nl> has joined #yocto07:12
*** selff <selff!~selff@46.221.0.162> has joined #yocto07:18
selffhello everyone, have a nice day. i asked a question about ap and wpa yesterday, but i couldnt find an answer. im sharing it again today, maybe someone can help.07:26
selffi want to use both wpa and ap in my image. when i run hostapd service in runtime, it switches to AP mode without any problems and read the "hostapd.network" settings.  when i want switch to wpa, i follow these steps:07:26
selffenable "wpa_supplicant@wlan0" and disable "hostapd", reboot. when i run the "wpa_supplicant@wlan0" service, it does not switch to wpa mode.07:26
selffeven though hostapd is closed, wpa uses the "hostapd.network" file which is contain ap ip etc. idk why but wpa is reading "hostapd.network" instead of "wlan.network".07:26
selffin short wpa_supplicant@wlan0 service reads hostapd.network instead of wlan.network.07:27
*** dev1990 <dev1990!~dev@dynamic-78-8-240-254.ssp.dialog.net.pl> has joined #yocto07:31
*** dacav <dacav!~dacav@h94-245-9-200.cust.a3fiber.se> has quit IRC (Ping timeout: 256 seconds)07:41
*** camus <camus!~Instantbi@183.192.143.37> has quit IRC (Read error: Connection reset by peer)07:41
*** camus <camus!~Instantbi@2409:8a1e:9115:e190:5138:5b88:8215:a434> has joined #yocto07:42
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto07:47
*** GillesM <GillesM!~gilles@105.61.128.77.rev.sfr.net> has joined #yocto07:49
*** selff <selff!~selff@46.221.0.162> has quit IRC (Ping timeout: 250 seconds)07:50
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto07:52
LetoThe2ndyo dudX07:55
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has quit IRC (Ping timeout: 246 seconds)07:57
*** selff <selff!~selff@46.221.0.162> has joined #yocto08:05
qschulzo/08:10
rburtonsielicki: it got renamed https://git.yoctoproject.org/poky/tree/meta/classes/python_pep517.bbclass.  you only need to use it if youre writing support for a new build system, otherwise use the setuptools/flit/poetry classes08:13
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has joined #yocto08:19
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has quit IRC (Ping timeout: 252 seconds)08:25
selffdoes anyone have any idea about my problem with ap and wpa? :'(08:32
rburtonobviously not. try talking to the wpa/hostap maintainers?08:33
selffI dont even know where to contact. need to some research, thank you.08:37
rburtonhttp://lists.infradead.org/mailman/listinfo/hostap08:37
selffrburton again an again ty08:40
LetoThe2ndneed to decide on the correct permutation of these: "work on u-boot for an iMX7 board", "drink", "curse each and everything". suggestions?08:46
*** janvermaete[m] <janvermaete[m]!~vermaetem@2001:470:69fc:105::ee7> has quit IRC (Quit: You have been kicked for being idle)09:00
*** gsalazar_ <gsalazar_!~gsalazar@132.120.90.149.rev.vodafone.pt> has joined #yocto09:03
*** gsalazar_ <gsalazar_!~gsalazar@132.120.90.149.rev.vodafone.pt> has quit IRC (Remote host closed the connection)09:03
*** gsalazar <gsalazar!~gsalazar@194.38.148.130> has quit IRC (Ping timeout: 272 seconds)09:06
*** tomzy <tomzy!~tomzy@84-10-27-202.static.chello.pl> has joined #yocto09:37
*** tomzy <tomzy!~tomzy@84-10-27-202.static.chello.pl> has quit IRC (Client Quit)09:37
*** tomzy72 <tomzy72!~tomzy@84-10-27-202.static.chello.pl> has joined #yocto09:37
*** tomzy72 <tomzy72!~tomzy@84-10-27-202.static.chello.pl> has quit IRC (Client Quit)09:38
*** tomzy <tomzy!~tomzy@84-10-27-202.static.chello.pl> has joined #yocto09:38
*** tomzy <tomzy!~tomzy@84-10-27-202.static.chello.pl> has quit IRC (Client Quit)09:40
*** mojuser <mojuser!~mojuser@84-10-27-202.static.chello.pl> has joined #yocto09:45
*** bonalais <bonalais!uid502939@id-502939.tinside.irccloud.com> has joined #yocto09:50
*** ardo <ardo!~ardo@host-188-10-58-99.business.telecomitalia.it> has quit IRC (Read error: Connection reset by peer)09:54
*** ardo <ardo!~ardo@host-188-10-58-99.business.telecomitalia.it> has joined #yocto09:54
*** arturkow <arturkow!~arturkow@84-10-27-202.static.chello.pl> has joined #yocto09:56
*** arturkow <arturkow!~arturkow@84-10-27-202.static.chello.pl> has quit IRC (Client Quit)09:58
*** ardo <ardo!~ardo@host-188-10-58-99.business.telecomitalia.it> has quit IRC (Read error: Connection reset by peer)09:59
*** bonalais <bonalais!uid502939@id-502939.tinside.irccloud.com> has quit IRC ()10:02
*** bonalais <bonalais!uid502939@id-502939.tinside.irccloud.com> has joined #yocto10:03
*** ardo <ardo!~ardo@host-188-10-58-99.business.telecomitalia.it> has joined #yocto10:03
*** goliath <goliath!~goliath@user/goliath> has joined #yocto10:10
LetoThe2ndwhat flag does wic need in order to create an empty FS?10:24
LetoThe2ndsomething like --fixed-size 50M --fstype=ext4  ?10:27
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has joined #yocto10:36
*** selff <selff!~selff@46.221.0.162> has quit IRC (Quit: Client closed)10:50
*** amitk <amitk!~amit@103.208.69.6> has quit IRC (Ping timeout: 260 seconds)10:56
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Ping timeout: 250 seconds)11:02
*** kroon <kroon!~kroon@89-253-118-72.customers.ownit.se> has quit IRC (Ping timeout: 260 seconds)11:08
*** kroon <kroon!~kroon@89-253-118-72.customers.ownit.se> has joined #yocto11:09
LetoThe2ndhave you ever seen a situation where u-boot , specifically u-boot-fslc happily builds, no errors, no nothing, but no artifacts are generated in the Yocto build? Manually building outside works nicely11:10
*** amitk <amitk!~amit@103.208.71.41> has joined #yocto11:13
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto11:14
qschulzLetoThe2nd: wdym by "no artifacts are generated"?11:21
qschulznothing in the deploy directory or nothing in the build directory?11:21
LetoThe2ndqschulz: the former, primarily. still investigating.11:25
qschulzLetoThe2nd: are you sure there's a do_deploy task?11:25
qschulzis the deploy task called?11:25
*** arturkow <arturkow!~arturkow@84-10-27-202.static.chello.pl> has joined #yocto11:26
LetoThe2ndwill try to find out11:28
*** arturkow <arturkow!~arturkow@84-10-27-202.static.chello.pl> has quit IRC (Quit: Client closed)11:37
*** arturkow <arturkow!~arturkow@84-10-27-202.static.chello.pl> has joined #yocto11:37
*** arturkow <arturkow!~arturkow@84-10-27-202.static.chello.pl> has quit IRC (Client Quit)11:37
*** arturkow <arturkow!~arturkow@84-10-27-202.static.chello.pl> has joined #yocto11:37
*** arturkow <arturkow!~arturkow@84-10-27-202.static.chello.pl> has quit IRC (Client Quit)11:37
LetoThe2ndwhat do people buy for personal builders these days? still threadrippers?11:49
rburtonmost likely the best bang-per-buck still11:50
rburtonbut you know you want to get a mac studio and boot asahi on it to benchmark that ;)11:50
LetoThe2ndk11:50
LetoThe2ndnope.11:50
rburtonbah11:51
LetoThe2ndbeen using an old phenom x2 at the moment, but that really needs upgrading11:51
LetoThe2nd1) looked at prices. 2) decided it will probably be just a run of the mill ryzen11:57
rburtonyeah prices are not great11:59
qschulzLetoThe2nd: if you're going for overkill, I've read that the new i9 12th gen are pretty good12:00
LetoThe2ndqschulz: the overkill days are gone, i'm back to common sense ;-)12:01
qschulzLetoThe2nd: then probably Ryzen product line which should have more cores than Intel at similar price points12:01
qschulz(note that Intel MB are notably more expensive than Ryzen compatible ones for some reason)12:02
*** camus <camus!~Instantbi@2409:8a1e:9115:e190:5138:5b88:8215:a434> has quit IRC (Ping timeout: 260 seconds)12:03
qschulzLetoThe2nd: though note that most Ryzen CPUs don't have integrated GPU (the G and GE product line does have it though, AMD calls them APUs)12:03
*** camus1 <camus1!~Instantbi@183.192.143.37> has joined #yocto12:03
*** dvorkindmitry <dvorkindmitry!~dv@5.167.98.73> has quit IRC (Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/)12:03
LetoThe2ndqschulz: yeah, 5700g sounds like a good one to get.12:03
qschulzso either go for G product line (last letter in the CPU product ID) or think about buying a small graphics card12:03
*** camus1 is now known as camus12:05
LetoThe2ndI even have one lying around here. but that means more hw, e.g. more power consumption.12:07
qschulzLetoThe2nd: I know I know, been looking for CPUs to replace my old server at home but don't want to increase the power consumption really..12:09
qschulzquite a difficult task to find 35W CPUs with integrated graphics today :)12:09
rburtonget a mac mini and boot asahi on it ;)12:20
rburtoni wonder if anyone makes thunderbolt sata docks that take four disks12:20
qschulzrburton: no thank you :)12:25
qschulzdon't have time to debug things on my server, it needs to work :)12:25
qschulzand I had a Mac mini at work running Linux (intel based, old one), graphics glitches every now and then12:26
rburtonwell if its a server it will be headless, right? :)12:27
qschulzrburton: well.. no :p12:28
qschulzwant to replace my RPi running Kodi/LibreElec with the server12:28
qschulzand also hope to be able to replace my desktop (which I very rarely use) with it12:28
qschulzbut I've yet to understand if it is possible and how to share GPU+VPU among different containers/KVM12:29
qschulzand now the 5600GE I'm after is impossible to find12:30
qschulzrburton: is it you who has a microserver gen8 too?12:31
qschulzI remember reading a tweet, either you or paul12:31
qschulzand looking for ARM based replacement12:31
qschulzwell.. maybe #yocto isn't the best place for this kind of discussion but it's rather calm today :)12:31
LetoThe2ndeverybody is busy day drinking and preparing bad jokes for tomorrow.12:34
*** kroon <kroon!~kroon@89-253-118-72.customers.ownit.se> has quit IRC (Quit: Leaving)12:40
*** MrSaturn <MrSaturn!~sam@cpe-72-224-69-22.maine.res.rr.com> has joined #yocto13:02
MrSaturnsilly question: If I do a "devtool build" where does the binary go?13:02
qschulzMrSaturn: ${B}13:04
*** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:2cf5:51cb:fa23:24f8> has quit IRC (Quit: vladest)13:07
*** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:d6d6:7366:5da8:23b6> has joined #yocto13:08
MrSaturnAlright, odd. I think something isn't working quite right in the recipe.13:09
MrSaturnIs there a way I can make this work with both bitbake and devtool?  https://pastebin.com/xPgS5PGc  When I do a devtool modify, then a bitbake build it can not find the logo.13:10
rburtonMrSaturn: don't use a task, just tell the fetcher where to put the file in the SRC_URI: https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-fetching.html#the-unpack13:12
rburtonqschulz: yeah thats me13:12
qschulzrburton: the only Aarch64 consumer board that was "suitable" for NAS was the Helios64 IIRC, but they shutdown last year13:14
MrSaturnrburton: The layer already has a 'SRC_URI += "file://company.bmp"' line. It looks like that task is move the logo to a specific location. This isn't my layer, so I am guessing at intention.13:20
MrSaturnIn devtool, "company.bmp" is in a directory called "oe-local-files"13:22
*** ar__ <ar__!~akiCA@user/akica> has joined #yocto13:33
*** codavi <codavi!~akiCA@user/akica> has joined #yocto13:37
*** ar__ <ar__!~akiCA@user/akica> has quit IRC (Ping timeout: 250 seconds)13:40
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto13:43
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto13:49
rburtonMrSaturn: someone didn't know that you can tell the fetcher where to put a file, that's all13:55
rburtona new task is overkill13:55
LetoThe2ndqschulz: the u-boot boot is weird. builddir is empty other than the .scmversion file.14:56
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:3958:796d:6d52:6def> has joined #yocto15:14
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Ping timeout: 272 seconds)15:26
RPkergoth: do you think the failure in https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/3382/steps/15/logs/stdio might be related to the sys.modules reset? :/15:36
RPJPEW: there is also an asyncio event loop issue in there :(15:36
RPkergoth: I mean the KeyError re: sys.modules15:37
kergothI'm wondering if sys.modules and sys.path are actually just dicts or another type, if assignment could cause an issue vs clearing and updating the dict15:54
kergothRP: ^15:54
kergothdon't really know15:54
*** gsalazar <gsalazar!~gsalazar@132.120.90.149.rev.vodafone.pt> has joined #yocto15:56
RPkergoth: Yes, that is what I'm wondering too. I'm pretty sure sys.path is just a list but sys.modules' contents might not copy well :/15:57
kergothModule import handling is voodoo to me, I should probably read up on that more15:57
*** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has quit IRC (Quit: Client closed)16:02
kergothI'd try clearing and updating sys.modules and see if that changes the behavior16:03
kergothI do wonder how these things are affected by multiconfig builds, since it's global state set by metadata which isn't global16:04
kergothguessing layers wouldn't change with that so probably fine16:04
*** dvorkindmitry <dvorkindmitry!~dv@5.167.98.73> has joined #yocto16:06
dvorkindmitryIs there a way to install SYSTEMD_SERVICE machine-specific, like SYSTEMD_SERVICE:${PN}:myarch = "ssss.service" ?16:06
qschulzdvorkindmitry: if this does not work you can always do SYSTEMD_SERVICE:${PN} = "${SSSS_SERVICE}" and have SSSS_SERVICE:myarch = "ssss.service"16:09
kergothoverrides work fine with any variable. they don't work on flags, but variables are fine16:10
kergothHmm when will kirkstone be branching? Wonderinga bout submitting stuff that doesn't belong in the release16:13
dvorkindmitryqschulz, kergoth, thank you to both of you. looks like it work16:13
*** tnovotny <tnovotny!~tnovotny@ip4-83-240-26-162.cust.nbox.cz> has quit IRC (Remote host closed the connection)16:13
RPkergoth: not sure I want to think about multiconfig in this context!16:14
dvorkindmitrywhy machine-specific SRC_URI should be written like SRC_URI:append:mymachine, while SYSTEMD_SERVICE:${PN}:mymachine ?16:15
smurraythe latter isn't an append?16:19
smurrayi.e. it overrides the definition.  If you did that for SRC_URI you'd lose the presumably non-machine-specific default value16:21
RPkergoth: going to give https://git.yoctoproject.org/poky/commit/?h=master-next&id=f8acc250920fc7b1c1a1703b640ebff07d16ef89 a try16:24
manuel1985'Subprocess output:x86_64-poky-linux-objcopy: Unable to recognise the format of the input file' <--- how can I skip this check? The file in question is a downloaded rust executable16:25
kergothRP: looks reasonable16:28
kergothI wonder if we couldn't subclass and use importlib.machinery.PathFinder to search our own bbpath-based-path directly rather than mucking about with sys.path. I also wonder if we could change sys.modules or import behavior in our python eval so it doesn't persist in bitbake's global sys.path and sys.modules.16:29
kergothlong term16:29
RPkergoth: yes, I think we do need to improve this longer term, probably with layer.conf syntax too16:31
* RP notes kirkstone branches are now available16:41
RPthey're not diverging yet but available16:42
kergothah, okay, so no need to hold off on post-kirkstone submissions?16:42
RPkergoth: just make them clearly not for kirkstone16:43
*** dvorkindmitry <dvorkindmitry!~dv@5.167.98.73> has quit IRC (Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/)16:51
amahnui[m]Hello rburton: I have set up freebsd tho I never successfully set up a de but I will begin setting up my coding environment while trying to set it up the de16:55
*** mckoan is now known as mckoan|away16:57
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat)16:59
*** ykrons <ykrons!~guillaume@62.192.23.101> has quit IRC (Ping timeout: 240 seconds)17:20
*** ykrons <ykrons!~guillaume@62.192.23.101> has joined #yocto17:32
*** troth <troth!~troth@c-24-8-35-226.hsd1.co.comcast.net> has quit IRC (Ping timeout: 245 seconds)17:33
*** troth <troth!~troth@c-24-8-35-226.hsd1.co.comcast.net> has joined #yocto17:49
MrSaturn2~2~                 https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-fetching.html#the-unpack17:57
MrSaturnSorry about the accidental paste. Just to make sure I understand: to fetch a file and put it in a specfic location, you do "SRC_URI +=..." then you need to put something in do_unpack?18:01
rfs613MrSaturn: only if you have some very esoteric unpacking needs. Normally the existing yocto handles all formats you're likely to encounter.18:08
MrSaturnrfs613: I have a file that I need to put in ${S}/tools/logos. Can this be accomplished without a do_unpack_append?18:09
rfs613MrSaturn: I think you may be confusing the unpack with the install18:10
MrSaturnrfs613: Perhaps. The file needs to be inplace before compilation18:12
rburtonMrSaturn: yes it can. i pointed you at the precise bit of the documetation that tells you how earlier today18:12
rburtonthe default location is WORKDIR18:13
rburtonbut you can change that, to ${S}/tools/logos18:13
MrSaturnrburton: oh shoot. I think I understand. I had to read it a third time.  SRC_URI += "file://mfg.bmp;subdir=${S}/tools/logos"18:17
rburtonyes18:17
MrSaturnSorry I am daft. I missed that it was a parameter in the URL18:19
MrSaturnHoly cow that worked. Let's see if devtool does the trick now.18:20
MrSaturnOk, this is madness. I am going to reach out to them and ask them their workflow.18:22
MrSaturnNow when I do a devtool build I get a "subdir argument isn't a subdirectory of unpack root"18:23
amahnui[m]<amahnui[m]> "Hello rburton: I have set up..." <- Hello rburton: please I can't find the issue tracker for yocto project18:25
rburtonbugzilla.yoctoproject.org18:25
amahnui[m]rburton: Thank you18:29
*** ferlzc <ferlzc!~ferlzc@177.52.29.172> has joined #yocto18:30
ferlzcHi, I created a recipe that's builds a library. I compile the library on the do_compile() and afterward I installed it using the following:do_install () {18:32
ferlzc     install -p ${D}${libdir}18:32
ferlzc     install -d ${D}${includedir}18:32
ferlzc     install ${S}/libulf.so ${D}${libdir}/libulf.so18:32
ferlzc    18:32
ferlzc     install ${S}/lib-ulf.h ${D}${includedir}18:32
ferlzc}18:32
rburtonversion your library18:32
rburtonthat's why you get insane errors18:32
rburtonif you really don't want to version your library then https://docs.yoctoproject.org/dev-manual/common-tasks.html#working-with-pre-built-libraries covers how to work around it18:33
rburtonbut version your library (i.e. libulf.so.1)18:33
rburtonI'm assuming I'm right as to what the problem is ;)18:33
ferlzcrburton that's one problem and you nailed18:34
rburtonhttps://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html talks about the library naming convention18:34
ferlzcthe other one is: I need to use this library in another recipe, but during the makefile I can seem to find the .h that I link for18:35
rburtondid you DEPEND on ulf or whatever you named the library recipe?18:36
ferlzcfor some reason the only way I found .h was using -I${TMPDIR}/sysroots-components/core2-64/lib-omneulf-client/usr/include, which is not a good solution18:36
rburtonyeah don't do that18:36
rburtonif you DEPENDed on ulf then its in the recipe's private sysroot18:37
ferlzcI did DEPEND the library on the new recipe18:37
rburtonare you manually compiling the app?18:37
rburtonbecause you're probably driving the compiler wrong18:37
ferlzcno I'm patching an Makefile18:38
rburtoneven worse: the makefile is probably terrible18:38
rburtonmakefiles are typically terrible and wrong18:38
rburtonspecifically, its probably ignoring LDFLAGS from the environment18:38
rburtonwriting a proper makefile is hard.  people think its easy, hack one up, and then wonder why people building distributions get annoyed at the makefiles.18:39
ferlzcthis an example of the Makefile18:39
ferlzcLDLIBSOPTIONS=-L/opt/omne/lib -L/opt/addons/lib -lulf -lcrypto -lpq -lpcrecpp18:39
ferlzc# Build Targets18:39
ferlzc.build-conf: ${BUILD_SUBPROJECTS}18:39
ferlzc"${MAKE}"  -f nbproject/Makefile-${CND_CONF}.mk ${CND_DISTDIR}/${CND_CONF}/${CND_PLATFORM}/libomnecpp.so18:39
ferlzc${CND_DISTDIR}/${CND_CONF}/${CND_PLATFORM}/libomnecpp.so: ${OBJECTFILES}18:39
ferlzc${MKDIR} -p ${CND_DISTDIR}/${CND_CONF}/${CND_PLATFORM}18:39
ferlzc${LINK.cc} -o ${CND_DISTDIR}/${CND_CONF}/${CND_PLATFORM}/libomnecpp.so ${OBJECTFILES} ${LDLIBSOPTIONS} -shared -fPIC18:39
ferlzc${OBJECTDIR}/OmneAuth.o: OmneAuth.cpp18:39
ferlzc${MKDIR} -p ${OBJECTDIR}18:39
ferlzc${RM} "$@.d"18:39
ferlzc$(COMPILE.cc) -O2 -I/opt/addons/include -I/opt/omne/include -fPIC  -MMD -MP -MF "$@.d" -o ${OBJECTDIR}/OmneAuth.o OmneAuth.cpp18:39
ferlzc${OBJECTDIR}/OmneCrypto.o: OmneCrypto.cpp18:39
ferlzc${MKDIR} -p ${OBJECTDIR}18:39
ferlzc${RM} "$@.d"18:39
ferlzc$(COMPILE.cc) -O2 -I/opt/addons/include -I/opt/omne/include -fPIC  -MMD -MP -MF "$@.d" -o ${OBJECTDIR}/OmneCrypto.o OmneCrypto.cpp18:39
ferlzc${OBJECTDIR}/OmneStrings.o: OmneStrings.cpp18:39
ferlzc${MKDIR} -p ${OBJECTDIR}18:39
ferlzc${RM} "$@.d"18:39
ferlzc$(COMPILE.cc) -O2 -I/opt/addons/include -I/opt/omne/include -fPIC  -MMD -MP -MF "$@.d" -o ${OBJECTDIR}/OmneStrings.o OmneStrings.cpp18:39
ferlzc${OBJECTDIR}/OmneULF.o: OmneULF.cpp18:39
ferlzc${MKDIR} -p ${OBJECTDIR}18:39
ferlzc${RM} "$@.d"18:39
ferlzc$(COMPILE.cc) -O2 -I/opt/addons/include -I/opt/omne/include -fPIC  -MMD -MP -MF "$@.d" -o ${OBJECTDIR}/OmneULF.o OmneULF.cpp18:40
ferlzci'm patching those /opt/omne/lib which is bad18:40
rburtonI'm assuming it doesn't define COMPILE.cc itself?18:40
ferlzccan you tell me more on how not to ignore the LDFLAGS on this Makefile ?18:41
rburtonwell, does it define COMPILE.cc or does it use the default?18:41
ferlzcit uses the default18:41
rburtonthe default COMPILE.cc does respect CXX CXXFLAGS CPPFLAGS so it *should* work18:42
rburtonread the tmp/****/recipename/temp/log.do_compile to see what compiler flags are being passed.18:42
rburtonit should be passing --sysroot pointing at the recipe sysroot for the recipe, which should contain an include/ulf.h18:43
rburtonits its now quarter to 8 so im going to see my kids. hope someone else can help when you have more info.  always hard to debug secret recipes though.18:43
ferlzcis like this:18:44
ferlzcg++    -c -O2 -I/usr/include -fPIC  -MMD -MP -MF "build/Release/GNU-Linux-x86/OmneAuth.o.d" -o build/Release/GNU-Linux-x86/OmneAuth.o OmneAuth.cpp18:44
ferlzcg++    -c -O2 -I/usr/include -fPIC  -MMD -MP -MF "build/Release/GNU-Linux-x86/OmneCrypto.o.d" -o build/Release/GNU-Linux-x86/OmneCrypto.o OmneCrypto.cpp18:44
ferlzcg++    -c -O2 -I/usr/include -fPIC  -MMD -MP -MF "build/Release/GNU-Linux-x86/OmneULF.o.d" -o build/Release/GNU-Linux-x86/OmneULF.o OmneULF.cpp18:44
ferlzcIn file included from OmneAuth.cpp:1:18:44
ferlzcOmneAuth.h:8:10: fatal error: libpq-fe.h: No such file or directory18:44
ferlzc    8 | #include <libpq-fe.h>18:44
ferlzc      |          ^~~~~~~~~~~~18:44
ferlzccompilation terminated.18:44
*** agners <agners!~ags@2a02:169:3df5:10:5232:3053:9692:978b> has joined #yocto18:44
rburtonthat's using the host compiler, not a cross compiler18:44
ferlzcrburton thank you very much for the help so far18:45
khemwhere is COMPILE.cc being set ?18:45
rburtonits a default make rule18:45
khemperhapps EXTRA_OEMAKE += "COMPILE.cc='${CC}'"18:45
khemmight be a good thing to do in recipe18:45
rburton$ make -f /dev/null  -p|grep COMPILE.cc18:45
ferlzcis not defining the COMPILE.cc18:45
rburtonCOMPILE.cc = $(CXX) $(CXXFLAGS) $(CPPFLAGS) $(TARGET_ARCH) -c18:45
khemOK is there some hard define for CXX in makefile ?18:46
rburtonoh do you need EXTRA_OEMAKE = "-e"?18:47
rburtonto force it to pull from the environment18:47
rburtonalways forget that we don't force make to do that anymore18:49
rburtonits only been what, five years18:49
*** bonalais <bonalais!uid502939@id-502939.tinside.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)19:00
ferlzcyes there is some hard define for CXX on the file, like so:CC=gcc19:09
ferlzcCCC=g++19:09
ferlzcCXX=g++19:09
rfs613sakoman: available for a quick chat about CVE backports in dunfell?19:10
sakomanrfs613: yes19:10
rfs613great! so I notice there are a lot (92 according to last metrics email)19:11
rfs613quite a few of them also exist in other branches19:11
rfs613do we have a requirement to fix them in newer branches before they can go in dunfell?19:12
rfs613I'm finding it challenging to switch between branches, to verify a fix works in all of them19:12
sakomanThere is a requirement that fixes go first to master before dunfell and the other branches19:13
sakomanThen it is up to the branch maintainers to take them if possible19:13
sakomanIn reality, with different versions in the various branches it is pretty rare to be able to cherry-pick19:14
khemmaster is must as sakoman says19:15
sakomanWhen kirkstone is out and I am maintaining two LTS branches I'll probably try really hard to get the fixes in both after master19:15
khemwe need to ensure its either fixed in master via virtue of new version being in master or apply the patch to master and ask for a backport to related branches19:15
rfs613indeed, but the effort of finding the patch, applying it, adding the approprate tags etc, sort of makes sense to try and do it for all branches. Otherwise I end up re-doign the same work again.19:16
khemyeah LTSs would matter19:16
sakomanBut the reality is that many CVEs only exist in older branches and not in master since they have more recent package versions19:16
sakomanSo more often than not CVE fixes for dunell don't have a master fix since they don't exist there19:16
zeddiiThat's always fine as well. AS long as someone shows the version in master doesn't have a given problem, a cherry-pick/patch to an older branch is fine.19:17
sakomanrfs613: I and other maintainers would love to see you do the patches for all currently supported branches19:17
sakomanBut please test that the patches not only apply but build in those older branches :-)19:18
rfs613sakoman: my only challenge is workflow, keeping multiple branches up-to-date, testing that the CVE fix at least builds on each branch... it slows down the cycle significantly. And I find it mentally challenging to jump between branches a lot, get my wires crossed.19:19
rfs613having fewer active branches would of course help... dunfell, kirkstone, master would be nice ;-)19:19
sakomanrfs613: I totally understand!  The important branches at this point would be master, kirkstone, and dunfell19:20
khempractically yes19:20
rfs613ok, so as I am focused on dunfell for now, maybe I'll just note which other branches a fix might be applicable to (it's pretty easy to check while I'm in there), but leave the actual work of fixing honister/hardknott (if applicable) to someone else.19:21
khemyeah knowing that other branches would need this fix too would be good atleat release maintainer will know19:22
rfs613the patches would have [dunfell] tag, so other branch maintainer might not look at them19:23
sakomanrfs613: honister and hardknott just have one to two months of active maintenance left so it is a short term problem19:23
sakomanrfs613: I know that for dunfell I look at all CVE patches in master and do a quick evaluation as to whether they exist in dunfell and whether a cherry-pick is possible19:24
rfs613my other question relates to timing w.r.t releases, do we have a preference on when to submit (esp) CVE fixes?19:25
sakomanrfs613: for CVEs the answer is always ASAP :-)19:25
sakomanI try to do some each week independent of whether a release is imminent or not19:26
sakomanThough at release time it does go to zero since I'm occupied with the release19:26
khemsakoman:  on this note when is 3.1.16 planned ? there are some important openssl fixes on dunfell since 3.1.1519:34
sakomankhem: from the weekly status update:19:35
sakomanYP 3.1.16 build date 2022/04/25YP 3.1.16 Release date 2022/05/0619:35
khemok thanks19:36
rfs613i've just posted CVE-2022-0204 for dunfell. In the comments after the shortlog, I put info about the other branches. Feedback on the formatting, usefulnes, etc welcomed.19:40
*** Wouter0100 <Wouter0100!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: Ping timeout (120 seconds))19:41
*** Wouter0100 <Wouter0100!~Wouter010@entry.nbg.netvos.nl> has joined #yocto19:41
*** Minvera <Minvera!~Minvera@user/Minvera> has joined #yocto20:04
RPNice, first ever oe-selftest pass with BB_SERVER_TIMEOUT set20:06
rfs613hmm, this is odd, I used "b4" to download my patch (in another copy of poky). It said it applies clean to current tree, and yet when I do the 'git am' on the .mbx file, it complains that the patch is corrupt.20:07
khemrfs613:  there patchwork too https://patchwork.yoctoproject.org/project/oe-core/list/20:09
khemI have had more success with pw20:09
rfs613khem: there was a commandline tool for patchwork too, I seem to recall...20:10
khemgit-pw yes20:17
khemhttps://github.com/getpatchwork/git-pw20:17
abelloniRP: so you started a master-next build to celebrate? :)20:18
RPabelloni: using server_timeout so it may explode20:19
RPabelloni: I saw the system had space and was curious to see how bad the issues are now20:19
RPabelloni: it isn't causing an issue is it?20:20
*** GillesM <GillesM!~gilles@105.61.128.77.rev.sfr.net> has quit IRC (Quit: Leaving)20:21
abelloninope, I'm waiting for my build to finish, that's all20:23
abelloniand then I'll send the series from rburton which I'm not really sure will be successfull ;)20:23
*** ferlzc_ <ferlzc_!~ferlzc@177.52.29.172> has joined #yocto20:26
RPabelloni: I hadn't seen that series. Hmm ;-)20:27
rfs613khem: oh, it looks like I corrupted the patch before sending it. Oops.20:29
*** Circuitsoft <Circuitsoft!uid393878@id-393878.lymington.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)20:29
rfs613I'll do a v2 later, time to pick up the little ones.20:29
*** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:d6d6:7366:5da8:23b6> has quit IRC (Remote host closed the connection)20:30
*** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:d6d6:7366:5da8:23b6> has joined #yocto20:31
*** ferlzc_ <ferlzc_!~ferlzc@177.52.29.172> has quit IRC (Remote host closed the connection)20:40
*** ferlzc <ferlzc!~ferlzc@177.52.29.172> has quit IRC (Remote host closed the connection)20:40
*** amitk <amitk!~amit@103.208.71.41> has quit IRC (Ping timeout: 246 seconds)20:44
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:3958:796d:6d52:6def> has quit IRC (Remote host closed the connection)20:53
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto20:53
RPabelloni: I'm worried that build is hanging :(21:15
abelloniRP: mine seems to be stuck too: https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/3379/steps/14/logs/stdio21:28
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has quit IRC (Ping timeout: 245 seconds)21:29
*** mvlad <mvlad!~mvlad@2a02:2f08:4114:c500:24d7:51ff:fed6:906d> has quit IRC (Remote host closed the connection)21:30
RPabelloni: I was referring to yours!21:30
abelloniAh!21:32
abellonithen yes, it seems stuck, I've started another one just to see21:32
RPabelloni: I logged into alma8 and it is inside a linux-yocto kernel build. I think it is the make hang21:34
RP$ pstree -p 341574921:34
RPrun.do_compile.(3415749)───make(4031649)───make(4041617)───make(4044688)───make(4044694)───sh(4044706)21:34
RPand 4044706 is a zombie21:34
RPabelloni: I think I can unblock it if you want. Or if anyone wants to study a make/signal bug...21:35
abelloniah, I'm pretty sure you'd love to do that before going to sleep ;)21:36
RPabelloni: unblock it or study it? I did study one of these before. I don't know what the issue is :(21:37
abelloniI'm not quite sure what would make that centos specific21:38
RPabelloni: make version?21:38
RPabelloni: something like https://git.savannah.gnu.org/cgit/make.git/commit/?id=88713683fed38fa5a7a649d065c73f4d945bade7 maybe?21:40
RPalthough that should be in 4.2.121:41
abellonifrom 2014?21:41
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Quit: Leaving)21:42
RPabelloni: https://savannah.gnu.org/bugs/?51400 i.e. https://git.savannah.gnu.org/cgit/make.git/commit/?id=78b5fec6898c26956d00548427cda1101cb80f8a21:44
RPabelloni: I suspect something like this21:44
RPabelloni: to be clear I think it is bug https://bugzilla.yoctoproject.org/show_bug.cgi?id=14712 on our side21:45
RPabelloni: I updated the bug21:48
abelloniok, I guess you can kill this build then21:48
RPabelloni: not quite sure what I did there but it has died21:50
*** alimon <alimon!~alimon@189.174.2.174> has quit IRC (Quit: Leaving.)21:51
*** codavi <codavi!~akiCA@user/akica> has quit IRC (Ping timeout: 250 seconds)21:58
RPJPEW: https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/3352/steps/14/logs/stdio - second time I've hit this despite the patches in -next and on the list :(22:00
JPEWRP: Weird, is that new? did something change?22:01
RPJPEW: it is memres bitbake22:01
RPJPEW: BB_SERVER_TIMEOUT=6022:02
RPI'm really tempted to just error if make 4.2.1 is present22:09
*** dgriego <dgriego!~dgriego@user/dgriego> has quit IRC (Quit: Textual IRC Client: www.textualapp.com)22:09
JPEWIs it warning in all the tests and we just don't see it?22:10
abelloniRP: wouldn't that just disable all the centos based workers?22:22
*** dev1990 <dev1990!~dev@dynamic-78-8-240-254.ssp.dialog.net.pl> has quit IRC (Quit: Konversation terminated!)22:26
*** gsalazar <gsalazar!~gsalazar@132.120.90.149.rev.vodafone.pt> has quit IRC (Ping timeout: 250 seconds)22:29
*** Minvera <Minvera!~Minvera@user/Minvera> has quit IRC (Remote host closed the connection)22:32
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto22:50
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)22:59

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