Tuesday, 2019-03-05

*** fenrig <fenrig!~fenrig@> has quit IRC00:10
*** flying_sausages_ <flying_sausages_!~flying_sa@static.88-198-40-49.clients.your-server.de> has quit IRC00:10
*** flying_sausages <flying_sausages!~flying_sa@static.88-198-40-49.clients.your-server.de> has joined #yocto00:11
*** LetoThe2nd <LetoThe2nd!~ubuntu@unaffiliated/letothe2nd> has quit IRC00:12
*** LetoThe2nd <LetoThe2nd!~ubuntu@unaffiliated/letothe2nd> has joined #yocto00:13
*** fenrig <fenrig!~fenrig@> has joined #yocto00:14
*** JPEWhacker <JPEWhacker!~yaaic@2605:a601:21d1:5200:3d56:ed18:d70f:fefe> has quit IRC00:22
*** fenrig <fenrig!~fenrig@> has quit IRC00:28
*** fenrig <fenrig!~fenrig@> has joined #yocto00:32
*** stwcx_ <stwcx_!~stwcx@> has quit IRC00:38
*** stwcx <stwcx!~stwcx@2604:880:a:6::c9c> has joined #yocto00:38
*** dl9pf <dl9pf!~quassel@opensuse/member/dl9pf> has quit IRC00:39
*** fenrig <fenrig!~fenrig@> has quit IRC00:47
*** fenrig <fenrig!~fenrig@> has joined #yocto00:50
*** erbo <erbo!~erik@linode.unixshell.se> has quit IRC00:51
*** fenrig <fenrig!~fenrig@> has quit IRC01:22
*** fenrig <fenrig!~fenrig@> has joined #yocto01:26
*** chandana73 <chandana73!~ckalluri@> has quit IRC01:39
*** fenrig <fenrig!~fenrig@> has quit IRC01:48
*** fenrig <fenrig!~fenrig@> has joined #yocto01:52
*** BuddyButterfly <BuddyButterfly!~BuddyButt@dslb-094-217-104-167.094.217.pools.vodafone-ip.de> has quit IRC02:14
*** learningc <learningc!~learningc@mti-37-145.tm.net.my> has joined #yocto02:19
*** BuddyButterfly <BuddyButterfly!~BuddyButt@p4FF9D26C.dip0.t-ipconnect.de> has joined #yocto02:27
*** fenrig <fenrig!~fenrig@> has quit IRC02:31
*** User_ <User_!~learningc@mti-37-145.tm.net.my> has joined #yocto02:31
*** fenrig <fenrig!~fenrig@> has joined #yocto02:34
*** learningc <learningc!~learningc@mti-37-145.tm.net.my> has quit IRC02:35
*** rubdos <rubdos!~rubdos@2a02:578:859d:701:a846:9858:21a:9451> has quit IRC02:43
*** nighty- <nighty-!~nighty@b157153.ppp.asahi-net.or.jp> has joined #yocto02:44
*** rubdos <rubdos!~rubdos@2a02:578:859d:701:a846:9858:21a:9451> has joined #yocto02:52
*** denix <denix!~denix@pool-100-15-91-218.washdc.fios.verizon.net> has joined #yocto03:15
*** learningc <learningc!~learningc@mti-37-145.tm.net.my> has joined #yocto03:33
*** User_ <User_!~learningc@mti-37-145.tm.net.my> has quit IRC03:35
*** User_ <User_!~learningc@mti-37-145.tm.net.my> has joined #yocto03:39
*** BuddyButterfly <BuddyButterfly!~BuddyButt@p4FF9D26C.dip0.t-ipconnect.de> has quit IRC03:39
*** learningc <learningc!~learningc@mti-37-145.tm.net.my> has quit IRC03:42
*** fenrig <fenrig!~fenrig@> has quit IRC04:05
*** fenrig <fenrig!~fenrig@> has joined #yocto04:08
*** User__ <User__!~learningc@mti-37-145.tm.net.my> has joined #yocto04:32
*** User_ <User_!~learningc@mti-37-145.tm.net.my> has quit IRC04:35
*** yizhao <yizhao!~zhaoyi@> has quit IRC04:44
*** yizhao <yizhao!~zhaoyi@> has joined #yocto04:51
yoctiNew news from stackoverflow: How to fix the "No symbol __gcov_flush in current context" error while flushing the coverage from the image generated through bitbake <https://stackoverflow.com/questions/54689237/how-to-fix-the-no-symbol-gcov-flush-in-current-context-error-while-flushing>05:23
*** NU-Slacker <NU-Slacker!~NU-Slacke@> has joined #yocto05:28
*** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-gxcfyeiyptmdtbyz> has quit IRC05:31
*** User_ <User_!~learningc@mti-37-145.tm.net.my> has joined #yocto05:32
*** User__ <User__!~learningc@mti-37-145.tm.net.my> has quit IRC05:35
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto05:54
*** AndersD <AndersD!~AndersD@194-237-220-218.customer.telia.com> has joined #yocto05:55
*** AndersD <AndersD!~AndersD@194-237-220-218.customer.telia.com> has quit IRC05:57
*** AndersD <AndersD!~AndersD@194-237-220-218.customer.telia.com> has joined #yocto05:58
*** yizhao <yizhao!~zhaoyi@> has quit IRC06:00
*** yizhao <yizhao!~zhaoyi@> has joined #yocto06:01
*** learningc <learningc!~learningc@mti-37-145.tm.net.my> has joined #yocto06:32
*** User_ <User_!~learningc@mti-37-145.tm.net.my> has quit IRC06:35
*** chandana73 <chandana73!~ckalluri@> has joined #yocto06:55
*** evadeflow <evadeflow!2ebd1c55@gateway/web/freenode/ip.> has joined #yocto06:56
*** evadeflow <evadeflow!2ebd1c55@gateway/web/freenode/ip.> has quit IRC06:57
*** NU-Slacker <NU-Slacker!~NU-Slacke@> has quit IRC07:02
*** tprrt <tprrt!~tprrt@> has joined #yocto07:05
*** fenrig <fenrig!~fenrig@> has quit IRC07:08
*** NU-Slacker <NU-Slacker!~NU-Slacke@> has joined #yocto07:12
*** fenrig <fenrig!~fenrig@> has joined #yocto07:12
*** NU-Slacker <NU-Slacker!~NU-Slacke@> has quit IRC07:23
*** User_ <User_!~learningc@mti-37-145.tm.net.my> has joined #yocto07:32
*** learningc <learningc!~learningc@mti-37-145.tm.net.my> has quit IRC07:35
*** kaspter <kaspter!~Instantbi@> has quit IRC07:40
*** kaspter <kaspter!~Instantbi@> has joined #yocto07:43
*** lucaceresoli <lucaceresoli!~lucaceres@> has joined #yocto07:45
*** TobSnyder <TobSnyder!~schneider@ip5f5aa32f.dynamic.kabel-deutschland.de> has joined #yocto07:49
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC07:53
*** lusus <lusus!~lusus@> has joined #yocto08:13
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto08:13
*** Bunio_FH <Bunio_FH!~bunio@81-18-201-214.static.chello.pl> has joined #yocto08:16
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC08:17
*** fl0v0 <fl0v0!~fvo@mue-88-130-104-106.dsl.tropolys.de> has joined #yocto08:19
*** sk_tandt <sk_tandt!~sk_tandt@net-5-88-141-17.cust.vodafonedsl.it> has joined #yocto08:26
*** ant_work <ant_work!~ant__@host205-129-static.31-195-b.business.telecomitalia.it> has joined #yocto08:32
*** learningc <learningc!~learningc@mti-37-145.tm.net.my> has joined #yocto08:32
*** User_ <User_!~learningc@mti-37-145.tm.net.my> has quit IRC08:35
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto08:40
*** mckoan|away is now known as mckoan08:41
*** AndersD <AndersD!~AndersD@194-237-220-218.customer.telia.com> has quit IRC08:44
*** AndersD <AndersD!~AndersD@194-237-220-218.customer.telia.com> has joined #yocto08:48
*** bluelightning_ is now known as bluelightning09:08
yoctiNew news from stackoverflow: How to generate code coverage for yocto modules <https://stackoverflow.com/questions/54999053/how-to-generate-code-coverage-for-yocto-modules>09:24
*** fenrig <fenrig!~fenrig@> has quit IRC09:31
*** User__ <User__!~learningc@mti-37-145.tm.net.my> has joined #yocto09:32
*** learningc <learningc!~learningc@mti-37-145.tm.net.my> has quit IRC09:35
*** rburton <rburton!~rburton@> has joined #yocto09:45
*** learningc <learningc!~learningc@mti-37-145.tm.net.my> has joined #yocto09:54
*** User__ <User__!~learningc@mti-37-145.tm.net.my> has quit IRC09:56
*** orzen <orzen!~orz@84-216-100-149.customers.ownit.se> has joined #yocto10:01
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto10:09
*** awe001 <awe001!~awe00@unaffiliated/awe00> has joined #yocto10:18
*** User__ <User__!~learningc@mti-37-145.tm.net.my> has joined #yocto10:32
*** Jacen <Jacen!~cdreher@> has joined #yocto10:32
*** gsalazar <gsalazar!~gsalazar@> has quit IRC10:34
*** learningc <learningc!~learningc@mti-37-145.tm.net.my> has quit IRC10:35
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC10:49
*** blueness_ <blueness_!~blueness@gentoo/developer/blueness> has joined #yocto10:50
kanavinRP, rburton I'll be on holiday until 25th of March11:11
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto11:11
LetoThe2ndkanavin: cool, enjoy!11:11
kanavinLetoThe2nd, thanks :)11:12
*** blueness_ <blueness_!~blueness@gentoo/developer/blueness> has quit IRC11:12
*** gsalazar <gsalazar!~gsalazar@> has joined #yocto11:13
rburtonkanavin: have a good one11:14
*** gsalazar <gsalazar!~gsalazar@> has quit IRC11:24
*** learningc <learningc!~learningc@mti-37-145.tm.net.my> has joined #yocto11:32
*** mckoan is now known as mckoan|away11:33
*** User__ <User__!~learningc@mti-37-145.tm.net.my> has quit IRC11:35
*** learningc <learningc!~learningc@mti-37-145.tm.net.my> has quit IRC11:55
rburtonRP: should src_patches() in patch.bbclass return patches that have apply=0 set?11:55
rburtonoh it doesn't via mysterious magic12:00
rburtongood stuff12:00
*** gsalazar <gsalazar!~gsalazar@> has joined #yocto12:09
Willie2Hi, i have used fsl-image-qt5 when developing my application. Thx to this forum i have everything as i want ( almost). Now i wonder what best practice is to create my "final" image. I have looked at creating my own image with qt5 support but it does not look trivial. The other idea i have was to create an bbappend to the  fsl-image-qt5 to remove examples etc. What is the best way to this?12:10
Willie2best is maybe not the word I'm looking for, rather common practice12:12
RPkanavin: thanks for the headsup, have fun!12:17
yoctiNew news from stackoverflow: yocto fails to build mono-xsp <https://stackoverflow.com/questions/55002380/yocto-fails-to-build-mono-xsp>12:24
LetoThe2ndWillie2: ideally, your image just contains IMAGE_INSTALL += "your_application"12:25
LetoThe2ndWillie2: and the recipe of your application would depend on qt and all the other things it needs.12:26
Willie2oh my god, i have been re-compling this 0,5GB image a few times each day and installing it12:29
LetoThe2ndWillie2: hm?12:30
Willie2nwm, just a lot of unnecessery installing for me :)12:30
LetoThe2ndWillie2: i mean, there are corner cases, sure. but generally the mind set is: "the image recipe should not know of any internal (dependencies) of the applications it ships"12:31
Willie2Okay nice. For some reason i thought QT needed complex instructions to get installed12:33
Willie2Since i looked at the meta-fsl-release image recipes12:34
LetoThe2ndWillie2: it might need tuning in the MACHINE or DISTRO configs. especially when we are talking about accelerated graphics drivers12:34
Willie2LetoThe2nd: hmm ok. I will still be using the standard imx6sabresd. I'm only using rootfs from Yocto12:35
LetoThe2ndWillie2: that sentence does not really make sense12:36
Willie2I'm not a good multi-tasker12:36
Willie2LetoThe2nd: Sorry, what I'ment was i will be using the same settings in DISTRO and MACHINE12:38
LetoThe2ndWillie2: imx6sabresd is the machine. if you stick to the board, this is the one thats most likely to not change12:38
LetoThe2ndWillie2: whereas there is really nothing wrong with taking the DISTRO that came with it and beating it into shape for what you really need. often this can slim down the build process substantially12:39
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC12:41
LetoThe2ndWillie2: and if your application build breaks if the image recipe leaves out things, this strongly indicates that your dependencies are incorrect12:41
Willie2LetoThe2nd: Thanks! This is really helpful. I will start by creating a "core-image" with my application and see how it builds12:44
LetoThe2ndWillie2: exactly. have fun!12:45
*** kaspter <kaspter!~Instantbi@> has quit IRC12:47
yoctiNew news from stackoverflow: Yocto /boot partition not using opkg/ipk packages <https://stackoverflow.com/questions/55002843/yocto-boot-partition-not-using-opkg-ipk-packages>12:55
*** tprrt <tprrt!~tprrt@> has quit IRC13:05
*** tprrt <tprrt!~tprrt@> has joined #yocto13:07
*** tprrt <tprrt!~tprrt@> has quit IRC13:24
*** tprrt <tprrt!~tprrt@> has joined #yocto13:24
*** geissonator <geissonator!~geissonat@45-18-127-186.lightspeed.austtx.sbcglobal.net> has joined #yocto13:30
*** learningc <learningc!~learningc@> has joined #yocto13:43
*** AndersD <AndersD!~AndersD@194-237-220-218.customer.telia.com> has quit IRC13:43
*** AndersD <AndersD!~AndersD@194-237-220-218.customer.telia.com> has joined #yocto13:44
*** User__ <User__!~learningc@> has joined #yocto13:46
*** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has joined #yocto13:47
Willie2Are the python variables documented anywhere? I want to change background picture and I think bb.utils.contains('DISTRO_FEATURES' can have something to do with it13:49
rburtonWillie2: define background picture13:49
Willie2The standard is so ugly with the green edges13:49
rburtonthe sato theme has nothing to do with distro features, if that's what you mean13:50
rburtonbut sato hasn't been green for a while, so maybe not13:50
Willie2rburton: The desktop picture i guess? that is in the background13:50
*** learningc <learningc!~learningc@> has quit IRC13:50
rburtonnothing to do with distro features13:50
*** learningc <learningc!~learningc@> has joined #yocto13:51
rburtonDISTRO_FEATURES is stuff like support for bluetooth, wifi, extended attributes, opengl, x1113:51
Willie2Okay, it was added when i put  ${@bb.utils.contains('DISTRO_FEATURES', 'x11 wayland', 'weston-xwayland xterm', '', d)} in my recipe thats why i guessed that13:51
rburtonnot what picture is used for the wallpaper13:51
rburton"if the distro contains x11 and wayland, install weston-xwayland and xterm'13:52
Willie2thx! Any idea where wallpaper settings are located?13:52
rburtonno, because you haven't said what is drawing the background13:53
*** tprrt <tprrt!~tprrt@> has quit IRC13:53
LetoThe2ndgiven that trigger to get it shown, probably somewhere in the weston-xwayland region13:53
Willie2It kinda looks like this (without the example applications )13:54
rburtonweston's wallpaper is grey13:54
Willie2But it has a ugly green edge on the top13:54
*** User__ <User__!~learningc@> has quit IRC13:54
rburtonthats very old sato13:54
rburtonchange the matchbox theme13:54
rburtoni also take offense at ugly, it was cool when it was drawn13:55
LetoThe2ndrburton: hrhrhr13:55
Willie2i dont even think i was born13:55
Willie2when taht was drawn13:55
*** tprrt <tprrt!~tprrt@> has joined #yocto13:55
*** User__ <User__!~learningc@> has joined #yocto13:55
rburtonhttps://www.yoctoproject.org/docs/1.0/poky-ref-manual/screenshots/ss-sato.png awwww13:56
Willie2that one13:56
rburtonah the days when that was cutting edge13:56
LetoThe2ndrburton: its carnival! shouldn't you be drunk like the rest of us old hags?13:56
rburtonWillie2: the green was removed quite a while ago. consider upgrading your OE.13:58
*** learningc <learningc!~learningc@> has quit IRC13:59
rburton2.2 moved to greys instead of greens13:59
rburtonso you're using 2.1 or earlier13:59
*** User__ <User__!~learningc@> has quit IRC14:00
*** learningc <learningc!~learningc@> has joined #yocto14:00
Willie2Hm, not sure if i can or should. I'm using a customized board from our supplier and they gave me customised bsp to work with14:00
rburtontell them they're selling you insecure software14:00
rburtonand ask what they're doing about it14:00
rburton2.1 was released in 201614:01
rburtonlatest point release was 2.1.3 in july 201714:01
rburton(i'm assuming you're using 2.1 and not anything even older)14:01
*** awe001 <awe001!~awe00@unaffiliated/awe00> has quit IRC14:03
Willie2I only have a few months linux experience and yocto even less so dont assume anything :d14:04
*** awe00 <awe00!~awe00@unaffiliated/awe00> has joined #yocto14:04
*** User__ <User__!~learningc@> has joined #yocto14:08
Willie2rburton: And the only way to get a newer sato is to use something newer?  like sumo or rocko14:09
rburtonyou could backport all the bits but thats hard14:10
rburtoneasier to just change the theme14:10
*** learningc <learningc!~learningc@> has quit IRC14:11
*** User__ <User__!~learningc@> has quit IRC14:14
Willie2Okay, I'll start with trying to add a custom wallpaper :)14:16
Willie2thx again!14:16
*** learningc <learningc!~learningc@> has joined #yocto14:41
*** Quazil <Quazil!~shannon@2601:40e:8280:2d6e:4ecc:6aff:fe0c:1a77> has joined #yocto14:41
QuazilI have a (custom) package that is failing to compile and it's not very clear why.14:42
QuazilIs there a way I can "step into" the build environment bitbake creates and watch the actual compilation?14:42
QuazilSomething like emerge's ebuild tool?14:42
LetoThe2ndQuazil: basically, bitbake -c devshell IIRC14:43
*** User__ <User__!~learningc@> has joined #yocto14:46
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC14:47
*** AndersD <AndersD!~AndersD@194-237-220-218.customer.telia.com> has quit IRC14:47
*** learningc <learningc!~learningc@> has quit IRC14:50
*** learningc <learningc!~learningc@> has joined #yocto14:52
*** User__ <User__!~learningc@> has quit IRC14:55
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC14:57
*** User__ <User__!~learningc@> has joined #yocto15:03
*** learningc <learningc!~learningc@> has quit IRC15:07
*** learningc <learningc!~learningc@2001:d08:d6:2436:cdf0:80b5:7ecf:d095> has joined #yocto15:07
*** User__ <User__!~learningc@> has quit IRC15:10
*** fl0v0 <fl0v0!~fvo@mue-88-130-104-106.dsl.tropolys.de> has quit IRC15:16
*** fl0v0 <fl0v0!~fvo@mue-88-130-104-106.dsl.tropolys.de> has joined #yocto15:16
*** gsalazar <gsalazar!~gsalazar@> has quit IRC15:18
*** gsalazar <gsalazar!~gsalazar@> has joined #yocto15:20
*** nighty- <nighty-!~nighty@b157153.ppp.asahi-net.or.jp> has quit IRC15:20
armpitYPTM: armin is on15:57
*** JPEW_ <JPEW_!cc4da372@gateway/web/freenode/ip.> has joined #yocto15:59
JPEW_#YPTM: Joshua Watt here15:59
*** TobSnyder <TobSnyder!~schneider@ip5f5aa32f.dynamic.kabel-deutschland.de> has quit IRC16:01
*** sjolley_ <sjolley_!473b8895@gateway/web/freenode/ip.> has joined #yocto16:01
sjolley_YPTM: Join with Zoom at: https://zoom.us/j/99089271216:01
RPYPTM: Richard joined16:01
vmesonYPTM: vmeson/Randy MacLeod est la16:02
* derRichard needs to refine his irc nickname highlight ;=)16:02
JPEW_YPTM: Zach Booth and Dustin Bain are also here16:02
*** chandana73 <chandana73!~ckalluri@> has quit IRC16:03
moto-timoYPTM: Tim joined16:04
*** retoatwork <retoatwork!~reto@> has joined #yocto16:08
*** sjolley_ <sjolley_!473b8895@gateway/web/freenode/ip.> has quit IRC16:08
*** ant_work <ant_work!~ant__@host205-129-static.31-195-b.business.telecomitalia.it> has quit IRC16:08
*** sjolley_ <sjolley_!~sjolley_@c-71-59-136-149.hsd1.or.comcast.net> has joined #yocto16:10
*** sk_tandt <sk_tandt!~sk_tandt@net-5-88-141-17.cust.vodafonedsl.it> has quit IRC16:14
armpitRP: http://errors.yoctoproject.org/Errors/Build/78095/16:15
JPEW_2.7 Planning document: https://docs.google.com/document/d/15jB6nUJU2wrtnu6w07L9RZpNlj6AoxSTPEX5aELts1g/edit?usp=sharing16:16
retoatworkIs there a tool to convert the reports generated by cve-check to JUnit format?16:19
RParmpit: nothing provides curl-dev = 7.61.0-r0.0 needed by curl-staticdev-7.61.0-r0.0.armv5e16:19
armpityeah, that is the error. I had the commit http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=stable/sumo-next&id=8b165b1063e47407c6e00af9cf6893e629052c2d16:21
armpitand that did not help16:22
armpitlast clean build is at http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=stable/sumo-next&id=d3dcc4f92e0fdf1e044bbd71741b77581f64ce6d16:25
*** learningc <learningc!~learningc@2001:d08:d6:2436:cdf0:80b5:7ecf:d095> has quit IRC16:29
*** Bunio_FH <Bunio_FH!~bunio@81-18-201-214.static.chello.pl> has quit IRC16:30
*** stephano <stephano!~stephano@> has joined #yocto16:30
armpitwhat was the bug# ?16:32
yoctiBug 8729: enhancement, Medium, Future, dimtass, IN PROGRESS REVIEW , grub: create a script to boot between rootfs and a maintenance partition16:33
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC16:35
*** JaMa <JaMa!~martin@ip-217-030-068-212.aim-net.cz> has joined #yocto16:37
sjolley_YPTM is over.16:37
armpitRP, I am re-running sumo-nmut2 to re-establish a clean point. sumo-next was rebased so I don't know 100% where is passed last16:39
*** chandana73 <chandana73!~ckalluri@> has joined #yocto16:39
armpitRP, i have a thud build running, if clean I will start on the result tool integration16:45
*** learningc <learningc!~learningc@2001:d08:d6:2436:ec10:76e:3af4:db9a> has joined #yocto16:45
*** lusus <lusus!~lusus@> has quit IRC16:53
*** JPEW_ <JPEW_!cc4da372@gateway/web/freenode/ip.> has quit IRC17:06
*** armpit <armpit!~armpit@2601:202:4180:c33:153a:43ee:4b76:7dc7> has quit IRC17:24
yoctiNew news from stackoverflow: Can't run Yocto image with runqemu like described in documentation <https://stackoverflow.com/questions/55008174/cant-run-yocto-image-with-runqemu-like-described-in-documentation>17:25
*** chandana73 <chandana73!~ckalluri@> has quit IRC17:35
*** chandana73 <chandana73!~ckalluri@> has joined #yocto17:41
*** chandana73 <chandana73!~ckalluri@> has quit IRC17:44
*** tprrt <tprrt!~tprrt@> has quit IRC17:47
*** chandana73 <chandana73!~ckalluri@> has joined #yocto17:48
*** learningc <learningc!~learningc@2001:d08:d6:2436:ec10:76e:3af4:db9a> has quit IRC18:05
*** noway96 <noway96!~noway96@50-244-213-195-static.hfc.comcastbusiness.net> has joined #yocto18:11
*** learningc <learningc!~learningc@> has joined #yocto18:17
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto18:17
*** fl0v0 <fl0v0!~fvo@mue-88-130-104-106.dsl.tropolys.de> has quit IRC18:19
noway96I'm trying to build network-manager from oe18:21
noway96I'm getting the following error: tmp/work/x86_64-poky-linux/mozjs/17.0.0-r0/mozjs17.0.0/js/src/config/rules.mk:726: recipe for target 'jsapi-tests' failed18:21
noway96any idea for workaround?18:21
*** learningc <learningc!~learningc@> has quit IRC18:38
*** awe00 <awe00!~awe00@unaffiliated/awe00> has quit IRC18:44
*** mihai <mihai!~mihai@unaffiliated/mihai> has joined #yocto19:10
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto19:18
*** rburton <rburton!~rburton@> has quit IRC19:21
*** rburton_ <rburton_!~rburton@> has joined #yocto19:21
*** armpit <armpit!~armpit@> has joined #yocto19:24
noway96turns out it was because of corrupted object files. Just cleaning and rebuilding worked19:27
*** vmeson <vmeson!~rmacleod@> has quit IRC19:59
*** sjolley_ <sjolley_!~sjolley_@c-71-59-136-149.hsd1.or.comcast.net> has quit IRC19:59
zeddiiRP: I have most everything working, except lttng for mips/mips64. I’m going to spend some time on that now, but will likely send a series later even if I don’t get it building.20:02
*** khem <khem!~khem@unaffiliated/khem> has quit IRC20:04
psrcodezeddii: is it lttng specific or related to yocto/oe? if lttng related I might be able to answer question if you have any20:16
zeddiiahah. I just figured it out. There were build errors against the 5.x kernel + my new libc headers. So I dumped the current lttng recipe in favour of one I keep around to build from the git branches. That fixed all archs except mips. But looking at it, I dropped a patch that we’ve been carrying for a while for mips to not have a  build_bug_on fire … When I dumped the 8 patches on the stable lttng branch AND kept tha20:18
zeddiipatch around, it seems to be building20:18
zeddiiphew. that’s a mouthful20:18
zeddiibut hopefully, that’ll get me moving with all arches.20:18
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto20:26
psrcodezeddii: I would be interested in seeing those patches, see if any can be ported upstream20:27
*** vmeson <vmeson!~rmacleod@> has joined #yocto20:31
*** rcw <rcw!~rcw@> has joined #yocto20:35
*** fancer <fancer!fancer@gateway/web/irccloud.com/x-uljquijkrfnyyglq> has joined #yocto20:45
*** rewitt <rewitt!rewitt@nat/intel/x-bgdfixjijetbzybx> has quit IRC20:51
JPEWkanavin: Are you still here?21:55
RPzeddii: cool, mips proving a pain as ever :/21:57
RPpsrcode: not sure if you saw but I managed to improve our lttng-tools ptest test scores. Still a few failing tests to investigate :/21:57
RParmpit: am I overdue any patch merging?21:58
RParmpit: that patch you pointed at earlier looked like the right fix, disappointing it didn't work21:58
psrcodeRP: yes. Thanks a lot. I'm currently setting up a dev env for yocto to help you a bit on that side (getting a weird mkfs4 error on core-image-minimal), did you saw the email I sent regarding the glibc problem we have with lttng-ust?21:59
armpitnot for sumo.. I just finish checkout thud-next. is has a openssl10 fix folks are wait for21:59
armpityeah, sumo is be troublesome this week22:00
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC22:00
RPpsrcode: yes, its on my todo list. Basically my repsonse is lets rip out those glibc patches22:00
RPpsrcode: if you wanted to send a patch removing them I'd likely take it22:00
RP(with a suitable justification in it)22:01
RPwe have no business carrying patches rejected upstream like those :(22:01
psrcodeRP: I might have questions regarding overall yocto/oe-core process regarding package update and all, we want (EfficiOS) to be a bit more proactive on the yocto packaging.22:01
RPpsrcode: I did hack out a set of tests as they hang. Wasn't sure if that was due to testing under qemu22:01
RPpsrcode: I preferred the suite completing than hanging and getting killed though!22:02
psrcodeyeah the notification tests, most probably missing the test executable. I'll look into it22:02
armpitRP, i looks like packagegroup-core-x11-base may have a problem..22:02
RPpsrcode: I suspect we could use the help. Happy to try and give the yocto/oe-core process pointers where I can (others here are helpful too)22:03
armpitdependency.. haven't tracked it down22:03
RPpsrcode: our ptest mangling to get on target is a bit ugly :/22:03
psrcodeRP: I'm sure I'll get to appreciate it ;p given enought time.22:04
RPpsrcode: its the bulk of the lttng-tools recipe. There may be some neater way to do it with upstream Makefile help22:04
psrcodeRP: as for the glibc stuff I'll wait for your feedback, take your time.22:05
RPpsrcode: I basically want to collate up the feedback from upstream and write a patch to OE-Core dropping the patches22:06
RParmpit: did you see the thud backport request for rng-tools?22:08
RParmpit: I just forwarded, just in case22:09
RParmpit: I'm happy enough to risk cherry-picking that one int22:09
RPpsrcode: Just for reference I'm a bit busy at the moment with the release, YP governance pieces and a conference next week :(22:10
psrcodeRP: I've cced Andreas (glibc) anyway I think I'll ping the bugzilla in the upcoming days, might be the best way to get their attention.22:10
armpitRP, I am good with that.22:13
RPpsrcode: sounds good22:13
psrcodeRP: take your time, we have a lttng-ust fix/workaround for it anyway.22:13
RPpsrcode: I don't like having broken glibc patches though ;-)22:14
RPkhem: did you see that discussion btw?22:14
psrcodei'm sure nobody does...22:14
psrcodeit was just a bit *unexpeceted* ;)22:15
RPpsrcode: We are getting better at sorting patches. That one looked sensible and was submitted upstream so seemed like an ok bet22:16
RPwe then never saw it get rejected22:16
psrcodeRP: one of the two was rejected, the other one (the one with a major impact) is in limbo.22:17
psrcodeanyway we can continue this via email when you have the time, I'm sure you have other things to do at the moment.22:17
RPpsrcode: but seemed likely to be rejected on the same basis?22:17
*** rcw <rcw!~rcw@> has quit IRC22:18
psrcodefrom my perspective based on the feedback from Compudj (mathieu desnoyers) but we are no glibc maintainers!22:18
RPpsrcode: right, neither are we :/22:19
RPpsrcode: however khem may have more of an idea22:19
RParmpit: tweaked thud, thanks22:24
psrcodeI'm currently trying to build a core-image-mininal inside lxc and I end up with the following error during the do_image_ext4 phase: https://pastebin.com/raw/KHFzEJLv22:28
psrcodeno much luck with google22:29
RPpsrcode: which filesystem is that on? It looks like the filesystem size calculation is going wrong and the image runs out of space22:30
*** awe00 <awe00!~awe00@unaffiliated/awe00> has joined #yocto22:30
RPpsrcode: would be interesting to see what the size of /root/oe-core/build/tmp-glibc/work/qemux86_64-oe-linux/core-image-minimal/1.0-r0/rootfs is by different measurement22:31
RPpsrcode: you can see the calculation it made...22:31
RPpsrcode: you could also try IMAGE_OVERHEAD_FACTOR = "2" or something instead of its default of 1.322:32
RPpsrcode: just force the rootfs to be larger22:33
RPhorrible hack but if it gets you working...22:33
psrcodeyeah -> du -ks yield: 100707 rootfs/22:33
psrcodewhile "du -ks --apparent-size" yield 158973 rootfs/22:33
psrcodele me try with the addition of apparent size22:33
psrcodethat fix it22:37
RPpsrcode: interesting. We tend to avoid zfs as we found we could break it too easily :/22:37
psrcodeI had a similar problem lately with zfs for tracefile size :P22:38
RPpsrcode: obviously it should work and we should figure this out and fix it...22:38
*** tgraydon <tgraydon!~textual@> has joined #yocto22:40
RPpsrcode: actually we should probably note this in a bug...22:40
psrcodeyeah will do for sure !22:40
RPthanks :)22:40
psrcodeeven add a base patch for it22:40
*** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-dlvzpcmvokhuqihs> has joined #yocto22:41
RPpsrcode: that log you shared along with the output from du and du --apparent-size gives a great place to start22:41
psrcodebut beer is calling22:41
RPwe shouldn't technically need apparent size as ext should handle sparse files and so on22:41
* RP is waiting for a late meeting :(22:42
RPjonmason: thanks for the patches! :)22:45
RPjonmason: did you get KMACHINE working?22:45
RPjonmason: halstead and I had a look at the arm server and I think we have some idea on what we need to sort there22:48
jonmasonI tried it but was unable to get the "KMACHINE_qemuarm = qemuarma15" working.  I think zeddii is looking at it22:58
*** awe00 <awe00!~awe00@unaffiliated/awe00> has quit IRC22:59
jonmasonRP: glad someone is working on the arm build servers.  As soon as I get back from SCaLE, I'll spend 100% of my time on that (assuming that the KMACHINE thing is done and you haven't solved the build issues yet)23:00
halsteadjonmason, We set -cpu host to get kvm acceleration working for qemuarm64 images.23:01
jonmasonbut didn't half the packages fail to build?23:05
*** dv_ <dv_!~dv@> has quit IRC23:27
halsteadjonmason, I was testing the oe-selftest prereqs specifically. There are many build problems I haven't looked at yet.23:28
*** stephano <stephano!~stephano@> has quit IRC23:38
rburton_psrcode: there's almost definitely a bug for that already23:41
*** dv_ <dv_!~dv@62-178-50-190.cable.dynamic.surfer.at> has joined #yocto23:41
rburton_psrcode: see poky-contrib:ross/du for my attempt at fixing this blind without access to a file system that i know is troublesome :)23:42
*** rburton_ <rburton_!~rburton@> has quit IRC23:42
khemRP: is it about https://www.sourceware.org/bugzilla/show_bug.cgi?id=1928223:49
yoctiBug 19282: was not found.23:49
khemRP: I have expressed my concern when they were originally proposed but they were still applied23:52
khemRP: its fine to drop 0026-reset-dl_load_write_lock-after-forking.patch and 0027-Acquire-ld.so-lock-before-switching-to-malloc_atfork.patch23:53
khemwe lose nothing23:53

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!