Tuesday, 2020-05-12

*** vineela <vineela!~vtummala@134.134.139.72> has quit IRC00:24
*** vineela <vineela!vtummala@nat/intel/x-ldjwggyrsvlvvtmz> has joined #yocto00:24
*** micka <micka!~micka@reverse-75.fdn.fr> has quit IRC00:40
*** vineela <vineela!vtummala@nat/intel/x-ldjwggyrsvlvvtmz> has quit IRC00:40
*** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC00:54
*** micka <micka!~micka@reverse-75.fdn.fr> has joined #yocto00:54
*** micka <micka!~micka@reverse-75.fdn.fr> has quit IRC01:11
*** Sandrita <Sandrita!18ca2637@gateway/web/cgi-irc/kiwiirc.com/ip.24.202.38.55> has quit IRC01:15
*** micka <micka!~micka@reverse-75.fdn.fr> has joined #yocto01:31
*** yizhao <yizhao!~zhaoyi@60.247.85.82> has joined #yocto01:46
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC01:51
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto01:53
*** yizhao <yizhao!~zhaoyi@60.247.85.82> has quit IRC01:54
*** kaspter <kaspter!~Instantbi@222.70.81.215> has quit IRC02:08
*** kaspter <kaspter!~Instantbi@222.70.81.215> has joined #yocto02:08
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC03:08
*** camus1 <camus1!~Instantbi@222.70.81.213> has joined #yocto03:43
*** kaspter <kaspter!~Instantbi@222.70.81.215> has quit IRC03:45
*** camus1 is now known as kaspter03:45
*** alejandrohs <alejandrohs!~alejandro@189.154.11.164> has quit IRC04:24
*** kaspter <kaspter!~Instantbi@222.70.81.213> has quit IRC04:39
*** camus1 <camus1!~Instantbi@222.70.81.210> has joined #yocto04:39
*** camus1 is now known as kaspter04:41
*** gtristan <gtristan!~tristanva@110.11.227.189> has quit IRC04:45
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:acce:67ec:9e5d:40e5> has joined #yocto04:45
*** pharaon2502 <pharaon2502!~manjaro-u@cpe-188-129-64-48.dynamic.amis.hr> has joined #yocto04:50
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:acce:67ec:9e5d:40e5> has quit IRC04:51
*** sgw <sgw!~sgw@134.134.137.77> has quit IRC04:59
*** agust <agust!~agust@pD95F11D0.dip0.t-ipconnect.de> has joined #yocto05:10
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC05:13
*** sgw <sgw!sgw@nat/intel/x-vxkypxqcpiodzgdj> has joined #yocto05:16
*** jkridner|pd <jkridner|pd!~jkridner@pdpc/supporter/active/jkridner> has quit IRC05:18
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto05:18
*** AndersD <AndersD!~AndersD@h83-209-96-136.cust.a3fiber.se> has joined #yocto05:23
*** AndersD_ <AndersD_!~AndersD@h83-209-96-136.cust.a3fiber.se> has joined #yocto05:25
*** rcoote <rcoote!~rcoote@221-224-024-217.ip-addr.vsenet.de> has joined #yocto05:27
*** AndersD <AndersD!~AndersD@h83-209-96-136.cust.a3fiber.se> has quit IRC05:27
*** jobroe <jobroe!~manjaro-u@p579EB307.dip0.t-ipconnect.de> has joined #yocto05:28
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:e947:2c45:5e8c:2589> has joined #yocto05:31
*** paulg_ <paulg_!~paulg@135-23-37-86.cpe.pppoe.ca> has quit IRC05:34
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:e947:2c45:5e8c:2589> has quit IRC05:37
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:8812:9113:a5d7:3761> has joined #yocto05:39
*** kroon <kroon!~kroon@213.185.29.22> has joined #yocto05:40
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:8812:9113:a5d7:3761> has quit IRC05:47
*** gtristan <gtristan!~tristanva@110.11.227.177> has joined #yocto05:50
*** alejandrohs <alejandrohs!~alejandro@189.154.11.164> has joined #yocto05:54
*** pohly <pohly!~pohly@p5B05600C.dip0.t-ipconnect.de> has joined #yocto05:57
*** vineela <vineela!~vtummala@134.134.137.77> has joined #yocto05:59
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has joined #yocto06:09
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:45c6:ea1d:6857:807e> has joined #yocto06:13
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:45c6:ea1d:6857:807e> has quit IRC06:18
*** edgar444 <edgar444!uid214381@gateway/web/irccloud.com/x-hrlyqiazvybufyzj> has joined #yocto06:22
*** leon-anavi <leon-anavi!~Leon@78.130.197.211> has joined #yocto06:24
cronoliohttp://paste.org.ru/?m5ddx1 full log06:26
*** frsc <frsc!~frsc@2003:a:e7a:6200:24d7:19e4:a9b3:3383> has joined #yocto06:28
*** mckoan|away is now known as mckoan06:30
Letothe2ndcronolio: despite the question lacking almost all content, i have to admit that we care mostly about building yocto and yocto-based stuff around here. (maybe thats becase why its called #yocto?)06:35
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@mob-176-243-9-254.net.vodafone.it> has joined #yocto06:37
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has joined #yocto06:37
cronolioLetothe2nd: is this really #yocto channel ? :)06:43
alejandrohscronolio: I cant tell if youre being sarcastic06:44
alejandrohseither way06:44
alejandrohscronolio: I agree with Letothe2nd, but skimming through your log youre missing a header file06:44
alejandrohscronolio: gshadow comes from glibc06:44
alejandrohscronolio: you can literally see the compilation command so you know what directories are being searched for header files (-I flags)06:45
cronolioin my case libc is musl06:45
alejandrohscronolio: you could also add -v to CFLAGS and it would tell you the specific order06:45
alejandrohscronolio: I was just about to say you need to check where that file should be coming from and why is it not finding it06:46
Letothe2ndcronolio: iÄm not being sarcastic, just referring to "21:27 < cronolio> in custom linux, not yocto"06:46
alejandrohscronolio: but you just answered your own question06:46
Letothe2ndcronolio: so i think the remark is absolutely legit.06:46
alejandrohsLetothe2nd: haha I meant him06:46
Letothe2ndcronolio: plus, as systemd specifically targets glibs, you're wll like... whatever.06:47
alejandrohscronolio: AFAIC gshadow comes from GLIBC not libc06:47
alejandrohsso, musl wouldnt have it06:47
alejandrohscronolio: at least my musl build does not either06:48
cronolioso.. in yocto.. it is possible to build systemd with musl ?06:49
Letothe2ndcronolio: as you can see in http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-core/systemd/systemd_245.5.bb?h=master#n25 the recipe suggests that it builds for musl, but http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-core/systemd/systemd_245.5.bb?h=master#n660 pretty directly says "use at your own precaution"06:52
alejandrohsit does06:52
Letothe2ndcronolio: as well as it states that you need to take care about the configuration: http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-core/systemd/systemd_245.5.bb?h=master#n9306:53
alejandrohsthe thud branch had 0022-Use-if-instead-of-ifdef-for-ENABLE_GSHADOW.patch06:53
alejandrohswhich was dropped on the 241 upgrade 4eb2b3f1503a41474d0c40ada296a9800840267c06:53
alejandrohsbut youre gonna have to debug why yourself bc its late06:54
alejandrohsgood night guys06:54
Letothe2ndlaters06:55
alejandrohscronolio: Also, as Letothe2nd said, the simplest answer probably is build with yocto :)06:56
cronoliothanks. looks like configuration part is what needed to me06:57
*** fl0v0 <fl0v0!~fvo@89.244.125.58> has joined #yocto06:58
alejandrohscronolio: you might get it to build now, but eventually you'll realize the solution that scales is yocto/OE06:58
alejandrohsalright night06:58
cronolioalejandrohs: yeah, i understand that here is yocto channel :)07:01
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto07:12
*** yacar_ <yacar_!~yacar_@91-168-169-253.subs.proxad.net> has joined #yocto07:18
*** ssajal <ssajal!~ssajal@otwaon1146w-lp140-01-64-229-138-221.dsl.bell.ca> has quit IRC07:19
cronoliothere is something from lfs, musl and now from yocto. it's just for fun. quality and some scaling not required :)07:31
*** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has joined #yocto07:37
*** gtristan <gtristan!~tristanva@110.11.227.177> has quit IRC07:40
*** nameclash <nameclash!~nameclash@ip1f11b23e.dynamic.kabel-deutschland.de> has joined #yocto07:46
*** vineela <vineela!~vtummala@134.134.137.77> has quit IRC07:49
*** aggurio <aggurio!~alex@67.red-79-156-8.staticip.rima-tde.net> has joined #yocto08:15
*** sstiller <sstiller!~sstiller@p200300F07F153001B59CDBCA569F6CF7.dip0.t-ipconnect.de> has joined #yocto08:19
*** gtristan <gtristan!~tristanva@110.11.227.177> has joined #yocto08:28
*** rburton <rburton!~rburton@192.198.151.44> has joined #yocto08:35
*** rcoote <rcoote!~rcoote@221-224-024-217.ip-addr.vsenet.de> has quit IRC08:36
*** rcoote <rcoote!~rcoote@221-224-024-217.ip-addr.vsenet.de> has joined #yocto08:37
*** meego <meego!~meego@82-64-5-168.subs.proxad.net> has joined #yocto08:39
*** rcoote <rcoote!~rcoote@221-224-024-217.ip-addr.vsenet.de> has quit IRC08:41
*** rcoote <rcoote!~rcoote@221-224-024-217.ip-addr.vsenet.de> has joined #yocto08:41
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has quit IRC08:51
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto08:51
*** sagner <sagner!~ags@2a02:169:3df5::edf> has quit IRC08:54
*** hpsy <hpsy!~hpsy@85.203.15.120> has joined #yocto08:58
*** Andy86 <Andy86!4d35ed15@h77-53-237-21.cust.a3fiber.se> has joined #yocto09:09
*** csanchezdll <csanchezdll!~user@galileo.kdpof.com> has joined #yocto09:13
*** KindOne <KindOne!kindone@freenode/father-christmas/kindone> has left #yocto09:14
*** tprrt <tprrt!~tprrt@upc31-1-78-208-110-13.fbx.proxad.net> has joined #yocto09:32
*** pharaon2502 <pharaon2502!~manjaro-u@cpe-188-129-64-48.dynamic.amis.hr> has quit IRC09:48
*** pharaon2502 <pharaon2502!~manjaro-u@cpe-188-129-64-48.dynamic.amis.hr> has joined #yocto09:49
*** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has joined #yocto09:54
*** meego <meego!~meego@82-64-5-168.subs.proxad.net> has quit IRC09:56
*** RobertBerger <RobertBerger!~rber@ppp-2-84-88-125.home.otenet.gr> has quit IRC09:57
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC10:11
*** dlan <dlan!~dennis@116.226.129.133> has joined #yocto10:12
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto10:12
*** curlybracket <curlybracket!~quassel@ip-89-176-35-52.net.upcbroadband.cz> has quit IRC10:13
*** tolszak <tolszak!~tolszak@apn-31-0-23-138.dynamic.gprs.plus.pl> has joined #yocto10:17
*** distcline <distcline!~dist@d8d86740a.access.telenet.be> has quit IRC10:18
tolszakHi, Is it possible to add extended partition on demand in wks file. I don't see such possiblity in docs10:19
*** distcline <distcline!~dist@d8d86740a.access.telenet.be> has joined #yocto10:19
paulbarkerLooks like downloads.yoctoproject.org is down. Anyone else having issues with it?10:26
mfe555paulbarker: same here10:30
qschulzWhy does it always happen when it's halstead night time :) ? Are the servers european-racists?10:33
*** khem <khem!~khem@unaffiliated/khem> has quit IRC10:44
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:88ee:1382:8d77:97bf> has joined #yocto10:46
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:88ee:1382:8d77:97bf> has quit IRC10:50
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:5128:f398:7eac:7c60> has joined #yocto10:50
*** meego_ <meego_!~meego@2a01:e0a:1ec:b0e0:883d:4b90:6ecd:4451> has joined #yocto10:52
paulbarkertolszak: I think you need to expand on that question a bit, it's a bit too vague for me to understand what you're wanting to do10:52
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto10:53
paulbarkerDamn, my build failed. I need to find a mirror for `opkg-0.4.2.tar.gz` or wait until downloads.yoctoproject.org gets fixed10:53
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:5128:f398:7eac:7c60> has quit IRC10:55
*** meego_ <meego_!~meego@2a01:e0a:1ec:b0e0:883d:4b90:6ecd:4451> has quit IRC10:56
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has quit IRC11:07
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@mob-176-243-9-254.net.vodafone.it> has joined #yocto11:08
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has joined #yocto11:08
*** joeythesaint <joeythesaint!~joe@vegas.deserted.net> has joined #yocto11:12
*** nameclash <nameclash!~nameclash@ip1f11b23e.dynamic.kabel-deutschland.de> has quit IRC11:13
tolszakpaulbarker: My old custom system have partition layout:11:18
tolszak1. boot 2. extended 3. other partitions11:18
tolszakI want to port it to yocto and extended partition is only created when I try to create > 4 partitions11:19
tolszakto have the same partition numbering as in old layout11:19
tolszakI need to create 2 artificial not used partitions in wks file just after boot partition11:19
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:4994:1909:a77c:1cad> has joined #yocto11:20
*** nameclash <nameclash!~nameclash@ip1f11b23e.dynamic.kabel-deutschland.de> has joined #yocto11:22
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:4994:1909:a77c:1cad> has quit IRC11:25
qschulzpaulbarker: http://git.yoctoproject.org/cgit/cgit.cgi/opkg/snapshot/opkg-0.4.2.tar.gz ?11:25
tolszakpaulbarker: So I would like to do it neat. Initial option is to make custom image type recipe with parted inside it. But if wks allows to add extended partition manually it is IMHO  alot better idea11:25
*** berton <berton!~berton@181.220.84.90> has joined #yocto11:29
*** rcoote <rcoote!~rcoote@221-224-024-217.ip-addr.vsenet.de> has quit IRC11:31
*** rcoote <rcoote!~rcoote@221-224-024-217.ip-addr.vsenet.de> has joined #yocto11:32
*** berton <berton!~berton@181.220.84.90> has quit IRC11:33
*** lfa_ <lfa_!~lfa@80-108-132-46.cable.dynamic.surfer.at> has quit IRC11:34
*** berton <berton!~berton@181.220.84.90> has joined #yocto11:34
*** rcoote <rcoote!~rcoote@221-224-024-217.ip-addr.vsenet.de> has quit IRC11:36
*** rcoote <rcoote!~rcoote@221-224-024-217.ip-addr.vsenet.de> has joined #yocto11:36
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:55c2:6cf:c6cf:279a> has joined #yocto11:49
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:55c2:6cf:c6cf:279a> has quit IRC11:53
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:55c2:6cf:c6cf:279a> has joined #yocto11:57
*** Guest5242 <Guest5242!a5e14925@gateway/web/cgi-irc/kiwiirc.com/ip.165.225.73.37> has joined #yocto12:17
*** Guest5242 is now known as PatrickE12:17
PatrickEHi is there an easy way to create a SDK which is identically with the one iam using in a build?12:18
PatrickEIam asking because,right now iam able to build the main application with the default sdk and with bitbake . But i want to add a dbus dependency and i want to add a shared object , so the SDK / standalone build will not work if i merge this12:20
paulbarkertolszak: Are you talking about the old msdos primary/extended partitioning?12:21
paulbarkerYou should be able to use the `--type` argument in your wks file: http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/scripts/lib/wic/ksparser.py#n15612:21
tolszakpaulbarker: Yes I do12:21
tolszakpaulbarker: Any idea why it is not in docs: https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#command-part-or-partition12:22
tolszakpaulbarker: :)12:22
paulbarkertolszak: wic has grown lots of new options and Yocto Project is currently without a dedicated docs maintainer. Patches welcome :)12:23
tolszakpaulbarker: Will give it a try thank you! it is highly possible I will contribute explanation for this option. Thanks12:23
*** ykrons <ykrons!~guillaume@62.192.23.101> has joined #yocto12:26
ykronsHi12:27
*** gtristan <gtristan!~tristanva@110.11.227.177> has quit IRC12:31
ykronsI would like to include an application in two differents images but the application has to be compiled with different options. It seems it is not possible to share variable between image and application recipes, is there another way? Is it possible to create two recipes that share everything (with an include) expect a variables that changes build options or is there a smarter way?12:31
qschulzykrons: two distros is the proper way to do it. Depending on what the option changes, just compile everything and bundle in different packages is another proper option. Hacks involve having two recipes including the same .inc file where 99% of the logic is written except PACKAGECONFIG = "foo bar".12:33
*** cronolio <cronolio!~alex@unaffiliated/cronolio> has quit IRC12:34
qschulzykrons: global data is global, local data is local. recipes set local data only )otherwise build or parsing order would matter which is not correct)12:35
PatrickEI use two distributions and one machine12:36
*** yacar_ <yacar_!~yacar_@91-168-169-253.subs.proxad.net> has quit IRC12:36
*** yacar_ <yacar_!~yacar_@91-168-169-253.subs.proxad.net> has joined #yocto12:36
ykronsqschulz, PatrickE: thanks for feedback. In my mind distos were a high level set of packages to install like X server etc. In my case, it is "just" like building a enduser application with different splashscreen image ... so distro seems to me overkill, but I'm not very familiar with distro12:48
PatrickEykrons i tried to copy the real world situation 1 to 1. That means i build one mainboard => one machine ...12:49
ykronsPatrickE, same for me mainboad <-> MACHINE, I should admit that then for me : one IMAGE <=> one product and I don't know what to do with DISTRO...12:52
PatrickEI use debug and release distros :D12:53
ykronsI see several similar products using the same DISTRO customized by different IMAge12:53
*** Sandrita <Sandrita!18ca2637@gateway/web/cgi-irc/kiwiirc.com/ip.24.202.38.55> has joined #yocto12:57
qschulzykrons: distros are lego vs mechano. images are boat vs car. You cna't build an image without a distro and a specific distro impacts many images.12:58
qschulzykrons: https://www.youtube.com/watch?v=o-8g0TPVVGg might be better explained :)12:58
qschulzmight explain better*12:58
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC12:59
qschulzykrons: if it's just a splashscreen that is changed, the two recipes hack seems acceptable to me (even hackier is to change it directly in the rootfs from the image recipe but... I don't like modifying behavior of a package from the image recipe)13:01
*** pohly <pohly!~pohly@p5B05600C.dip0.t-ipconnect.de> has quit IRC13:04
Letothe2ndqschulz: you are doing good in explaining :)13:05
*** pohly <pohly!~pohly@p5B05600C.dip0.t-ipconnect.de> has joined #yocto13:06
qschulzLetothe2nd: only took your words from Yocto dev days :)13:07
Letothe2ndqschulz: i know. :)13:08
*** radsquirrel <radsquirrel!~radsquirr@mail.fuzziesquirrel.com> has quit IRC13:10
*** radsquirrel <radsquirrel!~radsquirr@mail.fuzziesquirrel.com> has joined #yocto13:11
*** hchaumette <hchaumette!b0bce40f@lcs07-lyo-176-188-228-15.sfr.lns.abo.bbox.fr> has joined #yocto13:13
*** kroon <kroon!~kroon@213.185.29.22> has quit IRC13:16
ykronsqschulz, I will have a look to the video to clarify some concepts! Thanks. It is a bit more than a splashscreen and require different compilation, but it remains an application specific customization13:20
ykronsLetothe2nd, thanks for the video13:21
Letothe2ndykrons: :)13:23
*** ecdhe <ecdhe!~quassel@unaffiliated/ecdhe> has quit IRC13:24
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto13:26
zeddiiRP:  can you think of an example recipe that exports some variables from a called block of code ? My grepping has failed.  My reproducibility changes are needed in a couple of places in the kernel build, and I just copied and pasted the variable exports for now .. but obviously better if it can be one place to do the exports. It can’t be anonymous python or class exports, since it needs the code to be checked out, et13:27
*** ssajal <ssajal!~ssajal@otwaon1146w-lp140-01-64-229-138-221.dsl.bell.ca> has joined #yocto13:33
JPEWdenix. jonmason: Upon further thought, I don't think that moving those python recipes to OE-core is the best idea13:34
*** ericch <ericch!~ericch@pool-108-34-251-214.prvdri.fios.verizon.net> has joined #yocto13:35
jonmasonJPEW: Works for me13:36
jonmasonJPEW: I'm going to have a v2 of the TFA patch shortly.  Diego fixed the part you and denix were complaining about :)13:36
*** ecdhe <ecdhe!~quassel@unaffiliated/ecdhe> has joined #yocto13:37
denixJPEW: why?13:38
JPEWdenix: from a maintainence perspective, I think it would be better to put TFA in oe-core instead... it seems like it would be more likely to be maintained than 2 random python recipes... I might be biased though13:42
PatrickEOh i just tried -c populate_sdk  ....13:43
PatrickEbitbake is really powerful13:43
denixJPEW: isn't it what I proposed back then and got shot?13:43
JPEWdenix: Yes it is13:43
* JPEW looks back at that thread13:46
JPEWdenix, jonmason: I don't really have a problem with leaving TFA in meta-arm, I just think if anything is moving to oe-core, TFA seems the most likely to be maintained, since most aarch64 users are going to need it.13:52
zeddiithat jonmason is a slacker. he’ll let it bitrot in meta-arm :P13:52
jonmasonJPEW: I'd prefer to keep it in meta-arm13:52
jonmasonzeddii: ha!13:53
JPEWjonmason: Fair enough, but that means something has to be done with op-tee13:53
* zeddii ducks13:53
JPEWMake it dynamic on meta-python?13:53
jonmasonJPEW: I like that better than making it's own layer13:54
JPEWjonmason: Sounds good. I'll make a patch13:54
jonmasonzeddii: weren't you going to use TF-A from meta-arm....13:54
jonmason;-)13:55
denixJPEW: why do you say python modules will not be maintained in oe-core?13:55
denixJPEW: those are just python modules - how much maintenance do they require?13:55
denixjonmason: yeah, we are in this mess because of zeddii!13:56
jonmasondenix: always zeddii fault13:56
zeddiitruth!13:57
jonmasonsanity build of world + dog with new tf-a recipes (with deigo's change).  pushing to list upon expected successful completion13:57
zeddii@jonmason yes we will.13:57
zeddiijust fighting the battle of open sourcing lopper at the moment. wheee. and fixing kernel reproducible builds, THEN fight that battle :D13:58
JPEWdenix: Its not that they won't or can't be maintained... I just suspect it might be harder to do so?13:58
denixJPEW: python modules are low maintenance in general - just version updates, right?14:01
RPIf we have the maintainers there could be a case for gently expanding oe-core a little14:08
JPEWdenix: Ya it probably would be fine14:12
*** alimon <alimon!alimon@gateway/shell/linaro/x-isutvxgfzdmkzivl> has left #yocto14:13
tgamblindenix: there's also some runtime dependency work involved in maintenance, although those changes aren't usually recurring14:15
JPEWtgamblin: I think in this case it would be moving existing recipes from meta-python, does that make a difference?14:16
tgamblinJPEW: depends on which ones got moved, but yeah - I've been sending fixes for module recipes here and there over the last couple of weeks, and I have 4-5 more coming14:18
*** jobroe <jobroe!~manjaro-u@p579EB307.dip0.t-ipconnect.de> has quit IRC14:20
tgamblinWe could also end up wanting to migrate some Python modules (e.g. python3-fastentrypoints) to address the sluggishness of https://github.com/pypa/setuptools/issues/510, if we were going to consider adding more to oe-core14:20
paulg$ git log --oneline --since Jan |grep gcc-10 | wc -l14:25
paulg1014:25
paulgin case anyone cares.14:25
paulga few more just added over the wknd.14:25
Letothe2ndpaulg: https://twitter.com/TheYoctoJester/status/126010723347770163614:27
* paulg wouldn't have associated being a gcc fanboy with "kewl kids" but whatever....14:35
Letothe2nd:)14:35
*** rob_w_ <rob_w_!~rob@ppp-93-104-34-197.dynamic.mnet-online.de> has joined #yocto14:37
paulgthe above was mainline kernel, btw.   Should have made that explicit.14:38
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC14:41
jonmason"Why is this build taking so long?  meta-virtualizaton....dammit!"14:41
zeddiidon’t blame the messenger. blame libvirt14:42
Letothe2ndblame everything!14:43
*** tsjsieb <tsjsieb!~quassel@103.214.7.25> has quit IRC14:45
*** AndersD_ <AndersD_!~AndersD@h83-209-96-136.cust.a3fiber.se> has quit IRC14:46
*** rcoote <rcoote!~rcoote@221-224-024-217.ip-addr.vsenet.de> has quit IRC14:46
*** rcoote <rcoote!~rcoote@221-224-024-217.ip-addr.vsenet.de> has joined #yocto14:47
*** tsjsieb <tsjsieb!~quassel@2a06:5b80:1::2be3:ec4> has joined #yocto14:48
*** rcoote <rcoote!~rcoote@221-224-024-217.ip-addr.vsenet.de> has quit IRC14:51
*** rcoote <rcoote!~rcoote@221-224-024-217.ip-addr.vsenet.de> has joined #yocto14:51
smurrayjonmason: heh, I guess you don't use Qt ;)14:59
dl9pfYPTM: Jan-Simon is on14:59
smurrayYPTM: Scott Murray is on15:00
*** sstiller <sstiller!~sstiller@p200300F07F153001B59CDBCA569F6CF7.dip0.t-ipconnect.de> has quit IRC15:01
* paulbarker misses the first 5 mins of the YPTM call15:06
*** net_wayfarer <net_wayfarer!net_wayfar@gateway/shell/ircnow/x-zlwxtdmmrxkqqaye> has quit IRC15:08
*** gtristan <gtristan!~tristanva@110.11.227.189> has joined #yocto15:08
*** rcoote <rcoote!~rcoote@221-224-024-217.ip-addr.vsenet.de> has quit IRC15:11
*** frsc <frsc!~frsc@2003:a:e7a:6200:24d7:19e4:a9b3:3383> has quit IRC15:11
*** rcoote <rcoote!~rcoote@221-224-024-217.ip-addr.vsenet.de> has joined #yocto15:12
*** rcoote <rcoote!~rcoote@221-224-024-217.ip-addr.vsenet.de> has quit IRC15:16
*** rcoote <rcoote!~rcoote@221-224-024-217.ip-addr.vsenet.de> has joined #yocto15:16
ykronsqschulz, PatrickE : I will finally go the two recipes hack way. The video has confirmed my understanding of distro .. and we rereading the thread I see the "lego vs mecano ..." that I have missed the first time ... everything is clear now!15:19
ykronsthanks all15:20
RPalejandrohs: https://wiki.yoctoproject.org/wiki/LTS15:27
*** dreyna <dreyna!~dreyna@2601:646:4201:b1a0:d84c:c0c4:a716:ddf9> has joined #yocto15:27
*** jae1 <jae1!~jaewon@c-73-162-13-38.hsd1.ca.comcast.net> has joined #yocto15:31
*** fl0v0 <fl0v0!~fvo@89.244.125.58> has quit IRC15:32
*** net_wayfarer <net_wayfarer!net_wayfar@gateway/shell/ircnow/x-vpgwfltkbdodipii> has joined #yocto15:36
*** mischief <mischief!~mischief@c-73-162-223-48.hsd1.ca.comcast.net> has quit IRC15:38
*** vineela <vineela!~vtummala@134.134.139.76> has joined #yocto15:38
*** mischief <mischief!~mischief@2601:646:100:53:5bf8:35e5:561a:f73e> has joined #yocto15:40
*** mischief is now known as Guest6872015:41
*** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has quit IRC15:43
*** cpo <cpo!~cpo@helix.mybll.net> has quit IRC15:44
*** Guest68720 <Guest68720!~mischief@2601:646:100:53:5bf8:35e5:561a:f73e> has quit IRC15:45
halsteadqschulz, paulbarker, downloads.yoctoproject.org recovered on its own. I've been investigating for the last hour and I haven't tracked down the problem yet. I appreciate the report.15:55
alejandrohsRP: thanks15:56
paulbarkerhalstead: Thanks for looking into it15:59
*** cpo <cpo!~cpo@helix.mybll.net> has joined #yocto16:00
*** feddischson <feddischson!~feddischs@HSI-KBW-095-208-248-064.hsi5.kabel-badenwuerttemberg.de> has joined #yocto16:02
*** hchaumette <hchaumette!b0bce40f@lcs07-lyo-176-188-228-15.sfr.lns.abo.bbox.fr> has quit IRC16:03
khemJPEW: do we still need 32bit mingw SDK or 64bit is enough these days16:09
*** mischief1 <mischief1!~mischief@c-73-162-223-48.hsd1.ca.comcast.net> has joined #yocto16:12
JPEWkhem: I'm not sure. I don't need 32-bit so it might be worth asking on the ML.16:15
JPEWkhem: Is something breaking?16:15
khemyes gcc1016:21
rburtondrop it!16:21
rburton*surely* nobody needs a 32-bit sdk now16:22
khemhttps://autobuilder.yoctoproject.org/typhoon/#/builders/89/builds/189216:23
*** FrazerClews <FrazerClews!~frazer.cl@78.40.148.177> has quit IRC16:26
*** nerdboy <nerdboy!~sarnold@47.143.129.91> has joined #yocto16:36
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto16:37
*** FrazerClews <FrazerClews!~frazer.cl@78.40.148.177> has joined #yocto16:38
*** mckoan is now known as mckoan|away16:48
*** gaston53 <gaston53!c50186cf@197.1.134.207> has joined #yocto16:48
gaston53Hello, I build linux distribution for my SAMA5D27 atmel microchip board. I want to connect my board to wifi network instead of using ethernet cable. How can I do that please ?16:50
JPEWkhem: Is it just the i686 toolchain that failed? The x86_64 one passed?16:53
*** gaston53 <gaston53!c50186cf@197.1.134.207> has quit IRC17:03
*** PatrickE <PatrickE!a5e14925@gateway/web/cgi-irc/kiwiirc.com/ip.165.225.73.37> has quit IRC17:03
RPJPEW: I think so, yes17:06
*** gaston53 <gaston53!c50186cf@197.1.134.207> has joined #yocto17:06
*** gaston53 <gaston53!c50186cf@197.1.134.207> has quit IRC17:06
*** aggurio <aggurio!~alex@67.red-79-156-8.staticip.rima-tde.net> has quit IRC17:27
*** maudat <maudat!~moda@107-190-37-226.cpe.teksavvy.com> has joined #yocto17:29
*** jae1 <jae1!~jaewon@c-73-162-13-38.hsd1.ca.comcast.net> has quit IRC17:32
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:55c2:6cf:c6cf:279a> has quit IRC17:47
*** bzb <bzb!~bzb@135-23-193-53.cpe.pppoe.ca> has joined #yocto17:52
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC17:55
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto17:56
*** bzb <bzb!~bzb@135-23-193-53.cpe.pppoe.ca> has quit IRC18:27
*** chandana73 <chandana73!~ckalluri@149.199.62.129> has joined #yocto18:30
khemRP: sent a v518:31
khemI carved out a fix for mingw32 as well and it was pretty much limited to mingw32 I thought it is safe to have it in gcc18:32
khemRP: the fix for valgrind/aarch64 is in glibc so I dropped the gcc patch for that and instead bumped glibc 2.31 recipe to latest on branch this particular change should be good for dunfell too18:33
khemAlso merged the version mismatch for maintainer entry18:33
khemRP: hopefully this will fix all the issues we have known thus far18:34
khemJPEW: yes, so question is do we need to support 32bit windows for SDKs moving forward18:34
khemgiven that windows7 is EOL18:34
khemand moreover should we be spending precious AB cycles on it18:35
rburtoni'd say no we don't18:39
frayI vote to eliminate win 7 support..18:40
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto18:47
ant__well, there are the older releases if one badly needs win3218:50
ant__and there are tons of tools18:50
ant__in their eco-system18:50
zeddiievery time I see precious, I hear gollum’s voice.18:52
jonmasonzeddii: me too!18:53
rburtonant__: if someone badly needs 32-bit support they can bring it back18:53
rburtonits just a matter of what the priorities are18:53
*** amaury_d <amaury_d!~amaury_@lfbn-idf1-1-361-18.w86-195.abo.wanadoo.fr> has quit IRC18:57
*** woutervh <woutervh!~woutervh@188.189.112.146> has joined #yocto18:58
*** sgw <sgw!sgw@nat/intel/x-vxkypxqcpiodzgdj> has quit IRC19:05
*** yacar_ <yacar_!~yacar_@91-168-169-253.subs.proxad.net> has quit IRC19:10
JPEWYa, I think dropping 32-bit is fine19:11
JPEWI can't think of any legitimate reason for keeping it around; it hasn't really been any more effort to maintain over the x86_64 SDK previously, but maybe that's finally shifting.19:12
*** rburton <rburton!~rburton@192.198.151.44> has quit IRC19:25
*** rburton <rburton!~rburton@192.198.151.44> has joined #yocto19:27
Letothe2ndhum there's a vote going on?19:46
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC19:47
RPLetothe2nd: ?19:47
Letothe2nd18:40 < fray> I vote to eliminate win 7 support..19:47
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto19:47
Letothe2ndcan I vote for beer and metal?19:47
Shaunbeer and metal are already required to support win7, no?19:48
Letothe2nddespite public expectations I hold no grudge against Microsofts software products.19:50
*** vineela <vineela!~vtummala@134.134.139.76> has quit IRC19:52
JPEWjonmason: So, how would I go about building optee for testing?19:53
paulgbeer in an aluminum can covers both requirements.19:54
*** pharaon2502 <pharaon2502!~manjaro-u@cpe-188-129-64-48.dynamic.amis.hr> has quit IRC19:54
Letothe2ndpaulg: i have to admit that this is technically correct.19:55
jonmasonJPEW: I don't have a platform that is actively using it.  denix might.19:58
RPjonmason: lots of talk about trusted-fw :)20:02
Letothe2ndtrust? https://youtu.be/VaYf0OGN68Y20:04
*** Andy86 <Andy86!4d35ed15@h77-53-237-21.cust.a3fiber.se> has quit IRC20:04
jonmasonwhy did I just click Letothe2nd's link?20:04
Letothe2ndbecause.20:05
jonmasonRP: oh?20:05
Letothe2ndjonmason: i have to admit that this specific link was quite "serious" in comparison, though.20:06
jonmasonLetothe2nd: very 80's hair metal20:07
JPEWjonmason: Looks like it might build for qemu (TFA also)... I might add support for that in the recipes by default20:07
jonmasonJPEW: yes, I've seen that and have it on my never-ending todo list20:08
*** amaury_d <amaury_d!~amaury_@lfbn-idf1-1-361-18.w86-195.abo.wanadoo.fr> has joined #yocto20:08
jonmasonJPEW: are you okay with me pulling in my TF-A v2.3 recipe?20:08
RPjonmason: the question of whether its meta-arm or core due to the number of dependencies and some of the challenges of the meta-arm dependencies20:09
JPEWjonmason: Ya it's fine20:09
JPEWjonmason: Ya I think we should reopen that disucssion also :)20:09
jonmasonRP: We're trying to fix that now :)20:09
Letothe2ndjonmason: as you know for sure how complicated customer care, i should rather suggest: https://youtu.be/WPUJG2jTw9s20:09
JPEWjonmason: We were talking about it on the technical call this morning (afternoon?)20:10
RPjonmason: the worry is an oe-core which requires meta-arm to build any arm platform isn't a good message for OE :/20:10
jonmasondammit, I had a conflict this morning20:10
RPjonmason: as JPEW said, it came up and was discussed which is why I'm trying to make sure you know that happened! :)20:11
Letothe2ndRP: i second that worry hereby.20:11
JPEWjonmason: I think the argument could be made that TFA is a lot like u-boot: Most (all?) aarch64 needs it to boot so maybe it belongs in oe-core instead20:11
jonmasonRP: I completely understand.  If it makes sense to move then it should move.  The only issue would be when it would move (assuming it is being used in qemu)20:11
khemmeta-arm should just be an architecture layer I think and mostly try to be inert20:12
jonmasonJPEW: I'm hoping that other things needed by most aarch64 systems will be in meta-arm20:12
khemcurrently its leaning towards a BSP layer more20:12
jonmasonlike EDK2 and SCP20:12
RPjonmason: right, I've not formed a strong opinion on it as yet, I just have concerns20:12
jonmasonkhem: thats due to who we have working on it now20:12
denixjonmason: yeah, I missed all the morning meetings today due to conflict as well20:12
jonmasonif we can get a new hire to start and work on it in the next month or so, maybe it can be aswesome20:13
jonmason* cough *20:13
RPheh20:13
Letothe2ndas usual, there are coins to be inserted.20:13
JPEWjonmason: Ya, I know you are getting the dunfell release ready, so I think that putting the 2.3 there for now is fine, since moving it wouldn't be in the oe-core dunfell release anyway20:14
RPagreed, dunfell and what happens in master are two different things20:14
jonmasonwe're trailing the YP release due to python2 junk, which should be gone once I push my current HEAD20:15
JPEWBut looking at what is in meta-arm right now, the only thing you *need* to boot is TFA. Coresight and optee aren't mandatory (at least for non-security applications). Granted, I don't know what the roadmap is20:15
khemand also in many cases it might make sense to bring things to oe-core to make qemuuarm better or qemuarm64 e.g. grub is not used by all arches but we still keep it in OE-Core likewise we can do that for some components that are common enough for arm platforms usually20:15
RPjonmason: right, that all looks like a good move20:16
* RP wasn't feeling too good earlier on so isn't entirely sure about anything he said... :/20:17
jonmasonto me, the next "must have" is EDK2.  Which has been promised by the BSP team but are super slow to deliver (and it a huge PITA due to needing specific toolchain versions)20:17
jonmasonI'd like for my new hire to work on that not being hot garbage20:18
* RP is happy to forget about edk220:18
jonmasonits all that anyone cares about for aarch64 now, even though I hate it and want it to die20:18
khemjonmason: for py2 just say that meta-arm needs qtwebengine and we will accept it depend on meta-py2 :)20:19
jonmasonJPEW: is SCP recipe interesting at all for your layers?20:20
jonmasonor do you just use vendor binaries20:21
khemjonmason: if not edk2 then what what do you use for aarch64 as UEFI impl20:21
jonmasonu-boot can mostly fake it out20:21
jonmasonand u-boot is done in a sane manner20:22
jonmasonEDK2 looks like something that was farmed out to the cheapest contracting firm and was paid by LOC20:22
jonmasonI had to work on it once and hated life the whole time20:23
JPEWjonmason: I'm not actually that familiar with the lower levels of ARMv8... whats SCP?20:23
jonmasonhttps://github.com/ARM-software/SCP-firmware20:24
jonmasoneach vendor decides what secret sause they don't want to share, and usually its right around the SCP/MCP level20:26
denixkhem: we need chromium!20:26
JPEWjonmason: Is that usually where there is a pre-compiled binary that gets shoved in somewhere in ATF?20:27
jonmasonyes20:27
JPEWjonmason: Not sure. I honestly haven't looked at what the ATF builds for my SoCs are doing.... they just sort of work :)20:28
jonmasonJPEW: since ATF is BSD licensed, few vendors give it out anyway.  If Rockchip does, that I'm actually highly impressed20:28
JPEWExcept for the RK3399, I know that one has an M0 that it uses for something, but I think thats already built from source by ATF because you have to provide the arm-none-eabi-gcc for it to build20:28
jonmasonJPEW: are you using an embedded toolchain too?20:29
*** BritManuela <BritManuela!a3ac9b92@gateway/web/cgi-irc/kiwiirc.com/ip.163.172.155.146> has joined #yocto20:29
jonmasonthat's next on my todo list20:30
JPEWjonmason: Not quite sure what you mean. For RK3399 we do: http://git.yoctoproject.org/cgit/cgit.cgi/meta-rockchip/tree/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.3.bb#n11 and then http://git.yoctoproject.org/cgit/cgit.cgi/meta-rockchip/tree/recipes-devtools/gcc-arm-none-eabi/gcc-arm-none-eabi-native_9-2019-q4-major.bb20:30
JPEWBut thats not ideal. We'd rather build arm-none-eabi-gcc from source with either multilib or multiconfig20:31
JPEWJust haven't gotten there yet :)20:31
*** BritManuela <BritManuela!a3ac9b92@gateway/web/cgi-irc/kiwiirc.com/ip.163.172.155.146> has quit IRC20:31
jonmasonJPEW: this is litteraly something I'm planning on working on today.  I'll talk to you about it once I educate myself, since I think we will be doing similar things20:32
JPEWWell, builing optee-os and TFA for qemuarm64 was surprisingly easy. No idea if they boot :)20:32
khemso why do we need binary toolchains, cant we do something like gcc --freestanding and keep using the internal toolchain20:33
jonmasonarm is giving people bin toolchains.  so I'd like to support it.  ya know, with out actually supporting it20:34
JPEWkhem: Not in the RK3399 case because the main SoC is AArch64 and the M0 is AArch3220:34
jonmasonI assume the m0 is running an RTOS and doing mailbox stuff20:35
khemoh so you need multiconfig20:35
khemthat should work well these days20:35
JPEWkhem: Ya, I tried a few things, but got busy and didn't have time to sort it out so the binary toolchain stuck (for now)20:36
JPEWLike I said, I want to figure out some way to do it20:36
khembut using binary toolchain is easier option I guess until arm officially adopts mutliconfig as way to do it in future, maybe jonmason your new hire can help with that20:36
jonmasonJPEW: Ok, your patches do not apply now that I've thoroughly messed with tf-a recipes.  Could I respectifully ask you to rebase and resubmit?20:36
JPEWjonmason: Sure!20:36
jonmasonkhem: my new hire has told me how much he LOVES binary toolchains.  And I'm going to see if I can get him to work on them exclusively20:37
khemthats great to hear20:37
khemI think I understand from ARMs POV they just build one toolchain once and solve all sort of usecases20:38
JPEWjonmason: I don't see the commits in the meta-arm git tree yet for me to rebase on top of20:39
khemhe said to rebase on top of his HEAD :)20:40
jonmasonI pushed it like 10 mins ago20:40
JPEWjonmason: The 2.3 upgrade?20:40
jonmasonweird, not showing up20:40
*** KindOne <KindOne!kindone@freenode/father-christmas/kindone> has joined #yocto20:41
jonmasonok, I'm stupid.  Fixed now20:42
*** feddischson <feddischson!~feddischs@HSI-KBW-095-208-248-064.hsi5.kabel-badenwuerttemberg.de> has quit IRC20:43
*** vineela <vineela!~vtummala@134.134.137.73> has joined #yocto20:44
denixjonmason: supporting binary toolchains - you mean external-arm? yeah, just don't break it - it was periodically broken at the old place...20:46
jonmasondenix: I won't break it personally ;-)  So if it works now, then we are gold20:46
denixJPEW: you need multiconfig for aarch64+armv7 builds, right? you can check meta-ti to see how I did it. may not be ideal, but works with binary toolchains like external-arm as well as building both toolcains from sources20:47
JPEWdenix: Cool, I'll take a look20:47
denixJPEW: and as khem said, you can simply pass --freestanding parameter to linux toolchain. I was thinking adding TCLIBC=baremetal to my multiconfigs, but didn't need to20:48
JPEWdenix: Is there an representative recipe that would be good to look at?20:49
denixJPEW: well, our u-boot builds for both cores - cortex-r5f and cortex-a72/53. you can check that single recipe. there's ti-sci-fw that's only for cortex-r5f20:52
denixJPEW: the only remaining issue I have is to package some specific pieces into main rootfs/sdk from other multiconfig targets - i.e. do_deploy works, but I also need do_install20:55
denixJPEW: we disucssed it before - i.e. I need both aarch64 and armv7 toolchains in sdk20:56
denixJPEW: I was following RP's suggestions, but so far no luck20:57
JPEWdenix: Right. So in the u-boot recipe, is it that it can build for either machine, or uses both toolchains at once. I'm not seeing how the later is done in the recipe...?20:57
denixJPEW: either machine - different defconfigs. if you need to build both at the same time using separate toolchains, you'd need to separate them into individual steps/recipes20:58
JPEWdenix: Ah OK! Thats the difference, the ATF for RK3399 isn't set up to build split like that; they just expect to be able to call "arm-none-eabi-gcc"20:59
denixI don't see any other way - they have separate WORKDIR. the only way to "combine" them is via DEPLOYDIR20:59
JPEWdenix: Right21:01
denixJPEW: ^^^ by they I mean multiconfig versions of recipes, even the same recipe - one will be in aarch64 sysroot, the other is in armv7 sysroot21:01
*** dggonz <dggonz!57dbe71d@29.231.219.87.dynamic.jazztel.es> has joined #yocto21:01
dggonzhello21:02
*** dv_ <dv_!~dv@62.178.50.190> has quit IRC21:02
*** behanw <behanw!uid110099@gateway/web/irccloud.com/x-mhleplqgzdvbwkef> has joined #yocto21:03
dggonzI was wondering if you are seeing an strange bug I am experience. When I build an image using a wks.in file I get as a result an image does is non functional because all the files within the image have the uid/gid of the user that was used to build the image, instead of the right ones. if I copy the wks.in to a wks and remove the reference to the21:04
dggonzvariable I am using ${IMAGE_ROOTFS}, do bitbake -c cleanall core-image-minimal and then bitbake -c build core-image-minimal the generated image has the files uid/gid correctly set and it works fine21:04
JPEWdggonz: wic doesn't run under pseudo, so it can't "see" the permissions assigned to files21:05
*** pohly <pohly!~pohly@p5B05600C.dip0.t-ipconnect.de> has quit IRC21:05
JPEWdggonz: At least AFAIK21:05
kergothwic has its own understanding of the rootfs, you shouldn't be poking at IMAGE_ROOTFS Directly, afaik..21:06
dggonzok, let me explain what I was trying to solve, maybe there is another way around21:06
dggonzI have a directory which I want to place in a different partition so I am doing:21:06
dggonz--exclude-path=etc/certs/ on the rootfs21:07
dggonzand then in the partition I am trying to generate:21:07
dggonzpart /etc/certs --source rootfs --rootfs-dir=${IMAGE_ROOTFS}/etc/certs --ondisk mmbclk0 --fstype=ext4 --label certs   --align 1024 --fixed-size 10M21:07
dggonzthe actual files are there, but all the uid/gid are messed up on the resulting image21:08
dggonznot just those of the /etc/certs partition21:08
dggonzthis is the actual rootfs partition line for reference:21:08
dggonzpart /     --source rootfs                                        --ondisk mmcblk0 --fstype=ext4 --label rootfsA --align 1024 --fixed-size 370M --exclude-path=etc/certs/21:08
*** leon-anavi <leon-anavi!~Leon@78.130.197.211> has quit IRC21:09
JPEWjonmason: Patches sent. Works for me on RK3399 \o/21:12
jonmasonJPEW: thanks.  Building now, while I walk the dog21:16
*** berton <berton!~berton@181.220.84.90> has quit IRC21:16
*** dv_ <dv_!~dv@62-178-50-190.cable.dynamic.surfer.at> has joined #yocto21:16
RPdenix: the other approach might be to build the sdks separately, then have one target in the multiconfig which merges them together.  You may need to teach the SDK code to generate an intermediate output you can merge21:16
*** dggonz <dggonz!57dbe71d@29.231.219.87.dynamic.jazztel.es> has quit IRC21:18
* JPEW kinda wishes "-9n" was the default for gzip21:20
*** Spock_ncc1701 <Spock_ncc1701!~Spock_ncc@45.56.150.108> has joined #yocto21:30
denixRP: ok, I guess I can try merging separate sdks...21:31
*** dreyna_ <dreyna_!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto21:32
*** dreyna <dreyna!~dreyna@2601:646:4201:b1a0:d84c:c0c4:a716:ddf9> has quit IRC21:36
*** rburton <rburton!~rburton@192.198.151.44> has quit IRC21:40
*** rob_w_ <rob_w_!~rob@ppp-93-104-34-197.dynamic.mnet-online.de> has quit IRC21:41
*** jae1 <jae1!~jaewon@c-73-162-13-38.hsd1.ca.comcast.net> has joined #yocto21:42
*** Bunio_FH <Bunio_FH!~bunio@81-18-201-214.static.chello.pl> has quit IRC21:43
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has joined #yocto21:57
*** Jockum_ <Jockum_!~Jockum@h-37-123-162-113.NA.cust.bahnhof.se> has joined #yocto22:09
RPkhem: https://autobuilder.yoctoproject.org/typhoon/#/builders/89/builds/1895 has failures in step1b :(22:11
RPJPEW: ^^^22:11
*** Jockum <Jockum!~Jockum@h-37-123-162-113.NA.cust.bahnhof.se> has quit IRC22:12
*** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has quit IRC22:14
*** Spock_ncc1701 <Spock_ncc1701!~Spock_ncc@45.56.150.108> has quit IRC22:20
*** edgar444 <edgar444!uid214381@gateway/web/irccloud.com/x-hrlyqiazvybufyzj> has quit IRC22:22
*** woutervh <woutervh!~woutervh@188.189.112.146> has quit IRC22:25
*** vineela <vineela!~vtummala@134.134.137.73> has quit IRC22:28
*** jae1 <jae1!~jaewon@c-73-162-13-38.hsd1.ca.comcast.net> has quit IRC22:28
*** qschulz <qschulz!~quentin@ns326003.ip-37-187-106.eu> has quit IRC22:32
*** qschulz <qschulz!~quentin@ns326003.ip-37-187-106.eu> has joined #yocto22:34
*** geheimnis` <geheimnis`!~geheimnis@23.226.237.192> has quit IRC22:45
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@198.145.29.62> has quit IRC22:49
*** vineela <vineela!~vtummala@134.134.137.73> has joined #yocto22:49
*** geheimnis` <geheimnis`!~geheimnis@23.226.237.192> has joined #yocto22:50
*** agust <agust!~agust@pD95F11D0.dip0.t-ipconnect.de> has quit IRC22:52
*** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has joined #yocto22:54
khemRP:these are new errors glib-2.64.2/glib/gstrfuncs.c:477:10: error: implicit declaration of function 'stpcpy' [-Werror=implicit-function-declaration]23:02
khemglib-2.64.2/glib/gslice.c:1411:9: error: implicit declaration of function 'posix_memalign' [-Werror=implicit-function-declaration]23:02
khem../wayland-1.18.0/src/scanner.c:995:4: warning: incompatible implicit declaration of built-in function 'strndup'23:04
khemso I guess we can fix it at package level23:05
*** vineela <vineela!~vtummala@134.134.137.73> has quit IRC23:12
khemRP: send a backport to fix glib-2.0 issue23:20
khemlooking into wayland23:20
khemall meson regressions it seems23:25
*** ericch <ericch!~ericch@pool-108-34-251-214.prvdri.fios.verizon.net> has quit IRC23:25
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has quit IRC23:34
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@mob-176-243-9-254.net.vodafone.it> has joined #yocto23:35
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has joined #yocto23:35
khemRP: sent one for wayland too, have fun23:46

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