Friday, 2020-01-17

*** agust <agust!> has quit IRC00:11
*** ericch <ericch!> has quit IRC00:30
*** palate <palate!~palate@unaffiliated/palate> has quit IRC00:32
*** inf <inf!~informati@unaffiliated/informatic> has quit IRC00:33
*** inf <inf!~informati@unaffiliated/informatic> has joined #yocto00:34
*** PinkSnake <PinkSnake!51ff1123@> has quit IRC00:40
*** Ad0 <Ad0!~Ad0@> has quit IRC00:42
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has quit IRC00:43
*** Ad0 <Ad0!~Ad0@> has joined #yocto00:48
*** linuxjacques <linuxjacques!~jacques@nslu2-linux/jacques> has quit IRC01:01
*** sgw <sgw!sgw@nat/intel/x-txsilneduvvrrsqv> has joined #yocto02:15
*** vquicksilver <vquicksilver!~nobody@gentoo/contributor/vquicksilver> has quit IRC02:31
*** vquicksilver <vquicksilver!~nobody@gentoo/contributor/vquicksilver> has joined #yocto02:34
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto02:54
*** RP <RP!> has quit IRC02:56
*** clopez <clopez!> has quit IRC02:56
*** RP <RP!> has joined #yocto02:56
*** psrcode_ <psrcode_!~psrcode@> has quit IRC02:57
*** clopez <clopez!> has joined #yocto02:57
*** psrcode <psrcode!~psrcode@> has joined #yocto02:57
*** Yatekii <Yatekii!> has quit IRC02:57
*** khem <khem!~khem@unaffiliated/khem> has quit IRC03:02
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto03:07
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC03:16
*** learningc <learningc!~pi@> has quit IRC04:10
*** learningc <learningc!~pi@> has joined #yocto04:12
*** georgem <georgem!~georgem@> has quit IRC05:20
*** georgem <georgem!~georgem@> has joined #yocto05:22
*** fancer <fancer!fancer@gateway/web/> has quit IRC05:33
*** fancer <fancer!fancer@gateway/web/> has joined #yocto05:33
*** ndec <ndec!sid219321@linaro/ndec> has quit IRC05:34
*** ndec <ndec!sid219321@linaro/ndec> has joined #yocto05:34
*** comptroller <comptroller!> has quit IRC05:55
*** comptroller <comptroller!> has joined #yocto06:09
*** sgw <sgw!sgw@nat/intel/x-txsilneduvvrrsqv> has quit IRC06:12
*** ThomasD13 <ThomasD13!> has joined #yocto06:28
*** sgw <sgw!~sgw@> has joined #yocto06:30
*** stuom1 <stuom1!3eecd81d@> has joined #yocto06:37
*** AndersD <AndersD!> has joined #yocto06:48
*** pohly <pohly!> has joined #yocto06:49
*** denix0 <denix0!> has joined #yocto07:11
*** palate <palate!~palate@unaffiliated/palate> has joined #yocto07:13
*** mckoan_ <mckoan_!~marco@unaffiliated/mckoan> has joined #yocto07:13
*** geheimni1` <geheimni1`!~geheimnis@> has joined #yocto07:13
*** georgem <georgem!~georgem@> has quit IRC07:18
*** compenguy <compenguy!> has quit IRC07:18
*** roussinm <roussinm!> has quit IRC07:18
*** marka <marka!> has quit IRC07:18
*** davisr <davisr!> has quit IRC07:18
*** ecclescake <ecclescake!~tomeccles@> has quit IRC07:18
*** mckoan|away <mckoan|away!~marco@unaffiliated/mckoan> has quit IRC07:18
*** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has quit IRC07:18
*** champagneg <champagneg!> has quit IRC07:19
*** milloni <milloni!> has quit IRC07:19
*** seebs <seebs!~seebs@> has quit IRC07:19
*** nemik <nemik!> has quit IRC07:19
*** opello <opello!~opello@about/csharp/regular/opello> has quit IRC07:19
*** aehs29 <aehs29!~aehs29@> has quit IRC07:19
*** denix <denix!> has quit IRC07:19
*** u1106 <u1106!> has quit IRC07:19
*** sashko <sashko!~sashko@> has quit IRC07:19
*** lpoulain <lpoulain!lpoulain@gateway/shell/linaro/x-uzrjrouuhlmnvppc> has quit IRC07:19
*** geheimnis` <geheimnis`!~geheimnis@> has quit IRC07:19
*** jhar <jhar!> has quit IRC07:19
*** meow` <meow`!> has quit IRC07:19
*** jwessel <jwessel!~jwessel@> has quit IRC07:19
*** dStruct <dStruct!~matt@unaffiliated/dstruct> has quit IRC07:19
*** ilbelkyr <ilbelkyr!ilbelkyr@freenode/staff/atheme.ilbelkyr> has quit IRC07:19
*** denix0 is now known as denix07:19
*** geheimni1` is now known as geheimnis`07:19
*** TobSnyder <TobSnyder!> has joined #yocto07:22
stuom1Any ideas why on another computer I get during do_compile "/bin/bash: ./start: cannot execute binary file: Exec format error" and on another everything works?07:22
khemperhaps start is a binary for different machine07:24
*** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has joined #yocto07:24
khemwhat does it show if you run `file ./start` cmd07:25
stuom1it is compiled by the recipe and supposedly we have same host environments and working on same code07:25
stuom1i mean it is compiled by the toolchain of that program that the recipe is baking07:26
stuom1i dont have that file, probably it gets removed when everything is done07:27
khemok yocto does cross build so technically running the generated program on build host is not right and if it worked it was pure luck07:27
stuom1if it says "/bin/bash" it means it runs on host? How should it say if it was correct?07:30
*** agust <agust!> has joined #yocto07:38
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto07:47
*** mckoan_ is now known as mckoan07:50
*** jmiehe <jmiehe!> has joined #yocto07:54
*** guerinoni <guerinoni!> has joined #yocto07:57
stuom1how can I change autotools based recipe that it would stop searching for .so files in my host /lib and look instead from recipe sysroot08:00
*** AndersD <AndersD!> has quit IRC08:00
LetoThe2ndstuom1: probably by looking at and, there might be somthing hardcoded.08:00
*** georgem <georgem!~georgem@> has joined #yocto08:05
*** compenguy <compenguy!> has joined #yocto08:05
*** roussinm <roussinm!> has joined #yocto08:05
*** davisr <davisr!> has joined #yocto08:05
*** ecclescake <ecclescake!~tomeccles@> has joined #yocto08:05
*** champagneg <champagneg!> has joined #yocto08:05
*** jwessel <jwessel!~jwessel@> has joined #yocto08:05
*** milloni <milloni!> has joined #yocto08:05
*** seebs <seebs!~seebs@> has joined #yocto08:05
*** nemik <nemik!> has joined #yocto08:05
*** opello <opello!~opello@about/csharp/regular/opello> has joined #yocto08:05
*** aehs29 <aehs29!~aehs29@> has joined #yocto08:05
*** u1106 <u1106!> has joined #yocto08:05
*** sashko <sashko!~sashko@> has joined #yocto08:05
*** lpoulain <lpoulain!lpoulain@gateway/shell/linaro/x-uzrjrouuhlmnvppc> has joined #yocto08:05
*** jhar <jhar!> has joined #yocto08:05
*** meow` <meow`!> has joined #yocto08:05
*** dStruct <dStruct!~matt@unaffiliated/dstruct> has joined #yocto08:05
*** ilbelkyr <ilbelkyr!ilbelkyr@freenode/staff/atheme.ilbelkyr> has joined #yocto08:05
*** kamel_b <kamel_b!> has quit IRC08:08
*** kamel_b <kamel_b!> has joined #yocto08:08
*** thaytan <thaytan!> has quit IRC08:09
*** thaytan <thaytan!> has joined #yocto08:11
*** yann|work <yann|work!> has quit IRC08:26
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has quit IRC08:30
*** ifan <ifan!> has joined #yocto08:37
*** Bunio_FH <Bunio_FH!> has joined #yocto08:42
*** lfa_ <lfa_!~lfa@> has quit IRC08:59
*** karasz <karasz!> has quit IRC09:02
stuom1"QA Issua: package contains bad RPATH" when I added -rpath to LDFLAGS, what is this?09:07
stuom1(path exists, so at least that is not bad...)09:08
LetoThe2ndprobably bad means "host contaminated" in this context, but just guessing.09:08
*** guerinoni <guerinoni!> has quit IRC09:13
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto09:15
*** guerinoni <guerinoni!> has joined #yocto09:15
*** yann|work <yann|work!~yann@> has joined #yocto09:18
stuom1the build system was looking for my .so files on host, so I changed rpath to look them from sysroot, where they actually are09:19
stuom1but now that is wrong too *cries*09:19
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC09:20
stuom1but at least compilation succeeds now, so maybe that's something09:20
LetoThe2ndstuom1: why is it even manually looking for things, instead of relying on pkg-config respectively the known good cross compile aware build system facilites?09:20
stuom1i dont know how to answer that question, but it is using autotools and the package has not been designed to be cross-compiled, it seems09:22
LetoThe2ndso the proper approach is actually fixing the the package instead of doing obscure dances in the recipe.09:26
stuom1I have already successfully cross-compiled it by  copy-pasting the .so files to my host where it looks them from, but that's ugly09:27
stuom1now i got it too look from correct place but i get this QA error09:28
LetoThe2ndthats not ugly, thats stupid09:28
LetoThe2ndbecause: totally non-reproductible, you won't be able to even rebuild it yourself 3 weeks from now09:28
stuom1hence my efforts to fix it now :D09:28
LetoThe2ndgo fix stuff instead of throwing bandaids.09:29
LetoThe2ndbut the place to fix it is the library lookup mechanisms in the build system (you said autotools), not the recipe09:29
stuom1does it matter if i change LDFLAGS in recipe or in configure/makefile09:30
LetoThe2ndof course it does09:30
LetoThe2nd"fix" in recipe means: "this package does stupid stuff but i'd rather work around it instead of setting it straight"09:31
LetoThe2ndfix in package means: "i properly handled this"09:31
stuom1i dont have time to start developing someone else's stuff now, just need to get it work :D09:32
LetoThe2ndthe only exception is if you don't have access to the package,  but in this case it would still be better to carry it as patch next to the recipe, instead of doing tricks inside09:32
LetoThe2ndstuom1: i have heard that "reasoning" very often by now, here. fact: you will burn more time by "making it work"09:33
LetoThe2ndbut hey, go ahead. its your project.09:33
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto09:33
LetoThe2nd(hint: "i can compile this here" != "it works")09:34
stuom1well the end product on target works also09:36
qschulzstuom1: "works on my machine" © is the first page of all horror tales09:38
qschulzstuom1: it is actually not uncommon to patch makefiles, autotools, etc..09:39
qschulzBy doing so, you expand your knowledge in the build system and learn a bit more about the project. In the end it's your call, but that's what we strongly advise09:39
LetoThe2ndi refuse to call anything "working" which cannot be reproduced completely by kicking off a single line on an otherwise unprepared build system. (e.g. is CI-clean)09:39
stuom1I've already patched to and sure, I can add this LDFLAGS there too but I still the the QA issue09:40
LetoThe2ndstuom1: again, i don't think the LDFLAGS per se are the problem. its the mechanisms used to obtain them.09:42
*** florian_kc is now known as florian09:47
stuom1I added --enable-new-dtags to my -rpath and now QA errors are gone09:48
stuom1I dont know, if everything works, seems clean enough solution to me :D09:49
qschulzstuom1: When fixing the consequences and not the cause, you're just setting a timer on a bomb. Or in another word, hiding the dirt under the carpet :)09:51
LetoThe2nd*shrug* go ahead.09:51
qschulz*in other words*. TGIF.09:53
* LetoThe2nd needs to prepare the next live coding session. meh.09:54
stuom1i will come to your twitch chat to give great rpath suggestions to people Kappa09:55
LetoThe2ndgo ahead :)09:55
RPFor those not around last night, I'd like to try and collect together a list of companies/products/projects using Yocto. I'm doing that on the wiki here:
RPAny help appreciated (its a wiki!)09:58
LetoThe2ndRP: yeah you seem to have a strange rhythm these days :)09:59
RPLetoThe2nd: ?10:00
LetoThe2ndRP: at least for my employer speaking: its no secret that we are involved, obviously, but we do not want it publicly listed in such a form. sorry.10:00
LetoThe2ndRP: (you do stuff late at night, thats at least my impression)10:00
RPLetoThe2nd: ah, yes, I do :/10:00
RPLetoThe2nd: np, I appreciate some can't be listed. I'd just like to list the ones we can10:01
LetoThe2ndRP: its a common problem im industry-focused OSS projects.10:02
stuom1i also cannot tell after all the hacks I've admitted using, at least LetoThe2nd would never buy from us again10:03
RPRemember the challenge is that if we can't show anyone using the project, it makes it hard to justify its existence or why others should support it10:04
LetoThe2ndstuom1: nah, thats not the problem. actually its a good way of showing yourself if you are selling boards with yocto support10:05
LetoThe2nd(and yes, despite my clear words here, i am very well aware of the fact that hacks are an unavoidable way of real life)10:06
*** stuom153 <stuom153!3eecd81d@> has joined #yocto10:06
LetoThe2ndRP: you can happily list me as public enthusiast, volunteer supporter, jester, whatever. :)10:06
LetoThe2ndas live coder for hire, weirdo trainer, whatever suits your politics. i just cannot allow "company x is using yocto"10:07
RPLetoThe2nd: I think we have that one covered :)10:09
RPLetoThe2nd: Anyhow, as I said, lets see if we can collect the ones we actually can as there are some10:09
LetoThe2ndRP: just making the offers i can :)10:09
*** stuom1 <stuom1!3eecd81d@> has quit IRC10:10
*** stuom153 is now known as stuom110:11
qschulzRP: dumb question but isn't it a good start to grep for mails of contributors? I'm sure at least a decent amount of people use their profesionnal mail address to contribute?10:17
qschulzRP: each release of the linux kernel, there's a top 20 of companies contributing and individuals that's being created by some online media.10:18
*** tprrt <tprrt!~tprrt@> has joined #yocto10:18
LetoThe2ndqschulz: but usually those are asked before things being published. and for bigger contributing companies, its 1) obvious anyways 2) i'm pretty sure greg k-h has a mail from their legal somewhere saying "its ok that we're named"10:21
RPqschulz: Yes, I do have such a list. Its hard to tell if that does mean the company really uses it or is just experimenting10:22
RPqschulz: we may get to that eventually, we'll see10:22
qschulzLetoThe2nd: well, it is public anyway. Don't say it's used by this company but that company contributes to it. I actually  think that might encourage company to contribute? But a mix of both lists could be nice.10:26
LetoThe2ndqschulz: the different is between "can be found out by somebody who invests some time and thought" and "is advertised on the front page"10:27
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC10:30
qschulzLetoThe2nd: I understand. Legally I guess it depends of the country? If I'm not mistaken, e.g. in France, it's fine to take pictures of people in the streets if they are not the main object of the picture (e.g. crowd photo, landmark photo, etc.) and publish them without explicit consent.10:31
qschulzLetoThe2nd: but lawyer stuff :)10:31
qschulz(and I'm not sure we want to scare potential contributing companies out of the project)10:31
yoctiNew news from stackoverflow: Yocto Image file size reduces after adding a particular package <>10:34
*** warthog9 <warthog9!> has quit IRC10:53
*** warthog9 <warthog9!> has joined #yocto10:58
*** rburton <rburton!> has joined #yocto11:12
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC11:12
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto11:13
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto11:15
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC11:20
*** ThomasD13 <ThomasD13!> has quit IRC11:20
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto11:20
*** berton <berton!~berton@> has joined #yocto11:42
*** berton <berton!~berton@> has quit IRC11:50
*** berton <berton!~berton@> has joined #yocto12:02
*** warthog9 <warthog9!> has quit IRC12:10
*** tgamblin <tgamblin!> has quit IRC12:11
stuom1how can I change MACHINE type in image recipe? setting MACHINE = "xxx" doesnt seem to work12:11
LetoThe2ndstuom1: you cannot. simple as is.12:11
stuom1alright, what would be best way to make another image for qemuarm?12:12
stuom1I want to make 2 same images, one for target and one for qemu12:13
LetoThe2ndthen you need two builds.12:14
LetoThe2ndyou can semi-automate it with a multiconfig build, but under the its just like this: 2 seperate builds.12:14
LetoThe2ndor set the buld off with 'MACHINE=xyz bitbake myimage && MACHINE=qemuarm bitbake myimage' - yet thats all just variations.12:15
stuom1ok, that seems good, thanks!12:17
*** rangergord_ <rangergord_!> has joined #yocto12:57
*** rangergord <rangergord!> has quit IRC13:00
*** radsquirrel <radsquirrel!> has quit IRC13:02
*** radsquirrel <radsquirrel!> has joined #yocto13:02
ifanHi, I'm trying to move an old kernel to a newer yocto version, I can build it with these modifications to the recipe But each time i re-build it I get the following error : imx6qsabresd/kernel-source is not clean, please run 'make mrproper' (even if i run -c clean -c cleanssate) If i do what it says(run mrproper) it13:10
ifanruns but I still think something is wrong in my configuration, thx13:10
LetoThe2ndifan: that just looks outright wrong.13:11
LetoThe2ndyocto has built-in support for the handling of defconfigs13:12
ifanLetoThe2nd: you mean the entire function?13:13
LetoThe2ndifan: yup13:13
qschulzifan: there's already a defconfig in the kernel. You just have to tell the linux-yocto recipe  (assuming that's what you mean with "a newer yocto version)"13:13
*** Linus_SWE <Linus_SWE!51d83be2@gateway/web/cgi-irc/> has quit IRC13:14
ifanLetoThe2nd: both and linux-fslc-imx have those13:14
qschulzifan: vendor BSP is not a good reference most of the time :)13:14
ifanLetThe2nd: I just changed it so it could work with a newer version, I can try remove it and see what happens13:15
LetoThe2ndifan: if you want to supply your own defconfig, it should be passed in through SRC_URI and then it can be used automagically. if you want to use an in-tree defconfig, listen to qschulz13:15
LetoThe2ndifan: and i hope you're not actually investing time in a 3.14 kernel13:15
ifan:LetoThe2nd its a long story :)13:15
LetoThe2ndifan: 3.14 won't even build with anything newer than probably krogoth, unless you apply black magic13:16
LetoThe2ndand if you can do that, then you don't need our help anyways.13:16
*** tgamblin <tgamblin!~tgamblin@> has joined #yocto13:16
LetoThe2ndthe task is buggy anyways, as the defconfigs should be expanded, not copied.13:17
ifanLetoThe2nd: I'm trying to move to krogoth, once I got that working I will try to apply the board specific files. If i can get that to work I will try to move it to a newer kernel13:18
*** fg_ <fg_!> has joined #yocto13:18
LetoThe2ndthat sounds very confused.13:19
LetoThe2ndfrom *where* are you coming?13:19
ifanIt's hard to explain since I dont really understand what I'm doing :)13:20
LetoThe2ndthen you should maybe stop investing time to hack ancient software into ancient build systems and rather try to understand what you're doing :)13:21
*** guerinoni <guerinoni!> has quit IRC13:21
ifanThe manufacturer make u-boot and kernel for 3.14.28, I want to include their stuff into Yocto and then upgrade everything13:21
ifanif that makes sense, but first i wanted to try build the kernel for a standard machine13:22
LetoThe2ndwill not work13:22
ifanintegrating or upgrading?13:22
qschulzifan: FYI, I was HORRIFIED that we were still using krogoth a few months ago. Now we're on thud and hopefully I can push a little bit for newer releases. But upgrading or supporting krogoth now is non-sense especially with all the CVEs being patched since then.13:22
qschulzifan: wait a second, on which SoC is your board based?13:23
qschulzbecause imx SoC are very well supported upstream13:23
LetoThe2ndifan: u-boot, kernel and gcc and somewhat tied together. so once you got all building in krogoth, you can feel proud for 10 minutes, and then throw way everything just to start anew on a recent release.13:23
LetoThe2ndifan: the imx6 support in upstream is extremely good, so chances are that (unless you vendor gave you the utmost crappy hw), you will be able to boot surrent mainly with no more than just a custom device tree.13:24
LetoThe2ndand for just getting booted, probably not even a custom dt is needed.13:25
LetoThe2ndimx sabre support seems to be absolutely up to date:
LetoThe2ndifan: even more so:
ifanSo I should drop everything I'm doing and get on a newer branch13:27
qschulzifan: imx6 is really well supported since a a few releases (I had to bootstrap one on 4.14 like two years ago, didn't ask much more than that)13:28
LetoThe2ndifan: if i'm not totally mistaken, the file i just linked to says basically that imx6qsabresd is officially supported in the current meta-freescale layer. no ancient crap involved.13:28
ifanI am SO thankful for this information guys13:29
LetoThe2ndifan: so, many hours did we just save you? where can we send our invoice?13:29
LetoThe2ndqschulz: 50/50, mkay?13:29
ifanno more looking in mail threads from 2014 :]13:29
qschulzLetoThe2nd: HALF A BEER?13:29
LetoThe2ndqschulz: depends on the size of the beer.13:29
ifanprobably a few months13:30
qschulzifan: what's your board? custom?13:30
ifanIts from a company named Avalue, ACP-IMX613:33
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC13:33
zeddiiRP: I just finished all my local testing on 5.4, if I sent some builds to the AB, would that cause issues with higher priority builds ?13:35
fullstopsweet, "Cash Drawer interface (RJ11)"13:35
yoctiNew news from stackoverflow: Debug symbols not stripped from resulting binaries in Yocto <>13:35
*** andycooper is now known as andycooper_home13:35
LetoThe2ndifan: seriously, their manual is popcorn gold.13:35
fullstopalso, "OS Information: Yocto 1.5.1"13:35
LetoThe2ndwe support building on 12.04. do: git clone guest@ -b 4.4.2-pos13:36
fullstopI do like the DAC, though, I love Wolfson stuff.13:36
LetoThe2ndanyways, probably just a classic sabre with minor dt adjustments.13:36
ifannot sure I understand what popcorn gold means13:36
ifanbut don you guys trashtalk my board :<13:36
RPzeddii: no problem with other builds, we're quiet atm. We do have the maintenance window in around 5 hours though13:37
LetoThe2ndifan: why not? :P13:37
ifanshe is a beauty ;)13:38
LetoThe2nd"git checkout from this magic ip, pw right next to it in the pdf" is not exactly confidence inspiring :)13:38
zeddiiRP: ok. cool. Will try one before that, and then some after. I have to get a bit organized on the branch to push and do some version overrides (since I'm doing them in local.conf here).13:38
LetoThe2ndanyways, happy weekend everybody!13:38
ifanand thanks again13:39
fullstopYeah, she's a worthy POS....system.  ;-)  Point of Sale being abbreviated POS always amused me, though.13:39
zeddiiBut I did extra testing on this one. All arches + two c-libraries for all of sato,minimal and kernel-dev. I *know* that systemtap won't get me this time :D13:39
RPzeddii: :D13:39
fullstopHave a good weekend, LetoThe2nd.13:39
qschulzLetoThe2nd: o/13:40
qschulzifan: yeah it shouldn't be too hard, try to find something based on imx6qdl.dtsi or imx6q.dtsi. Apparently ift's a Micrel KSZ9031 for the Ethernet PHY, that's supported upstream. You even have upstream support for the GPU. Honestly, it might be even worth spending a few weeks/months or consulting bucks on using upstream kernel directly.13:42
qschulzifan: I would follow LetoThe2nd 's advice by starting from a board which isn't toofar in specs. Then most likely some different pinmuxing, clocks, etc. But nothing unfixable13:43
qschulz(and by upstream support for the GPU I mean actual OSS driver)13:45
ifanqshulz: I will try that, thank you very much for all the info :>13:49
*** learningc <learningc!~pi@> has quit IRC13:50
stuom1LetoThe2nd informed me it's possible to build another image by "MACHINE="qemuarm" bitbake myimage". This works, but I also want to add DISTRO= variable there but that doesnt work anymore. It only takes one variable and disregards the second13:56
*** kreyren[m] <kreyren[m]!~kreyrenm]> has quit IRC13:57
*** kreyren[m] <kreyren[m]!~kreyrenm]> has joined #yocto13:57
stuom1Is there some special way to do it with bitbake? Normally (outside bitbaking) you can put as many environment variables as you want13:57
*** wooosaiiii <wooosaiiii!> has quit IRC13:59
*** ericch <ericch!> has joined #yocto13:59
*** grma <grma!~gruberm@> has joined #yocto14:00
qschulzstuom1: that should work actually I think14:00
qschulzCan you give use the line your using?14:00
stuom1MACHINE="qemuarm" DISTRO="tdx-xwayland" bitbake myimage14:01
stuom1but distro doesnt change. If I put just DISTRO, it works14:01
qschulzstuom1: interesting for sure. Well usually the DISTRO ?= is set in conf/local.conf.14:05
stuom1yes i probably need to setup some multiconfig as Leto suggested but this was just for trying now fast14:05
qschulzstuom1: you can try do debug this thing by running MACHINE="qemuarm" DISTRO="tdx-xwayland" bitbake myimage -e | less and check for a line starting with DISTRO=. Then you look up and you'll see what's overriding what or setting the variable to some value14:06
stuom1ok, future me will handle all this on Monday14:09
stuom1bitbake is now busy and doesnt let me try anything :P14:10
qschulzstuom1: you can have two instances running if you copy paste your dev environment somewhere else :)14:12
*** learningc <learningc!~pi@> has joined #yocto14:12
frosteyesIs it common to use yocto-check-layer?14:16
stuom1I need to consider that but I rarely bake something that takes so long I cannot wait14:16
rburtonstuom1: $ ls -d build-*|wc -l14:17
rburtonjust remember to set tmpdir to something different :)14:17
stuom1you have 13 build environments?14:21
stuom1quite a collector14:21
rburtonsome are just alternative configurations like "with musl" or "with mingw sdk", others are just identical configurations for parallel builds14:22
frosteyesthe reason I ask is that meta-virtualization, which I guess is a pretty common layer, is returning som issues. (Nothing provide ostree for
frosteyesAnd when running on arm64 - nothing provide syslinux for
*** PaowZ <PaowZ!~Vince@> has joined #yocto14:25
rburtonfrosteyes: former sounds like a missing layer dependency. ostree is in meta-oe14:25
frosteyesStill running in 2.6, so it might be an old issue.14:27
rburtonthe syslinux thing is fair: syslinux only works on IA, so a dependency should be conditional on architecture14:27
frosteyesI think so to.14:27
frosteyesSo it was more of a "hey, yes yocto-check-layer should be used, and it is just a matter of being better to use it"  or more of. It is not very used, so don't expect it to work..14:28
rburtona mainstream layer that doesn't pass check-layer should be fixed, yes14:29
*** georgem <georgem!~georgem@> has quit IRC14:32
*** georgem <georgem!~georgem@> has joined #yocto14:33
*** stuom1 <stuom1!3eecd81d@> has quit IRC14:34
*** TobSnyder <TobSnyder!> has quit IRC14:40
*** lh_ <lh_!sid77898@osuosl/staff/lh> has joined #yocto14:47
*** lh_ is now known as lh14:48
*** goliath <goliath!> has joined #yocto14:58
*** PaowZ <PaowZ!~Vince@> has quit IRC15:02
*** PaowZ <PaowZ!~Vince@> has joined #yocto15:03
qschulzhalstead: hi, just here to report two things uses weak encryption according to FF: Broken Encryption (TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, 256 bit keys, TLS 1.0)15:05
qschulzhalstead: I don't know if it's your "job" or not but "Also, your password will be e-mailed to you when your account is created. " I hope not :) I guess we are talking about a temporary password and that we are not being sent our password plaintext :)15:06
qschulzBTW, I registered with my personal mail and not company one on the wiki, so no worries if the name is noit matching the email address you usually receive mails from on the ML :) (to anyone accepting/refusing wiki users)15:07
*** kpo <kpo!> has quit IRC15:14
*** kriive <kriive!~kriive@> has joined #yocto15:14
kriiveHi everyone! Should I put every custom configuration (e.g. nginx site configuration) in a separate layer?15:16
qschulzkriive: separate from what?15:16
kriiveIn case of nginx I can't put the conf in the same layer (because I don't control the repo), but in case of a package (or a number of them) of mine that requires a configuration, should I put configs in a separate layer (i.e. different from the layers containing the recipi that compiles and installs the actual binary)?15:19
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto15:20
kriiveSorry for not being too clear, I'm still learning it and many concepts are a little foggy15:21
qschulzkriive: if it's related to some distro configuration, then I'd say a layer for the distro maybe? Otherwise, I'd say it's fine to put the conf in your layer I guess. It's foggy to me as well. One layer for the BSP support and one for everything else is usually what I see/think15:23
*** comptroller <comptroller!> has quit IRC15:31
*** jmiehe <jmiehe!> has quit IRC15:34
*** berton_ <berton_!~berton@> has joined #yocto15:43
*** comptroller <comptroller!~comptroll@> has joined #yocto15:44
*** berton <berton!~berton@> has quit IRC15:45
*** ifan <ifan!> has quit IRC15:58
mckoananyone is experiencing an extremely high memory consumption when building with zeus, particularly the meta-toolchain?16:10
mckoanthat never happened before, so I was wondering why16:12
* mckoan tries reducing BB_NUMBER_THREADS16:13
*** PaowZ <PaowZ!~Vince@> has quit IRC16:19
*** PaowZ <PaowZ!~Vince@> has joined #yocto16:21
*** Bunio_FH <Bunio_FH!> has quit IRC16:23
*** PaowZ <PaowZ!~Vince@> has joined #yocto16:24
*** warthog9 <warthog9!> has joined #yocto16:27
RPmckoan: what is using the memory?16:30
mckoanRP: mainly xz16:31
RPmckoan: right, we're kind of aware it can do this :/16:32
mckoanRP: I have 'only' 16GB16:32
RPmckoan: have a look at XZ_DEFAULTS in bitbake.conf16:34
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto16:34
mckoanRP: and nativesdk-clang16:34
RPmckoan: it depends which xz it is mind, the one in rpm is probably passed parameters through rpmbuild16:35
*** jww <jww!> has joined #yocto16:42
*** berton__ <berton__!~berton@> has joined #yocto16:53
*** berton_ <berton_!~berton@> has quit IRC16:56
*** goliath <goliath!> has quit IRC17:01
*** fg_ <fg_!> has quit IRC17:01
*** hpsy <hpsy!~hpsy@> has quit IRC17:09
*** yann|work <yann|work!~yann@> has quit IRC17:10
RPkhem: finally binutils doing what we need17:13
RPmoto-timo: ^^^17:13
*** kriive <kriive!~kriive@> has quit IRC17:14
khemRP: cool what fix did you choose17:17
khemmckoan: XZ_DEFAULTS = "--threads=n" will limit it17:18
*** rangergord <rangergord!> has joined #yocto17:18
khemwhere n is a number according to your CPU muscle17:18
mckoankhem: thanks, I'll give it a try17:18
khemmckoan: and also install pigz17:19
*** rangergord_ <rangergord_!> has quit IRC17:19
khemclang packaging gets a lot of help with pigz17:19
mckoankhem: pigz is already the newest version (2.4-1)17:20
*** kriive <kriive!> has joined #yocto17:23
RPkhem: doesn't work yet but its progress, failures are later17:26
*** kriive <kriive!> has quit IRC17:28
*** shan1 <shan1!> has joined #yocto17:28
shan1Hi all, I created a Yocto Image for Raspberry PI 3 with RT Linux kernel and created a base image. Everything is fine till I wish to expand the SD Card. When I delete the 2nd partition and create a new one I get a `resource is busy IOCTL` warning and there is no `resize2fs` binary in the image. What is it that I am doing wrong here?17:31
*** ericch <ericch!> has quit IRC17:32
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC17:34
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has quit IRC17:36
RPkhem: now we have buildtools and uninative clashing head on :/17:37
RPkhem: I'll disable uninative since it shouldn't be needed here17:38
*** shan1 <shan1!> has left #yocto17:42
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto17:45
*** Bunio_FH <Bunio_FH!> has joined #yocto17:46
*** hpsy <hpsy!~hpsy@> has joined #yocto17:51
*** falstaff <falstaff!~quassel@> has joined #yocto17:55
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC17:56
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto17:56
*** lucaceresoli <lucaceresoli!> has quit IRC18:00
mckoankhem: far better, completed! Thanks!18:00
RPkhem, moto-timo: mail on the list about what I managed18:03
RPkhem: is the glibc ready to go if it passes?18:03
mckoanhave a nice weekend18:04
*** mckoan is now known as mckoan|away18:05
khemRP: yes and I will send a SRCREV bump once the final 2.31 is released18:05
yoctiNew news from stackoverflow: Manually building a Kernel source from Yocto build <>18:06
khemRP: I want to figure out wider issues18:06
khemif any18:06
khemrather than later18:06
*** WillMiles <WillMiles!> has joined #yocto18:13
RPkhem: sounds wise :)18:14
RPkhem: I don't think my binutils hack is too bad, no worse than our gcc patching really...18:14
* RP -> food18:15
*** hpsy <hpsy!~hpsy@> has quit IRC18:33
*** Dracos-Carazza <Dracos-Carazza!> has quit IRC18:37
khemRP: I think it does address a problem where people are using a distro for wide range of yocto releases18:41
khembut agains containers are cooler :)18:42
khemRP: oe-core does not use PIE/PIC by default that unveiled the issue in prelink that happened yesterday18:43
khemI am glad that there was a test on AB to catch it18:43
*** tprrt <tprrt!~tprrt@> has quit IRC18:50
*** Dracos-Carazza <Dracos-Carazza!> has joined #yocto18:50
*** yann|work <yann|work!> has joined #yocto18:52
RPkhem: containers are cooler, this fixes the autobuilder challenge though18:54
RPkhem: we should probably create a specific test case for that18:54
Crofton|roadContainers are the shiney new thing!19:02
*** Dracos-Carazza <Dracos-Carazza!> has quit IRC19:04
*** Dracos-Carazza <Dracos-Carazza!> has joined #yocto19:05
khemCrofton|road: actually crates are even shinier :)19:06
khemoh this python2 removal needs to be in meta-py2 before its gone from core,19:07
* khem rebases it out of yoe/mut19:08
*** AndersD <AndersD!> has joined #yocto19:08
*** Dracos-Carazza <Dracos-Carazza!> has quit IRC19:16
rburtonkhem: ha, yes, i haven't sent the addition yet19:17
*** Dracos-Carazza <Dracos-Carazza!> has joined #yocto19:21
*** Dracos-Carazza <Dracos-Carazza!> has quit IRC19:30
*** AndersD <AndersD!> has quit IRC19:32
*** Dracos-Carazza <Dracos-Carazza!> has joined #yocto19:33
JaMawhat about the python-* removals which were merged before zeus was released? should they be added to meta-python2?20:00
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC20:06
*** baldgeek <baldgeek!~dan@> has quit IRC20:09
rburtonJaMa: they should have been added to meta-python, so will already be in meta-python220:18
kergothooh, removing python2 from oe-core sounds awesome20:30
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto20:32
*** hpsy <hpsy!~hpsy@> has joined #yocto20:33
yoctiNew news from stackoverflow: Use a yocto layer's recipe or class without inheriting all bbappends <>20:36
khemkergoth: yeah it will be a good PR for 3.1 release as well20:36
*** hpsy <hpsy!~hpsy@> has quit IRC20:39
*** hpsy <hpsy!~hpsy@> has joined #yocto20:40
*** hpsy <hpsy!~hpsy@> has quit IRC20:41
*** goliath <goliath!> has joined #yocto20:48
fullstopCan I do something like file://*.patch;patch=1 as part of a SRC_URI in order for bitbake to pull in all of the patch files (which may be different based on machine) and apply them?21:10
LetoThe2ndfullstop: nope21:11
fullstopHey!  You're supposed to be enjoying your weekend!21:11
fullstopokay.. can I reference SRC_URI as a variable when using overrides?21:13
*** Bunio_FH <Bunio_FH!> has quit IRC21:13
fullstopsomething like SRC_URI_jetson-nano = "${SRC_URI} file://blabblah"21:14
fullstopnope, recursion death21:16
JaMaSRC_URI_append_jetson-nano will do the same without death21:17
fullstopThat's what I was looking for.. _append_21:17
fullstopthanks, JaMa21:17
fullstopThat worked perfectly.21:19
*** tgamblin <tgamblin!~tgamblin@> has quit IRC21:26
*** goliath <goliath!> has quit IRC21:48
*** JaMa <JaMa!~martin@> has quit IRC22:04
*** pohly <pohly!> has quit IRC22:11
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC22:13
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto22:14
RPzeddii: I replied to mail, sorry, it is AB config22:22
armpitzeddii, for $20 he will fix it ; )22:25
*** rburton <rburton!> has quit IRC22:32
RParmpit: er, I'd pay $20 for someone to fix this one! :)22:38
RParmpit: long standing AB issue :/22:38
*** WillMiles <WillMiles!> has quit IRC22:38
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC22:39
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto22:39
*** agust <agust!> has quit IRC22:56
zeddiiahah. thanks23:05
zeddiiI see some other similar error, but most everything seems to be building.23:06
zeddiifingers crossed :D23:06
*** guerinoni <guerinoni!> has joined #yocto23:07
*** goliath <goliath!> has joined #yocto23:08
khemzeddii: I have created a defconfig for ppc64le, is it possible for you to add it to linux-yocto23:13
zeddiiI can use it to create a BSP fragment. sure.23:14
RPzeddii: the other similar errors may be real. Its only step2d of quick itself (or full) that show this23:30
RPzeddii: the clue btw is in its configuration23:37
khemzeddii: ok. I need to first make OpenFirmware understand it and load it properly23:37
RPzeddii: - it sets PREMIRRORS = "" but I don't remember how upstream gets disabled there :/23:39
RPzeddii: oh, its running oe-selftest -r buildoptions.SourceMirroring.test_yocto_source_mirror'23:40
RPzeddii: so not a normal build...23:40
* RP -> Zzz23:40
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC23:48
*** guerinoni <guerinoni!> has quit IRC23:49
*** goliath <goliath!> has quit IRC23:55

Generated by 2.17.2 by Marius Gedminas - find it at!