*** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has joined #yocto | 00:01 | |
*** tgoodwin <tgoodwin!~tgoodwin@pool-100-16-74-100.bltmmd.fios.verizon.net> has quit IRC | 00:06 | |
*** alejandrohs <alejandrohs!~alejandro@cpe-68-201-52-49.elp.res.rr.com> has joined #yocto | 00:29 | |
*** Kyubi <Kyubi!~Kyubi@149.199.62.130> has quit IRC | 01:21 | |
*** Kyubi <Kyubi!~Kyubi@149.199.62.130> has joined #yocto | 01:34 | |
*** camus <camus!~Instantbi@58.246.136.202> has joined #yocto | 01:44 | |
*** kaspter <kaspter!~Instantbi@58.246.136.202> has quit IRC | 01:45 | |
*** camus is now known as kaspter | 01:45 | |
*** manuel_ <manuel_!~manuel198@213-147-161-151.nat.highway.bob.at> has joined #yocto | 02:36 | |
*** manuel__ <manuel__!~manuel198@213-147-161-228.nat.highway.bob.at> has quit IRC | 02:39 | |
Guest87383 | rabbit9911: this means the libgbm.so that you have does not have SONAME encoded in ELF | 02:48 |
---|---|---|
Guest87383 | can you post output of readelf -d libgbm.so ? | 02:48 |
*** tgoodwin <tgoodwin!~tgoodwin@pool-100-16-74-100.bltmmd.fios.verizon.net> has joined #yocto | 03:01 | |
*** kiwi_29 <kiwi_29!~kiwi_29@c-73-231-211-214.hsd1.ca.comcast.net> has joined #yocto | 03:04 | |
rabbit9911 | Guest873383: https://pastebin.com/35ik3tT9 | 03:06 |
rabbit9911 | So you are right it does not have the soname encoded. The way its working is there are a few libraries softlinked to this one libMali.so | 03:10 |
rabbit9911 | All precompiled blobs to me | 03:11 |
*** kiwi_29 <kiwi_29!~kiwi_29@c-73-231-211-214.hsd1.ca.comcast.net> has quit IRC | 03:12 | |
rabbit9911 | But I don't understand why copying libMali.so -> libgbm.so would work but ln -s libMali.so libgbm.so does not. | 03:18 |
*** spooster <spooster!~Spooster@c-68-61-72-182.hsd1.mi.comcast.net> has quit IRC | 03:19 | |
*** spooster <spooster!~Spooster@c-68-61-72-182.hsd1.mi.comcast.net> has joined #yocto | 03:20 | |
Guest87383 | yeah soname is missing | 03:21 |
Guest87383 | so yocto shlibs resolver will be confused because this library can not be found in dependency manager as a result | 03:22 |
*** Guest87383 is now known as khem | 03:22 | |
*** khem <khem!khemmatrix@unaffiliated/khem> has joined #yocto | 03:22 | |
*** khem <khem!khemmatrix@gateway/shell/matrix.org/x-wwmlshtcttjbzkqt> has joined #yocto | 03:22 | |
khem | yeah symlinks are not used as names it will resolve to real .so | 03:23 |
*** Wouter01000 <Wouter01000!~Wouter010@84-80-174-188.fixed.kpn.net> has quit IRC | 03:27 | |
*** mranostaj <mranostaj!~mranostaj@pdpc/supporter/active/mranostay> has quit IRC | 03:37 | |
*** gonkulator <gonkulator!~brandon@75.71.150.20> has quit IRC | 03:52 | |
*** gonkulator <gonkulator!~brandon@75.71.150.20> has joined #yocto | 03:57 | |
*** ahadi <ahadi!~ahadi@88.130.223.220> has quit IRC | 03:58 | |
*** ahadi <ahadi!~ahadi@i59F44C37.versanet.de> has joined #yocto | 04:00 | |
*** gonkulator <gonkulator!~brandon@75.71.150.20> has quit IRC | 04:04 | |
*** sakoman <sakoman!~steve@72.173.249.164> has quit IRC | 04:05 | |
*** gonkulator <gonkulator!~brandon@75.71.150.20> has joined #yocto | 04:10 | |
*** sakoman <sakoman!~steve@72.173.249.164> has joined #yocto | 04:16 | |
*** kaspter <kaspter!~Instantbi@58.246.136.202> has quit IRC | 04:34 | |
*** kaspter <kaspter!~Instantbi@58.246.136.202> has joined #yocto | 04:34 | |
*** mattsm <mattsm!~mattsm@104-181-154-57.lightspeed.austtx.sbcglobal.net> has joined #yocto | 05:05 | |
*** sakoman1 <sakoman1!~steve@72.173.249.164> has joined #yocto | 05:12 | |
*** ByteLawd <ByteLawd!extor@unaffiliated/extor> has quit IRC | 05:13 | |
*** ByteLawd <ByteLawd!extor@unaffiliated/extor> has joined #yocto | 05:13 | |
*** sakoman <sakoman!~steve@72.173.249.164> has quit IRC | 05:15 | |
*** jrdn <jrdn!~jrdn@S010668ff7b6b7383.ok.shawcable.net> has joined #yocto | 05:21 | |
*** sakoman1 <sakoman1!~steve@72.173.249.164> has quit IRC | 05:26 | |
*** alessioigor <alessioigor!~alessioig@93-47-228-8.ip115.fastwebnet.it> has joined #yocto | 05:29 | |
*** alessioigor <alessioigor!~alessioig@93-47-228-8.ip115.fastwebnet.it> has quit IRC | 05:33 | |
rabbit9911 | Okay. It looks like just creating a new *empty) libgm.so (with proper soname) linked against the libmali.so is making yocto happy. | 05:37 |
*** gendevbot <gendevbot!~devbot@176.235.187.234> has quit IRC | 05:37 | |
*** gendevbot <gendevbot!~devbot@176.235.187.234> has joined #yocto | 05:39 | |
*** jobroe <jobroe!~manjaro-u@p579eb60e.dip0.t-ipconnect.de> has joined #yocto | 06:06 | |
*** OutBackDingo_ <OutBackDingo_!~quassel@unaffiliated/outbackdingo> has quit IRC | 06:09 | |
*** kiwi_29 <kiwi_29!~kiwi_29@c-73-231-211-214.hsd1.ca.comcast.net> has joined #yocto | 06:10 | |
*** kiwi_29 <kiwi_29!~kiwi_29@c-73-231-211-214.hsd1.ca.comcast.net> has quit IRC | 06:17 | |
*** gonkulator <gonkulator!~brandon@75.71.150.20> has quit IRC | 06:19 | |
*** jobroe <jobroe!~manjaro-u@p579eb60e.dip0.t-ipconnect.de> has quit IRC | 06:28 | |
*** jobroe <jobroe!~manjaro-u@p579eb60e.dip0.t-ipconnect.de> has joined #yocto | 06:28 | |
*** AndersD <AndersD!~AndersD@h83-209-96-136.cust.a3fiber.se> has joined #yocto | 06:38 | |
*** AndersD_ <AndersD_!~AndersD@h83-209-96-136.cust.a3fiber.se> has joined #yocto | 06:40 | |
*** AndersD <AndersD!~AndersD@h83-209-96-136.cust.a3fiber.se> has quit IRC | 06:42 | |
*** gonkulator <gonkulator!~brandon@75.71.150.20> has joined #yocto | 06:45 | |
*** kaspter <kaspter!~Instantbi@58.246.136.202> has quit IRC | 06:47 | |
*** kaspter <kaspter!~Instantbi@58.246.136.202> has joined #yocto | 06:47 | |
*** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto | 06:49 | |
*** Flurin <Flurin!90027ebc@bbcs-126-188.pub.wingo.ch> has joined #yocto | 06:59 | |
*** w00die_ <w00die_!~w00die@212.91.255.186> has quit IRC | 07:01 | |
*** w00die_ <w00die_!~w00die@212.91.255.186> has joined #yocto | 07:03 | |
*** Flurin is now known as flurin | 07:03 | |
*** felipealmeida <felipealmeida!~felipealm@177.42.48.84> has quit IRC | 07:05 | |
*** spooster <spooster!~Spooster@c-68-61-72-182.hsd1.mi.comcast.net> has quit IRC | 07:06 | |
*** felipealmeida <felipealmeida!~felipealm@177.97.186.118> has joined #yocto | 07:06 | |
*** spooster <spooster!~Spooster@c-68-61-72-182.hsd1.mi.comcast.net> has joined #yocto | 07:06 | |
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto | 07:06 | |
*** agust <agust!~agust@p508b685a.dip0.t-ipconnect.de> has joined #yocto | 07:09 | |
*** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC | 07:28 | |
*** pankaj347 <pankaj347!7ab2fec0@122.178.254.192> has joined #yocto | 07:29 | |
hmw1 | hi i have an external layer that is providing a patch that is already in an other external layer how do i remove one in my layer | 07:29 |
hmw1 | two diverend layers both do a bbappend with the same patchfile | 07:30 |
*** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto | 07:30 | |
*** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC | 07:41 | |
*** thekappe <thekappe!c65a42b1@198.90.66.177> has joined #yocto | 07:41 | |
*** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto | 07:43 | |
thekappe | hello guys ! I've noticed that some recipes build directory are in <machine>-poky-linux and some other ones are in all-poky-linux. Why is this happenning ? how do I put a recipe build dir in <machine>-poky-linux ? Thanks ! | 07:44 |
*** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has joined #yocto | 07:44 | |
abelloni | thekappe: all-poky-linux are for recipes that generate package that are not machine dependent | 07:45 |
abelloni | e.g python scripts | 07:45 |
*** dreyna <dreyna!~dreyna@c-71-202-37-249.hsd1.ca.comcast.net> has quit IRC | 07:50 | |
thekappe | @abelloni, I have a recipe that builds a binary file and since it's related to a specific machine I want that recipe build folder being put in <machine>-poky-linux. How can I do that ? I've added "COMPATIBLE_MACHINE=<machine-name>" but it doesn't work | 07:50 |
*** ahadi <ahadi!~ahadi@i59F44C37.versanet.de> has quit IRC | 07:51 | |
*** gsalazar <gsalazar!955a6fad@gateway/web/cgi-irc/kiwiirc.com/ip.149.90.111.173> has joined #yocto | 07:52 | |
*** mckoan|away is now known as mckoan | 07:52 | |
mckoan | good morning | 07:52 |
*** ahadi <ahadi!~ahadi@i59F44C37.versanet.de> has joined #yocto | 07:53 | |
*** spooster <spooster!~Spooster@c-68-61-72-182.hsd1.mi.comcast.net> has quit IRC | 07:55 | |
abelloni | thekappe: PACKAGE_ARCH = "${MACHINE_ARCH}" | 07:59 |
thekappe | abelloni, thanks man | 08:00 |
*** Yumasi <Yumasi!~guillaume@2a01:e0a:5cb:4430:2f12:f782:a87b:e2ae> has joined #yocto | 08:05 | |
*** leon-anavi <leon-anavi!~Leon@78.130.197.211> has joined #yocto | 08:05 | |
*** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC | 08:08 | |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has joined #yocto | 08:08 | |
*** alejandrohs <alejandrohs!~alejandro@cpe-68-201-52-49.elp.res.rr.com> has quit IRC | 08:11 | |
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/irccloud.com/x-ejhevqtptegfmney> has joined #yocto | 08:13 | |
*** yannholo <yannholo!~yannholo@fs-141-0-205-41.fullsave.info> has joined #yocto | 08:16 | |
*** jrdn <jrdn!~jrdn@S010668ff7b6b7383.ok.shawcable.net> has quit IRC | 08:18 | |
*** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto | 08:23 | |
LetoThe2nd | yo dudX | 08:32 |
mckoan | hi LetoThe2nd | 08:40 |
*** cengiz_io <cengiz_io!~cengiz_io@159.89.7.238> has quit IRC | 08:51 | |
*** cengiz_io <cengiz_io!~cengiz_io@159.89.7.238> has joined #yocto | 08:52 | |
*** minimaxw1ll is now known as minimaxwell | 08:57 | |
*** Anarky <Anarky!~Anarky@lfbn-lyo-1-2112-92.w90-66.abo.wanadoo.fr> has joined #yocto | 09:04 | |
*** mbulut <mbulut!~nameclash@ip1f121f26.dynamic.kabel-deutschland.de> has joined #yocto | 09:07 | |
kayterina | hello | 09:07 |
*** mbulut <mbulut!~nameclash@ip1f121f26.dynamic.kabel-deutschland.de> has quit IRC | 09:10 | |
*** Anarky <Anarky!~Anarky@lfbn-lyo-1-2112-92.w90-66.abo.wanadoo.fr> has quit IRC | 09:14 | |
*** mihai <mihai!~mihai@unaffiliated/mihai> has joined #yocto | 09:21 | |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has joined #yocto | 09:29 | |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has quit IRC | 09:46 | |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has joined #yocto | 09:47 | |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has joined #yocto | 09:48 | |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has joined #yocto | 09:49 | |
*** grumble <grumble!~Thunderbi@freenode/staff/grumble> has quit IRC | 09:59 | |
*** grumble <grumble!~Thunderbi@freenode/staff/grumble> has joined #yocto | 10:03 | |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has quit IRC | 10:04 | |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has quit IRC | 10:05 | |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has joined #yocto | 10:05 | |
*** intera91 <intera91!521f818d@cpc142184-mcam2-2-0-cust140.18-3.cable.virginm.net> has joined #yocto | 10:05 | |
intera91 | good morning | 10:05 |
intera91 | working from a docker container, I cannot create the final wic file due to limitation of the overlay fs, has anyone found a way around that? | 10:06 |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has joined #yocto | 10:07 | |
LetoThe2nd | good thing about new build infrastructure: moar power. bad thign about new infrastructure: much starwalking and physical access until everything works. | 10:07 |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has quit IRC | 10:08 | |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has joined #yocto | 10:09 | |
qschulz | LetoThe2nd: starwalking/walk of fame? | 10:10 |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has joined #yocto | 10:10 | |
LetoThe2nd | stairwalking. | 10:10 |
qschulz | hihi | 10:10 |
LetoThe2nd | server housing is on production floor. | 10:10 |
LetoThe2nd | but then i'll compile the s**t out of everything!!! | 10:11 |
qschulz | intera91: have you heard about pyrex by any chance? | 10:11 |
intera91 | qschulz: apart from the plates which can go in the oven: no | 10:12 |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has quit IRC | 10:12 | |
qschulz | intera91: https://github.com/garmin/pyrex | 10:12 |
LetoThe2nd | mh... oven... | 10:12 |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has joined #yocto | 10:12 | |
qschulz | might help you with getting started with containers | 10:12 |
qschulz | haven't used yet but some cool kids here do | 10:13 |
qschulz | JPEW: might want to pay me for marketing soon ;) | 10:13 |
intera91 | @qschulz: everuthjing compiles fine and its just that last stage creating tye wic file as the python script wants to know the filesystem block size and that is a fail as overlayfs doesn't support that system call | 10:14 |
*** kiwi_29 <kiwi_29!~kiwi_29@c-73-231-211-214.hsd1.ca.comcast.net> has joined #yocto | 10:15 | |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has quit IRC | 10:16 | |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has joined #yocto | 10:16 | |
RP | LetoThe2nd: I prefer the idea of starwalking | 10:18 |
*** kiwi_29 <kiwi_29!~kiwi_29@c-73-231-211-214.hsd1.ca.comcast.net> has quit IRC | 10:19 | |
LetoThe2nd | RP: as Ronnie James Dio told us, real metal heads can either go stargazing or, space trucking. no starwalking allowed. | 10:20 |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has quit IRC | 10:22 | |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has joined #yocto | 10:22 | |
RP | LetoThe2nd: but what to do if your star needs walking? | 10:23 |
LetoThe2nd | RP: it will take me a lifetime to get that picture out of my head again. | 10:31 |
*** zkrx <zkrx!~slimshady@adsl-89-217-237-59.adslplus.ch> has quit IRC | 10:40 | |
*** NiniC0c0 <NiniC0c0!56ee833f@lfbn-idf2-1-900-63.w86-238.abo.wanadoo.fr> has joined #yocto | 10:44 | |
NiniC0c0 | Hallo Yocto Wizards ! Is it possible to override variable set in machine.conf from image recipe ? | 10:45 |
*** zkrx <zkrx!~slimshady@adsl-89-217-237-59.adslplus.ch> has joined #yocto | 10:47 | |
RP | NiniC0c0: possible, yes. I suspect what you're trying to change is something not capable of being changed in an image though. Which variable? | 10:47 |
LetoThe2nd | NiniC0c0: you can override it, but only for the rest of the recipe. | 10:48 |
LetoThe2nd | for all other cases, see yocto chant #1 | 10:48 |
RP | e.g. trying to change the libc from within an image wouldn't make sense as much more than just the image is affected by it | 10:48 |
NiniC0c0 | Hi RP, currently i'm using a custom bbclass to build FIT image. To configure this recipe I have set some variables inside machine.conf (kernel source/device-tree...) but I would like to override this configuration depending the image | 10:50 |
NiniC0c0 | and i'm not sure about the right way | 10:50 |
RP | NiniC0c0: the challenge is that the kernel is already built by the time the image recipe is processed so the image recipe can't change the kernel configuration | 10:51 |
RP | NiniC0c0: you can definitely do things like that but you need to think a little differently about what you're doing, for example they might be separate machines (inheriting one machine from another and tweaking it is cheap) | 10:52 |
RP | assuming you really do need different kernels | 10:52 |
NiniC0c0 | RP understand ! Thank you for your time :) | 10:53 |
qschulz | NiniC0c0: for the device tree, just ship more device trees in your fitimage, or make use of overlays, or both. Provided you can detect which variant you want to boot from u-boot (or a conf file, such as uExt.conf (not sure it's named this way) that you would create per image) | 10:55 |
*** MartinH90 <MartinH90!2edfa3d6@HSI-KBW-46-223-163-214.hsi.kabel-badenwuerttemberg.de> has joined #yocto | 10:55 | |
qschulz | for the kernel, just make a superset of everything you need and that should b enough (if you need a driver in one image but don't need it in the other image, just have it for both or compile it as a module and include it ony in the image you want to use it in) | 10:56 |
NiniC0c0 | qschulz Are you saying that u-boot is able to set overlay before starting kernel ? Interesting, I need to double check that | 10:56 |
qschulz | NiniC0c0: yup, fdt command lets you do that | 10:56 |
NiniC0c0 | qschulz I will check, you made my day | 10:56 |
NiniC0c0 | again ;) | 10:56 |
qschulz | (and actually... u-boot is already doing that for the memory DT node, it's implicitely done | 10:56 |
MartinH90 | Hello community, anybody here with experience with npm recipe generation? I fail generating the cute-files demo from the Yocto wiki (https://wiki.yoctoproject.org/wiki/TipsAndTricks/NPM) on Zeus release. | 10:57 |
qschulz | NiniC0c0: and I THINK bootm actually supports applying device tree overlays directly without using fdt command | 10:57 |
qschulz | like, bootm 0x4678764654#dtb#dtbo#dtbo, etc... | 10:57 |
LetoThe2nd | MartinH90: zeus is not exactly a good place to start out unfortunately... maybe try with either dunfell, gatesgarth or master, and if you run into problems then please provide a full problem description/log | 11:02 |
MartinH90 | LetoThe2nd thanks! Maybe I can backport the recipes then. Here an error log: ERROR: cute-files-1.0.2-r0 do_compile: Execution of '/home/martin/workspace-npm/build/tmp/work/aarch64-my-project/cute-files/1.0.2-r0/temp/run.do_compile.2479040' failed with exit code 1: | 11:05 |
MartinH90 | npm WARN using --force I sure hope you know what you are doing. | 11:05 |
MartinH90 | npm ERR! Cannot read property 'replace' of null | 11:05 |
qschulz | MartinH90: last edit of this page was almost three years ago | 11:06 |
LetoThe2nd | MartinH90: a) is that on a maintened release also? b) that doesn't look like a full og (pastebin, please) | 11:06 |
qschulz | (this page = this page in the wiki) | 11:06 |
LetoThe2nd | qschulz: yes, i noticed too, but i wouldn't really blame it as the npm fetcher at least should be maintained. | 11:06 |
qschulz | the wiki isn't actively maintained, unlike docs.yoctoproject.org | 11:07 |
qschulz | LetoThe2nd: npm has seen major changes in the last few years IIRC | 11:07 |
qschulz | +bbclass/fetcher | 11:07 |
LetoThe2nd | qschulz: it has! | 11:07 |
MartinH90 | LetoThe2nd qschulz: Here is the pastebin: https://pastebin.com/nNYwrrtv | 11:10 |
*** flurin <flurin!90027ebc@bbcs-126-188.pub.wingo.ch> has quit IRC | 11:11 | |
LetoThe2nd | MartinH90: sounds like there is your explanation, ain't it? the package doesn't even compiole properly in itself. | 11:13 |
MartinH90 | LetoThe2nd I tried with different npm packages and all produce the same error message. I was hoping this is a known bug and there is a fix already available ;-) | 11:14 |
LetoThe2nd | MartinH90: TypeError: Cannot read property 'replace' of null | 11:14 |
LetoThe2nd | ah wait. maybe that package has no shrinkwrap file? | 11:15 |
LetoThe2nd | then its indeed known behaviour. go check the ml | 11:15 |
MartinH90 | LetoThe2nd a shrinkwrap file was not generated, there was an error in devtool add. A package-lock.json was generated. See pastebin: https://pastebin.com/JQjviscd | 11:21 |
*** armpit <armpit!~armpit@2601:202:4180:a5c0:ec25:e174:9590:a68b> has quit IRC | 11:22 | |
intera91 | does anyone use pyrex? following the instructions only results in Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /tmp/tmpgzhcag55 | 11:24 |
intera91 | does anyone use pyrex? following the instructions only results in Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /tmp/tmpgzhcag55 | 11:25 |
intera91 | there is a python script which tries to create a temporary dir and file with a raqndomly generated name and that fails spectacularly | 11:26 |
LetoThe2nd | MartinH90: nah thats not what i meant. the npm bbclass behaves unexpectedly/badly when there is no shrinkwrap file supplied. there has been a thread and also a workaround patch on the ml | 11:29 |
MartinH90 | LetoThe2nd great, thanks! | 11:32 |
*** kaspter <kaspter!~Instantbi@58.246.136.202> has quit IRC | 11:34 | |
*** armpit <armpit!~armpit@2601:202:4180:a5c0:2c79:666e:318d:cf6b> has joined #yocto | 11:35 | |
*** pankaj347 <pankaj347!7ab2fec0@122.178.254.192> has quit IRC | 11:37 | |
*** mckoan is now known as mckoan|away | 11:42 | |
*** inf^ is now known as inf | 11:48 | |
*** intera91 <intera91!521f818d@cpc142184-mcam2-2-0-cust140.18-3.cable.virginm.net> has quit IRC | 11:49 | |
*** hthiery[m] <hthiery[m]!hthierymat@gateway/shell/matrix.org/x-karhtffrowaxkibs> has joined #yocto | 11:52 | |
hthiery[m] | Hi all. what is the best/easiest way to set the DL_DIR from environment. I would like to avoid putting it in the local.conf. | 11:54 |
LetoThe2nd | hthiery[m]: DL_DIR= :) | 11:57 |
*** kiwi_29 <kiwi_29!~kiwi_29@c-73-231-211-214.hsd1.ca.comcast.net> has joined #yocto | 12:01 | |
*** davidinux <davidinux!~davidinux@217.138.197.44> has joined #yocto | 12:04 | |
*** kiwi_29 <kiwi_29!~kiwi_29@c-73-231-211-214.hsd1.ca.comcast.net> has quit IRC | 12:05 | |
hthiery[m] | LetoThe2nd: you mean just setting DL_DIR as env before starting bitbake? | 12:06 |
hthiery[m] | LetoThe2nd: here this seems not to works the downloads still land in the value from local.conf | 12:06 |
qschulz | hthiery[m]: don't set it in the local.conf? | 12:12 |
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC | 12:12 | |
hthiery[m] | LetoThe2nd: isnt there a way to override that? | 12:12 |
qschulz | hthiery[m]: it depends on which order the files/env is parsed. It seems local.conf is parsed after the environment, therefore if you have a DL_DIR= in your local.conf, this one will override whatever you pass from the env | 12:14 |
LetoThe2nd | hthiery[m]: no i mean, just do DL_DIR=.... bitbake whatever. | 12:14 |
qschulz | hthiery[m]: also, I vaguely recall that passing vars like this does not work on all shells | 12:15 |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has quit IRC | 12:15 | |
LetoThe2nd | ah. sure, if you have a "=" assignment in your local conf.... | 12:15 |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has joined #yocto | 12:16 | |
hthiery[m] | LetoThe2nd: qschulz I have to admit that I'm new to yocto and I use a present configuration/setup. With setting this up there is a local.conf that has the DL_DIR set but I would like to use another location for downloads | 12:17 |
LetoThe2nd | hthiery[m]: try changing the assignment in local.conf for a ?= | 12:18 |
hthiery[m] | LetoThe2nd: this is in the local.conf DL_DIR ?= "${BSPDIR}/downloads/" and when I now run DL_DIR=~/yocto-dl bitbake <target> is is still downloaded to the location specified in local.con | 12:26 |
*** gpanders <gpanders!~gpanders@gateway/tor-sasl/gpanders> has quit IRC | 12:31 | |
*** gpanders <gpanders!~gpanders@gateway/tor-sasl/gpanders> has joined #yocto | 12:32 | |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has quit IRC | 12:33 | |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has joined #yocto | 12:34 | |
LetoThe2nd | hthiery[m]: BSPDIR is not canonical, hence my guess it that your build setup has seom hidden magic somewhere. | 12:34 |
*** gpanders <gpanders!~gpanders@gateway/tor-sasl/gpanders> has quit IRC | 12:35 | |
*** gpanders <gpanders!~gpanders@gateway/tor-sasl/gpanders> has joined #yocto | 12:36 | |
*** berton <berton!~user@200-180-244-11.user3p.brasiltelecom.net.br> has joined #yocto | 12:38 | |
hthiery[m] | LetoThe2nd: hmmm .. the environment I use seems to be based on https://github.com/Freescale/fsl-community-bsp-base/blob/master/setup-environment#L166 | 12:38 |
hthiery[m] | LetoThe2nd: in this the BSPDIR is used | 12:41 |
zibri | hthiery[m]: i'm not sure DL_DIR is picked up from the environment by default, try `BB_ENV_EXTRAWHITE=DL_DIR DL_DIR=... bitbake`. you can check with bitbake -e if it's picked up or not. | 12:41 |
hthiery[m] | zibri: this seems to do the trick | 12:43 |
zibri | cool! :) | 12:44 |
hthiery[m] | zibri: is this somewhere documented in the manual? | 12:54 |
zibri | hthiery[m]: yes, it's a bitbake variable (starts with BB_) (as opposed to layer variables) and is documented with bitbake; see bitbake-user-manual-metadata.rst and bitbake-user-manual-ref-variables.rst in bitbake/doc/bitbake-user-manual/ | 12:59 |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has quit IRC | 12:59 | |
zibri | i suppose DL_DIR also is a bitbake variable, but it's only a convention :) | 13:00 |
*** Lyghtnox <Lyghtnox!56ec5c03@lfbn-nan-1-761-3.w86-236.abo.wanadoo.fr> has joined #yocto | 13:00 | |
*** tgoodwin <tgoodwin!~tgoodwin@pool-100-16-74-100.bltmmd.fios.verizon.net> has joined #yocto | 13:00 | |
zibri | (when i say bitbake variable in this context, i mean it's a variable use internally by the tool itself.) | 13:00 |
Lyghtnox | Hi | 13:02 |
Lyghtnox | Does anyone know how to add a kernel parameter in yocto? | 13:02 |
Lyghtnox | I tried to add it in /etc/sysctl.conf but it didn't seem to work. I'm trying to enable the memory cgroup | 13:02 |
qschulz | hthiery[m]: https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-ref-variables.html#term-BB_ENV_EXTRAWHITE | 13:02 |
qschulz | Lyghtnox: for which board? | 13:03 |
*** OutBackDingo <OutBackDingo!~quassel@unaffiliated/outbackdingo> has joined #yocto | 13:03 | |
Lyghtnox | qschulz Raspberry pi 2 | 13:03 |
NiniC0c0 | There is a way inside Yocto to "auto-load" overlay (without any init-script or hack:) ) maybe like the raspberry with a config file ? | 13:04 |
qschulz | Lyghtnox: either in cmdline.txt in boot partition or in bootargs environment variable in u-boot | 13:04 |
LetoThe2nd | zibri: interesting, thanks! i didn't even think about the possibility that DL_DIR isn't whitelisted. | 13:06 |
qschulz | NiniC0c0: look in U-Boot sources for boards using uEnv.txt | 13:06 |
qschulz | uEnv.txt is just a file to be put in some partition accessible to u-boot. Then it's up to you to modify uEnv.txt how you want | 13:07 |
NiniC0c0 | qschulz is it the only way isn't it ? i'm listing all possibilities before start coding the solution :) | 13:07 |
zibri | letothe2nd: you add it to extrawhite once and then forget about it :) | 13:07 |
qschulz | NiniC0c0: it has nothing to do with Yocto. If you want to use DT overlays in U-Boot, then it's a UBoot "problem". | 13:08 |
Lyghtnox | qschulz I wasn't aware of the cmdline file. Thanks! | 13:09 |
*** JaMa <JaMa!~martin@ip-109-238-218-228.aim-net.cz> has quit IRC | 13:09 | |
NiniC0c0 | qschulz Sure! sorry for asking. My bad | 13:09 |
qschulz | you could technically have a second u-boot environment in some partition that you then import with `env import`, it has its security challenges though (there's an allowlist now, so you can import only the variables you want from that second env) | 13:09 |
qschulz | NiniC0c0: no no, don't you worry, I was just trying to highlight that we might not be the best support for this particular issue :) | 13:10 |
NiniC0c0 | qschulz Your are always the best support ;) | 13:10 |
*** gonkulator <gonkulator!~brandon@75.71.150.20> has quit IRC | 13:14 | |
*** manuel__ <manuel__!~manuel198@213-147-161-151.nat.highway.bob.at> has joined #yocto | 13:15 | |
*** manuel_ <manuel_!~manuel198@213-147-161-151.nat.highway.bob.at> has quit IRC | 13:18 | |
mcfrisk | on dunfell, after do_compile() failed, and I've modified SRC_URI with a patch, should bitbake apply the patch automatically without manually calling clean() task in between? | 13:18 |
*** ncaidin_lf <ncaidin_lf!a2fa0255@162.250.2.85> has joined #yocto | 13:18 | |
*** blauskaerm <blauskaerm!blauskaerm@gateway/vpn/mullvad/blauskaerm> has quit IRC | 13:20 | |
*** blauskaerm <blauskaerm!blauskaerm@gateway/vpn/mullvad/blauskaerm> has joined #yocto | 13:21 | |
qschulz | mcfrisk: yes, except if devtool is used | 13:22 |
*** gonkulator <gonkulator!~brandon@75.71.150.20> has joined #yocto | 13:25 | |
*** ncaidin_lf <ncaidin_lf!a2fa0255@162.250.2.85> has quit IRC | 13:27 | |
RP | mcfrisk: yes, it should rerun fetch/unpack/patch as SRC_URI changed | 13:27 |
zeddii | RP: I'll poke at perf more today. If you've got a few mins at some point for that reproducibility crash course. I'll take you up on the offer. | 13:30 |
mcfrisk | qschulz RP: thanks, then either my setup or BSP's are breaking things.. | 13:31 |
hthiery[m] | zibri: qschulz thank you for pointing to that | 13:36 |
*** OutBackDingo <OutBackDingo!~quassel@unaffiliated/outbackdingo> has quit IRC | 13:45 | |
*** spooster <spooster!~Spooster@c-68-61-72-182.hsd1.mi.comcast.net> has joined #yocto | 13:58 | |
*** sakoman <sakoman!~steve@72.173.249.164> has joined #yocto | 13:59 | |
*** gonkulator <gonkulator!~brandon@75.71.150.20> has quit IRC | 14:02 | |
*** gonkulator <gonkulator!~brandon@75.71.150.20> has joined #yocto | 14:04 | |
JPEW | qschulz: I'll give you a hefty discount on using Pyrex ;) | 14:06 |
*** aleblanc <aleblanc!~textual@192-222-183-114.qc.cable.ebox.net> has joined #yocto | 14:07 | |
qschulz | JPEW: deal | 14:12 |
RP | zeddii, JPEW: I've just realised we could make a change to the selftest which might make things easier for people | 14:25 |
RP | http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/t222&id=33d27ee65135613597f68dd1a60dbf4bcf59512a | 14:25 |
RP | zeddii: so in your case you'd change targets to ['perf'] and sstate_targets to ['virtual/kernel'] and then run oe-selftest -r reproducible.ReproducibleTests.test_reproducible_builds | 14:26 |
RP | zeddii: that should rebuild near enough just perf using sstate for the rest | 14:26 |
zeddii | ahaha. gotcha. I'll grab that proposed patch and try that. | 14:26 |
*** eyal <eyal!5747e56a@87.71.229.106> has joined #yocto | 14:27 | |
RP | zeddii: if you run OEQA_DEBUGGING_SAVED_OUTPUT=/tmp/perf-diffoscope oe-selftest -r reproducible.ReproducibleTests.test_reproducible_builds it should dump diffoscope output into said directory too | 14:27 |
RP | zeddii: I was trying to think about the easiest way to explain this and its easiest with that patch :) | 14:27 |
zeddii | Agreed. I've been there as well. A patch is easier than re-explaining or even a doc, since it is live in the code. | 14:28 |
RP | zeddii: happy to take any other questions on reproducibility but I think this and simply running "strings /usr/bin/perf | grep <BUILDPATH>" is probably enough for you to get started with | 14:29 |
eyal | hi all. | 14:29 |
eyal | any of u might have created a yocto recipe for installing python app on virtualenv ? | 14:29 |
eyal | meaning i don't want to just install cetrain pip modules. i want the recipe to create virtualenv, install modules on it using pip so the main code could run as : `source venv/bin/activate && python3 my-code.py` | 14:29 |
zeddii | RP: that should be enough. I'll run with it. | 14:29 |
RP | zeddii: I've not tested that patch but I'm sure you can figure out it and let me know if it works :) | 14:30 |
*** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has quit IRC | 14:30 | |
zeddii | absolutely. | 14:30 |
RP | easier than trying to explain running two builds with partial sstate overlap etc | 14:30 |
*** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has joined #yocto | 14:31 | |
JPEW | RP: Ah very good! | 14:36 |
JPEW | I don't know if anyone is inheriting the class and overriding it for their own tests, but if so you might have the keep the "images" variable | 14:38 |
JPEW | vmeson: Would be most likely? | 14:38 |
JPEW | RP: you could do: `bitbake(' '.join(getattr(self, 'images', self.targets)))` to make it look for the old name first and use the new name if it's not found | 14:40 |
*** kaspter <kaspter!~Instantbi@2409:8a1e:9115:5120:1c43:cbeb:1e96:c9ae> has joined #yocto | 14:43 | |
RP | JPEW: ok, will tweak | 14:49 |
*** intera91 <intera91!521f818d@cpc142184-mcam2-2-0-cust140.18-3.cable.virginm.net> has joined #yocto | 14:51 | |
intera91 | sorry to repeat was afk, is anyone using the pyrex project? | 14:51 |
RP | green reproducibility: https://autobuilder.yoctoproject.org/typhoon/#/builders/118/builds/43 - only 45 exclusions and working rpm :) | 14:52 |
RP | dl9pf: ^^^, finally :) | 14:52 |
JPEW | intera91: I'm the maintainer of Pyrex | 14:54 |
*** oberstet <oberstet!~oberstet@213.170.219.39> has joined #yocto | 14:56 | |
*** jrdn <jrdn!~jrdn@S010668ff7b6b7383.ok.shawcable.net> has joined #yocto | 14:59 | |
*** pegu <pegu!~user@81.191.145.158> has quit IRC | 15:18 | |
*** jobroe <jobroe!~manjaro-u@p579eb60e.dip0.t-ipconnect.de> has quit IRC | 15:21 | |
thekappe | hello guys ! | 15:23 |
*** armpit <armpit!~armpit@2601:202:4180:a5c0:2c79:666e:318d:cf6b> has quit IRC | 15:23 | |
thekappe | one question.. If I want to add an udev rules | 15:23 |
thekappe | which is the best recipe to use ? | 15:23 |
*** Konsgn <Konsgn!~Konsgnx3@66-109-34-138.static.firstlight.net> has joined #yocto | 15:25 | |
*** Konsgn <Konsgn!~Konsgnx3@unafiliated/joyseph> has joined #yocto | 15:25 | |
qschulz | thekappe: I don't think there's anything specific to it, I've been adding the files manually to /etc/udev/{rules,scripts} in handcrafted recipes | 15:26 |
*** armpit <armpit!~armpit@2601:202:4180:a5c0:2c79:666e:318d:cf6b> has joined #yocto | 15:26 | |
qschulz | it's a simple install ${WORKDIR} ${D} | 15:27 |
*** derRicha1d is now known as derRichard | 15:30 | |
*** eyal <eyal!5747e56a@87.71.229.106> has quit IRC | 15:31 | |
*** ykrons <ykrons!~guillaume@62.192.23.101> has joined #yocto | 15:33 | |
*** AndersD_ <AndersD_!~AndersD@h83-209-96-136.cust.a3fiber.se> has quit IRC | 15:37 | |
*** armpit <armpit!~armpit@2601:202:4180:a5c0:2c79:666e:318d:cf6b> has quit IRC | 15:42 | |
*** ahadi <ahadi!~ahadi@i59F44C37.versanet.de> has quit IRC | 15:43 | |
*** ahadi <ahadi!~ahadi@89.244.122.228> has joined #yocto | 15:44 | |
*** armpit <armpit!~armpit@2601:202:4180:a5c0:2c79:666e:318d:cf6b> has joined #yocto | 15:46 | |
*** armpit <armpit!~armpit@2601:202:4180:a5c0:2c79:666e:318d:cf6b> has quit IRC | 15:58 | |
*** armpit <armpit!~armpit@2601:202:4180:a5c0:74bb:a268:2b28:e34f> has joined #yocto | 15:59 | |
fray | I'm blanking, it thought there was a bitbake target that would populate someplace under the TMPDIR with the native packages. (I'm trying to run QEMU directly, not via runqemu).. any clue you can give me? | 16:05 |
JPEW | bitbake -c addto_recipe_sysroot qemu-native ? | 16:12 |
*** gonkulator <gonkulator!~brandon@75.71.150.20> has quit IRC | 16:12 | |
fray | where does it get stuffed then? | 16:13 |
stefan-schmidt[m | khem: I played wanted to try plymouth on our musl enabled distro and saw that it fails building. As it needs rpmatch(), I added the external rpmatch-musl package as recipe and a patch to plymouth using it. Is that something you want feed back into meta-oe or somewhere else? | 16:13 |
JPEW | fray: RECIPE_SYSROOT_NATIVE | 16:13 |
JPEW | There's a script to do this for you.... | 16:13 |
stefan-schmidt[m | khem: and why do I find you here and not on #oe as well :D | 16:13 |
stefan-schmidt[m | khem: btw, long time no see. The conferences kept us connected :-) | 16:14 |
JPEW | fray: oe-run-native and oe-find-native-sysroot | 16:14 |
dl9pf | RP: YAY !! | 16:14 |
RP | dl9pf: I've merged it | 16:14 |
JPEW | RP, dl9pf: \o/ | 16:15 |
* RP is pleased to finally have some of those patches into master, its been a horrible patchset | 16:15 | |
dl9pf | some bits were well-hidden | 16:15 |
fray | I'm trying it now.. thanks | 16:16 |
RP | fray: build-sysroots recipe too | 16:16 |
RP | fray: depends whether you want a specific set of dependencies or everything that was previously built | 16:16 |
RP | build-sysroots is a horrible hack and I'd expect can break in interesting ways | 16:17 |
fray | problem is that I can't 'runqemu' cause ther eis no qemu file.. so someone game me a magic line, which Ic an't run directly, since the libraries can't be found.. it's a never ending cycle of failure | 16:18 |
fray | the scripting 'seems' to be working for the most part.. I just hate this magic stuff because nobody bothered to add the right qemu vars to this machine.conf | 16:18 |
fray | "but the reproducer is easier this way".. no doorknob.. it's not.. ARGH | 16:18 |
*** gonkulator <gonkulator!~brandon@75.71.150.20> has joined #yocto | 16:19 | |
JPEW | RP: build-sysroots looks like some deep magic.... I can't quite grok how it actually puts anything in the sysroot :) | 16:19 |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has joined #yocto | 16:19 | |
JPEW | Or more specifically how it puts everything in the sysroot | 16:19 |
RP | JPEW: From memory, I think it would likely just walk the sstate manifests | 16:20 |
RP | so if you've built two things with overlapping files for example, tough luck... | 16:20 |
*** dakhouya <dakhouya!d82e07b2@216.46.7.178> has joined #yocto | 16:22 | |
fray | and their reproducer instructions don't reproduce the problem.. I hate this crap | 16:23 |
*** Lyghtnox <Lyghtnox!56ec5c03@lfbn-nan-1-761-3.w86-236.abo.wanadoo.fr> has quit IRC | 16:25 | |
dakhouya | Hi, I'm trying to use different version of lib boost in the same build. Is there someone that know how to achieve this? I'm using PREFERRED_VERSION_pn-boost to set one version, but don't find info to bind boost version to a specific recipe. | 16:26 |
thekappe | @thanks qschulz! | 16:28 |
qschulz | dakhouya: you need two recipes named slightly different so that they are different to the eyes of bitbake | 16:33 |
qschulz | dakhouya: basically what was done for openssl 1.0 and 1.1 "cohabitation" | 16:33 |
dakhouya | Thanks for the tip | 16:38 |
dakhouya | I'll try that! | 16:38 |
*** nslu2-log_ <nslu2-log_!~nslu2-log@milla.nas-admin.org> has quit IRC | 16:41 | |
*** nslu2-log <nslu2-log!~nslu2-log@milla.nas-admin.org> has joined #yocto | 16:42 | |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has quit IRC | 16:49 | |
khem | zeddii: RP seeing some kernel error msgs on qemuarm https://errors.yoctoproject.org/Errors/Details/572577/ | 16:50 |
khem | this is latest master-next | 16:50 |
paulg | demand a refund! | 16:50 |
zeddii | I saw that in early January as well. Tried to fix it with the kernel command line, and it didn't take for all cases. Didn't have more time to muck around with it, so I moved on. | 16:51 |
*** leon-anavi <leon-anavi!~Leon@78.130.197.211> has quit IRC | 16:52 | |
paulg | reminds me of some pci horrors zeddii and I dealt with on arm versatile like 10y ago - nobody was quite sure what the qemu should do (even rmk) since the hardware was all dead and buried. | 16:52 |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has joined #yocto | 16:53 | |
zeddii | actually, I lie. My patch to try and address it has been in tree since December 28th | 16:53 |
RP | khem: I've not see that... | 16:54 |
intera91 | @JPEW: sorry was afk | 16:54 |
intera91 | @JPEW: installed on vanilla ubuntu 20.04 as working on warrior branch for an AMD bsp. followed instructions to the letter | 16:55 |
intera91 | @JPEW: and it fails to create the temporary /tmp/tmp<whatever> and stops there | 16:56 |
* JPEW looks at some code | 16:57 | |
JPEW | Is /tmp writeable for your user? | 16:57 |
intera91 | @JPEW: yes | 16:57 |
*** spooster <spooster!~Spooster@c-68-61-72-182.hsd1.mi.comcast.net> has quit IRC | 16:58 | |
*** spooster <spooster!~Spooster@c-68-61-72-182.hsd1.mi.comcast.net> has joined #yocto | 16:58 | |
JPEW | Any other output? | 16:59 |
intera91 | @JPEW: going to pastebin the output just a sec | 16:59 |
JPEW | intera91: If you can send your pyrex.ini file, that would be helpful also | 17:00 |
* JPEW has to step away for a little bit, but I'll be back | 17:00 | |
intera91 | @JPEW: https://pastebin.com/YhdyZ5S3 | 17:04 |
*** aleblanc <aleblanc!~textual@192-222-183-114.qc.cable.ebox.net> has quit IRC | 17:07 | |
khem | RP: I have upcoming gcc 11 too so perhaps thats related | 17:07 |
khem | but I have seen similar errors for qemuppc64 last week which was not gcc 11 | 17:08 |
khem | RP: https://errors.yoctoproject.org/Errors/Build/117464/ first pass on my world build with gcc 11 | 17:08 |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has quit IRC | 17:08 | |
khem | not so bad | 17:08 |
intera91 | @jpew: the pyrex.ini is unchanged from generated by meta-pyrex/mkconfig > ./pyrex.ini | 17:11 |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has joined #yocto | 17:11 | |
*** zyga_ <zyga_!~zyga@unaffiliated/zyga> has joined #yocto | 17:12 | |
*** zyga_ <zyga_!~zyga@unaffiliated/zyga> has quit IRC | 17:12 | |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has joined #yocto | 17:14 | |
RP | khem: not bad, we've definitely seen worse | 17:14 |
*** w00die_ <w00die_!~w00die@212.91.255.186> has quit IRC | 17:14 | |
RP | khem: did you see the glibc disable isa patch on the list? | 17:14 |
khem | thats like 50k tasks just oe core has 5 recipes I think | 17:15 |
khem | yeah I have not checked my emails yet been on phone ever since I woke up | 17:16 |
khem | but now I see, | 17:16 |
*** w00die_ <w00die_!~w00die@212.91.255.186> has joined #yocto | 17:16 | |
khem | yeah i think its ok to disable it. we use manual tunes so there is no need for this for us | 17:16 |
khem | but real fix is something else | 17:17 |
*** zkrx <zkrx!~slimshady@adsl-89-217-237-59.adslplus.ch> has quit IRC | 17:17 | |
khem | its a good feature actually for x86 maybe we need to have more tunes | 17:18 |
*** kaspter <kaspter!~Instantbi@2409:8a1e:9115:5120:1c43:cbeb:1e96:c9ae> has quit IRC | 17:20 | |
*** vineela <vineela!~vtummala@134.134.137.75> has joined #yocto | 17:25 | |
RP | khem: I'm wondering why its showing up for them but not in our automated tests | 17:27 |
jonesv[m] | Does somebody use connman around here? Seems dead, I can't get accepted to the mailing list. I thought it was more lightweight than network-manager, but maybe I should stick to nm? What do you guys use? | 17:27 |
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/irccloud.com/x-ejhevqtptegfmney> has quit IRC | 17:29 | |
*** zkrx <zkrx!~slimshady@adsl-89-217-237-59.adslplus.ch> has joined #yocto | 17:30 | |
khem | I think its poking at build machine | 17:30 |
khem | atleast thats how the checks are | 17:31 |
*** halstead_ is now known as halstead | 17:31 | |
khem | for this isa level stuff, they were not done for cross builds in mind :) | 17:31 |
*** aleblanc <aleblanc!~textual@192-222-183-114.qc.cable.ebox.net> has joined #yocto | 17:31 | |
khem | stefan-schmidt: | 17:32 |
RP | khem: if its looking at the build machine that would break reproducibility? :/ | 17:33 |
khem | howdy, yes long time I am rusted in my den here I wish the world was normal sooner yes rpmatch-musl is right approach you took and I would certainly like to have that | 17:33 |
khem | stefan-schmidt: perhaps we can have this library in oe-core along with other musl helpers | 17:34 |
khem | stefan-schmidt: re oe irc, I switched to using matrix and am using IRC bridge and lazily just joined one channel since I was experimenting but you remind me of joining it | 17:35 |
khem | RP: yes I know there was a fix that HJ sent for this but it seems thats not enough, atleast it solved the issues I was seeing | 17:36 |
khem | RP: you are not yet running into 8M size limit issue on core-image-minimal in -ctestimage ? | 17:37 |
RP | khem: no, I'm wondering why | 17:40 |
RP | JPEW: I think I understand the slowness in the repro selftest - its the sync calls | 17:41 |
RP | JPEW: happen between every cmp call | 17:41 |
intera91 | @JPEW: have you seen the pastebin? | 17:41 |
JPEW | intera91: Ya, that's bizzare | 17:41 |
intera91 | @jpew: tell me about it | 17:41 |
JPEW | It seems like a permission problem... can you try `export TMPDIR=/some/other/path` ? | 17:42 |
JPEW | RP: the `cmp` command calls sync? | 17:42 |
RP | JPEW: it was an attempt to try and ensure we didn't have IO backlog on the workers | 17:43 |
RP | JPEW: in oeqa/utils/commands.py | 17:43 |
JPEW | Ah, needs sync=False | 17:44 |
RP | JPEW: yes, nice easy fix for that one | 17:44 |
JPEW | Perhaps the default on that should be False :) | 17:45 |
intera91 | @JPEW: maybe moving forward: docker: Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /tmp/ssh-xNiHN8B2DYbr/agent.2428. | 17:45 |
RP | JPEW: that would remove the benefit elsewhere :/ | 17:46 |
RP | JPEW: we don't often run thousands of short commands | 17:46 |
*** MartinH90 <MartinH90!2edfa3d6@HSI-KBW-46-223-163-214.hsi.kabel-badenwuerttemberg.de> has quit IRC | 17:47 | |
*** mihai- <mihai-!~mihai@unaffiliated/mihai> has joined #yocto | 17:47 | |
*** mihai <mihai!~mihai@unaffiliated/mihai> has quit IRC | 17:47 | |
JPEW | RP: Fair enough | 17:47 |
*** gsalazar <gsalazar!955a6fad@gateway/web/cgi-irc/kiwiirc.com/ip.149.90.111.173> has quit IRC | 17:48 | |
RP | JPEW: I've fast track merged that so watch it break somehow.... | 17:48 |
*** linums <linums!~linums@84.198.214.27> has quit IRC | 17:48 | |
*** linums <linums!~linums@apn-94-44-227-83.vodafone.hu> has joined #yocto | 17:48 | |
RP | JPEW: watching a running build in top is painful | 17:48 |
JPEW | intera91: Ya, it looks like (for some reason) the docker daemon can't access your /tmp | 17:50 |
* RP moves sync out the way to get the build to finish | 17:50 | |
intera91 | @jpew: ls -lah / | grep tmp | 17:50 |
intera91 | drwxrwxrwt 25 root root 124K Feb 26 17:50 tmp | 17:50 |
intera91 | what am i missing here | 17:51 |
*** dev1990_ <dev1990_!~dev@dynamic-78-8-42-145.ssp.dialog.net.pl> has quit IRC | 17:52 | |
JPEW | intera91: can you try `mkdir /tmp/foo; docker run -it --rm --mount type=bind,source=/tmp/foo,target=/tmp/foo busybox` | 17:53 |
JPEW | That will tell of if it's docker in general, or pyrex in particular | 17:53 |
RP | JPEW: https://autobuilder.yoctoproject.org/typhoon/#/builders/119/builds/45/steps/13/logs/stdio - compare the speed of rpm vs ipk :) | 17:53 |
intera91 | mkdir /tmp/foo; docker run -it --rm --mount type=bind,source=/tmp/foo,target=/tmp/foo busybox | 17:53 |
intera91 | docker: Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /tmp/foo. | 17:53 |
intera91 | See 'docker run --help'@jpew: | 17:53 |
intera91 | foo exists | 17:54 |
RP | sakoman: you really want that patch! | 17:56 |
JPEW | RP: Sheesh. Indeed! | 17:56 |
JPEW | intera91: Are you running the docker snap? | 17:56 |
intera91 | @jpew yes | 17:57 |
RP | JPEW: over two hours vs less than two minutes :) | 17:57 |
JPEW | intera91: Ah, that would do it! | 17:57 |
RP | JPEW: I think I found the bottleneck that has been bugging me! | 17:57 |
JPEW | RP: Cool.... that explains why we never see it locally either... the sync doens't matter so much when you aren't doing multiple builds at once | 17:57 |
intera91 | should I delete docker and resintall another way? | 17:57 |
intera91 | reinstall rather | 17:58 |
RP | JPEW: right, there is an mlocatedb update happening on that machine which is why it was so slow | 17:58 |
JPEW | intera91: Ya, I think it's just `apt install docker.io` | 17:59 |
RP | halstead: I do have to wonder if we really want/need mlocate doing that kind of thing... | 17:59 |
JPEW | I'll update the readme | 17:59 |
intera91 | ok trying that | 17:59 |
JPEW | RP: Or at least exclude the build directories | 17:59 |
intera91 | didn't know snap apps had these kind of limitations | 17:59 |
JPEW | intera91: Ya, they run in confinement themselves, so they don't have access to the entire filesystem | 17:59 |
JPEW | Most of the time, this doesn't matter, but when you do bind mounts it does | 18:00 |
intera91 | what a wate of time am so sorry | 18:00 |
JPEW | intera91: It's OK. I didn't even know docker snap was a thing. Now I can warn others :) | 18:00 |
intera91 | well there's you silver lining | 18:01 |
JPEW | intera91: Do you have a GitHub username? | 18:02 |
intera91 | intera91 | 18:03 |
sakoman | RP: I haven't enabled the reproducible stuff in dunfell yet due to the load they put on the autobuilder. I have the patches in a branch and do run builds with them on occasion. Maybe this improves things enough that I can enable it by default. | 18:05 |
RP | sakoman: you still run some basic reproducibility tests though? | 18:05 |
RP | this will help those too | 18:06 |
sakoman | Yes, I do | 18:06 |
dl9pf | wow, 1h vs 2min is significant | 18:06 |
halstead | RP, mlocate should be disabled. Something to improve there. | 18:06 |
dl9pf | and possibly opens the path for repro in dunfell ;) | 18:07 |
RP | halstead: I'll leave that one with you | 18:07 |
RP | I'm sure we do have basic reproducibility testing in dunfell, just not world | 18:07 |
* RP heads afk | 18:08 | |
*** yannholo <yannholo!~yannholo@fs-141-0-205-41.fullsave.info> has quit IRC | 18:08 | |
JPEW | intera91: https://github.com/garmin/pyrex#requirements :) | 18:13 |
intera91 | @jpew: excellent ;-) | 18:14 |
*** blauskaerm <blauskaerm!blauskaerm@gateway/vpn/mullvad/blauskaerm> has quit IRC | 18:46 | |
khem | RP: bitbake master-next today is unhappy http://sprunge.us/Ar9tXz | 18:48 |
khem | RP: I am seeing less space on core-image-minimal is there a place where buildhistory for AB is available ? I can quickly compare | 18:49 |
khem | RP: I have EXTRA_IMAGE_FEATURES_append = " package-management ssh-server-dropbear" | 18:50 |
khem | I wonder if thats causing it | 18:50 |
khem | perhaps yes because dropbear pulls in pam etc if distro features have pam so it could be it | 18:50 |
*** aleblanc <aleblanc!~textual@192-222-183-114.qc.cable.ebox.net> has quit IRC | 18:56 | |
*** Hauke1 is now known as Hauke | 18:56 | |
*** aleblanc <aleblanc!~textual@192-222-183-114.qc.cable.ebox.net> has joined #yocto | 19:04 | |
*** wyre_ is now known as wyre | 19:14 | |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has quit IRC | 19:18 | |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has joined #yocto | 19:22 | |
*** kyanres <kyanres!~kyanres@ecascr.ecatou.fr> has quit IRC | 19:22 | |
*** linums <linums!~linums@apn-94-44-227-83.vodafone.hu> has quit IRC | 19:26 | |
*** alejandrohs <alejandrohs!~alejandro@cpe-68-201-52-49.elp.res.rr.com> has joined #yocto | 19:26 | |
*** linums <linums!~linums@apn-94-44-232-189.vodafone.hu> has joined #yocto | 19:26 | |
khem | does anyone know if the Linux on mars that landed recently is yocto project based ? | 19:31 |
georgem_home | khem: I gather they're using this board https://medium.com/@chuck.ward/qualcomms-snapdragon-flight-board-b1914dea9796 based on what I've heard so far. If that's true and they're using the vendor stuff provided it would be linaro linux. Maybe they've put something else on it though. | 19:33 |
khem | georgem_home: for helicopter yes | 19:33 |
georgem_home | for anything other than that I don't know | 19:34 |
khem | main cpu is Powerpc 750@200mhz | 19:34 |
khem | https://mars.nasa.gov/mars2020/spacecraft/rover/brains/ | 19:34 |
georgem_home | ah ok. cool | 19:34 |
khem | so Snapdragon maybe running yocto ? | 19:35 |
*** rangergord <rangergord!rangergord@gateway/shell/xshellz/x-kmbfnokkdabbswtl> has joined #yocto | 19:35 | |
rangergord | Is there anything wrong with using Ubuntu Server as the distro for an Atom embedded system? | 19:35 |
rangergord | Sorry I know it's off-topic, but I'm specifically weighing Ubuntu Server vs Yocto | 19:36 |
rangergord | I benchmarked my app and it runs like a dream on Ubuntu. I'm asking from a stability POV, or any other POV I'm missing. | 19:37 |
khem | rangergord: its ok I guess, you have to know your requirements and then weigh in what matters to you and you will make a good decision | 19:37 |
GeneralStupid | rangergord: ubuntu is a linux distribution, yocto helps you build your own distritibutio. Its not comparable and it depends on your requirements | 19:37 |
rangergord | my requirements are having Postgres, having Qt libraries, letting me easily add dependencies, and being rock solid | 19:38 |
rangergord | Is there anything innately inferior about using a server distro on an embedded system? Like some shortcoming I'm not thinking of? | 19:38 |
georgem_home | It boils down to whether or not you're going to spend more time clobbering Ubuntu server to get what you need or building something custom with Yocto. | 19:38 |
rabbit9911 | rangergord:https://www.youtube.com/watch?v=iDllXa8SzUg | 19:39 |
rangergord | for sure Ubuntu would be faster for me. I use it daily. And I use Ubuntu Server on my home server. | 19:39 |
rangergord | rabbit9911: thanks! gonna watch this | 19:39 |
GeneralStupid | yocto produces an image file for you, which you could flash or upgrade... | 19:39 |
georgem_home | rangergord: depends... if you have to customize the heck out of it for your application it still might be more of a pain in the long run. Just depends what you're doing. | 19:39 |
*** leon-anavi <leon-anavi!~Leon@78.130.197.211> has joined #yocto | 19:39 | |
georgem_home | and yeah a sane update solution would be part of what you'd need to customize on Ubuntu | 19:40 |
rangergord | what sort of customizations are you referring to? Other than the boot logo/printout | 19:40 |
GeneralStupid | So if you are trying to built something like a router it will be more suitable | 19:40 |
rangergord | nah it's a touchscreen device. meant to be on 24/7. gets rebooted during maintenance. | 19:41 |
GeneralStupid | rangergord: that dosnt matter. customitazion means, build one package with an build configuration | 19:41 |
GeneralStupid | not really easy to change this in ubuntu | 19:42 |
rangergord | ah...no, no customizations. it's the same base image for everything. | 19:42 |
rangergord | and same hardware | 19:42 |
GeneralStupid | same for me, i have the same base image for every device. And same hardware. | 19:42 |
GeneralStupid | But i still need customizations | 19:42 |
GeneralStupid | e.g. special kernel | 19:42 |
georgem_home | what if you want to run with a read-only root and store your user settings in a different partition... this kind of thing | 19:42 |
GeneralStupid | or in en EEPROM :-D | 19:43 |
georgem_home | yeah | 19:43 |
GeneralStupid | Maybe you want to have 2 partitions and failsafe upgrade... | 19:43 |
georgem_home | yup. that's what we do | 19:43 |
GeneralStupid | (pointing to rauc) | 19:43 |
GeneralStupid | same here, i guess that would be PITA to realize with ubuntu | 19:43 |
rangergord | ah, I see what you mean | 19:43 |
GeneralStupid | its fine to run ubuntu on such a machine, if its working for you | 19:44 |
georgem_home | you just have to weigh your needs and see which way ends up taking more time in the long run | 19:44 |
khem | if you want end to end control and also care for compliance and maintain it for long time yocto might be better and its bottom up approach means you only build what you need. Desktop distros start with a larger featureset and sometimes you start removing stuff and that does not work as well as bottom up | 19:44 |
GeneralStupid | khem: also correct. My image is 25 Mb - and its big :-D | 19:44 |
rangergord | khem: I would be starting with the server distro though, then adding x11 | 19:44 |
rangergord | the systems all have 120GB SSDs and 2GB of RAM. I hesitate to call it embedded | 19:45 |
khem | I have seen cases where someone started with some desktop/server binary distro but then moved to use something custom because they realized thats best for them | 19:45 |
rangergord | coming from a 256MB system running Busybox and a 12yo kernel :) | 19:45 |
khem | its not about just how much resources you have anymore | 19:46 |
khem | people are using yocto to build their servers and containers | 19:46 |
GeneralStupid | its just a way to customize every aspect of your image. Maybe you could compare it more with Gentoo | 19:46 |
khem | its how much you want to allow the overhead to be | 19:46 |
rangergord | thing is, I'm on my own working on this. Literally the only "software" guy. I'm a decent Linux user, but I wouldn't be able to troubleshoot kernel issues on my own for example. So delegating to Ubuntu here seems safer. | 19:46 |
GeneralStupid | and my 25M are really huge, it got big when i added systemd :) | 19:47 |
khem | yeah community support is a big aspect | 19:47 |
*** dakhouya <dakhouya!d82e07b2@216.46.7.178> has quit IRC | 19:47 | |
GeneralStupid | rangergord: yes, true. Maybe just start there | 19:48 |
khem | and this community is quite helpful I reckon :) | 19:48 |
rabbit9911 | rangergord: You could think of poky as equiv to ubuntu server. You can use it as is w/o much customization if you want. | 19:48 |
rabbit9911 | But it leaves the option open to massive customization if you need it | 19:48 |
rabbit9911 | What most people do is put poky in its own read-only directory and tweak what they need in their own custom layer. Then upgrading means just checking out the newer version of poky. | 19:49 |
khem | rangergord: I would recommend to do some research and perhaps that will help e.g. https://medium.com/@zertsekel/yocto-vs-ubuntu-for-embedded-e6b13d583e05 | 19:49 |
GeneralStupid | what rabbit9911 says is exactly what we do... | 19:50 |
GeneralStupid | Its really nice, i nightly built that image on jenkins | 19:50 |
GeneralStupid | upgrade is done via rauc | 19:51 |
rangergord | thanks. I'm gonna read that article then watch rabbit's 30 min youtube video | 19:51 |
rabbit9911 | Working on products with yocto/buildroot/openwrt and also one with redhat.. I would for sure say yocto is the best solution right now. | 19:52 |
rabbit9911 | Its worth the upfront investment | 19:52 |
khem | georgem_home: so it seems the helicopter runs linux | 19:52 |
rangergord | it's easy to say "Debian is just for prototyping" but you guys mentioned specific scenarios where it's harder, like the "two partitions with fallback" thing | 19:52 |
georgem_home | khem: yeah, hard to say if they used what comes with that dev kit or replaced it with something else | 19:53 |
khem | so there is one planet where there are more systems running linux than windows :) | 19:53 |
georgem_home | well here too if you count Android | 19:54 |
rangergord | I'll tell you one concern that's making me wary of another "custom distro". My previous system, was an old ARM, with Busybox. In addition to having to build my own packages (instead of something tested by Ubuntu/Debian ), I could never get reliable stack traces in core dumps. Like it was a total crapshoot whether a core dump would tell me what happened. I don't expect ever to have this issue on x64 | 19:54 |
rangergord | server distro. | 19:54 |
*** intera91 <intera91!521f818d@cpc142184-mcam2-2-0-cust140.18-3.cable.virginm.net> has quit IRC | 19:54 | |
rangergord | So for an intermediate-level (and perhaps by the standard of this channel, novice) user, Ubuntu seems a safer choice | 19:55 |
georgem_home | rangergord: yeah that sort of thing would probably be easier in Ubuntu. You can do it with yocto but I won't tell you I've never run into issues before. | 19:56 |
rangergord | although, that issue might have been related to the ARM processor, so perhaps Poki would never have similar issues on x64 | 19:56 |
georgem_home | well also... to be clear... | 19:56 |
georgem_home | I was cross debugging. With ubuntu you'd probably debug on the target. | 19:56 |
georgem_home | that's just easier in general | 19:57 |
rangergord | I would totally include gcc/gdb in my custom distro, if only for convenience :) | 19:57 |
rabbit9911 | Another consideration. Yocto is nice for tracking license and CVEs. So if you ever want to add secure boot (which is almost a must now a days) You will have to make sure you dont include GPLv3 libraries/apps in your image. Yocto can do this. | 19:59 |
*** gonkulator <gonkulator!~brandon@75.71.150.20> has quit IRC | 20:00 | |
rabbit9911 | Also once you enable secure boot on target you lose the ability to use the package manager on target unless you have an overlayfs. | 20:01 |
khem | georgem_home: | 20:01 |
khem | I doubt they will use soc vendor SDK :) | 20:02 |
rangergord | that's good to know, although my systems are open. Users have shell access and root password. | 20:02 |
rabbit9911 | Also as soon as your company grows and you make a product that uses a super cheap arm64 or risc-v processor you will bet super hard up trying to get debian working on it. | 20:03 |
khem | RP: yeah the problem is including ssh server in minimal image and it tips over that df check | 20:03 |
stefan-schmidt[m | khem: I will have a look to update what I have here to oe-core master (we are on dunfell here) and prepare patches early next week. | 20:07 |
khem | stefan-schmidt: | 20:07 |
khem | ok | 20:07 |
stefan-schmidt[m | khem: folks here also looking at llvm/clang as default toolchain. In combination with musl. Thought that might interest you :-) | 20:08 |
*** yates <yates!~user@fv-nc-f7af8b91e1-234237-1.tingfiber.com> has joined #yocto | 20:10 | |
rabbit9911 | stefan-schmidt[m: You are looking to add llvm/clang+musl as a default toolchain to poky? | 20:12 |
yates | do some layers which are publicly available for yocto source code from the linaro project? | 20:12 |
stefan-schmidt[m | rabbit9911: not poky itself but based on it | 20:12 |
yates | s/do/are/ | 20:12 |
rabbit9911 | stefan-schmidt[m: As a layer then? | 20:13 |
stefan-schmidt[m | rabbit9911: well, patches should go into the normal oe layers, but we plan to use it as default for our OpenHarmony distro | 20:14 |
stefan-schmidt[m | so far we only switched to musl though, move to llvm/clang is on the agenda | 20:14 |
*** gonkulator <gonkulator!~brandon@75.71.150.20> has joined #yocto | 20:20 | |
*** linums <linums!~linums@apn-94-44-232-189.vodafone.hu> has quit IRC | 20:23 | |
rabbit9911 | stefan-schmidt[m: poky-tiny I believe uses musl as the default today. Is this just expanding support to more packages perhaps? | 20:25 |
stefan-schmidt[m | rabbit9911: not sure what you mean. OE/yocto does have musl support for a long time now. And a llvm/clang layer as well | 20:27 |
stefan-schmidt[m | rabbit9911: I just thought that khem would be interested to know that we are planning to take this for our distro in production | 20:28 |
stefan-schmidt[m | nd sure, if we see problems we get the packages fixed. Like for plymouth. | 20:28 |
rangergord | is anyone here using .NET Core on Yocto? | 20:29 |
*** Konsgn <Konsgn!~Konsgnx3@unafiliated/joyseph> has quit IRC | 20:31 | |
*** Konsgn <Konsgn!~Konsgnx3@66-109-34-138.static.firstlight.net> has joined #yocto | 20:31 | |
*** Konsgn <Konsgn!~Konsgnx3@unafiliated/joyseph> has joined #yocto | 20:31 | |
*** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has quit IRC | 20:42 | |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has quit IRC | 20:47 | |
*** Konsgnx1 <Konsgnx1!~Konsgnx3@66-109-34-138.static.firstlight.net> has joined #yocto | 20:50 | |
*** Konsgn <Konsgn!~Konsgnx3@unafiliated/joyseph> has quit IRC | 20:50 | |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has joined #yocto | 20:52 | |
*** oberstet <oberstet!~oberstet@213.170.219.39> has quit IRC | 20:52 | |
*** Konsgn <Konsgn!~Konsgnx3@66-109-34-138.static.firstlight.net> has joined #yocto | 20:53 | |
*** Konsgn <Konsgn!~Konsgnx3@unafiliated/joyseph> has joined #yocto | 20:53 | |
*** Konsgnx1 <Konsgnx1!~Konsgnx3@66-109-34-138.static.firstlight.net> has quit IRC | 20:53 | |
*** richbridger <richbridger!~richbridg@089144194174.atnat0003.highway.a1.net> has joined #yocto | 20:55 | |
*** Konsgn <Konsgn!~Konsgnx3@unafiliated/joyseph> has quit IRC | 20:55 | |
*** Konsgn <Konsgn!~Konsgnx3@unafiliated/joyseph> has joined #yocto | 20:55 | |
*** Konsgn <Konsgn!~Konsgnx3@unafiliated/joyseph> has quit IRC | 20:57 | |
zeddii | RP: clearly I'm not going to be able to do the reproducible tests locally on my home builder. It's been running for 4 hours now. And that's with your patch. | 20:58 |
rangergord | rabbit9911: finished the video, great stuff. Although, thanks to one of the people in the Q&A at the end let me find the debos project, which creates a Debian rootfs from a recipe you give it (apt files to instal,overlay fs, etc), AND it integrates ostree. I'm gonna look into that as a compromise. | 20:58 |
* zeddii calls it a day | 20:58 | |
rangergord | so a lot of "Debian golden master" shortcomings are negated with this | 20:59 |
rangergord | I think if I was still using a legit embedded system instead of an Atom system I would have gone with Yocto for sure | 21:00 |
yates | is there a "reference" yocto project available for playing around / learning? e.g., something like the raspberry pi? | 21:04 |
rangergord | debos is based on debootstrap which is one of the tools the speaker recommended to build a robust/reproducible Debian if you're gonna insist on it | 21:04 |
*** dreyna <dreyna!~dreyna@c-71-202-37-249.hsd1.ca.comcast.net> has joined #yocto | 21:04 | |
*** dreyna_ <dreyna_!~dreyna@c-71-202-37-249.hsd1.ca.comcast.net> has joined #yocto | 21:05 | |
*** aleblanc <aleblanc!~textual@192-222-183-114.qc.cable.ebox.net> has quit IRC | 21:07 | |
*** dreyna <dreyna!~dreyna@c-71-202-37-249.hsd1.ca.comcast.net> has quit IRC | 21:09 | |
rabbit9911 | rangergord: Yep I heard that too. I would just be nervous if you ever think you would use a board that's not supported by debian out of the box. Usually the bean counters come in at some point and find they can save millions by using a cheap SBC based on some cellphone product. Usually what happens though is in 5 years if you still need to support | 21:15 |
rabbit9911 | your old product you start running out of disk space. Most of our yocto recipe mods are to remove features we dont need to save flash space. And when you A/B upgrade you run out of space fast. | 21:15 |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has quit IRC | 21:16 | |
rabbit9911 | I have been looking at NixOS on the side too. I don't think its ready to do what Yocto does.. but it's interesting. | 21:17 |
rangergord | rabbit9911: no chance of that happening. we sell a handful of devices a year only. Any savings on hardware would have to be spent by increasing the size of the dev team, or me falling behind | 21:17 |
*** sbach <sbach!~sbachmatr@192.184.90.156> has quit IRC | 21:18 | |
*** sbach <sbach!~sbachmatr@192.184.90.156> has joined #yocto | 21:19 | |
*** berton <berton!~user@200-180-244-11.user3p.brasiltelecom.net.br> has quit IRC | 21:20 | |
khem | stefan-schmidt: yes, meta-clang is your way to glory 🙂 we use it here as well. Now working on using it default for everything earlier we only used it for certain large components like browser | 21:21 |
*** aleblanc <aleblanc!~textual@192-222-183-114.qc.cable.ebox.net> has joined #yocto | 21:22 | |
khem | one of these days I am thinking of creating meta-bsd and bring some BSD alternatives from OpebBSD/NetBSD/FreeBSD to yocto world as well dont know when though | 21:22 |
khem | stefan-schmidt: building a clang based toolchain needs quite a bit of compute but once you have it built then it compiles other larger C++ files quite quickly compared to gcc | 21:23 |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has joined #yocto | 21:23 | |
khem | so Webkit or Chromium devs are happy | 21:24 |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has quit IRC | 21:24 | |
khem | yates: meta-96boards perhaps ? | 21:25 |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has joined #yocto | 21:25 | |
khem | rangergord: I know mono is well maintained in yocto world look at meta-mono https://git.yoctoproject.org/cgit/cgit.cgi/meta-mono | 21:26 |
rangergord | thanks but would be crazy to use Mono today. It's probably gonna be gone next year when the grand unification is complete. | 21:26 |
stefan-schmidt[m | khem: yup, meta-clang is what we are planning to use. A lot of things to sort out though next to the OE work. Keeping latest upstream find a way to reabse patches from an in house compiler team and last but not least we have meta-zephyr and meta-freertos on our agenda | 21:27 |
stefan-schmidt[m | khem: lots of things to juggle, but we will get there eventually. | 21:27 |
rangergord | OK it's not going anywhere, but new development will only be on .NET Core | 21:27 |
* stefan-schmidt[m is happy that he is not doing the toolchain work though ;-) | 21:27 | |
khem | stefan-schmidt: cool, I think you can easily plugin your own fork of llvm-repo into meta-clang if you like, I think I have left way for that | 21:28 |
rabbit9911 | rangergord: Sounds like its worth a try then! Just from my POV I have been at 3 companies now that have moved to yocto from various other solutions and its always super painful because it happens after you they have 10+ products and 10 years cruft that needs to be duplicated or changed at risk of thousands of products in the field. | 21:28 |
khem | although I would love if folks maintain their changes as patches and work on upstreaming them | 21:28 |
stefan-schmidt[m | khem: the aim from our OSTC side is really upstream and push our compiler team to rebase on latest and hopefully even submit upstream | 21:29 |
stefan-schmidt[m | we will see how that goes :-) | 21:29 |
khem | good deal | 21:29 |
khem | as of now we can do everything we do with gcc in oe-core with clang too | 21:30 |
stefan-schmidt[m | It feels good to work with OE again after so many years | 21:30 |
khem | you can build eSDKs too | 21:30 |
rabbit9911 | You still need gcc for kernel though right? | 21:30 |
stefan-schmidt[m | that's cool and likely to be interesting for our SDK work at some point | 21:31 |
khem | good to hear stefan-schmidt | 21:31 |
stefan-schmidt[m | rabbit9911: quite a bit of it does not need gcc anymore | 21:31 |
khem | rabbit9911: sort of, I have run a clang compiled kernel on rpi4 though | 21:31 |
stefan-schmidt[m | depends on your config, maybe some drivers | 21:31 |
khem | glibc is another key piece which is joined at hip with gcc | 21:32 |
khem | u-boot works with clang | 21:32 |
khem | busybox does too | 21:32 |
khem | so essentially if you are ok with musl then your base system is set | 21:32 |
khem | kernel for x86/arm/arch64/riscv64 is getting better with time | 21:33 |
khem | with clang | 21:33 |
stefan-schmidt[m | For me the usage of both musl and clang for everything feels like a bold move. But our toolchain expert is in favour of it and I can clearly see the benefits | 21:34 |
stefan-schmidt[m | We need to validate quite a bit though. Say musl with systemd :-) | 21:34 |
khem | yes it is bold move but musl is everywhere now and so is clang so perhaps not a bad time to start | 21:34 |
stefan-schmidt[m | jup | 21:35 |
khem | yeah musl+systemd is a PITA and will remain so, I have given up on that | 21:35 |
rabbit9911 | I keep wanting to try s6-init in place of systemd :) which does support musl | 21:35 |
stefan-schmidt[m | and for us an intersting part is how musl plays with zephyr and freertos and maybe orther RTOS systems | 21:35 |
khem | infact for many systems I care for systemd is not as appealing anyway | 21:35 |
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has quit IRC | 21:36 | |
khem | musl has FDPIC port ( nommu ) for cortex-M | 21:36 |
khem | so you will be well serverd | 21:36 |
rabbit9911 | I get why systemd is supported in yocto but at the same time is feels like a bad fit for embedded devices. | 21:36 |
khem | its convenient for sue | 21:36 |
khem | sure | 21:37 |
stefan-schmidt[m | rabbit9911: everbody defines embedded differntly. Do we talk 512kb flash or 8GB? | 21:37 |
stefan-schmidt[m | khem: we will see how this pans out. We start bold and make plans with the best judgement we have and we will see if we hit walls :-) | 21:38 |
khem | stefan-schmidt: yeah its getting there, we have issues on systems with 1G of RAM | 21:38 |
khem | storage really does not matter | 21:38 |
khem | everything is competeing for compute and RAM | 21:38 |
rabbit9911 | Then you add glib and dbus. | 21:38 |
khem | so one has to know how much journald can thrash | 21:38 |
stefan-schmidt[m | yeah, so "embedded" can be everything from 64KB to 6G :-) | 21:38 |
stefan-schmidt[m | depending on who talks about it | 21:39 |
khem | if you have range of products then having a common profile matters for scale | 21:39 |
stefan-schmidt[m | that is the idea yes, a wide range actually. Thus the RTOS kernel part next to Linux | 21:40 |
rabbit9911 | even at 6G.. The less on the device the less you have to maintain | 21:40 |
yates | i downloaded yocto. shouldn't i be able to build poky by just running "make"? http://paste.ubuntu.com/p/zyR744BwRz/ | 21:41 |
khem | I have learnt that starting small at platform level is key | 21:41 |
khem | yates: | 21:41 |
yates | i downloaded like this: git clone -b gatesgarth git://git.yoctoproject.org/poky.git | 21:42 |
yates | khem: | 21:42 |
yates | this is under lubuntu 18.04.5 | 21:43 |
khem | try https://github.com/yoedistro/yoe-distro | 21:43 |
khem | 10 steps - https://github.com/yoedistro/yoe-distro#workspace-setup | 21:43 |
khem | stefan-schmidt: thats a good approach, remember its not the platform or tools which your products will differentiate on, but the services and apps, so OS is kind of a necessary evil, ideally if I could say the apps with minimum OS overhead that is preferred | 21:46 |
stefan-schmidt[m | khem: I got that memo a long time ago. It has the nice benefit that its way easier to collaborate on these "uninteresting" pieces. I like that a lot. :-) | 21:51 |
rabbit9911 | khem: +1 Its always tempting to take the new thing and all of the extra stuff you dont need because its easy. The hidden cost of security/stability/general maintenance are usually an after thought. | 21:52 |
*** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC | 21:52 | |
RP | zeddii: was that in the initial build? Hopefully better once sstate is populated? | 22:01 |
zeddii | yah. it just completed. | 22:03 |
zeddii | but I see no mention of perf :D | 22:03 |
zeddii | even with me putting it in as the target | 22:03 |
zeddii | I'll investigate on Monday | 22:03 |
zeddii | https://pastebin.com/nD6htMie | 22:04 |
*** agust <agust!~agust@p508b685a.dip0.t-ipconnect.de> has quit IRC | 22:10 | |
*** beneth <beneth!~beneth@irc.beneth.fr> has left #yocto | 22:15 | |
*** beneth <beneth!~beneth@irc.beneth.fr> has joined #yocto | 22:18 | |
*** vineela <vineela!~vtummala@134.134.137.75> has quit IRC | 22:20 | |
*** leon-anavi <leon-anavi!~Leon@78.130.197.211> has quit IRC | 22:22 | |
*** vineela <vineela!~vtummala@134.134.137.75> has joined #yocto | 22:23 | |
*** aleblanc <aleblanc!~textual@192-222-183-114.qc.cable.ebox.net> has quit IRC | 22:25 | |
smurray | yates: see https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html#yocto-project-quick-build | 22:28 |
RP | zeddii: did you remove perf from the exclusions list? | 22:31 |
RP | zeddii: I had forgotten you might need to do that :/ | 22:32 |
RP | obvious in hindsight | 22:32 |
RP | zeddii: now you have hot sstate it should be faster | 22:32 |
RP | zeddii: I'm guessing "different_excluded=1" was perf | 22:32 |
v0n | hum I still get this "No IMAGE_CMD defined for IMAGE_FSTYPES entry 'container'" :-( | 22:33 |
RP | JPEW: diffoscope upstream have fixed the html diff size "hang" :) | 22:35 |
yates | smurray: thanks! | 22:38 |
*** beneth <beneth!~beneth@irc.beneth.fr> has left #yocto | 22:42 | |
*** dev1990 <dev1990!~dev@217.96.227.63.ipv4.supernova.orange.pl> has joined #yocto | 23:01 | |
*** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has quit IRC | 23:05 | |
*** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has joined #yocto | 23:06 | |
*** dev1990 <dev1990!~dev@217.96.227.63.ipv4.supernova.orange.pl> has quit IRC | 23:10 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!