10:12 <Guest58> Hello, What are the equivalent package's PR for DISTRO and MACHINE conf files?

10:51 <RP> Guest58: there isn't anything equivalent, that wouldn't make sense

11:04 <Guest58> RP how do you trace changes in DISTRO or MACHINE config file?

11:05 <Guest58> +s

11:05 <RP> Guest58: the task signatures (hashes) reflect them

11:09 <Guest58> ok thank you

18:17 <Tyaku_> Hello, I am building a RUSTC package, and I have this error: error: linker `cc` not found    (https://pastebin.com/x9cvzxpK) did you know how to solve it ? some depends to a recipe providing cc native ?

18:48 <dario> what does your recipe look like? are you using any of the rust/rust-common/cargo classes?

19:01 <Tyaku_> This is my recipe:

19:01 <Tyaku_> https://pastebin.com/BTyGfx05

19:02 <Tyaku_> inherit cargo cargo-update-recipe-crates

19:08 <Tyaku_> rustc language sucks, really. It's all a mess to implement rust things in yocto.

19:16 <Tyaku_> I found a discussion about all these magic things here: https://lore.kernel.org/all/AM9PR09MB46425FBA22E1F732F504C397A84D9@AM9PR09MB4642.eurprd09.prod.outlook.com/

19:16 <Tyaku_> Someone made a patch in b/meta/conf/bitbake.conf to add "cc" in HOSTTOOLS variable.

19:16 <Tyaku_> I'm going to try it..

19:26 <Tyaku_> https://pastebin.com/Ty39fuVp     By cc in HOSTTOOLS, I have now a new error.. "arm-poky-linux-gnueabi-gcc: error: unrecognized command-line option '-m64'"  or thread 'main' panicked at 'execution failed', /home/mathieu/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/build.rs:656:9

19:55 <Tyaku_> If someone have a lot of free time :-), please can you try to make a recipe to build mitmproxy and put it in meta-python. I can share some base, but I don't realy know how "good" it is, as currently it's a lot of funky stuffs due to all these rusty thngs.

19:56 <Tyaku_> *And my understanding of this (deprecated?) language

20:44 <Tyaku_> https://pastebin.com/uxw7PM0m Any ideas about this error ? ring v0.16.20 is a dependency of mitmproxy-rs (what i try to build)

20:45 <Tyaku_> When we search on google with just "ring v0.16.20" we find the error.. It seems like a cross compiling issue. People says, you just have to do "sudo apt install musl-tools. In yocto I don't know.

21:08 <Tyaku_> arm-poky-linux-gnueabi-gcc: error: unrecognized command-line option '-m64'

21:09 <Tyaku_> I think there is a missmatch in the cargo's or rusty things. To build the dependencies it see this target: x86_64-unknown-linux-gnu

21:09 <Tyaku_> But I am building for a 32bit ARM (armv7)

21:17 <Xogium> hi :) totally new to yocto here and I run into a bit of a snag trying to follow the quick build buide with poky. I try to compile yocto codename mickledore and I run into this. Does that ring a bell ? https://paste.xogium.me/WI.txt

21:18 <Xogium> *quick build guide, sorry

21:18 <Xogium> fyi I run archlinux as the host

21:19 <Xogium> kirkstone earlier worked fine, but mickledore, nop

21:24 <LetoThe2nd> Xogium: well, as you already mention it - does it reproduce on a supported distro? ;-)

21:24 <Xogium> I was planning on using the latest release but the layer for stm32mp1 hasn't been updated by st yet

21:25 <Xogium> LetoThe2nd: I am not sure. Can I get away with just making a basic systemd-nspawn container to check this out, or does it require a full vm ?

21:26 <LetoThe2nd> Xogium: container should do fine

21:26 <Xogium> I'd be surprised if it does, granted. Otherwise I assume more people would have asked that same question

21:27 <Xogium> does yocto compile its own perl or does it uses the one from the host ?

21:28 <Xogium> for what it's worth I come from the buildroot world, so at the very least I am not a total newb when it comes to custom build of embedded linux

21:28 <Xogium> but I'm trying to figure out buildroot vs yocto still

21:28 <LetoThe2nd> Xogium: well, there are also occasionally bugs and hiccups in supported distros, so i would not necessarily be surprised. but if it reproduces, then i'd say "file a bug, this should legitimately be addressed", and otherwise its more like "good luck" ;-)

21:29 <LetoThe2nd> Xogium: almost certainly builds its own, but of course it depends a bit on the context.

21:30 <Xogium> right

21:31 <Xogium> I think I know why st hasn't updated yet, they only target lts releases

21:32 <LetoThe2nd> Xogium: it always depends. there's good reasons for staying on HEAD, there's reasons to stick with LTS only.

21:33 <Xogium> your lts seem to have a much longer life support than buildroot's

21:33 <Xogium> 5 years, I think ?

21:33 <LetoThe2nd> Xogium: 4 years. don't know about the BR one

21:33 <Xogium> only one year

21:33 <Xogium> stable last only 3 months

21:34 <LetoThe2nd> Xogium: its always a matter of usecase and resources.

21:34 <Xogium> yeah

21:35 <Xogium> I'm only getting started, so I might ask very dumb questions along the way ;p

21:39 <LetoThe2nd> Xogium: thats no problem. just be aware of a bunch of very basic things. 1) most of the yocto devs do stuff at work time. hence, EU/US office times are good times to ask, others not so much. right now, very bad, its just coincidence I am around. 2) BR vs. Yocto is very similar in some things, very different in others. as a basic rule of thumb, BR is "give me a usable filesystem, don't overcomplicate it" and Yocto is "make it

21:39 <LetoThe2nd> reproducible and customizable first". 3) recipe data is local, configuration data is global 4) tmp is transient data :-)

21:44 <Xogium> all good. I am in EU too. I just got my schedule all messed up by now, that's christmas for you

21:45 <LetoThe2nd> Xogium: have fun, then!

21:45 <Xogium> thanks !