Monday, 2020-09-14

*** m1ster_r0b0t <m1ster_r0b0t!~m1ster_r0@prometheus.umask.eu> has quit IRC00:01
*** m1ster_r0b0t <m1ster_r0b0t!~m1ster_r0@prometheus.umask.eu> has joined #yocto00:02
*** yann <yann!~yann@88.120.44.86> has quit IRC00:26
*** dev1990 <dev1990!~dev@62.87.215.57> has quit IRC00:46
*** dp <dp!~phillid@oh.not.bad.aye.yeah.nah.nz> has joined #yocto01:34
*** manuel1985 <manuel1985!~manuel@213-147-160-39.nat.highway.bob.at> has quit IRC01:35
*** kaspter <kaspter!~Instantbi@58.246.136.202> has joined #yocto01:37
*** manuel1985 <manuel1985!~manuel@089144217128.atnat0026.highway.a1.net> has joined #yocto01:51
dpHi all, I know about `bitbake-layers show-recipes` but is there a way to list recipes within specific layers, aside from including only the desired layer in my bblayers.conf?01:57
*** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC02:01
*** alicef <alicef!~none@gentoo/developer/alicef> has joined #yocto02:01
zeddiicd $layer; find . -name '*.bb' ?02:16
zeddii:)02:16
dpYeah that's what I'm resorting to otherwise02:26
*** kaspter <kaspter!~Instantbi@58.246.136.202> has quit IRC02:28
*** kaspter <kaspter!~Instantbi@58.246.136.202> has joined #yocto02:28
*** nslu2-log_ <nslu2-log_!~nslu2-log@milla.nas-admin.org> has joined #yocto02:29
*** nslu2-log <nslu2-log!~nslu2-log@milla.nas-admin.org> has quit IRC02:30
*** nslu2-log_ is now known as nslu2-log02:30
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has quit IRC02:55
*** hpsy1 <hpsy1!~hpsy@92.118.12.72> has joined #yocto02:55
*** hpsy <hpsy!~hpsy@92.118.12.72> has quit IRC02:56
*** nslu2-log_ <nslu2-log_!~nslu2-log@milla.nas-admin.org> has joined #yocto03:09
*** nslu2-log <nslu2-log!~nslu2-log@milla.nas-admin.org> has quit IRC03:11
*** nslu2-log_ is now known as nslu2-log03:12
*** camus1 <camus1!~Instantbi@58.246.136.202> has joined #yocto03:56
*** kaspter <kaspter!~Instantbi@58.246.136.202> has quit IRC03:56
*** camus1 is now known as kaspter03:56
*** jrdn <jrdn!~jrdn@S010668ff7b6b7383.ok.shawcable.net> has joined #yocto04:06
*** ibinderwolf <ibinderwolf!~quassel@etrn.topcontrol.it> has joined #yocto05:05
*** beneth <beneth!~beneth@irc.beneth.fr> has joined #yocto05:06
*** feddischson <feddischson!~feddischs@HSI-KBW-109-192-195-181.hsi6.kabel-badenwuerttemberg.de> has joined #yocto05:08
*** kaspter <kaspter!~Instantbi@58.246.136.202> has quit IRC05:33
*** kaspter <kaspter!~Instantbi@58.246.136.202> has joined #yocto05:33
*** jobroe <jobroe!~manjaro-u@p579eb7b4.dip0.t-ipconnect.de> has joined #yocto05:34
*** nslu2-log_ <nslu2-log_!~nslu2-log@milla.nas-admin.org> has joined #yocto05:36
*** nslu2-log <nslu2-log!~nslu2-log@milla.nas-admin.org> has quit IRC05:36
*** nslu2-log_ is now known as nslu2-log05:36
*** nslu2-log_ <nslu2-log_!~nslu2-log@milla.nas-admin.org> has joined #yocto05:38
*** nslu2-log <nslu2-log!~nslu2-log@milla.nas-admin.org> has quit IRC05:41
*** matthewzmd <matthewzmd!~user@72.138.138.18> has joined #yocto05:41
*** nslu2-log_ is now known as nslu2-log05:41
*** AndersD <AndersD!~AndersD@h-98-128-162-82.NA.cust.bahnhof.se> has joined #yocto05:46
*** pohly <pohly!~pohly@p54849295.dip0.t-ipconnect.de> has joined #yocto05:51
*** khem <khem!~khem@unaffiliated/khem> has quit IRC05:53
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto05:54
*** khem <khem!~khem@unaffiliated/khem> has quit IRC05:57
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto05:57
*** AndersD <AndersD!~AndersD@h-98-128-162-82.NA.cust.bahnhof.se> has quit IRC05:58
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto05:58
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto05:59
*** matthewzmd <matthewzmd!~user@72.138.138.18> has quit IRC06:00
*** zandrey <zandrey!~zandrey@cable-static2-2-7.rsnweb.ch> has quit IRC06:00
*** matthewzmd <matthewzmd!~user@72.138.138.18> has joined #yocto06:00
*** matthewzmd <matthewzmd!~user@72.138.138.18> has quit IRC06:06
*** matthewzmd <matthewzmd!~user@72.138.138.18> has joined #yocto06:07
*** manuel1985 <manuel1985!~manuel@089144217128.atnat0026.highway.a1.net> has quit IRC06:12
*** jrdn <jrdn!~jrdn@S010668ff7b6b7383.ok.shawcable.net> has quit IRC06:12
*** ilkappe <ilkappe!c65a42b1@198.90.66.177> has joined #yocto06:23
ilkappehello guys, I'm struggling with kernel patches. I've to patch the defconfig and a Kconfig file inside a kernel tree. So, I've downlaaded the kernel with bitbake, modified the mentioned files inside the git/ folder. So that if I run "git status" I can see the previous files as modified. The I create the patch running "git diff > mypatch.patch". Then06:28
ilkappeI copied the patch insid the "files" folder in the recipe folder. By the way the do_patch tasks seems to do nothing as the final .config files is not modified at all. ANy suggestion ?06:28
khemilkappe: check in recipe which file its using for creating .config06:36
*** NiksDev <NiksDev!~NiksDev@192.91.101.32> has quit IRC06:38
*** NiksDev <NiksDev!~NiksDev@192.91.101.31> has joined #yocto06:39
khemsometimes defconfig is added via file:// and used06:39
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has joined #yocto06:39
*** leon-anavi <leon-anavi!~Leon@78.130.197.211> has joined #yocto06:41
*** mckoan|away is now known as mckoan06:42
mckoangood morning06:42
ilkappekhem, yep, no defconfig is added via file:// it's the one in the kernel's config folder. The strange thing by the way is that the patches seems to have no effect on the repo since if I run git status in the kernel folder I can't see any new commit on the tree06:47
*** gsalazar <gsalazar!955ab50e@gateway/web/cgi-irc/kiwiirc.com/ip.149.90.181.14> has joined #yocto06:58
*** agust <agust!~agust@p508b6ab0.dip0.t-ipconnect.de> has joined #yocto06:59
erboilkappe: In addition to adding the patch to files/, do you also add it to SRC_URI?07:23
*** dev1990 <dev1990!~dev@62.87.215.57> has joined #yocto07:25
*** yann <yann!~yann@88.120.44.86> has joined #yocto07:27
ilkappeerbo, yes I have ! The strange thin is also that the patches are not in the WORKDIR dir07:27
*** manuel1985 <manuel1985!~manuel@62.99.131.178> has joined #yocto07:28
*** lucaceresoli <lucaceresoli!~lucaceres@78-134-51-148.v4.ngi.it> has joined #yocto07:29
*** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has quit IRC07:29
*** rcoote <rcoote!~rcoote@221-224-024-217.ip-addr.vsenet.de> has joined #yocto07:30
*** nrossi <nrossi!nrossimatr@gateway/shell/matrix.org/x-vlcppgqtjebyiqdd> has joined #yocto07:40
*** carlsb3rg <carlsb3rg!c147b478@193.71.180.120> has joined #yocto07:45
*** manuel1985 <manuel1985!~manuel@62.99.131.178> has quit IRC07:45
carlsb3rgHi! I need some custom bootloader arguments in my bake and realize I can use the canned directdisk-bootloader-config from poky/scripts/lib/wic/canned-wks/, but I want the directdisk-bootloader-config.cfg to be a part of my bsp layer and not change the original directdisk-bootloader-config.cfg in the poky directory. How do I go about that?07:49
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto07:52
carlsb3rgI was thinking of .bbappending the recipe that provides "WKS_FILE" and the rest of the WKS stuff to change the directory where it searches for wks files, but that might not be the right way to go. The directdisk-bootloader-config.wks file includes common.wks.inc which is also in the poky directory. I guess what I'm saying is that I can't find any07:53
carlsb3rgway of changing the bootloader parameters without modifying files in the poky directory.07:53
*** marquiz <marquiz!marquiz@nat/intel/x-ndepsixevuefawfv> has quit IRC07:53
*** hpsy1 <hpsy1!~hpsy@92.118.12.72> has quit IRC07:58
*** hpsy <hpsy!~hpsy@92.118.12.72> has joined #yocto07:58
erboilkappe: That is strange. If you do e.g. "bitbake -e virtual/kernel | grep ^SRC_URI", do you see that the final SRC_URI really contains your patch?08:00
*** marquiz <marquiz!marquiz@nat/intel/x-byrgunridvsmudrk> has joined #yocto08:00
*** manuel1985 <manuel1985!~manuel@62.99.131.178> has joined #yocto08:00
*** chris_ber <chris_ber!~quassel@213.138.44.181> has joined #yocto08:04
ilkappeerbo, thanks, I've missed a typo in SRC_URI08:07
*** goliath <goliath!~goliath@82.150.214.1> has joined #yocto08:18
*** zandrey <zandrey!~zandrey@193.8.40.126> has joined #yocto08:21
*** wooosaiiii <wooosaiiii!~wooo@89-212-21-243.static.t-2.net> has joined #yocto08:27
*** kanavin_home <kanavin_home!~ak@2a02:2450:1011:56f:b652:c378:b428:fdf> has joined #yocto08:29
*** psnsilva_ <psnsilva_!~psnsilva@207.15.249.5.rev.vodafone.pt> has joined #yocto08:37
*** PaowZ <PaowZ!~vince@2a01:e35:2e3e:4ac0:7da9:2f6a:f755:42c5> has quit IRC08:39
*** PaowZ <PaowZ!~vince@2a01:e35:2e3e:4ac0:7da9:2f6a:f755:42c5> has joined #yocto08:39
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has joined #yocto09:08
*** psnsilva__ <psnsilva__!~psnsilva@194.38.148.130> has joined #yocto09:18
*** psnsilva_ <psnsilva_!~psnsilva@207.15.249.5.rev.vodafone.pt> has quit IRC09:20
*** sinseman44 <sinseman44!a5e14d32@165.225.77.50> has joined #yocto09:22
*** eduardas <eduardas!~eduardas@85.254.96.13> has joined #yocto09:35
xantozhi. is there a way to stop wic from writing to /etc/fstab ?09:41
xantozfor reasons, I need a manually created /etc/fstab, and I don't want wic to touch it09:42
*** zandrey <zandrey!~zandrey@193.8.40.126> has quit IRC09:42
*** ak77 <ak77!~akrpic77@193.46.75.3> has quit IRC09:46
*** mort <mort!~mort96@snow/mort96> has quit IRC09:46
*** ak77 <ak77!~akrpic77@193.46.75.3> has joined #yocto09:46
*** mario-goulart <mario-goulart!~user@static.107.70.9.5.clients.your-server.de> has quit IRC09:46
*** mario-goulart <mario-goulart!~user@static.107.70.9.5.clients.your-server.de> has joined #yocto09:46
*** mort <mort!~mort96@snow/mort96> has joined #yocto09:46
*** armpit <armpit!~armpit@2601:202:4180:a5c0:e1aa:69c3:1411:f726> has quit IRC09:46
*** armpit <armpit!~armpit@2601:202:4180:a5c0:2975:33fa:6fa4:1208> has joined #yocto09:47
*** nslu2-log <nslu2-log!~nslu2-log@milla.nas-admin.org> has quit IRC09:53
*** nslu2-log <nslu2-log!~nslu2-log@milla.nas-admin.org> has joined #yocto09:54
*** nslu2-log <nslu2-log!~nslu2-log@milla.nas-admin.org> has quit IRC09:59
*** nslu2-log <nslu2-log!~nslu2-log@milla.nas-admin.org> has joined #yocto09:59
*** LocutusOfBorg <LocutusOfBorg!~locutusof@ubuntu/member/locutusofborg> has quit IRC10:04
paulbarkerxantoz: `--no-fstab-update`10:05
paulbarkerxantoz: As an argument to the wic program10:06
xantozright. where does it get called, normally?10:06
paulbarkerxantoz: It's executed from image_types_wic.bbclass10:06
xantozok, so I should override that somehow?10:07
paulbarkerI think `WIC_CREATE_EXTRA_ARGS` is the variable to add command line args for wic10:07
xantozah, that might be easier10:07
paulbarkerIt's not terribly well documented, you may have to look at https://git.openembedded.org/openembedded-core/tree/meta/classes/image_types_wic.bbclass10:07
xantozright now I tried just removing the "--fsoptions" in the .wks file10:07
paulbarkerAnd https://git.openembedded.org/openembedded-core/tree/scripts/wic10:07
*** LocutusOfBorg <LocutusOfBorg!~locutusof@ubuntu/member/locutusofborg> has joined #yocto10:08
*** florian_kc is now known as florian10:08
xantozthanks for the tips10:09
*** jobroe_ <jobroe_!~manjaro-u@p579eba78.dip0.t-ipconnect.de> has joined #yocto10:20
*** jobroe <jobroe!~manjaro-u@p579eb7b4.dip0.t-ipconnect.de> has quit IRC10:22
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto10:45
*** radsquirrel <radsquirrel!~bradleyb@mail.fuzziesquirrel.com> has quit IRC10:59
*** jtrimble <jtrimble!64247c08@pool-100-36-124-8.washdc.fios.verizon.net> has joined #yocto11:01
jtrimbleHi all -- a question regarding multiconfig:  What are the advantages of using a "multiconfig" arrangement over just having multiple yocto build directories pointing to the same source layers?11:02
rburtonjtrimble: multiconfig lets you build a single artifact that has multiple configurations in11:14
rburtonthink an image that ships a hypervisor, a linux filesystem, and a rtos app11:30
rburtonor firmware, or whatever11:30
*** kamel_b <kamel_b!~kamel@ec2-52-47-93-88.eu-west-3.compute.amazonaws.com> has quit IRC11:36
*** kamel_b <kamel_b!~kamel@ec2-52-47-93-88.eu-west-3.compute.amazonaws.com> has joined #yocto11:38
*** berton <berton!~berton@181.220.78.182> has joined #yocto11:46
*** BobPungartnik <BobPungartnik!~BobPungar@177.41.204.30> has joined #yocto11:47
qschulzkinda stupid question but why do we not disable configure and compile tasks for allarch inheriting recipes?11:55
rburtonbecause you can still configure and so on11:55
rburtonthink an icon theme11:55
rburtonlike adwaita11:55
rburtonthat configures and "compiles" (converts SVG to PNG), but the output is arch-independent11:56
rburtonallarch does break configure so if it looks for a proper compiler, it fails11:56
bluelightningok, outreachy project submitted11:59
bluelightningwe may have a corresponding influx of potential contributors soon (hopefully !)11:59
bluelightningndec ^^ FYI12:00
qschulzrburton: makes sense, thx!12:04
paulbarkerbluelightning: That looked like a really useful project, I hope we have plenty of applications :)12:10
RPbluelightning: thanks for doing it!12:10
*** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-mrioxxbuqjrilpxn> has joined #yocto12:16
*** psnsilva__ <psnsilva__!~psnsilva@194.38.148.130> has quit IRC12:18
ndecbluelightning: thanks!12:34
*** psnsilva <psnsilva!~psnsilva@2001:818:dae7:b100:8cbe:5797:375a:2468> has joined #yocto12:35
*** Konsgnx <Konsgnx!~Konsgnx3@66-109-34-138.tvc-ip.com> has joined #yocto12:38
*** kanavin_home <kanavin_home!~ak@2a02:2450:1011:56f:b652:c378:b428:fdf> has quit IRC12:44
JPEWRP: Well, I think the bitbaker cooker is a lot more stable now. After rebasing, I ran 4000+ iterations of the torture test this weekend and I stopped it without it deadlocking. Before that it was only getting about 100 before something would break12:45
RPJPEW: that is good news :)12:46
RPJPEW: I also now know where its blocking causing the timeout problems on the autobuilder, its the SyncThread. Any ideas on why that could be so slow? Simply IO bound?12:46
JPEWPossibly. Could be waiting on semaphore or something also12:47
RPJPEW: a sempahore from where? :/12:47
RPbitbake is otherwise "gone" at that point12:47
*** sstiller <sstiller!~sstiller@b2b-94-79-174-114.unitymedia.biz> has joined #yocto12:48
JPEWRP: Ya, I don't know. I/O seems more likely. I don't think I ever saw that one in the torture test, so I/O seems most likely12:48
RPJPEW: ideas for better debug to help diagnose welcome, I've not gotten to thinking about it yet12:48
RPJPEW: does your torture test include invalid metadata to parse?12:48
JPEWIt doesn't12:48
JPEWThat's a good idea though12:49
*** nslu2-log_ <nslu2-log_!~nslu2-log@milla.nas-admin.org> has joined #yocto12:51
*** nslu2-log <nslu2-log!~nslu2-log@milla.nas-admin.org> has quit IRC12:54
*** nslu2-log_ is now known as nslu2-log12:54
JPEWRP: On the bad news, parsing seems to have gotten slower. A simple clean `bitbake -p` takes ~35s for me when it used to take < 20s (sorry, I don't have the exact numbers from before). Not sure if this is just my local setup or if it did indeed get slower...12:56
*** kanavin_home <kanavin_home!~ak@2a02:2450:1011:56f:b652:c378:b428:fdf> has joined #yocto12:57
JPEWRP: Nevermind. Must just be me. I went back and it's still slower. I must have changed something in local.conf w/o realizing13:00
*** Sandrita <Sandrita!b8a36cf4@gateway/web/cgi-irc/kiwiirc.com/ip.184.163.108.244> has joined #yocto13:04
*** maudat <maudat!~moda@bras-vprn-mtrlpq2848w-lp130-10-174-92-198-55.dsl.bell.ca> has joined #yocto13:05
*** nslu2-log_ <nslu2-log_!~nslu2-log@milla.nas-admin.org> has joined #yocto13:05
*** nslu2-log <nslu2-log!~nslu2-log@milla.nas-admin.org> has quit IRC13:07
*** nslu2-log_ is now known as nslu2-log13:08
*** ilkappe <ilkappe!c65a42b1@198.90.66.177> has quit IRC13:13
*** bradleyb is now known as radsquirrel13:26
*** Sandrita <Sandrita!b8a36cf4@gateway/web/cgi-irc/kiwiirc.com/ip.184.163.108.244> has quit IRC13:32
manuel1985Is anyone around here building yocto on AWS? Which kind of machine instance do you use? That is, which combination of CPU/memory is ideal? I don't want to pay for ressources I don't use.13:33
rburtonspin the machine down when its not building, just ensure you have persistent storage for sstate13:34
*** PaowZ <PaowZ!~vince@2a01:e35:2e3e:4ac0:7da9:2f6a:f755:42c5> has quit IRC13:35
*** ssajal <ssajal!~ssajal@bras-base-otwaon1146w-grc-11-174-88-220-58.dsl.bell.ca> has joined #yocto13:36
*** PaowZ <PaowZ!~vince@2a01:e35:2e3e:4ac0:7da9:2f6a:f755:42c5> has joined #yocto13:44
*** ericch <ericch!~ericch@pool-108-34-251-214.prvdri.fios.verizon.net> has joined #yocto13:46
*** rangergord <rangergord!rangergord@gateway/shell/xshellz/x-jrxrwcifhbizgppe> has joined #yocto13:46
*** AndersD <AndersD!~AndersD@h83-209-96-136.cust.a3fiber.se> has joined #yocto13:46
*** AndersD_ <AndersD_!~AndersD@h-17-226.A137.corp.bahnhof.se> has joined #yocto13:48
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has joined #yocto13:48
*** AndersD_ <AndersD_!~AndersD@h-17-226.A137.corp.bahnhof.se> has quit IRC13:48
*** sagner <sagner!~ags@31-10-206-124.static.upc.ch> has joined #yocto13:49
*** AndersD <AndersD!~AndersD@h83-209-96-136.cust.a3fiber.se> has quit IRC13:50
*** jrdn <jrdn!~jrdn@S010668ff7b6b7383.ok.shawcable.net> has joined #yocto13:53
JPEWmanuel1985: When I was experimenting with it, I chose C5aXlarge nodes. Seemed to have the best size/cost tradeoff (at the time).13:59
rburtonthe graviton2 arm nodes are cheap and in my benchmarking of comparable speed13:59
*** jtrimble <jtrimble!64247c08@pool-100-36-124-8.washdc.fios.verizon.net> has quit IRC14:00
manuel1985JPEW, rburton: Thanks!14:00
*** sstiller <sstiller!~sstiller@b2b-94-79-174-114.unitymedia.biz> has quit IRC14:01
JPEWmanuel1985: I also just setup my nodes to mount a EFS volume for the sstate cache. Maybe not the most cost effective, but it was really easy and works really well14:04
JPEWFully disclosure, I'm not doing anywhere near production volume builds, just playing around :)14:04
manuel1985JPEW: Is there a reason you chose EFS over EBS or instance store? Is it cheaper? Or because you can access EFS simultanously from different hosts? I'm very new to AWS... Made my account just yesterday... Still trying to make sense of all these options there are...14:12
JPEWRight. You could do EBS I think, but you'd have to stand up an NFS server instance in front of it so that your nodes can access it. This seemed more complicated than I wanted to do for my expirement.14:15
*** psnsilva <psnsilva!~psnsilva@2001:818:dae7:b100:8cbe:5797:375a:2468> has quit IRC14:23
*** dexterlb <dexterlb!~dexterlb@2a01:9e40:2:2::2> has joined #yocto14:25
*** srijan_root <srijan_root!0e66a0b2@14.102.160.178> has joined #yocto14:27
srijan_rootFacing an issue compiling binutils. The error says:fatal: repository '/opt/grays-poky/build-grays/downloads/git2/sourceware.org.git.binutils-gdb.git/' does not existWhereas I see this directory over there. Can also do a git clone, so it is not a network issue.14:28
srijan_rootFacing this issue with binutils14:29
*** goliath <goliath!~goliath@82.150.214.1> has quit IRC14:29
*** D`K_C is now known as dkc14:32
*** carlsb3rg <carlsb3rg!c147b478@193.71.180.120> has quit IRC14:32
*** Sandrita <Sandrita!d0586e2e@gateway/web/cgi-irc/kiwiirc.com/ip.208.88.110.46> has joined #yocto14:36
*** j241 <j241!~Adium@20.ip-51-79-160.net> has joined #yocto14:40
*** j241 <j241!~Adium@20.ip-51-79-160.net> has quit IRC14:41
RPJPEW: I've wondered about performance. Sadly its not something I've had any time on recently14:43
RPJPEW: that sync threads thing was a performance measure, wondering if we should just get rid of it14:43
*** sagner <sagner!~ags@31-10-206-124.static.upc.ch> has quit IRC14:46
*** manuel1985 <manuel1985!~manuel@62.99.131.178> has quit IRC14:47
*** feddischson <feddischson!~feddischs@HSI-KBW-109-192-195-181.hsi6.kabel-badenwuerttemberg.de> has quit IRC14:49
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has quit IRC14:50
*** eduardas <eduardas!~eduardas@85.254.96.13> has quit IRC14:52
*** maudat <maudat!~moda@bras-vprn-mtrlpq2848w-lp130-10-174-92-198-55.dsl.bell.ca> has quit IRC14:57
*** maudat <maudat!~moda@64.18.88.250> has joined #yocto14:57
JPEWRP: I'm trying to figure out what the sync thread is doing15:01
*** stephano <stephano!~stephano@c-73-164-244-205.hsd1.or.comcast.net> has joined #yocto15:02
*** rcw <rcw!~rcw@45.72.241.84> has joined #yocto15:06
RPJPEW: its writing out bb_caches to disk15:08
RPJPEW: so iterating over the caches calling .sync()15:08
RPJPEW: we do this so bitbake can get on with doing whatever it wants whilst the cache is saved out in parallel15:09
*** maudat <maudat!~moda@64.18.88.250> has quit IRC15:11
*** maudat <maudat!~moda@bras-vprn-mtrlpq2848w-lp130-10-174-92-198-55.dsl.bell.ca> has joined #yocto15:12
*** PaowZ <PaowZ!~vince@2a01:e35:2e3e:4ac0:7da9:2f6a:f755:42c5> has quit IRC15:21
*** PaowZ <PaowZ!~vince@2a01:e35:2e3e:4ac0:7da9:2f6a:f755:42c5> has joined #yocto15:22
JPEWRP: Oh, I misunderstood the "get rid of it" part. You mean get rid of the thread and sync on the main thread, not get rid of the sync() completely?15:22
RPJPEW: right15:23
RPJPEW: just block there15:23
JPEWRP: It seems like final_cleanup() is always right after shutdown(), so the thread likely isn't really gaining anything15:23
RPJPEW: under many workloads it would be long done by then though15:24
RPJPEW: the cleanup is just to block if its still there15:24
JPEWWell, I guess the thread parallelizes the parse_cache_savemerge(), fetcher_parser_done(), and profile saving?15:25
RPJPEW: right15:25
*** PaowZ <PaowZ!~vince@2a01:e35:2e3e:4ac0:7da9:2f6a:f755:42c5> has quit IRC15:28
*** srijan_root <srijan_root!0e66a0b2@14.102.160.178> has quit IRC15:34
RPJPEW: FWIW there is an open bug about parsing failures and unclean bitbake shutdowns causing locks so it may be worth a second torture run like that15:36
JPEWK, I'll modify the test to do that and give it a go15:39
RPJPEW: thanks. Reporter said the issues weren't fixed :/15:43
*** PaowZ <PaowZ!~vince@2a01:e35:2e3e:4ac0:7da9:2f6a:f755:42c5> has joined #yocto15:44
*** sxiii <sxiii!~sw@cm-84.214.223.252.getinternet.no> has joined #yocto15:44
sxiiiHey hey guys! Had anybody experience in making graphics driver autodetection for yocto?15:45
qschulzi'm not sure this is specific in any way to Yocto?15:47
*** sinseman44 <sinseman44!a5e14d32@165.225.77.50> has quit IRC15:47
sxiiiYes and no (I'm not sure). I was trying to to it with alpine and totally failed. That's why I am asking before I switch to something different :)15:48
sxiiiI am trying to build a distribution with sole purpose of giving presentations. That's the reason for graphics driver15:49
qschulzsxiii: why do you need to know about the graphic driver?15:51
sxiiiLet's say we have nvidia and two screens (one full-hd laptop screen and a 4K projector). We need to be sure that resolutions are okay. Or we can have AMD graphics and 1 screen. Or intel graphics... Etc. Ideally, I need automatic videodriver detection and support. Or I might try to stick with some generic driver, too, but I'm not sure that this will give some reasonable results15:53
sxiiiI don't actually need to know, I just want the full-resolution of the device to be automatically utilized.15:54
*** sxiii <sxiii!~sw@cm-84.214.223.252.getinternet.no> has quit IRC16:02
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC16:03
*** sxiii <sxiii!~sw@cm-84.214.223.252.getinternet.no> has joined #yocto16:04
*** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has joined #yocto16:07
*** chris_ber <chris_ber!~quassel@213.138.44.181> has quit IRC16:13
*** sw_ <sw_!~sw@cm-84.214.223.252.getinternet.no> has joined #yocto16:14
*** sxiii <sxiii!~sw@cm-84.214.223.252.getinternet.no> has quit IRC16:15
*** rubdos_ <rubdos_!~rubdos@2a02:578:859d:700:8b44:5716:382d:a7da> has quit IRC16:20
*** rubdos <rubdos!~rubdos@2a02:578:859d:700:8b44:5716:382d:a7da> has joined #yocto16:21
*** mckoan is now known as mckoan|away16:23
*** sw_ <sw_!~sw@cm-84.214.223.252.getinternet.no> has quit IRC16:25
*** sxiii <sxiii!~sw@cm-84.214.223.252.getinternet.no> has joined #yocto16:31
*** sw_ <sw_!~sw@cm-84.214.223.252.getinternet.no> has joined #yocto16:38
*** sxiii <sxiii!~sw@cm-84.214.223.252.getinternet.no> has quit IRC16:40
*** sxiii <sxiii!~sw@cm-84.214.223.252.getinternet.no> has joined #yocto16:42
*** havok101 <havok101!~havok101@2601:241:8a00:46e0:1cf:4ff4:58ea:1a8d> has joined #yocto16:42
*** sw_ <sw_!~sw@cm-84.214.223.252.getinternet.no> has quit IRC16:43
havok101Hey, so when I used boot2qt. It generated a configure-qtcreator.sh script for setting up the kit in qt creator for new machines. Is there such a thing for eclipse? Or is there any good instruction to setup eclipse? All seem to use the yocto plugin which is not supported for newer eclipse releases.16:44
*** sw_ <sw_!~sw@cm-84.214.223.252.getinternet.no> has joined #yocto16:45
*** sxiii <sxiii!~sw@cm-84.214.223.252.getinternet.no> has quit IRC16:48
*** PaowZ <PaowZ!~vince@2a01:e35:2e3e:4ac0:7da9:2f6a:f755:42c5> has quit IRC16:55
*** PaowZ <PaowZ!~vince@2a01:e35:2e3e:4ac0:7da9:2f6a:f755:42c5> has joined #yocto16:56
*** nslu2-log_ <nslu2-log_!~nslu2-log@milla.nas-admin.org> has joined #yocto16:56
*** nslu2-log <nslu2-log!~nslu2-log@milla.nas-admin.org> has quit IRC16:58
*** nslu2-log_ is now known as nslu2-log16:59
*** sw_ is now known as sxiii17:00
*** vineela <vineela!~vtummala@134.134.137.73> has joined #yocto17:15
*** lucaceresoli <lucaceresoli!~lucaceres@78-134-51-148.v4.ngi.it> has quit IRC17:20
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC17:29
*** fatalhalt <fatalhalt!~fatalhalt@2601:244:4d01:52df:225:90ff:feda:2428> has joined #yocto17:29
*** nerdboy <nerdboy!~sarnold@47.143.129.51> has joined #yocto17:29
JPEWRP: I know there is a bug with the config fragment to reproduce that issue, but I can't find it ATM. Do you happen to know what it is?17:36
*** manuel1985 <manuel1985!~manuel@089144217128.atnat0026.highway.a1.net> has joined #yocto17:36
JPEWhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=14034 Maybe?17:42
*** kanavin_home <kanavin_home!~ak@2a02:2450:1011:56f:b652:c378:b428:fdf> has quit IRC17:44
*** nslu2-log_ <nslu2-log_!~nslu2-log@milla.nas-admin.org> has joined #yocto17:45
*** nslu2-log <nslu2-log!~nslu2-log@milla.nas-admin.org> has quit IRC17:47
*** nslu2-log_ is now known as nslu2-log17:48
*** kanavin_home <kanavin_home!~ak@2a02:2450:1011:56f:b652:c378:b428:fdf> has joined #yocto17:58
*** jobroe_ <jobroe_!~manjaro-u@p579eba78.dip0.t-ipconnect.de> has quit IRC17:58
*** jadelclemens <jadelclemens!~jadelclem@c-174-51-134-157.hsd1.co.comcast.net> has joined #yocto18:03
jadelclemensHey all, running into a weird issue with Git repos and bitbake. It's failing to clone a specific repo as a submodule (permission denied (publickey) error), but it doesn't have the same issue cloning other repos on the same git server using the same keypair. I am also able to clone this repo with no incident manually (outside of bitbake)18:04
jadelclemensAny ideas what may be going on here?18:04
fraysubmodules, are each cloned one at a time in OE.  So if you are xpecting the original SRC_URI to point to the credentials it won't work right..18:07
fraythe other thing you can do is manually specify the URIs for all of the submodules within your SRC_URI of the recipe, that might give you more info why it's failing..18:08
fray(basically use "git:..." for each URL not gitsm)18:08
jadelclemensSo the username is encoded in the request URI (git@[submodule URI]) and the credentials should be handled by ssh (as configured in .ssh/config). What I'm seeing is that gitsm had issues with user and password included in the URI, but that is not the case with my setup18:11
jadelclemensIn fact it looks like bitbake isn't cloning the submodule manually (via a URI in a recipe) but as a consequence of a recursive clone of the parent repository.18:16
*** samvlewis <samvlewis!~samvlewis@45.32.247.239> has quit IRC18:16
jadelclemensOr, sorry, it configures a number of submodules and then does a recursive submodule update --init then sync18:16
*** samvlewis <samvlewis!~samvlewis@45.32.247.239> has joined #yocto18:17
frayusername is not transfered to the submodules18:21
fraythe submodule uri's are used -exactly- as speified in the submodule18:22
frayso if you need to provide credentials for the submodules, you will need to break it out manually and specify each URI within the recipe itself..18:22
frayThe behavior I am describing started sometime last year if I remember correctly (2019)18:22
*** roussinm <roussinm!~mroussin@ipagstaticip-d73c7528-4de5-0861-800b-03d8b15e3869.sdsl.bell.ca> has joined #yocto18:23
jadelclemensWell, my submodule URIs do specify the username, and credentials should be handled by my ssh agent (using keypairs specified in ~/.ssh/config). Is there something about the bitbake configure process that would interfere with the ssh agent being able to provide those credentials?18:24
jadelclemensThis is in .gitmodules - the recipe does not specify separate URIs for submodules, just adds shell commands to update the submodules we need for a given Yocto build18:24
*** rcoote <rcoote!~rcoote@221-224-024-217.ip-addr.vsenet.de> has quit IRC18:32
*** stacktrust <stacktrust!~stacktrus@cpe-67-250-48-90.nyc.res.rr.com> has quit IRC18:35
*** stacktrust <stacktrust!~stacktrus@cpe-67-250-48-90.nyc.res.rr.com> has joined #yocto18:36
*** nerdboy <nerdboy!~sarnold@47.143.129.51> has quit IRC18:49
*** nerdboy <nerdboy!~sarnold@47.143.129.51> has joined #yocto18:49
*** nerdboy <nerdboy!~sarnold@47.143.129.51> has quit IRC18:49
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto18:49
*** m1ster_r0b0t <m1ster_r0b0t!~m1ster_r0@prometheus.umask.eu> has quit IRC19:11
*** m1ster_r0b0t <m1ster_r0b0t!~m1ster_r0@prometheus.umask.eu> has joined #yocto19:11
*** elcfd <elcfd!~jester@92.40.169.104.threembb.co.uk> has joined #yocto19:13
elcfdhi, i have a recipe which pulls a private git repo. in order to connect i have my credentials in .gitconfig using git credential helper19:14
elcfdhowever, bitbake does not seem to pick this up. is this by design?19:14
erboelcfd: not really an answer to your question, but I usually go for git over ssh, and ssh key authorization for private repos19:26
elcfderbo < normally i would but work have their git server setup without ssh access. it seems im going to have to go into meetings with IT to get this changed!19:28
elcfdwas hoping to avoid having to do this because it wont be a quick process19:28
erboAh, the dreaded IT meeting :)19:28
elcfdindeed - you want what port opened!19:28
elcfdi nmapped the server they are filtering the ssh port :(19:29
erboelcfd: Hmm, this (old) SO post seems to indicate that it should work to have it in .gitconfig19:32
elcfderbo < do you have the link for the post?19:39
erboelcfd: right, I intended to paste that at the end of the last message :) https://stackoverflow.com/questions/53656233/yocto-fetch-private-repo-using-https19:40
*** jadelclemens <jadelclemens!~jadelclem@c-174-51-134-157.hsd1.co.comcast.net> has quit IRC19:40
*** jadelclemens <jadelclemens!~jadelclem@c-174-51-134-157.hsd1.co.comcast.net> has joined #yocto19:49
elcfderbo < thanks - i think it may actually be the work proxy causing the authentication error message i am seeing.19:50
*** kiwi_29 <kiwi_29!~kiwi_29@c-73-231-211-214.hsd1.ca.comcast.net> has joined #yocto19:55
*** elcfd <elcfd!~jester@92.40.169.104.threembb.co.uk> has quit IRC20:01
*** dev1990 <dev1990!~dev@62.87.215.57> has quit IRC20:09
*** dev1990 <dev1990!~dev@62.87.215.57> has joined #yocto20:10
*** jadelclemens <jadelclemens!~jadelclem@c-174-51-134-157.hsd1.co.comcast.net> has quit IRC20:13
JPEWRP: Ok, that was pretty easy to reproduce. Looks like another multiprocessing termination bug. FWIW, the re-write I've been working on seems to fix it20:21
JPEWwill run more tests overnight20:21
*** nslu2-log_ <nslu2-log_!~nslu2-log@milla.nas-admin.org> has joined #yocto20:30
*** nslu2-log <nslu2-log!~nslu2-log@milla.nas-admin.org> has quit IRC20:33
*** nslu2-log_ is now known as nslu2-log20:33
*** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has quit IRC20:45
*** Sandrita <Sandrita!d0586e2e@gateway/web/cgi-irc/kiwiirc.com/ip.208.88.110.46> has quit IRC20:49
*** nslu2-log_ <nslu2-log_!~nslu2-log@milla.nas-admin.org> has joined #yocto20:57
RPJPEW: hmm. So its definitely not fixed by existing patches? :(20:57
RPJPEW: you found a fragment I guess? I was afk20:57
*** nslu2-log <nslu2-log!~nslu2-log@milla.nas-admin.org> has quit IRC20:59
*** nslu2-log_ is now known as nslu2-log20:59
*** Konsgnx <Konsgnx!~Konsgnx3@66-109-34-138.tvc-ip.com> has quit IRC21:00
JPEWRP: Ya, I did. It's the exact one from the bug report. And it's pretty easy to reproduce, just CTRL+C after the stacktrace appears from the invalid expansion21:02
*** kiwi_29 <kiwi_29!~kiwi_29@c-73-231-211-214.hsd1.ca.comcast.net> has quit IRC21:02
RPJPEW: ah, I wasn't doing the Ctrl+C21:03
JPEWRP: The torture test finds it in less than 10 iterations for me, and most of those are where it completely misses the window because it's too early or too late21:03
RPJPEW: I wonder if blocking the SIGINT from the children would help21:03
JPEWRP: Hmm, maybe. I can try it21:04
RPJPEW: or maybe blocking it in the parent21:04
RPJPEW: worth a try since you can easily reproduce!21:04
*** berton <berton!~berton@181.220.78.182> has quit IRC21:13
JPEWRP: `signal.signal(signal.SIGINT, signal.SIG_IGN)` seems to fix the problem. It's done over 100 iterations now21:15
dv_hm there is no 3.2 schedule page on the wiki? https://wiki.yoctoproject.org/wiki/Yocto_3.1_Schedule exists, but https://wiki.yoctoproject.org/wiki/Yocto_3.2_Schedule is 40421:15
dv_given that gatesgarth (3.2) is planned for october, that is a little weird ... ?21:15
JPEWRP: Patch sent21:17
RPJPEW: great, thanks!21:18
RPdv_: its a sign that we don't have enough people to do everything :(21:18
*** Piraty <Piraty!~irc@unaffiliated/piraty> has quit IRC21:20
*** hch <hch!~hch@unaffiliated/hch> has quit IRC21:20
*** Piraty <Piraty!~irc@unaffiliated/piraty> has joined #yocto21:21
*** hch <hch!~hch@unaffiliated/hch> has joined #yocto21:21
*** maudat <maudat!~moda@bras-vprn-mtrlpq2848w-lp130-10-174-92-198-55.dsl.bell.ca> has quit IRC21:26
*** ak77_ <ak77_!~akrpic77@193.46.75.3> has joined #yocto21:32
*** wooosaiii <wooosaiii!~wooo@89-212-21-243.static.t-2.net> has joined #yocto21:32
*** ak77 <ak77!~akrpic77@193.46.75.3> has quit IRC21:34
*** zandrey <zandrey!~zandrey@cable-static2-2-7.rsnweb.ch> has joined #yocto21:35
*** wooosaiiii <wooosaiiii!~wooo@89-212-21-243.static.t-2.net> has quit IRC21:35
RPsakoman: did you make any progress with https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/1389 - the python version issue?21:38
*** beneth <beneth!~beneth@irc.beneth.fr> has left #yocto21:39
RPsakoman: its a bit invasive but I think we split utils.setup_buildtools_tarball into two and then call the second half from the qa-send script21:41
*** lucaceresoli <lucaceresoli!~lucaceres@78-134-51-148.v4.ngi.it> has joined #yocto21:50
*** havok101 <havok101!~havok101@2601:241:8a00:46e0:1cf:4ff4:58ea:1a8d> has quit IRC21:55
*** lucaceresoli <lucaceresoli!~lucaceres@78-134-51-148.v4.ngi.it> has quit IRC22:03
*** kiwi_29 <kiwi_29!~kiwi_29@c-73-231-211-214.hsd1.ca.comcast.net> has joined #yocto22:09
*** agust <agust!~agust@p508b6ab0.dip0.t-ipconnect.de> has quit IRC22:18
dv_RP: oh..22:18
dv_RP: could this lead to gatesgarth being postponed?22:18
RPdv_: the release is going ahead as planned, we just don't have all the planning documents and wiki updated :/22:18
dv_ah I see22:19
RPwell, assuming we actually build M3 (feature freeze). That is two weeks behind right now but I'm not overly concerned about that22:19
dv_I originally wanted to look up in what milestone we are in22:19
dv_and I assume that gstreamer 1.18 (which got released ~7 days ago) won't make it in .. too late for that22:19
RPdv_: how big a change is it and are there good reasons we'd want it?22:20
RPits late and past feature freeze so we'd need a compelling reasons22:20
dv_well it is always good to stick to the latest gstreamer version. support is much easier then22:20
dv_oh thats what you mean22:20
dv_no, I dont think there are pressing reasons for an exception22:20
RPI understand latest is "best" but we do have to draw a line somewhere!22:21
dv_of course, of course. thats why I wanted to know the current milestone. if it were an early one, I'd try to get 1.18 in22:21
dv_but M3 is a late one22:22
dv_anyway, thanks for the info22:22
RPdv_: np, thanks for checking!22:22
dv_you're welcome.22:27
dv_oh, one last thing (different topic), then I anyway have to go: why does the SDK's environment file add optimization and debug symbol flags to CFLAGS, CXXFLAGS, LDFLAGS, and also to build system specific scripts like meson.cross?22:28
dv_this gets very annoying when you try to build a debug build, wanna step through it with gdb, only to find that stuff has been optimized out22:29
dv_optimization and debug symbol flags (-g etc.) shouldn't really be part of a BSP setup22:29
dv_err, part of an SDK setup22:30
RPdv_: I'd imagine people do want the optimization flags there in general22:30
RPI'd assume we're thinking people will split the debug symbols out like we do with in tree builds22:30
zeddiiRP: I'm sending some -stable bumps and a fixed up lttng-modules patch in the next few minutes. just one more build to see pass.22:30
dv_for yocto builds, yeah.22:30
dv_but if you use the SDK, the situation is different22:30
RPdv_: It depends. If we remove that info its hard to someone to get it back but easier for them to remove it if needed22:31
RPzeddii: ok, I'm about to start a build and head to bed. I wonder whether sleep will win :)22:31
dv_hm. maybe some flag that can enables/disables it?22:31
dv_I'll discuss this with my BSP colleaguees22:32
dv_-e22:32
RPdv_: I was just wondering about two environment files. That has big impact on the docs though22:32
RPdv_: its worth thinking about22:32
dv_true22:32
dv_alright22:33
dv_anyway, gotta go, l8r!22:33
zeddiiit built. sending the queue. feel free to let sleep win.22:33
*** gsalazar <gsalazar!955ab50e@gateway/web/cgi-irc/kiwiirc.com/ip.149.90.181.14> has quit IRC22:34
RPzeddii: series doesn't apply? :/22:35
*** marka <marka!~marka@198-84-181-245.cpe.teksavvy.com> has quit IRC22:35
zeddiisome kind of strange encoding on one patch.22:35
zeddiigit send email complained on the way out.22:35
RPzeddii: patch just before the ones you sent in the branch?22:37
RPlinux-yocto/config: netfilter: Enable nat for ipv4 and ipv622:37
zeddiibugger.22:37
zeddiiI missed one.22:37
zeddiiI can resend, or you can grab it off the branch. apparently I can't count.22:38
zeddiirushing never pays off.22:38
RPzeddii: I have it :)22:38
zeddiiI'll follow up to my 0/N in case someone out there is trying to grab the patches and apply them.22:39
zeddiimy AB run is green now with those changes, so in theory, it shouldn't cause you any issues.22:39
RPzeddii: I was rushing to get to sleep to which obviously meant it all was doomed ;-)22:39
RPzeddii: I'm off to bed now, will see what happened tomorrow22:39
zeddiimy first AB runs .. didn't go well, hence why I ended up with lttng changes :D22:39
zeddiilater!22:39
paulg2020 and ltt is still a thing.22:44
paulgltt-ng-ng-ng22:44
paulgwouldn't have predicted that back in 2005 or whatever.22:46
*** yann <yann!~yann@88.120.44.86> has quit IRC23:09
*** nslu2-log_ <nslu2-log_!~nslu2-log@milla.nas-admin.org> has joined #yocto23:12
*** nslu2-log <nslu2-log!~nslu2-log@milla.nas-admin.org> has quit IRC23:15
*** nslu2-log_ is now known as nslu2-log23:15
*** kiwi_29 <kiwi_29!~kiwi_29@c-73-231-211-214.hsd1.ca.comcast.net> has quit IRC23:24

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