Tuesday, 2022-04-05

*** wCPO3 <wCPO3!~wCPO@mail.klausen.dk> has joined #yocto00:08
*** mario-go` <mario-go`!~user@static.> has joined #yocto00:08
*** wCPO <wCPO!~wCPO@mail.klausen.dk> has quit IRC (Write error: Connection reset by peer)00:08
*** wCPO3 is now known as wCPO00:08
*** mario-goulart <mario-goulart!~user@chicken/developer/mario-goulart> has quit IRC (Read error: Connection reset by peer)00:09
*** bantu <bantu!~bantu@edna.bantux.com> has quit IRC (Quit: No Ping reply in 180 seconds.)00:09
*** zkrx <zkrx!~slimshady@adsl-89-217-230-95.adslplus.ch> has quit IRC (Ping timeout: 256 seconds)00:09
*** bantu <bantu!~bantu@edna.bantux.com> has joined #yocto00:10
*** zkrx <zkrx!~slimshady@adsl-89-217-230-95.adslplus.ch> has joined #yocto00:11
*** pabigot <pabigot!~pab@67-1-16-117.tcso.qwest.net> has quit IRC (Ping timeout: 256 seconds)00:12
*** woky_ <woky_!~woky@li1651-31.members.linode.com> has quit IRC (Ping timeout: 256 seconds)00:12
*** woky <woky!~woky@li1651-31.members.linode.com> has joined #yocto00:12
*** dti <dti!~dtometzki@fedora/dtometzki> has joined #yocto00:13
*** tperrot <tperrot!~tprrt@shells.bootlin.com> has quit IRC (Ping timeout: 256 seconds)00:13
*** tperrot <tperrot!~tprrt@shells.bootlin.com> has joined #yocto00:13
*** pabigot <pabigot!~pab@67-1-16-117.tcso.qwest.net> has joined #yocto00:13
*** rfs613- <rfs613-!~rfs613@rfs.netwinder.org> has joined #yocto00:13
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has quit IRC (Ping timeout: 256 seconds)00:13
*** opello <opello!~opello@about/csharp/opello> has quit IRC (Ping timeout: 256 seconds)00:13
*** rfs613 <rfs613!~rfs613@rfs.netwinder.org> has quit IRC (Ping timeout: 256 seconds)00:13
*** fray <fray!~fray@> has quit IRC (Ping timeout: 256 seconds)00:13
*** lukma <lukma!~lukma@85-222-111-42.dynamic.chello.pl> has quit IRC (Ping timeout: 256 seconds)00:13
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 256 seconds)00:13
*** The_Pacifist <The_Pacifist!~The_Pacif@c-73-181-150-3.hsd1.wa.comcast.net> has quit IRC (Ping timeout: 256 seconds)00:13
*** lukma <lukma!~lukma@85-222-111-42.dynamic.chello.pl> has joined #yocto00:14
*** opello <opello!~opello@about/csharp/opello> has joined #yocto00:15
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto00:15
*** The_Pacifist <The_Pacifist!~The_Pacif@c-73-181-150-3.hsd1.wa.comcast.net> has joined #yocto00:15
*** dev1990 <dev1990!~dev@dynamic-78-8-240-254.ssp.dialog.net.pl> has quit IRC (Quit: Konversation terminated!)00:17
*** fray <fray!~fray@> has joined #yocto00:26
*** rfs613- is now known as rfs61300:28
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)00:51
*** starblue <starblue!~juergen@dslb-088-078-108-004.088.078.pools.vodafone-ip.de> has quit IRC (Ping timeout: 246 seconds)01:13
*** starblue <starblue!~juergen@dslb-188-109-107-144.188.109.pools.vodafone-ip.de> has joined #yocto01:15
*** alejandrohs <alejandrohs!~alejandro@user/alejandrohs> has quit IRC (Ping timeout: 272 seconds)01:53
*** alejandrohs <alejandrohs!~alejandro@user/alejandrohs> has joined #yocto01:54
*** jclsn9 <jclsn9!~jclsn@> has joined #yocto02:02
*** jclsn <jclsn!~jclsn@> has quit IRC (Ping timeout: 272 seconds)02:05
*** Chaser <Chaser!~Chaser@user/chaser> has quit IRC (Ping timeout: 256 seconds)02:11
*** Chaser <Chaser!~Chaser@user/chaser> has joined #yocto02:25
*** tangofoxtrot <tangofoxtrot!~tangofoxt@user/tangofoxtrot> has quit IRC (Ping timeout: 272 seconds)02:45
*** tangofoxtrot <tangofoxtrot!~tangofoxt@user/tangofoxtrot> has joined #yocto02:45
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto02:48
*** jclsn90 <jclsn90!~jclsn@> has joined #yocto03:01
*** jclsn9 <jclsn9!~jclsn@> has quit IRC (Ping timeout: 246 seconds)03:03
*** amitk <amitk!~amit@> has joined #yocto04:01
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)04:53
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Ping timeout: 260 seconds)05:16
*** roussinm <roussinm!~mroussin@bras-base-qubcpq1306w-grc-35-74-12-165-208.dsl.bell.ca> has quit IRC (Quit: WeeChat 3.3-dev)05:16
*** goliath <goliath!~goliath@user/goliath> has joined #yocto05:57
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has joined #yocto06:18
*** JaMa <JaMa!~martin@ip-109-238-218-228.aim-net.cz> has quit IRC (Quit: reboot)06:25
LetoThe2ndRP: sorry only now saw your highlight concerning unexports06:29
*** JaMa <JaMa!~martin@ip-109-238-218-228.aim-net.cz> has joined #yocto06:30
*** frieder <frieder!~frieder@i59F726F8.versanet.de> has joined #yocto06:30
*** Circuitsoft <Circuitsoft!uid393878@id-393878.lymington.irccloud.com> has joined #yocto06:33
*** mckoan|away is now known as mckoan06:34
mckoangood morning06:34
LetoThe2ndyo dudX && mckoan06:36
*** kroon <kroon!~kroon@89-253-118-72.customers.ownit.se> has joined #yocto06:54
*** florian_kc <florian_kc!~florian@dynamic-002-244-191-025.2.244.pool.telefonica.de> has joined #yocto06:59
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has joined #yocto07:06
*** kranzo <kranzo!~kranzo@http-v.fe.bosch.de> has joined #yocto07:29
landgrafRP: Can we close resident bitbake bug?07:29
*** kanavin_ <kanavin_!~Alexander@2a02:2454:29b:3b00:d35d:e3cf:58b5:748b> has quit IRC (Ping timeout: 252 seconds)07:34
*** dev1990 <dev1990!~dev@dynamic-78-8-240-254.ssp.dialog.net.pl> has joined #yocto07:37
*** florian_kc <florian_kc!~florian@dynamic-002-244-191-025.2.244.pool.telefonica.de> has quit IRC (Ping timeout: 260 seconds)07:41
*** kanavin <kanavin!~Alexander@2a02:2454:29b:3b00:d35d:e3cf:58b5:748b> has joined #yocto07:41
*** Schiller <Schiller!~Schiller@dynamic-002-247-255-062.2.247.pool.telefonica.de> has joined #yocto07:46
SchillerIs there a ready to use Dockerfile for the YPAutobuilder. With all the buildesentials, users, directories etc. ?07:48
mckoanSchiller: that would be a great idea! RP ^07:51
RPSchiller: not that I know of, no. It could be interesting though07:52
RPlandgraf: there were still some issues but I think we're close07:52
Schillerlandgraf: Can you give an example for potential issues? Would be good to know before ill try to set it up.07:56
qschulzamahnui[m]: then you know where to look for next changes to be made: scripts/oe-setup-builddir line 45 in poky git repo07:56
landgrafSchiller: Sorry?07:58
landgrafSchiller: was it for me? :)07:58
Schillerlandgraf: Yes :)07:59
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto08:01
landgrafSchiller: RP reported successful build https://bugzilla.yoctoproject.org/show_bug.cgi?id=14023#c11 that's why I'm wondering too :)08:01
* landgraf will run local tests over the night. Don't need additional room heating during the day.08:03
*** bps <bps!~bps@> has joined #yocto08:15
*** kroon_ <kroon_!~kroon@89-253-118-72.customers.ownit.se> has joined #yocto08:21
*** Emantor <Emantor!~Emantor@magratgarlick.emantor.de> has quit IRC (Quit: ZNC - http://znc.in)08:22
*** Emantor_ <Emantor_!~Emantor@magratgarlick.emantor.de> has joined #yocto08:22
*** kroon <kroon!~kroon@89-253-118-72.customers.ownit.se> has quit IRC (Ping timeout: 248 seconds)08:22
*** Schlumpf <Schlumpf!~Schlumpf@> has joined #yocto08:26
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto08:30
amahnui[m]<qschulz> "amahnui: then you know where..." <-  qschulz:  πŸ™πŸ½πŸ™πŸ½πŸ₯³πŸ₯³its working now without issues.08:36
amahnui[m]Thanks so much πŸ™08:36
*** manuel <manuel!~manuel@2a02:1748:dd5c:f290:c553:9012:6082:a89a> has quit IRC (Quit: Leaving)08:37
LetoThe2ndis there a ready, or close-to-ready way to boot an rpi3/4 from usb instead of uSD?08:43
LetoThe2ndagherzan: paulbarker ^^^^^08:43
agherzanLetoThe2nd: I personally never did it but I know people who do it regularly so there shouldn't be a technical issue with it08:44
LetoThe2ndagherzan: happen to know a public repo or setup for it?08:45
agherzanI guess the only small tweak would be to deal with the root device in cmdline08:45
agherzanOh well - and the other mounts (like boot partition).08:46
LetoThe2ndyeah thats obvious.08:46
agherzanHm... I think you'd find a couple on Google - let me do a short search08:46
RPlandgraf: We had our first successful build, but there was an intermittent failure in them in maybe 1 in 4 builds. I think I found and fixed that issue but there is at least one intermittent issue which could be from memres: https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/3400/steps/14/logs/stdio08:49
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto08:50
agherzanLetoThe2nd: This is basically what you need https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#boot-sequence08:50
agherzanAnd from there I would expect only very minor things to deal with on the image side.08:51
LetoThe2ndagherzan: thanks!08:51
agherzanLetoThe2nd: keep in mind that there could be another moving part on your board - the firmware version on EEPROM.08:52
*** simonew <simonew!~simonew@eth1-fw1-nbg6.eb.noris.de> has joined #yocto08:53
agherzanI'd look into that only if things don't work as you expect.08:53
LetoThe2ndagherzan: okay, understood. I just wanted to get a rough idea of the state. because if there are hard blockers ahead I'd like to rather not waste time on it :)08:55
amahnui[m]> amahnui: then you know where to look for next changes to be made: scripts/oe-setup-builddir line 45 in poky git repo08:56
amahnui[m]qschulz I just sent a patch for it.08:56
*** bps <bps!~bps@user/bps> has quit IRC (Ping timeout: 268 seconds)09:03
RPamahnui[m]: since that is a patch to openembedded-core and not the docs, there is a different mailing list that needs to go to09:08
RPamahnui[m]: also, you need to have a look at the submitting patches docs as you need to write a proper summary line for the patch09:08
amahnui[m]> amahnui: since that is a patch to openembedded-core and not the docs, there is a different mailing list that needs to go to09:11
amahnui[m]RP Your'e right. I will delete that one right away and direct it to the `openembedded-core@lists.openembedded.org` I think09:11
amahnui[m]> amahnui: also, you need to have a look at the submitting patches docs as you need to write a proper summary line for the patch09:12
amahnui[m]I will do that right away before sending the next patch09:12
RPamahnui[m]: you don't need to quote me here on irc, you can just reply using my nickname as a prefix as you've been doing09:16
*** bonalais <bonalais!uid502939@id-502939.tinside.irccloud.com> has joined #yocto09:18
amahnui[m]RP:  Okay I understand09:20
*** bps <bps!~bps@> has joined #yocto09:50
*** starblue <starblue!~juergen@dslb-188-109-107-144.188.109.pools.vodafone-ip.de> has quit IRC (Ping timeout: 268 seconds)09:54
*** starblue <starblue!~juergen@dslb-188-109-107-144.188.109.pools.vodafone-ip.de> has joined #yocto09:56
*** huseyinkozan <huseyinkozan!~hk@> has joined #yocto10:00
*** kranzo <kranzo!~kranzo@http-v.fe.bosch.de> has quit IRC (Quit: Client closed)10:00
LetoThe2ndis it normal for bitbake core-image-minimal -cdo_image_bootimg -Sprintdiff to crank away for minutes?10:16
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 272 seconds)10:20
RPLetoThe2nd: usually it will take around two parse times10:20
RPthat code doesn't function well :(10:21
LetoThe2ndstill, something feels fishy about it. my local run, that is.10:25
*** Schlumpf <Schlumpf!~Schlumpf@> has quit IRC (Ping timeout: 250 seconds)10:26
BignauxRonan[m]i still can't find a compatible qemu cpu to pass glib-2.0 configure test with meson qemuwrapper thing. if anyone has idea of disable such test for uncompatible machine.10:26
rburtonwhy do you need to run glib checks in qemu?10:28
BignauxRonan[m]that's meson build that do that ..10:30
BignauxRonan[m]glib use now meson, and meson checks with qemu to look if elf is runnable10:31
rburtonour glib has been using meson for a long time10:32
rburtonit knows its in a cross build and doesn't run things10:32
qschulzamahnui[m]: if there are changes to the patch/commit title/commit log, a newer version needs to be sent instead of just answering to the original mail with a modified version10:32
rburtonsetting a qemu wrapper complicates things because qemu isn't perfect10:32
BignauxRonan[m]i don't write it, that's default behavior10:33
rburtonBignauxRonan[m]: i guarantee you that out of the box in yocto, glib doesn't try to run stuff in qemu10:33
LetoThe2ndrburton: and in the box? (badum-tsh!)10:34
BignauxRonan[m]rburton: pure poky https://pasteall.org/D1nU10:35
rburtonah meson does have some qemu mojo10:37
rburtonif you don't have a working user-mode qemu, turn off the qemu-usermode feature in your playstation2 machine10:37
BignauxRonan[m]i'll try to do that thanks10:39
*** Schlumpf <Schlumpf!~Schlumpf@> has joined #yocto10:41
amahnui[m]qschulz: I sent a new patch to ```openembedded-core@lists.openembedded.org```  https://lists.openembedded.org/g/openembedded-core/message/16401610:50
LetoThe2ndRP: the fun part is that the diffsigs seems to block forever on "writing locked sigs to ... .inc"10:51
amahnui[m]After the `source oe-init-build-env` command worked, I ran `bitbake core-image-sato` and got the error `ERROR: The bblayers.conf file doesn't contain any BBLAYERS definition`. after checking the file, I found out that the bblayers.conf file was empty10:54
*** Schlumpf <Schlumpf!~Schlumpf@> has quit IRC (Quit: Ping timeout (120 seconds))10:56
rburtonsounds like the bit of code that writes the initial bblayers.conf needs to handle whitespace in directories too10:56
*** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC (Quit: install gentoo)10:59
amahnui[m]rburton:  Please which code handles that, So I can check it and try to solve it.10:59
*** alicef <alicef!~none@gentoo/developer/alicef> has joined #yocto11:00
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto11:06
rburtonamahnui[m]: the same code, oe-setup-builddir specifically11:07
rburtonnote that the code checks for a file existing at all, so you'll likely want to delete the existing build directory each time as you fix issues11:07
amahnui[m]rburton: thanks I'll get on it right away11:09
rburtonhm definitely seeing rust-native build more often than i'd like11:10
rburtoni swear it just rebuilt because i changed target distro features11:10
*** jclsn90 is now known as jclsn11:13
amahnui[m]rburton:  please are you speaking about the bblayers.conf error?11:16
amahnui[m]Okay I'm asking beacause I was somehow lost11:17
RPrburton: we should audit it's hash data11:22
*** Guest11 <Guest11!~Guest11@> has joined #yocto11:23
*** selff <selff!~selff@> has joined #yocto11:23
selffhi, everyone11:26
selffwhen i write yocto image to 16gb sd card with wic --auto expend option, the filesystem can only use 7gb. does not expand the rest of the space. i have x6 100mb partitions. i want all the remaining space to go to filesystem. what could it be caused by?11:26
*** Guest11 <Guest11!~Guest11@> has quit IRC (Quit: Connection closed)11:34
rburtonRP: hm, fun.  poky.conf uses package_ipk by default but the local.conf in poky uses package_rpm11:55
rburtonso if you use poky but not the template local.conf you get different behaviour11:55
*** kroon_ <kroon_!~kroon@89-253-118-72.customers.ownit.se> has quit IRC (Quit: Leaving)11:56
*** Schlumpf <Schlumpf!~Schlumpf@> has joined #yocto11:57
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto12:01
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto12:15
*** kroon <kroon!~kroon@89-253-118-72.customers.ownit.se> has joined #yocto12:23
LetoThe2ndRP: diffsigs is now stuck since an hour or so.12:23
*** MrSaturn <MrSaturn!~sam@cpe-72-224-69-22.maine.res.rr.com> has quit IRC (Quit: leaving)12:28
*** kroon <kroon!~kroon@89-253-118-72.customers.ownit.se> has quit IRC (Quit: Leaving)12:37
*** codavi <codavi!~akiCA@user/akica> has joined #yocto12:47
RPLetoThe2nd: obviously something badly wrong there :(12:53
RPrburton: hmm, that isn't expected12:54
LetoThe2ndRP: might be related to docker. maybe i'll actually find it.13:04
vvnrburton: following yesterday's conversation about the distro being the integration point, if you have a proprietary product using a open-source distro, would you write your own distro based on the public one, similar to how poky-altcfg requires poky.conf?13:05
*** ar__ <ar__!~akiCA@user/akica> has joined #yocto13:07
rburtonif you're actually deriving from it, sure13:08
*** codavi <codavi!~akiCA@user/akica> has quit IRC (Ping timeout: 250 seconds)13:10
*** selff <selff!~selff@> has quit IRC (Ping timeout: 250 seconds)13:39
*** hushmoney <hushmoney!~hushmoney@de1.hashbang.sh> has joined #yocto13:47
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto13:50
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has quit IRC (Remote host closed the connection)14:16
RPI'm thinking, pseudo fix, lidsdl unwind dependency removal,  the apt patches but not the test and then build rc1 ?14:28
LetoThe2ndRP: thinking is overrated.14:45
*** simonew <simonew!~simonew@eth1-fw1-nbg6.eb.noris.de> has quit IRC (Ping timeout: 250 seconds)14:52
sgwRP: abelloni: Ignore the patches I just sent!14:53
sgwtoo early to be sending those emails.14:54
tgamblinzeddii: hypothetically, how much of a pain would it be to add features/nf_tables/nf_tables.scc to the linux-yocto KERNEL_FEATURES list in a future release?14:54
zeddiitgamblin. it's easy enough to do, but if we add it by default, it should be to support some sort of core functionality, or be enabled by distro/machine configuration.15:01
tgamblinzeddii: Right now I am only aware of iptables-nft relying on it in oe-core, which is not (yet) the default build for that recipe15:02
*** bonalais <bonalais!uid502939@id-502939.tinside.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)15:07
*** GLumen <GLumen!~Gregory@97-126-1-223.tukw.qwest.net> has joined #yocto15:12
*** GLumen_ <GLumen_!~Gregory@97-126-1-223.tukw.qwest.net> has joined #yocto15:13
*** Schiller <Schiller!~Schiller@dynamic-002-247-255-062.2.247.pool.telefonica.de> has quit IRC (Ping timeout: 250 seconds)15:13
LetoThe2ndi've got a changed sig error and did bitbake core-image-minimal -cdo_image_bootimg -Snone, then bitbake core-image-minimal -cdo_image_bootimg -Sprintdiff. I got The differences between the current build and any cached tasks start at the following tasks:15:17
*** GLumen <GLumen!~Gregory@97-126-1-223.tukw.qwest.net> has quit IRC (Ping timeout: 246 seconds)15:17
LetoThe2nd/data/imx7/kirkstone-build/poky/meta/recipes-core/images/core-image-minimal.bb:do_image_qaThe differences between the current build and any cached tasks start at the following tasks:15:17
LetoThe2ndhow to proceed from there?15:17
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)15:33
*** grma <grma!~gruberm@> has quit IRC (Remote host closed the connection)15:37
*** goliath <goliath!~goliath@user/goliath> has joined #yocto15:39
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)15:46
frayI'm seeing cases where I do something like: SRC_URI = "file:///foo/bar/my_file.c"  that the file ends up (after do_fetch) in ${WORKDIR}/foo/bar/my_file.c  Why isn't it directly in ${WORKDIR}?  Or is there a simple way I can get it to end up directly in WORKDIR?15:48
fray(the issue is a user has to pass in a preparsed .c file for a utility, and this file could be passed in from anywhere on the disk.. so this moving path is driving me nuts)15:49
*** grma <grma!~gruberm@> has joined #yocto15:51
*** starblue <starblue!~juergen@dslb-188-109-107-144.188.109.pools.vodafone-ip.de> has quit IRC (Ping timeout: 268 seconds)15:51
*** starblue <starblue!~juergen@dslb-188-109-107-144.188.109.pools.vodafone-ip.de> has joined #yocto15:52
vvnfray: SRC_URI = "file:///foo/bar/my_file.c;subdir=${WORKDIR}" (or subdir=., try both)15:53
fraythanks, I will try that.15:54
*** manuel1985 <manuel1985!~manuel198@> has joined #yocto15:59
*** Schlumpf <Schlumpf!~Schlumpf@> has quit IRC (Quit: Client closed)16:15
*** mckoan is now known as mckoan|away16:16
RPDon't suppose anyone knows much about thunderbolt docks hardlocking thinkpads? :/16:21
frayyikes, no..  I've heard of some issues with bad cables doing that.. but not hte docks themselves16:27
RPfray: the dock is fine with one laptop but not the new one :/16:28
fraythudnerbolt 2/3/4?  (old vs new)16:30
RPfray: 416:30
frayI use a thunderbold 3 dock on my MacBook..  I've got a thunderbolt 2 dongle.16:30
RPwell, the older laptop may not be using v416:30
fray4 is relatively new standard.. so it's probably a 2 or 3.. it's possible ther eis a bug in the new machine against say thunderbold 2 devices.16:31
fraythe PCIe is roughly the same, but the speed is vastly differently between the three16:31
RPthe dock is definitely a 4, its a new one16:31
*** Minvera <Minvera!~Minvera@user/Minvera> has joined #yocto16:32
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat)16:36
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 248 seconds)16:40
*** camus <camus!~Instantbi@> has joined #yocto16:41
amahnui[m]Hello rburton , The bblayers.conf file now contains the BBLAYER definitions but then it still gives the error... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/b7e8ee9052f6140dd96db1a048956c24ee5b73e9)16:53
amahnui[m]When I run the `bitbake core-image-sato` command16:54
amahnui[m] * Hello rburton , The bblayers.conf file now contains the BBLAYER definitions but then it still gives the error... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/909c744ea825d4d82a0cb9bd561d9cc086055938)16:56
amahnui[m] * Hello rburton , The bblayers.conf file now contains the BBLAYER definitions but then it still gives the error... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/b7ed0534ce8ab2ffa9c7dc59dfb17d38d4c3d05b)16:57
amahnui[m] * Hello rburton , The bblayers.conf file now contains the BBLAYER definitions but then it still gives the error... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/6e938d52ea5898a0b70ad631cede3a873c524464)16:57
*** manuel1985 <manuel1985!~manuel198@> has quit IRC (Quit: Leaving)17:13
*** frieder <frieder!~frieder@i59F726F8.versanet.de> has quit IRC (Remote host closed the connection)17:14
*** florian_kc <florian_kc!~florian@dynamic-002-244-191-025.2.244.pool.telefonica.de> has joined #yocto17:17
amahnui[m]I manually added the quotes around the `test repo` in the bblayer.conf file to see how it will react gave the same error17:26
*** goliath <goliath!~goliath@user/goliath> has joined #yocto17:27
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 246 seconds)17:31
amahnui[m]I think the file that grabs those directories from bblayer.conf when bitbake command is run is where the issue comes from, but I can't find the exact file that handles that operation.17:34
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has quit IRC (Remote host closed the connection)17:49
*** elfenix|cloud <elfenix|cloud!sid516192@id-516192.helmsley.irccloud.com> has left #yocto17:53
amahnui[m]Please which mailing list accepts changes to bitbake/toaster?18:03
Saur[m]amahnui: The problem is that the `BBLAYERS` variable is a whitespace separated list of paths, i.e., the first thing bitbake does when using it is calling `split()` on it, which obviously is not compatible with trying to use paths that contain spaces in it...18:03
amahnui[m]* list accepts patches for changes to18:03
amahnui[m]Saur: That makes a lot of sense I saw the python script and did not see a way to get arround that issue18:05
amahnui[m]What if a condition was made to check for quotes and not to split at a white space until it meets the second quote.18:07
Saur[m]amahnui: I believe the only solution is to detect the problem sooner, i.e., in the `oe-init-build-env` code itself.18:07
Saur[m]There is really no point in generating the bblayers.conf file with such paths in it as it will never be usable anyway.18:08
*** kevinrowland <kevinrowland!~kevinrowl@> has joined #yocto18:09
amahnui[m]Saur: Thats right.18:11
fraySRC_URI = .... ;subdir=${WORKDIR} doesn't work.  It complains about a circular dependency18:12
vvnfray: a quick and dirty fix I have for your problem is to use a symlink my_file.c -> /foo/bar/my_file.c and use SRC_URI = "file://my_file.c" instead of the full path.18:15
NishanthMenonjust curious - is there a standard name (suffix/prefix) folks use for machine names when a single build can support multiple boards?18:17
fraymy worry is that I need to use the exact file the user passes in, but there is a default version already in the system..  otherwise I'd add the users path to FILESEXTRAPATHS18:19
frayI suppose what I can do is just pass it in that way and if the user has other files in the directory that conflict they'll just get errors..18:19
fraybut ya, something is really broken. file://foo/bar/foo.c results in ${WORKDIR}/foo/bar/foo.c being created.   If I do subdir=.., it creates ${WORKDIR}/../foo/bar/foo.c18:20
fraythat seems broken it me (not the subdir part) but that it puts files into subdirectories without that being specified18:20
amahnui[m]Please which mailing list accepts patches for bitbake changes18:25
fraybitbake-devel see lists.openembedded.org18:27
amahnui[m]fray: Thanks18:28
moto-timoRP: with the patch I just sent to bb and toaster MLs, hardknott and honister both build via the UI on the honister branch18:43
moto-timoI always build 'quilt-native' as the target... as that is what the toaster-container smoketests  build18:45
LetoThe2ndanybody around who can give me some pointers on a changing basehash problem? already did the -Snone + -Sprintdiff dance, but that only gave me a "starts in task"18:47
LetoThe2ndah found it19:03
LetoThe2ndit seems like ${BB_CURRENTTASK} is not expanded on the second parse? is that posssible?19:08
*** shaysenberg <shaysenberg!~shaysenbe@> has joined #yocto19:09
*** shaysenberg <shaysenberg!~shaysenbe@> has left #yocto (Leaving)19:12
*** skoech[m] <skoech[m]!~skoechmat@2001:470:69fc:105::1:f0c9> has joined #yocto19:29
RPmoto-timo: I think the master fails is because you didn't clear the environment between the two builds and it's the pre renaming envvars?19:30
moto-timoRP: ah... possibly... that has happened before ;)19:30
RPmoto-timo: thanks for testing hardknott and honister though, that sounds promising19:34
moto-timoRP: hardknott also passes on hardknott branch with what I have in contrib timo/hardknott/toaster-fixes... not sure if the last two commits there are needed or not19:35
*** florian_kc <florian_kc!~florian@dynamic-002-244-191-025.2.244.pool.telefonica.de> has quit IRC (Ping timeout: 268 seconds)19:37
RPmoto-timo: I think those are "nice to have" but probably don't break toaster. I'm leaning to not risking them on hardknott at this point19:37
moto-timoRP: fair enough... that is a rebased "old" branch19:37
RPI'm trying to fix it without risking anything else19:38
*** GillesMM <GillesMM!~gilles@> has joined #yocto19:39
*** GillesMM <GillesMM!~gilles@> has quit IRC (Remote host closed the connection)19:39
cambrian_invaderGLumen_: bitbake-whatchanged always says the same things have changed, whether run before or after a complete build19:41
RPmoto-timo: I merged the honister patch thanks19:41
moto-timoRP: testing hardknott similar patch now (rebased again)19:41
GillesMHello how can I use keymaps receipe ?19:50
sotaoverridetrying to add a super simple bash script to target (runs some nmcli commands). What's the RDEPENDS for bash scripts that would take care of the "requires /bin/bash" bitbake error?19:55
RPsotaoverride: RDEPENDS_${PN} += "bash" ?19:56
LetoThe2ndRP: dang you typed faster19:56
LetoThe2ndRP: as compensation you owe me a hint on the BB_CURRENTTASK-in-reparse phenomenon ;-)19:57
*** leon-anavi <leon-anavi!~Leon@> has quit IRC (Ping timeout: 260 seconds)19:58
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto19:59
vvnif you have a machine specific service (e.g. install stuffs on a partition, etc.) do you usually write an explicit recipe for it (e.g. install-on-emmc.bb) or do you append such script/service to a generic recipe?19:59
Saur[m]RP: Btw, regarding the mail discussion we had the other day regarding appending to `PREMIRRORS`, I just realized that it was all based on a mistake on my part. I had mixed up the problem with combining ??= and += for ?= and +=. It is ??= with += that is problematic, but since we use `PREMIRRORS ?= ...` in our configuration, adding the sourceware URLS using += is not problem (for us). Sorry for the noise.20:01
LetoThe2ndvvn: depends - if it is something that has value of its own, or that relates to an existing recipe, basically.20:01
moto-timoRP: hardknott patch sent20:02
moto-timoRP: still fails on master branch but I'm going to take the win for hardknott/honister working and move on20:02
vvnLetoThe2nd: e.g. my system can run on the SD card (default) or the eMMC (requires to run a service). How would you personally package such systemd service?20:03
LetoThe2ndvvn: i personally would probably put it into a recipe of its own, just gut feeling without knowing more about it.20:05
RPLetoThe2nd: I'm missing context, I guess I need to scroll back?20:07
RPSaur[m]: ah, right. I was thinking something didn't seem quite right20:07
RPmoto-timo: I don't understand master not working :/20:07
RPLetoThe2nd: BB_CURRENTTASK would only be set in the running task context maybe?20:08
vvnLetoThe2nd: I see. I like that it is very explicit, but I struggle to figure out how to organize the code. Would you add this recipe in a BSP layer's recipes-bsp or on your distro layer?20:08
RPin a general metadata parse, it would have no correct value20:08
LetoThe2ndRP: in a nutshell: i'm having a basehash changed error, and it seems that BB_CURRENTTASK is not expanded in the reparse. diffsigs gave me image_task vs ${BB_CURRENTTAST}20:08
moto-timoRP: me either. Punting at this point. Dunfell and kirkstone work and those are what matter the most.20:09
LetoThe2ndvvn: very generically, i would put it into the bsp, and at to MACHINE_RDEPENDS (or whatsitcalled) for the MACHINE conf that needs it.20:09
RPmoto-timo: person on the list said master worked for them20:10
RPLetoThe2nd: BB_CURRENTTASK wouldn't get set at parse time at all20:10
vvnLetoThe2nd: it makes a lot of sense, I will do that thank you.20:10
LetoThe2ndRP: so the conclusion would be that BB_CURRENTTASK must not be used in a recipe at all, because it would always fall over?20:10
LetoThe2ndvvn: have fun20:11
RPLetoThe2nd: I didn't say that, I'm sure we have users20:11
RPLetoThe2nd: I'd suspect it is a red herring20:12
vvnLetoThe2nd: I wouldn't call that fun, but anything that ease the maintenance is a win20:12
moto-timoRP: yeah, it's only a 'master' project on hardknott or honister branch that fails... 'master' on 'master' is fine, 'master' or 'dunfell' on 'dunfell' are fine. shrug.20:12
LetoThe2ndRP: i know you didn't say that, let me try to rephrase. it would always fail the diffsig when used - exception: in python code, because thats the only usage i could easily spot in actual artifact generation.20:13
LetoThe2ndRP: or do you mean this actually hides a completely different problem?20:13
RPmoto-timo: oh, right. In that case I'm not worrying about that, yes20:15
RPmoto-timo: will be the variable renaming20:15
moto-timoRP: yep, let it go :)20:15
moto-timohappy to have achieved what we did :)20:15
* LetoThe2nd congratulates moto-timo and RP without knowing the archievement, but hey! awesome!20:16
RPLetoThe2nd: we have recipes using BB_CURRENTTASK. Note that BB_HASHEXCLUDE_COMMON includes BB_CURRENTTASK20:16
LetoThe2ndRP: ok, then I'll dig a bit more. thanks! (bedtime, finally)20:17
RPLetoThe2nd: so I think the idea this is your problem is incorrect20:17
LetoThe2ndkthx :-(20:17
RPLetoThe2nd: it could be but I can't really see it20:17
RPLetoThe2nd: sorry, you did ask my view though :)20:17
*** florian_kc <florian_kc!~florian@dynamic-002-244-191-025.2.244.pool.telefonica.de> has joined #yocto20:19
GLumen_cambrian_invader: Sanity check, you have `CACHE` defined, right? (I mostly spend my time debugging why SSTATE caching fails, and am less familiar with the logic around re-use of the working directories)20:21
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)20:23
GLumen_cambrian_invader: Does `bitbake -S printdiff <image>` tell you anything interesting?20:27
vvnLetoThe2nd: actually MACHINE_EXTRA_RDEPENDS += "specific-package1 specific-package2" avoids the need for .bbappend and overrides, or using generic scripts in machine-specific path (e.g. generic-package/beaglebone/install-script)20:28
cambrian_invadernot really20:29
*** florian_kc <florian_kc!~florian@dynamic-002-244-191-025.2.244.pool.telefonica.de> has quit IRC (Ping timeout: 272 seconds)20:30
cambrian_invaderthis time I added UBOOT_SIGN_ENABLE=1 in my loca.conf and now gcc is getting rebuilt20:41
cambrian_invaderI just hate how a one line config change can literally turn into a lost hour\20:42
RPmoto-timo: thanks, I merged hardknott too20:55
moto-timoRP: thank you! I couldn't test those changes prevously :)20:56
*** Minvera <Minvera!~Minvera@user/Minvera> has quit IRC (Remote host closed the connection)21:00
*** florian_kc <florian_kc!~florian@dynamic-002-244-191-025.2.244.pool.telefonica.de> has joined #yocto21:12
*** huseyinkozan <huseyinkozan!~hk@> has quit IRC (Quit: Konversation terminated!)21:13
* RP builds 4.0 rc121:30
* RP can't help thinking there was something I'm forgetting to do21:30
* vvn concludes one year later that trying to maintain a generic machine configuration file is a bad idea because machine-level tweaks are often needed and thus these files are product specific21:37
*** florian_kc <florian_kc!~florian@dynamic-002-244-191-025.2.244.pool.telefonica.de> has quit IRC (Ping timeout: 250 seconds)21:41
*** ar__ <ar__!~akiCA@user/akica> has quit IRC (Ping timeout: 268 seconds)21:50
*** goliath <goliath!~goliath@user/goliath> has joined #yocto22:00
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)22:08
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto22:08
GLumen_I'm trying to debug an issue with `bitbake --dump-signatures=printdiff` and Multiconfig: I'm building an initramfs config alongside the normal device config, and for ...reasons... I have different TMPDIRs for each config. `write_diffscenetasks` is choking on the stampsfile for `core-image-tiny-initramfs:do_rootfs` which is correctly placed under the initramfs TMPDIR, but `find_siginfo` is only searching under the TMPDIR for the device config.22:12
GLumen_Any advice?22:12
kergothif your'e using multiconfig, you probably need to specify the multiconfig when using -S printdiff.22:23
*** chep <chep!~chep@82-65-36-115.subs.proxad.net> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)22:27
*** chep <chep!~chep@82-65-36-115.subs.proxad.net> has joined #yocto22:29
GLumen_kergoth: Unfortunately I'm using `INITRAMFS_IMAGE_BUNDLE = "1"`, so even when specifying `mc::image` I hit the same error. I guess I could temporarily disable INITRAMFS_IMAGE_BUNDLE and then run dump-signatures separately on core-image-tiny-initramfs and my device recipe.22:40
*** dev1990 <dev1990!~dev@dynamic-78-8-240-254.ssp.dialog.net.pl> has quit IRC (Quit: Konversation terminated!)23:20
*** camus <camus!~Instantbi@> has joined #yocto23:24
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 246 seconds)23:28
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Ping timeout: 250 seconds)23:33
*** camus <camus!~Instantbi@2409:8a1e:9115:e190:704b:4b0d:8dc4:7c21> has joined #yocto23:52
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)23:54
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Ping timeout: 240 seconds)23:55
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto23:57

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