<khem>
oh well, scarthgap does not yet have go backported
mathieudb has quit [Ping timeout: 272 seconds]
mathieudb has joined #yocto
mathieudb has quit [Changing host]
mathieudb has joined #yocto
_whitelogger has joined #yocto
mckoan|away has quit [Read error: Connection reset by peer]
mckoan|away has joined #yocto
Daanct12 has joined #yocto
AtleoS has quit [Quit: AtleoS]
vvn has joined #yocto
_whitelogger has joined #yocto
jmd has joined #yocto
jmd has quit [Remote host closed the connection]
Articulus has joined #yocto
PeterM has joined #yocto
goliath has joined #yocto
savolla has joined #yocto
PeterM has quit [Ping timeout: 240 seconds]
PeterM has joined #yocto
PeterM has quit [Client Quit]
zeemate has joined #yocto
frieder has joined #yocto
savolla has quit [Quit: WeeChat 4.4.3]
savolla has joined #yocto
Chaser has joined #yocto
MarcWeDLM has joined #yocto
mckoan|away is now known as mckoan
<bjdooks>
khem: yeah, we're a little stuck at the moment as the spec's been out for a while but it hasn't got quite yet to the point where anyone has actual hardware out... which has been making linux-kernel, qemu and other bits rather difficult to sort. I've been testing with buildroot, but we still have a few bugs so
frgo has joined #yocto
alperak has joined #yocto
kpo has joined #yocto
rfuentess has joined #yocto
Wouter0100 has quit [Quit: Ping timeout (120 seconds)]
Wouter0100 has joined #yocto
Chaser has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
leon-anavi has joined #yocto
wooosaiiii has quit [Ping timeout: 260 seconds]
wooosaiiii has joined #yocto
wooosaiiii has quit [Ping timeout: 248 seconds]
wooosaiiii has joined #yocto
berton has joined #yocto
florian has joined #yocto
kpo has quit [Ping timeout: 268 seconds]
Chaser has joined #yocto
michaelo has quit [Ping timeout: 265 seconds]
michaelo has joined #yocto
<dvergatal>
hi how can i check if MACHINEOVERRIDES contains value? because bb.utils.contains does work... ;/
<mcfrisk>
RP: is there some issue with "oeqa selftest: read qemu options from TEST_RUNQEMUPARAMS" in master-next? It's been there a while but not gone to master
<dvergatal>
i meant doesn't work
<mcfrisk>
dvergatal: bitbake -e recipe, then check the variables and end effect with all overrides applied.
<dvergatal>
mcfrisk: no this is not what i wanted to do
<dvergatal>
mcfrisk: what i want to achieve is to check if MACHINE is in MACHINEOVERRIDE specific group
<dvergatal>
and for that purpouse i have created such group and added it in multiple MACHINEOVERRIDE vars for some machines but now i would like to check this variable MACHINEOVERRIDE if it contains this specified group but the list is separated with `:` sign and thus bb.utils.contains function will not work
<RP>
mcfrisk: I need to write a reply about that one, it isn't an easy reply to write :/
<mcfrisk>
dvergatal: if it's a bitbake variable, then bitbake -e will show it and how it was constructed. This includes MACHINE and MACHINEOVERRIDES. Maybe the code you debug isn't visible there but end results are.
<mcfrisk>
RP: so slirp no good and testing should use tap devices? I find slirp easy to use and it works in a lot of environments and uses, well mostly ssh into qemu machine
<dvergatal>
mcfrisk: i know i see this variable and it looks like this MACHINEOVERRIDES="eg500all:eg500-hw:dido:eg-x86-64:eg500"
<dvergatal>
so strings are ':' separated
<dvergatal>
hmmmm i'm doing it wrong instead of MACHINEOVERRIDES i should use MACHINE_FEATURES....
<RP>
mcfrisk: now I'm kind of forced into writing the reply or discussing here :/
rfuentess has quit [Remote host closed the connection]
<bhstalel>
khem are you planning to present the clang work in the next summit ? cuz if not, I am planning to do it as a continuation of my previous summit topic "The story of Yocto toolchain"
ablu has quit [Ping timeout: 252 seconds]
ablu has joined #yocto
zeemate has quit [Ping timeout: 276 seconds]
mckoan is now known as mckoan|away
rfuentess has joined #yocto
belsirk has joined #yocto
rfuentess has quit [Ping timeout: 248 seconds]
Xagen has quit [Ping timeout: 252 seconds]
cyxae has joined #yocto
bhstalel has quit [Ping timeout: 240 seconds]
Xagen has joined #yocto
Xagen has quit [Ping timeout: 260 seconds]
020ABA3XB is now known as vmeson
zeemate has joined #yocto
michaelo has quit [Quit: leaving]
jmd has joined #yocto
michaelo has joined #yocto
michaelo has quit [Client Quit]
Daanct12 has quit [Quit: WeeChat 4.6.3]
dgriego has quit [Quit: Bye]
dgriego has joined #yocto
goliath has quit [Quit: SIGSEGV]
Xagen has joined #yocto
<rburton>
kanavin: re 997d54363a3cb3a0e949b3626855f2fa41afeb2b, think we can revert that now?
<rburton>
(python3-native isn't actually a needed dependency, and rebuilding rust because python got a rebuild gets very boring very quickly)
<rburton>
kanavin: also makes me want to build busybox-native so we can have a native sh that is isolated entirely from the host
florian has quit [Quit: Ex-Chat]
mbulut has joined #yocto
savolla has quit [Quit: WeeChat 4.4.3]
frieder has quit [Remote host closed the connection]
<rburton>
msg JPEW
<rburton>
damnit irc
<fray>
lol
belsirk has quit [Remote host closed the connection]
mbulut has quit [Ping timeout: 272 seconds]
florian has joined #yocto
<Saur>
khem: I just checked and the Go applications we have report the source files just fine via `dwarfsrcfiles`, so it seems it is just Rust that has the problem...
<khem>
Saur: I see, thats good to know. Perhaps means specific to rust compiler hopefully something small to address
<khem>
RP: should I move all TOOLCHAIN assignments to respective recipes and just not have default-toolchains.inc at all?
<RP>
khem: I think that might be the best way forward
<RP>
I'm not against the file but I'm not sure we need it
<patersonc>
Evening all. I'd like to submit a fix to a recipe in meta-oe Walnascar. Do I just submit a patch based on Walnascar? Or do I submit it based on master and then backport to Walnascar? Or submit to both at the same time?
cyxae has quit [Quit: cyxae]
<khem>
patersonc:if master needs it then it goes into master and then backported to release branches you can submit same time
<khem>
with subject line prefixed with branchname [branch][meta-oe][PATCH]: .....