qschulz has quit [Remote host closed the connection]
qschulz has joined #yocto
<khem>
rburton: core-image-ptest-python3-numpy has failures for me when running on armhost and targetting qemuarm64, this is with clang, but it works ok for qemux86-64
sakoman has quit [Ping timeout: 252 seconds]
jclsn has quit [Ping timeout: 272 seconds]
jclsn has joined #yocto
Articulus5 has joined #yocto
sakoman has joined #yocto
Articulus has quit [Read error: Connection reset by peer]
Articulus5 has quit [Remote host closed the connection]
Articulus5 has joined #yocto
Vonter has quit [Ping timeout: 245 seconds]
Vonter has joined #yocto
jmd has joined #yocto
HarishSadineni62 has joined #yocto
HarishSadineni62 has quit [Client Quit]
rob_w has joined #yocto
goliath has joined #yocto
Guest21 has joined #yocto
vthor has quit [Remote host closed the connection]
savolla has joined #yocto
Guest21 has quit [Ping timeout: 276 seconds]
frieder has joined #yocto
ok4nd has joined #yocto
Jones42 has joined #yocto
Kubu_work has quit [Ping timeout: 265 seconds]
ok4nd has quit [Quit: Client disconnecting]
kanavin has joined #yocto
zkrx has quit []
zkrx has joined #yocto
<mathieudb>
khem: I do not know what I did with the glibc upgrade patch. I clearly remember this one, as I had a very small conflict to fix, yet it looks like it was never in my branch. Taking it now
vermaete has joined #yocto
<vermaete>
Is there a reason to have and SRCREV and SRC_URI[sha256] in a recipe?
<dvergatal>
hi all is it possible to run target machine image in qemu with teh usage of runqemu described in the manual https://docs.yoctoproject.org/dev-manual/qemu.html or do I have to modify the image for qemu?
<khem>
dvergatal:well, kernel configured for targt might not work on qemu right away
<khem>
so you might have to look for defconfig option differences
<dvergatal>
khem: it still shouts that i don't have qemuboot.conf
Jones42 has joined #yocto
<khem>
ah yes, runqemu depends on some scripts and configurations that are built when a target is a qemu based machine
<khem>
see meta/conf/machine/include/qemu.inc
<khem>
I think it might not work out of box for non-qemu machines
<dvergatal>
yeah this is what i thought
<dvergatal>
i will have to create a separate machine config for that purpouse
druppy has joined #yocto
Jones42 has quit [Ping timeout: 260 seconds]
druppy has quit [Quit: druppy]
druppy has joined #yocto
druppy has quit [Ping timeout: 248 seconds]
<dvergatal>
ok building new machine image and will than work on adjusting kernel config for qemu
goliath has quit [Quit: SIGSEGV]
leon-anavi has quit [Remote host closed the connection]
jmd has quit [Remote host closed the connection]
<rburton>
khem: I’m on holiday now, pester jonmason :)
dmoseley_ has joined #yocto
dmoseley has quit [Ping timeout: 276 seconds]
<jonmason>
what did rburton break?
<RP>
jonmason: everything :) Looking forward to your help!
* jonmason
channels my best rburton with "burn it down!"
<RP>
jonmason: you need to increase your number of nearly finished branches too :)
<RP>
JPEW: one thing which puzzles me - why doesn't the bb.utils.join_deps() call trigger errors?
<JPEW>
RP: Huh, that is a good question
<jonmason>
only 33 WIP branches for meta-arm, not nearly enough
<JPEW>
RP: Or explode_deps_versions2 for that matter
<khem>
in meta-clang -mbranch-protection=standard is removed from TUNE_CCARGS ( for a different reason ) but we do not see this problem when building with meta-clang due to this
<khem>
however, if I use clang just with oe-core and set TC_CXX_RUNTIME = "llvm" and build say systemd for qemuarm64 then we see the problem
<khem>
rburton's clang cleansup have regressed some bits as well sadly, but not too badly, I am sending couple of patches for that