Wednesday, 2020-10-14

*** linums <linums!~linums@> has quit IRC00:56
*** linums <linums!> has joined #yocto00:58
*** stacktru1t <stacktru1t!> has quit IRC01:10
*** stacktru1t <stacktru1t!> has joined #yocto01:13
*** camus1 <camus1!~Instantbi@> has joined #yocto01:14
*** kaspter <kaspter!~Instantbi@> has quit IRC01:14
*** camus1 is now known as kaspter01:14
*** linums <linums!> has quit IRC01:30
*** kpo__ <kpo__!> has quit IRC01:30
*** linums <linums!> has joined #yocto01:30
*** kpo__ <kpo__!> has joined #yocto01:31
*** linums <linums!> has quit IRC01:34
*** linums <linums!~linums@> has joined #yocto01:34
*** linums <linums!~linums@> has quit IRC01:56
*** linums <linums!> has joined #yocto01:57
*** hpsy <hpsy!~hpsy@> has quit IRC02:29
*** hpsy <hpsy!~hpsy@> has joined #yocto02:29
*** camus1 <camus1!~Instantbi@> has joined #yocto03:02
*** kaspter <kaspter!~Instantbi@> has quit IRC03:02
*** camus1 is now known as kaspter03:02
*** sakoman <sakoman!> has quit IRC03:17
*** armpit <armpit!~armpit@2601:202:4180:a5c0:d58b:c80e:7cac:2737> has quit IRC03:25
*** armpit <armpit!~armpit@2601:202:4180:a5c0:283a:e7e0:f7dd:41c0> has joined #yocto03:36
*** paulg <paulg!> has quit IRC04:32
*** paulg <paulg!> has joined #yocto04:38
*** paulg <paulg!> has quit IRC04:49
*** thaytan <thaytan!> has quit IRC04:56
*** jobroe <jobroe!> has joined #yocto05:05
*** ThomasD13 <ThomasD13!> has joined #yocto05:15
ThomasD13Hi, is the mega manual gone for yocto? I can't find it on their website05:21
ThomasD13Argh! Found it!05:22
*** beneth` <beneth`!> has joined #yocto05:25
*** paulg <paulg!> has joined #yocto05:35
*** camus1 <camus1!~Instantbi@> has joined #yocto05:39
*** kaspter <kaspter!~Instantbi@> has quit IRC05:39
*** camus1 is now known as kaspter05:39
*** AndersD <AndersD!> has joined #yocto05:39
*** agust <agust!> has joined #yocto05:56
*** feddischson <feddischson!> has joined #yocto06:04
*** AndersD <AndersD!> has quit IRC06:06
*** chris_ber <chris_ber!~quassel@> has joined #yocto06:11
*** w00die <w00die!~w00die@> has quit IRC06:16
*** w00die <w00die!~w00die@> has joined #yocto06:18
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has joined #yocto06:34
LetoThe2ndyo dudX06:35
*** paulg <paulg!> has quit IRC06:37
*** frsc <frsc!> has joined #yocto06:37
LetoThe2ndmoto-timo: whoa, just saw you proprely bearded on LI!06:38
*** dreyna <dreyna!> has quit IRC06:38
*** dreyna <dreyna!> has joined #yocto06:39
*** alejandrohs <alejandrohs!~alejandro@2605:6000:1306:9479::a59> has quit IRC06:40
*** manuel1985 <manuel1985!> has joined #yocto06:41
*** vineela <vineela!~vtummala@> has joined #yocto06:42
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto06:43
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto06:44
*** mckoan|away is now known as mckoan06:48
mckoangood morning06:48
*** thaytan <thaytan!> has joined #yocto06:50
*** leon-anavi <leon-anavi!~Leon@> has quit IRC06:51
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto06:51
*** kaspter <kaspter!~Instantbi@> has quit IRC06:59
*** kaspter <kaspter!~Instantbi@> has joined #yocto06:59
*** vineela <vineela!~vtummala@> has quit IRC07:01
*** fl0v0 <fl0v0!> has joined #yocto07:01
*** joeythesaint <joeythesaint!> has quit IRC07:04
*** joeythesaint <joeythesaint!~joe@2605:6400:2:fed5:22:c968:e405:6881> has joined #yocto07:04
RPThomasD13: Apparently you're using a setup which is multiconfig enabled and not building the right config which is why you were seeing issues. One of the TI people commented overnight.07:06
Ad0thanks denix07:07
*** hpsy <hpsy!~hpsy@> has quit IRC07:07
ThomasD13RP great, thank you for the notification! Is the chatlog of this channel somewhere available so I can read his answer?07:09
RPThomasD13: There is, I don't remember where. What he said was "(21:44:33) denix: RP: the discussion here you had earlier today (it was 6am for me) about TI u-boot - there's nothing wrong with it, but it is multiconfig-enabled, so the other guy was not trying the right variant of it..."07:10
ThomasD13Since 2 hours, I also discovered that the setup uses two different machine configurations. I assume also I have to search to missing piece somewhere there07:11
*** thaytan <thaytan!> has quit IRC07:13
*** pohly <pohly!> has joined #yocto07:15
*** thaytan <thaytan!> has joined #yocto07:21
*** xtron <xtron!~xtron@> has joined #yocto07:22
*** rcoote <rcoote!> has joined #yocto07:23
RPThomasD13: that would be the two multiconfigs ?07:26
*** ptsneves <ptsneves!b0dd7824@> has joined #yocto07:32
*** yann <yann!~yann@> has joined #yocto07:33
ThomasD13RP, when I start to build the standard TI image with bitbake, bitbake returns two build configurations: They are identical except of the machine configuration (and target FPU): j7-evm and j7-evm-k3r5. The stuff which I miss is for the Cortex R5 (j7-evm-k3r5).07:34
ThomasD13Then I discovered the multiconfig directory at
ThomasD13Yocto multiconfig wasnt yet a topic for me. I have to read and understand the concept of it first. But I think to answer your question there are two (multi)configs: j7-evm and j7-evm-k3r507:35
*** sagner <sagner!> has joined #yocto07:36
*** PaowZ_ <PaowZ_!~Vince@> has joined #yocto07:37
RPThomasD13: right, so you'll probably have mc: j7-evm:<recipename> and mc:j7-evm-k3r5:<recipename> if I remember how they work correctly. One of those may not exist and be the default plain <recipename>07:38
ThomasD13RP, MACHINE=j7-evm-k3r5 u-boot-ti-staging is doing its job! amazing! :D thank you again!07:44
*** rewitt <rewitt!~rewitt@unaffiliated/rewitt> has quit IRC07:44
*** rewitt <rewitt!~rewitt@unaffiliated/rewitt> has joined #yocto07:45
*** manuel1985 <manuel1985!~manuel@> has joined #yocto07:45
*** NiksDev <NiksDev!~NiksDev@> has quit IRC07:47
*** xtron1 <xtron1!~xtron@> has joined #yocto07:48
*** leon-anavi <leon-anavi!~Leon@> has quit IRC07:51
*** xtron <xtron!~xtron@> has quit IRC07:51
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto07:51
Ad0where did tpm2-tss go in zeus and above?07:52
*** kpo__ <kpo__!> has quit IRC07:58
*** kpo__ <kpo__!> has joined #yocto07:59
*** NiksDev <NiksDev!~NiksDev@> has joined #yocto07:59
*** xtron1 is now known as xtron08:01
*** georgem <georgem!~georgem@> has quit IRC08:08
*** georgem <georgem!~georgem@> has joined #yocto08:09
*** davidinux <davidinux!~davidinux@> has quit IRC08:20
*** davidinux <davidinux!~davidinux@> has joined #yocto08:22
*** gsalazar90 <gsalazar90!5e3dbd6b@gateway/web/cgi-irc/> has joined #yocto08:23
*** gsalazar <gsalazar!5e3dbd6b@gateway/web/cgi-irc/> has quit IRC08:23
*** hpsy <hpsy!~hpsy@> has joined #yocto08:26
*** gsalazar90 is now known as gsalazar08:28
*** hpsy <hpsy!~hpsy@> has quit IRC08:38
*** hpsy <hpsy!~hpsy@> has joined #yocto08:39
*** kaspter <kaspter!~Instantbi@> has quit IRC08:41
*** kaspter <kaspter!~Instantbi@> has joined #yocto08:41
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto08:42
*** megabread <megabread!~megabread@2a01:4b00:e031:2600:4a5:d985:3fd8:ec2e> has joined #yocto08:43
ptsnevesHey guys. I had the weirdest issue with the fetcher where wget locks on hsts file. I am thinking of submitting a patch to set the hsts-file=/dev/null, but wanted to hear your opinion it. Basically if many wget instances are trying to update the database wget hangs. We had a case of a hand of several hours.08:49
*** JaMa <JaMa!> has quit IRC08:56
*** JaMa <JaMa!> has joined #yocto08:58
*** JaMa <JaMa!> has quit IRC09:03
*** JaMa <JaMa!> has joined #yocto09:04
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has joined #yocto09:11
*** ykrons <ykrons!~guillaume@> has joined #yocto09:16
*** florian_kc is now known as florian09:19
*** kpo__ <kpo__!> has quit IRC09:32
*** kpo__ <kpo__!> has joined #yocto09:33
*** leon-anavi <leon-anavi!~Leon@> has quit IRC09:51
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto09:51
paulbarkerptsneves: That sounds like a bug in wget. A workaround in bitbake may be needed though depending on what others think10:11
paulbarkerIt'd be worth checking what version of wget you have in your host distro and checking if any relevant changes have been made to wget upstream since then10:12
paulbarkerI'm pretty sure the host's wget is used rather than it being built by bitbake10:12
*** Klanticus <Klanticus!~quassel@> has joined #yocto10:20
ptsnevespaulbarker i tracked it down to an flock line 566.10:28
ptsnevesI think this is still the case. It gets worse though when the home of the user is in a NFS share. NFS shares do not honor flocks so the file may just become corrupted. Besides working around it, i am not sure this is wget's fault :S10:29
paulbarkerflock has worked over NFS for a long time:
ptsnevespaulbarker i misread or read an old manual. Regardless the lock potential is there and it probably is worsened by bad NFS connections10:54
*** RP <RP!~RP@2001:8b0:aba:5f3c:96de:80ff:fe6d:2d2b> has quit IRC10:57
*** dreyna <dreyna!> has quit IRC11:03
paulbarkerptsneves: I think trying to work around bad NFS connections in bitbake would be impossible. But I don't think wget instances should be ending up deadlocked11:04
paulbarkerDo you have any reason to suspect a bad NFS connection in your case? If so I'd try to fix that first, then if deadlocks still occur report it upstream to wget11:06
ptsnevespaulbarker i do indeed, the issue is that NFS share fixing seems to be a complicated topic (of course not your concern :). What we did was work around it by adding FETCHCMD_wget += "--hsts-file=/dev/null"11:08
*** frsc <frsc!> has quit IRC11:09
paulbarkerptsneves: Ok, I'm glad you at least have a local workaround. Personally I don't think that's suitable for carrying in bitbake but others may have different opinions11:10
LetoThe2ndpaulbarker: thou shall not have any opinion! other than mine, at least!!11:11
paulbarkerLetoThe2nd: I've always been a fan of the phrase "When I want your opinion I'll give it to you"11:11
LetoThe2ndpaulbarker: closely related, a famous bavarian satirist once coined the phrase "nobody has to be a minority. everybody can voluntarily join the majority!"11:13
ptsnevespaulbarker i also think it is not suitable. At least it is now in the chat logs so anybody can look for it they want.11:14
ptsnevesLetoThe2nd that is actually a really nice quote :D11:14
LetoThe2ndfor the record, it was
ptsnevesLetoThe2nd can you provide the quote in german? I would like to send to a german colleague :)11:17
LetoThe2ndptsneves: #911:17
LetoThe2ndptsneves: the translation was not 100% exact, but hopefully kept the spirit.11:17
ptsnevesLetoThe2nd Google translate still came up pretty close to what you wrote :)11:21
ptsnevesits also funny because the guy is from Munich11:22
LetoThe2ndwell a lot of people are from Munich11:23
ptsneveseven the minority which is not seems to have the right to join the majority :D11:23
*** berton <berton!~berton@> has joined #yocto11:40
*** Konsgnx <Konsgnx!> has joined #yocto11:42
*** fabatera <fabatera!> has joined #yocto11:45
*** ptsneves <ptsneves!b0dd7824@> has quit IRC11:47
*** leon-anavi <leon-anavi!~Leon@> has quit IRC11:51
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto11:51
*** frsc <frsc!> has joined #yocto11:51
*** frsc <frsc!> has quit IRC11:56
*** elGamal <elGamal!> has quit IRC11:59
*** elGamal <elGamal!> has joined #yocto12:00
*** sagner <sagner!> has quit IRC12:03
*** dv <dv!~dv@> has joined #yocto12:06
dvI am building SDK for my image. It says "FileNotFoundError". What can be wrong?
*** ptsneves <ptsneves!b0dd7824@> has joined #yocto12:10
*** frsc <frsc!> has joined #yocto12:13
*** kaspter <kaspter!~Instantbi@> has quit IRC12:28
*** kaspter <kaspter!~Instantbi@> has joined #yocto12:28
*** kpo__ <kpo__!> has quit IRC12:30
*** kpo__ <kpo__!> has joined #yocto12:31
*** sagner <sagner!> has joined #yocto12:56
*** eduardas <eduardas!~eduardas@> has joined #yocto12:57
fabateraHi! Python version used during build depends on host' python installation? Can I change the python version used during build?13:00
LetoThe2ndfabatera: try to rephrase, please13:02
*** freen <freen!> has joined #yocto13:02
freenwhat is the purpose of the function python() into a .bbclass and how is it called?13:03
ptsnevesfreen the python() function is called at parsing time, at the same time the "regular" metadata bb metada is parsed. If my understanding is correct13:05
fabateraSorry my english is not the best :~13:05
LetoThe2ndfabatera: no problem,I just do not yet understand what your question is13:06
fabateraWhen python functions are executed during build, (e.g /bitbake/lib/bb/ , which python interpreter is used?13:07
freenptsneves do you mean that the python() function is called at parsing time from recipes inheriting it?13:08
LetoThe2ndBitbake itself runs on the host python13:08
freenptsneves I mean recipes inheriting the bbclass13:09
ptsnevesfreen yes as far as i know they are executed at parse time and count for the recipe state before any task is executed13:10
freenptsneves thank you13:11
ptsnevesfor example having a MY_VAR = "1" in the .bbclass is the same as python() { d.setVar("MY_VAR", "1") }13:11
ptsnevesfor the recipe which inherits the class naturally13:11
fabateraLetoThe2nd Thanks! Yes, I was wondering it was on the host. There is a way to change the python version used other than update-alternatives? Maybe only virtualenv13:14
LetoThe2ndfabatera: what is it that you are *actually* trying to archieve? What is your *real* problem?13:15
fabateraThere are python errors during build. I've found that the error is related to the version I have on build server (I fixed some errors to check that). I want to have a python interpreter set13:18
fabatera...only for this build environment. Because the machine is shared13:19
LetoThe2ndfabatera: that is still highly unspecific, but generally people use containers nowadays on problems like that.13:19
*** elGamal <elGamal!> has quit IRC13:20
*** elGamal <elGamal!> has joined #yocto13:21
fabateraLetoThe2nd I don't have the logs available anymore to explain better. But the container should work. Thanks!13:24
*** linums <linums!> has quit IRC13:24
*** linums <linums!~linums@> has joined #yocto13:25
eduardashello, has anyone worked on a Linux-based Zigbee enabled embedded system? does mainline kernel have any kind of support for it?13:28
*** RP <RP!> has joined #yocto13:33
paulbarkerfabatera: If your python version is too old for bitbake chances are you'll have other problems as well. What host distro and version are you using? And which Yocto version are you building?13:35
*** fabatera <fabatera!> has quit IRC13:37
*** fabatera <fabatera!> has joined #yocto13:43
*** RPI_IMX6 <RPI_IMX6!> has joined #yocto13:44
dvI am building SDK for my image. It says "FileNotFoundError". What can be wrong?
RPI_IMX6   Running `rustc --crate-name signal_hook_registry /home/william/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/cargo_home/registry/src/ --error-format=json13:47
RPI_IMX6--json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -Cembed-bitcode=no -C debuginfo=2 -C metadata=935d5c63acc88142 -C extra-filename=-935d5c63acc88142 --out-dir13:47
RPI_IMX6/home/william/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/armv7-unknown-linux-gnueabihf/release/deps --target armv7-unknown-linux-gnueabihf -C13:47
RPI_IMX6linker=/home/william/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/wrappers/ -L13:47
RPI_IMX6dependency=/home/william/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/armv7-unknown-linux-gnueabihf/release/deps -L13:47
RPI_IMX6dependency=/home/william/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/deps --extern13:47
RPI_IMX6arc_swap=/home/william/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/armv7-unknown-linux-gnueabihf/release/deps/libarc_swap-bed3a5c411a41a7b.rmeta --extern13:47
RPI_IMX6libc=/home/william/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/armv7-unknown-linux-gnueabihf/release/deps/liblibc-e8a1de2073893db9.rmeta --cap-lints allow`     Running `rustc --crate-name time13:47
RPI_IMX6/home/william/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/cargo_home/registry/src/ --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C13:47
RPI_IMX6opt-level=3 -Cembed-bitcode=no -C debuginfo=2 -C metadata=2ab97d6e9d94e118 -C extra-filename=-2ab97d6e9d94e118 --out-dir /home/william/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/armv7-unknown-linux-gnueabihf/release/deps --target13:47
RPI_IMX6armv7-unknown-linux-gnueabihf -C linker=/home/william/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/wrappers/ -L13:47
RPI_IMX6dependency=/home/william/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/armv7-unknown-linux-gnueabihf/release/deps -L13:47
RPI_IMX6dependency=/home/william/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/deps --extern13:47
RPI_IMX6libc=/home/william/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/armv7-unknown-linux-gnueabihf/release/deps/liblibc-e8a1de2073893db9.rmeta --cap-lints allow`       Fresh which v3.1.0       Fresh getrandom v0.1.14The following warnings were13:47
RPI_IMX6emitted during compilation:warning: gcc: error: unrecognized command line option ‘-fmacro-prefix-map=/home/william/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1=/usr/src/debug/chirpstack-concentratord/3.0.2-r1’error: failed to run custom build13:47
RPI_IMX6command for `libloading v0.5.2`13:47
RPI_IMX6how to fix it? Please help. Thanks.13:47
eduardasRPI_IMX6: usually a good idea to post losts of lines to pastebin or similar site13:49
eduardasRPI_IMX6: not directly into IRC13:49
RPI_IMX6Ok. Thanks.13:49
eduardasRPI_IMX6: not sure what is going on.. you are using rustc to cross-compile some Rust-based component and doing it via bitbake?13:51
eduardasRPI_IMX6: is meta-rust involved here?13:51
*** fabatera <fabatera!> has quit IRC13:53
eduardasRPI_IMX6: what layers and their versions/branches are you using?13:53
*** sakoman <sakoman!> has joined #yocto13:53
eduardasRPI_IMX6: is the chirpstack-concentratord recipe your own doing? probably would also be a good idea to post that13:54
RPI_IMX6eduardas , I am not familiar with it. just following the instruction with
RPI_IMX6try to bitbake  chirpstack-gateway-os-base13:56
*** ericch <ericch!> has joined #yocto13:57
eduardasRPI_IMX6: here's the recipe I suppose:
eduardasRPI_IMX6: also meta-rust seems to be in use13:57
*** rr123_ <rr123_!~xxiao@> has joined #yocto13:58
eduardasRPI_IMX6: I am not really familair with it but perhaps someone here is13:58
*** sgw <sgw!> has left #yocto13:58
rr123_have not used yocto for a couple years, just refreshed a bit and found there is no musl official support from the oe-core?13:58
RPI_IMX6eduardas ,Thanks for your help.13:59
LetoThe2ndrr123_: huh?13:59
rr123_openwrt/buildroot/alpine...all use musl these days, any plan for yocto to include musl as an official libc?13:59
ThomasD13Can someone describe how to image and machine configuration are related? Has the image configuration a reference which machine configuration should be used, or the other way around?13:59
LetoThe2ndrr123_: you can build with musl right out of the box13:59
rr123_LetoThe2nd: i might be asking the wrong question13:59
rr123_it has been a while for me to work with yocto but it seems I need come back :014:00
rr123_LetoThe2nd: do I need include some meta-musl as google shows? or just change conf to get musl14:00
eduardasRPI_IMX6: no problem, though I suppose I'm not really all that much helpful since it does not look trivial14:01
*** paulg <paulg!> has joined #yocto14:01
RPI_IMX6Is there a way to skip chirpstack-concentratord ? I use bitbake -k chirpstack-concentratord. Does not work.14:02
RPI_IMX6bitbake -k chirpstack-gateway-os-base . Does not skip it also.14:03
rr123_last time i worked with yocto, toast was getting ready, not sure if I should use toast to play with configurations14:03
eduardasRPI_IMX6: I'd really just suggest contacting the original author of the metadata:
LetoThe2ndrr123_: toaster is still a complicated thing14:03
eduardasRPI_IMX6: or posting in GitHub issues:
eduardasthough people may be unresponsive14:04
*** freen <freen!> has left #yocto14:04
rr123_LetoThe2nd: thanks, stopped reading it immediately.14:04
LetoThe2ndrr123_: but building with musl is hopefully as easy as just setting TCLIBC accordingly
LetoThe2ndrr123_: i don't use it often but should be no problem14:04
rr123_I felt yocto is really designed for those BSP vendors(windriver,mentor,etc), not for individuals like me :)14:04
rr123_over-engineering is the word I had in mind then14:05
eduardasrr123_: it is not really all that bad... I hear OpenWrt has much worse documentation14:05
rr123_eduardas: not as good as yocto who had a paid tech writer I think, but openwrt is much simpler for developer to handle14:05
LetoThe2ndrr123_: it all depends on the usecase.14:06
paulbarkerzeddii: Do you know if we're carrying any extra patches in linux-yocto to build perf from Linux 4.19 with gcc 10? greg-kh says it doesn't build in linux-stable 4.19, I wonder if we have anything to suggest14:06
rr123_same as buildroot, yocto you have to find with itself, and very hard to debug when build falls apart, that's what  Iremembered14:06
rr123_to find --> to fight14:07
LetoThe2ndit all depends (TM)14:07
rr123_since yocto is very complex, it's good for consultants indeed as many small players can not master the complexity under deadline pressue14:08
rr123_yocto is nice for big guns to make BSP, anyone here uses it directly to make products?14:08
LetoThe2ndrr123_: sorry, but what do you want to tell us?14:08
rr123_LetoThe2nd: trying to flush old memories and see what changed, i just resumed building sato last night and still reading14:09
paulbarkerrr123_: Sadly having a fully configurable, custom linux distro generator is a complicated problem domain. So any solution will be complex14:09
paulbarkerThe "simpler" solutions are all missing key features IMHO14:09
paulbarkerLot's has changed over the past couple of years though, I'd recommend giving things a try with a clean slate, if you run into any issues feel free to raise them14:10
ThomasD13rr123_, i do.14:10
LetoThe2ndrr123_: if it stops your rambling in which i cannot see any real conversational value, then let me answer your question with: "yes, we are building hw + complete software based on yocto, with a team of 4".14:10
rr123_what are the key features that other distro missing, is there a page for that? really interested? CI build? CVE maintenance? I know meta-layer is the selling point meanwhile it comes with overrides and complexity14:11
zeddiipaulbarker: I don't recall merging them that far back. but let me check.14:11
rr123_really interested? --> really interested.14:11
*** ThomasD13 <ThomasD13!> has quit IRC14:12
LetoThe2ndrr123_: layers, and compliance.14:12
ptsnevesrr123_ bsp support? Extremely small size and boot time14:13
paulbarkerzeddii: I guess maybe not as master & dunfell don't have a recipe for linux 4.19, zeus obviously doesn't have gcc 1014:13
LetoThe2ndrr123_: last time i looked, wrt had literally no way to help me in compliance, e.g. license manifest generation, package exclusion, etc.14:13
rr123_LetoThe2nd: one more question, does your project involve any GUI?(gtk, qt,etc), those x11-alike packages bring yocto to a new level for me14:13
ptsnevesby the way i have a product with a completely maintained yocto ditro just by me14:14
ptsnevessupport 3 different boards14:14
LetoThe2ndrr123_: we do guis, yes, but no public framework in use for it.14:14
rr123_ptsneves: thanks, that must mean uclibc or musl then, with openwrt I can have 8MB images with quite a lot packages loaded14:14
rr123_LetoThe2nd: i see, something like sdl2 which is lighter.14:14
rr123_one more question, what about opkg vs rpm? from openwrt/buildroot/debian world I would like to use opkg, is it somehow tested by yocto's build/CI nightly build, or for non-rpm package, users are on their own?14:15
eduardasrr123_: I worked only for small OEMs and I can say that Yocto is ok even for them... companies with not more than 100 employees14:16
paulbarkerrr123_: If it's in oe-core it's expected to work. Yes, opkg is tested14:16
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC14:16
rr123_thanks guys, sorry for the tone, was in a hurry to get back to yocto14:17
eduardasrr123_: the problem is more of a cultural one... management not wanting engineers to spend time reading lots of docs14:17
paulbarkerrr123_: openwrt has major bugs in their opkg fork still unfixed after I reported them in 201314:17
paulbarkerI wouldn't put openwrt within a mile of a real product14:17
*** otavio <otavio!~otavio@debian/developer/otavio> has quit IRC14:17
rr123_i think opkg was updated in openwrt already14:18
eduardaspaulbarker: tell that to 8devices, Qualcomm, Ubiquity, etc. :)14:18
eduardasthere is also some hard forking going on with it14:18
eduardassince OpenWrt does not really support an agent for A/B update scheme out of the box14:19
paulbarkerI prefer my package manager not to silently ignore archive extraction errors14:19
*** lxc <lxc!> has joined #yocto14:20
eduardaspaulbarker: IIRC the opkg maiantainer in OE said he would be willing to help merge upstream opkg with OpenWrt opkg to consolidate the effort14:20
*** fabatera <fabatera!> has joined #yocto14:20
eduardasI wonder whether that went anywhere14:21
rr123_I saw eduradas in openwrt-devel channel, haha14:21
paulbarkereduardas: I made that offer back when I was opkg maintainer14:21
paulbarkerIt went nowhere14:21
lxcsdk contains gcc for cross-compile to target, what would be the way to add gcc x86 toolchain to the sdk as well?14:21
rr123_paulbarker: thanks for the git url14:21
eduardasrr123_: I am tuned in to all channels that have anything in common with embedded Linux :)14:21
*** fl0v0 <fl0v0!> has quit IRC14:21
* paulbarker shuts up about openwrt14:22
rr123_eduardas: openwrt,buildroot,yocto,musl...14:22
qschulzrr123_: BTW, openwrt uses a very old fork of Buildroot and AFAIR, they were trying hard to go back to upstream Buildroot14:22
rr123_qschulz: yes the buildroot is a bit out of date, though still OK to use14:22
rr123_unlike yocto which is LF project, or buildroot which has a company backing it up, openwrt is purely volunteers14:23
qschulzrr123_: who backs up buildroot?14:23
eduardasrr123_: there is the Prpl Foundation that kind of seeks to productize OpenWrt... Qualcomm, Ubiquity are part of it14:24
dvI am building SDK for my image. It says "FileNotFoundError". What can be wrong?
rr123_qschulz: well not officially but I think bootlin is taking the lead?14:24
eduardasrr123_: they still have conferences, you can take a look at their videos on Youtube, but I am not sure where this is going14:24
rr123_eduardas: yeah, sadly mips is not doing well14:24
qschulzrr123_: nope. Bootlin sponsored a bit of a few events, sponsors a **bit** of Thomas time IIRC but nothing else14:25
rr123_eduardas: i'm a heavy openwrt users for years14:25
rr123_can't type in the morning14:25
qschulzrr123_: (I worked for Bootlin for three years, can trust me on this one ;) )14:26
rr123_qschulz: cool, full discolure i worked at ubiquiti ;)14:26
rr123_both buildroot and yocto have great docs, comparing to openwrt14:27
rr123_both buildroot/yocto are bsp, openwrt is pretty a ready-to-go customizable product as it has a web-ui14:28
eduardasrr123_: meta-openwrt saves the day? :D14:30
eduardasstealing all the nice OpenWrt components14:31
eduardasincluding web-ui14:31
eduardasthough I wonder whether anyone ever used for a router or similar product14:32
manuel1985I would like to write an append to the recipe which creates /lib/systemd/system/getty.service, but I couldn't yet find out which recipe to append to. Explained everything here, has anyone any ideas?
qschulzmanuel1985: well, it's systemd, you've found it with oe-pkgdata-util14:32
rr123_eduardas: that's an interesting one, thanks14:33
rr123_i'm actually going to check that out14:33
*** linums <linums!~linums@> has quit IRC14:33
qschulzmanuel1985: so generated by systemd itself, you'd need to patch the source beofre compilation or replace it in a do_install with yours14:35
*** linums <linums!> has joined #yocto14:35
rr123_is running systemd on, say 16MB flash board a good idea? so far I have not used systemd for that, also I don't want to push yocto towards a slightly-smaller gentoo distro14:36
eduardasrr123_: well, at the very least you can reduce its size via configuration14:37
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto14:37
eduardasrr123_: I personally always use it, lthough not on a 16MB flash14:37
manuel1985qschulz: I see, thank you!14:38
paulbarkerrr123_: RAM may be your constraint with systemd more so than flash size14:38
fabaterapaulbarker LetoThe2nd The problem was host's python version indeed. I'm in Dunfell but changed poky layer to master (to take a look on linux5.8 recipe), and left on master. Then, the python build error started during do_unpack: "Exception: TypeError: '_sre.SRE_Match' object is not subscriptable". Python 3.5 is installed.14:39
rr123_while i just restarted the study of yocto, i'm sure there are other "official" alternatives to systemd for space-constrained devices, sysvinit or something, will find out14:39
eduardasrr123_: my motivation for systemd is whether I want non-embedded Linux people to understand my system more easily14:40
* rr123_ did not realize systemd is memory 'hungry', e.g. a system with 64MB RAM14:40
qschulzrr123_: of course there is support for sysvinit, we use it here14:40
eduardasrr123_: my system with the least RAM has 512 MB to be honest14:41
eduardasrr123_: so I've been spoiled by not really being forced to care14:42
JaMajonmason: around?14:42
rr123_looks like lots of fun ahead, thanks folks. My comfort zone is 16MB-flash/64~128MB RAM. Whenever I had to work on android stuff its emmc space + 8GB RAM blows me away14:42
jonmasonJaMa: yes14:43
JaMajonmason: can you check the new tune files if I give you partial tune-test results? There are quite a few and it would be better to fix before finishing the script to run14:44
JaMajonmason: see the log.* files in
JaMaor short version here
*** linums <linums!> has quit IRC14:45
JaMathat's already with the 2 fixes from me and peter applied14:46
jonmasonyeah, if you wanna spam meta-arm mailing list, I'll do the cleanups14:46
jonmasonIs this script upstreamed?14:47
*** linums <linums!> has joined #yocto14:47
JaMajonmason: it's not on oe-core/master14:47
* zeddii hands jonmason a mop14:47
jonmasonI have a few more tunes coming.  Just thinking it would be good to run this against them to prevent any more stupid errors on my part14:48
JaMaRP asked to convert it to selftest test which should be better than this naive shell script, but I haven't got to it yet (and not sure when will)14:48
JaMajonmason: you can cherry-pick it from that jansa/tune-test branch14:48
jonmasonwill do14:48
JaMain previous run, I had it restricted to vfp4 tunes which I was testing last time (few years back) and when it finished so quickly I was assuming it's the new build server being fast :)14:49
JaManow it's significanly slower (doing 4/76 MACHINE, because these arm ones have like 150 availtunes)14:50
*** fabatera <fabatera!> has quit IRC14:50
jonmasonyeah, its a bit ugly now14:51
jonmasonI want to clean up the tunes infra a bit, but haven't had the time yet.14:52
*** fl0v0 <fl0v0!> has joined #yocto14:54
*** eduardas <eduardas!~eduardas@> has quit IRC14:57
*** NiksDev <NiksDev!~NiksDev@> has quit IRC14:57
*** cccrow <cccrow!> has joined #yocto15:00
*** maudat <maudat!> has joined #yocto15:01
*** cccrow <cccrow!> has quit IRC15:01
*** cccrow <cccrow!> has joined #yocto15:01
*** vmeson <vmeson!> has quit IRC15:03
*** linums <linums!> has quit IRC15:09
*** linums <linums!> has joined #yocto15:09
*** linums <linums!> has quit IRC15:10
*** linums <linums!~linums@> has joined #yocto15:10
*** fl0v0 <fl0v0!> has quit IRC15:15
*** camus1 <camus1!~Instantbi@> has joined #yocto15:15
*** NiksDev <NiksDev!~NiksDev@> has joined #yocto15:15
*** kaspter <kaspter!~Instantbi@> has quit IRC15:16
*** camus1 is now known as kaspter15:16
*** tgamblin_ <tgamblin_!> has joined #yocto15:26
*** tgamblin <tgamblin!> has quit IRC15:27
*** tgamblin_ is now known as tgamblin15:29
*** manuel1985 <manuel1985!~manuel@> has left #yocto15:30
*** cccrow <cccrow!> has quit IRC15:30
*** mckoan is now known as mckoan|away15:33
*** RPI_IMX6 <RPI_IMX6!> has quit IRC15:36
*** linums <linums!~linums@> has quit IRC15:44
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC15:46
*** chris_ber <chris_ber!~quassel@> has quit IRC15:47
*** linums <linums!> has joined #yocto15:49
*** ptsneves <ptsneves!b0dd7824@> has quit IRC16:00
*** jrdn <jrdn!> has joined #yocto16:04
jrdnIs there a reason why my -dbg packages aren't being populated in the esdk?  They populate fine for my image in a full bitbake install but the generated esdk has the -dbg packages with an empty usr/lib16:06
*** nrossi <nrossi!nrossimatr@gateway/shell/> has left #yocto16:07
*** sagner <sagner!> has quit IRC16:08
moto-timoLetoThe2nd: Things grow in Oregon16:14
*** jobroe <jobroe!> has quit IRC16:30
*** linums <linums!> has quit IRC16:37
*** goliath <goliath!> has quit IRC16:41
*** megabread <megabread!~megabread@2a01:4b00:e031:2600:4a5:d985:3fd8:ec2e> has quit IRC16:42
*** RP <RP!> has quit IRC16:48
ecdheMy build products all end up in ${DEPLOY_IMAGE_DIR}.  I'd like to move 3-4 of these (e.g, Image, uboot.scr) into a directory called ${DEPLOY_IMAGE_DIR}/fat.  What's the best way to do that?  Initially, I tried to add a .bbappend that extended the kernel recipe and the U-Boot recipe with a do_deploy_append(), but then I read that you're not supposed to directly copy files into ${DEPLOY_IMAGE_DIR} because it16:49
ecdhebypasses sstate cache. Is there a better way to do this?  Or are subdirectories in ${DEPLOY_IMAGE_DIR} not recommended?16:49
*** RP <RP!~RP@2001:8b0:aba:5f3c:96de:80ff:fe6d:2d2b> has joined #yocto16:50
*** rabbit9911 <rabbit9911!> has joined #yocto16:52
rabbit9911Can you override do_install_append rules listed in the bb file from a bbappend file?  The same question for appended variables like SRC_URI_append in the bb file as well.16:55
*** dreyna <dreyna!~dreyna@2601:646:4201:e280:d40b:f024:230:36d> has joined #yocto16:59
*** dreyna <dreyna!~dreyna@2601:646:4201:e280:d40b:f024:230:36d> has quit IRC17:04
*** fitzsim <fitzsim!> has joined #yocto17:07
kergothrabbit9911: both are still going to be there, but yours will run after the other.17:07
denixecdhe: you should use DEPLOYDIR instead17:10
*** sgw <sgw!> has joined #yocto17:12
*** vmeson <vmeson!> has joined #yocto17:14
*** frsc <frsc!> has quit IRC17:18
*** otavio <otavio!~otavio@> has joined #yocto17:18
*** otavio <otavio!~otavio@debian/developer/otavio> has joined #yocto17:18
*** vineela <vineela!vtummala@nat/intel/x-gbropfphtqgbjwnh> has joined #yocto17:19
*** dexterlb <dexterlb!~dexterlb@2a01:9e40:2:2::2> has quit IRC17:32
*** dexterlb <dexterlb!~dexterlb@2a01:9e40:2:2::2> has joined #yocto17:33
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has quit IRC17:43
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC17:48
*** mihai- <mihai-!~mihai@unaffiliated/mihai> has joined #yocto17:50
*** w00die <w00die!~w00die@> has quit IRC17:51
*** mihai <mihai!~mihai@unaffiliated/mihai> has quit IRC17:53
*** w00die <w00die!~w00die@> has joined #yocto17:53
*** goliath <goliath!> has joined #yocto17:58
*** xtron <xtron!~xtron@> has quit IRC18:01
mischiefdoes anyone know how DBUS_SESSION_BUS_ADDRESS is supposed to get into systemd's environment in yocto? it's not present on my zeus build.18:01
jrdnmischief: export $(dbus-launch) ?18:04
jrdnworks for me when connected over ssh e.g.18:05
*** manuel1985 <manuel1985!> has joined #yocto18:15
*** hpsy <hpsy!~hpsy@> has quit IRC18:19
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has quit IRC18:23
*** rabbit9911 <rabbit9911!> has quit IRC18:26
ecdhedenix: I read that.  But I'd like to make a sub directory, will that get copied over?18:32
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has joined #yocto18:45
*** NiksDev <NiksDev!~NiksDev@> has quit IRC18:57
*** xtron <xtron!~xtron@> has joined #yocto18:59
*** rcoote <rcoote!> has quit IRC19:12
*** hpsy <hpsy!~hpsy@> has joined #yocto19:16
*** kiwi_29 <kiwi_29!> has joined #yocto19:33
*** kanavin_home <kanavin_home!~ak@> has quit IRC19:39
*** goliath <goliath!> has quit IRC19:45
*** kanavin_home <kanavin_home!~ak@2a02:2450:1011:4f7:596d:bf31:3950:5bda> has joined #yocto19:54
jrdndoes SDKIMAGE_FEATURES not apply to the extensible sdk?  Trying to sort out why the -dbg packages are empty in packages-split20:02
*** alican <alican!> has joined #yocto20:06
*** creich <creich!> has quit IRC20:09
*** creich <creich!> has joined #yocto20:10
*** feddischson <feddischson!> has quit IRC20:11
*** Ox861726f6c64 <Ox861726f6c64!~Ox861726f@gateway/tor-sasl/ox861726f6c64> has joined #yocto20:12
khemSDKIMAGE_FEATURES is only for traditional SDK20:22
*** dv <dv!~dv@> has quit IRC20:23
*** goliath <goliath!> has joined #yocto20:26
RPmoto-timo: I'm around if you want to talk...20:30
*** khem <khem!~khem@unaffiliated/khem> has quit IRC20:43
*** kaspter <kaspter!~Instantbi@> has quit IRC20:44
*** kaspter <kaspter!~Instantbi@> has joined #yocto20:45
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto20:48
*** pohly <pohly!> has quit IRC20:53
*** alican <alican!> has quit IRC20:56
*** kiwi_29 <kiwi_29!> has quit IRC21:00
*** kiwi_29 <kiwi_29!> has joined #yocto21:02
*** Konsgnx <Konsgnx!> has quit IRC21:04
*** kiwi_29 <kiwi_29!> has quit IRC21:06
*** kiwi_29 <kiwi_29!> has joined #yocto21:11
*** berton <berton!~berton@> has quit IRC21:15
*** xtron <xtron!~xtron@> has quit IRC21:17
*** ssajal <ssajal!> has quit IRC21:17
*** alejandrohs <alejandrohs!~alejandro@2605:6000:1306:9479::a59> has joined #yocto21:22
*** kaspter <kaspter!~Instantbi@> has quit IRC21:31
*** kaspter <kaspter!~Instantbi@> has joined #yocto21:33
*** agust <agust!> has quit IRC21:33
*** lxc <lxc!> has quit IRC21:42
*** kiwi_29 <kiwi_29!> has quit IRC21:42
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has quit IRC21:43
*** dreyna <dreyna!> has joined #yocto21:43
*** kiwi_29 <kiwi_29!> has joined #yocto21:43
*** Ox861726f6c64 <Ox861726f6c64!~Ox861726f@gateway/tor-sasl/ox861726f6c64> has quit IRC22:09
*** rsalveti <rsalveti!uid117878@gateway/web/> has quit IRC22:11
*** diamondman <diamondman!sid306859@gateway/web/> has quit IRC22:12
*** rsalveti <rsalveti!uid117878@gateway/web/> has joined #yocto22:13
*** ric96 <ric96!sid234506@gateway/web/> has quit IRC22:14
*** diamondman <diamondman!sid306859@gateway/web/> has joined #yocto22:15
*** jrdn <jrdn!> has quit IRC22:15
*** ric96 <ric96!sid234506@gateway/web/> has joined #yocto22:16
*** vmeson <vmeson!> has quit IRC22:16
*** vmeson <vmeson!> has joined #yocto22:16
*** manuel1985 <manuel1985!> has quit IRC22:17
*** netrace <netrace!~netrace@unaffiliated/netrace> has joined #yocto22:18
*** camus1 <camus1!~Instantbi@> has joined #yocto22:21
*** kaspter <kaspter!~Instantbi@> has quit IRC22:22
*** camus1 is now known as kaspter22:22
*** kanavin_home <kanavin_home!~ak@2a02:2450:1011:4f7:596d:bf31:3950:5bda> has quit IRC22:36
*** beneth` <beneth`!> has left #yocto22:42
*** yann <yann!~yann@> has quit IRC22:47
*** laurittr <laurittr!> has quit IRC23:01
*** laurittr <laurittr!> has joined #yocto23:08
*** kiwi_29 <kiwi_29!> has quit IRC23:18
*** Klanticus <Klanticus!~quassel@> has quit IRC23:21
*** vineela <vineela!vtummala@nat/intel/x-gbropfphtqgbjwnh> has quit IRC23:23
*** ssajal <ssajal!> has joined #yocto23:34
*** ericch <ericch!> has quit IRC23:35
*** kaspter <kaspter!~Instantbi@> has quit IRC23:37
*** camus1 <camus1!~Instantbi@> has joined #yocto23:37
*** camus1 is now known as kaspter23:40
*** kiwi_29 <kiwi_29!> has joined #yocto23:49
*** kiwi_29 <kiwi_29!> has quit IRC23:58
*** maudat <maudat!> has quit IRC23:59
*** kiwi_29 <kiwi_29!> has joined #yocto23:59

Generated by 2.17.2 by Marius Gedminas - find it at!