vmeson has quit [Remote host closed the connection]
vmeson has joined #yocto
vvn has joined #yocto
enok has quit [Ping timeout: 248 seconds]
florian has quit [Ping timeout: 248 seconds]
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
starblue has quit [Ping timeout: 265 seconds]
davidinux has quit [Ping timeout: 260 seconds]
davidinux has joined #yocto
starblue has joined #yocto
jwinarsk has quit [Quit: Connection closed for inactivity]
qschulz has quit [Quit: qschulz]
qschulz has joined #yocto
davidinux has quit [Ping timeout: 252 seconds]
davidinux has joined #yocto
Guest47 has joined #yocto
Guest47 has quit [Client Quit]
Xagen has joined #yocto
prabhakalad has quit [Ping timeout: 272 seconds]
ptsneves has joined #yocto
<khem>
halstead:is AB under maintenance right now ?
jclsn has quit [Ping timeout: 272 seconds]
jclsn has joined #yocto
ptsneves has quit [Ping timeout: 260 seconds]
vvn has quit [Quit: WeeChat 4.5.2]
davidinux has quit [Ping timeout: 244 seconds]
starblue has quit [Ping timeout: 248 seconds]
starblue has joined #yocto
davidinux has joined #yocto
starblue has quit [Ping timeout: 265 seconds]
starblue has joined #yocto
hoyes has quit [Ping timeout: 260 seconds]
michaelo has quit [Ping timeout: 260 seconds]
michaelo has joined #yocto
hoyes has joined #yocto
Minvera has quit [Remote host closed the connection]
Minvera has joined #yocto
Minvera has quit [Ping timeout: 252 seconds]
fray has quit [Ping timeout: 268 seconds]
fray has joined #yocto
enok has joined #yocto
enok has quit [Client Quit]
enok has joined #yocto
neverpanic has quit [Ping timeout: 265 seconds]
druppy has joined #yocto
Chaser has joined #yocto
hoyes has quit [Quit: Ping timeout (120 seconds)]
hoyes has joined #yocto
druppy has quit [Ping timeout: 268 seconds]
frieder has joined #yocto
hoyes has quit [Ping timeout: 252 seconds]
goliath has joined #yocto
Chaser_ has joined #yocto
Chaser has quit [Ping timeout: 248 seconds]
hoyes has joined #yocto
ptsneves has joined #yocto
dmoseley_ has quit [Ping timeout: 245 seconds]
dmoseley has joined #yocto
hoyes has quit [Ping timeout: 244 seconds]
wojci has joined #yocto
rob_w has joined #yocto
hoyes has joined #yocto
Chaser_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
hoyes has quit [Ping timeout: 268 seconds]
olani- has joined #yocto
rfuentess has joined #yocto
Kubu_work has joined #yocto
<khem>
vmeson: minifi-cpp is giving me headaches as it does not build with latest clang and I see its stuck at 0.15.0 and latest release is 0.99.1 from Feb this year, it was added by WRS devs, Can you help in getting it upgraded to 0.99.1 ?
olani- has quit [Remote host closed the connection]
olani- has joined #yocto
florian has joined #yocto
prabhakalad has joined #yocto
<ak77>
hello.
Chaser has joined #yocto
ablu has quit [Ping timeout: 265 seconds]
ablu has joined #yocto
florian has quit [Ping timeout: 248 seconds]
<mcfrisk>
in oe-core selftests, can I set the target MACHINE? Or are the tests expected to run on all target machines supported by oe-core?
<RP>
mcfrisk: in theory they're supposed to run for a variety of machines. I think we use qemuarm64 and qemux86-64
<RP>
mcfrisk: we do skip some tests for some arches
<mcfrisk>
RP: I'm adding tests to uki.bbclass for systemd based initrd variant, and test runs easily on qemu, u-boot firmware and genericarm64 target machine on aarch64 build host. the same config will not run on x86_64
<mcfrisk>
so @skipIfNotArch(['aarch64']) will make sure test only runs if target is aarch64 based, I presume. this will include running on x86_64 and aarch64 build host. But can I set the target MACHINE to be genericarm64 since there are dependencies to kernel config etc
savolla has joined #yocto
savolla has quit [Quit: WeeChat 4.4.3]
savolla has joined #yocto
florian_kc is now known as florian
enok has quit [Ping timeout: 248 seconds]
florian_kc has joined #yocto
<rburton>
mcfrisk: there are a few tests that explicitly set machine because its not easy to have a generic one, so you could just set machine=genericarm64. there's a point that genericarm64 is a non-core machine so if it can work with just qemuarm64 then would that give similar coverage but work _everywhere_?
Chaser_ has joined #yocto
Chaser has quit [Ping timeout: 252 seconds]
<mcfrisk>
rburton: ok, I will check qemuarm64 and qemuarm. the test works on genericarm64 but I guess that's not enabled for selftests. sadly there is major kernel differences between those but I'll check if initrd will work on them.
savolla has quit [Ping timeout: 252 seconds]
gecko_ has quit [Quit: Konversation terminated!]
gecko_ has joined #yocto
enok has joined #yocto
<rburton>
RP: so i'm looking at that buildhistory patch and i think the reset behaviour is more broken than the patch suggests
gecko_ has quit [Client Quit]
<rburton>
RP: basically, if reset is enabled then nothing from sstate is in buildhistory
<rburton>
i'm sure that used to work...
<rburton>
huh
<rburton>
maybe it didn't. the package files hook runs on package_setscene, but if a package comes from sstate that wont run
<tlwoerner>
qschulz: sounds great! i'll take a look at them as soon as i can (maybe later today)
<tlwoerner>
i'm keen on this change
Chaser_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Minvera has joined #yocto
enok has quit [Ping timeout: 244 seconds]
pidge has quit [Ping timeout: 244 seconds]
pidge has joined #yocto
Minvera has quit [Ping timeout: 244 seconds]
cyxae has joined #yocto
alessio has joined #yocto
enok has joined #yocto
<RP>
rburton: there were changes in that area fairly recently to try and fix some things...
chep` has joined #yocto
wojci_ has joined #yocto
chep has quit [Read error: Connection reset by peer]
wojci has quit [Remote host closed the connection]
chep` is now known as chep
pidge has quit [Ping timeout: 244 seconds]
pidge has joined #yocto
ctraven has quit [Ping timeout: 245 seconds]
ctraven has joined #yocto
Guest40 has joined #yocto
<rburton>
RP: some by you, and some by the same person who sent the latest fix
<rburton>
test case time!
<RP>
rburton: definitely]
<Guest40>
can anyone please tell me, what needs to be done. if I need to add my applications in syslog.conf.Sysklogd is in poky->meta->extended. I am using scarthgap
Xagen has joined #yocto
Chaser has joined #yocto
wojci_ has quit [Ping timeout: 248 seconds]
neverpanic has joined #yocto
ashux88 has joined #yocto
ashux88 has quit [Client Quit]
ashux88 has joined #yocto
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ashux88 has quit [Client Quit]
Xagen has joined #yocto
antoniovado has joined #yocto
davidinux has quit [Ping timeout: 276 seconds]
<Guest40>
is it possible to do do_patch after do_install. I have created a patch in which syslog.conf has my apps as well. Yocto gives me error "missing upstream status in patch". Since syslog.conf is not yet there. I'll appreciate your response
<rburton>
guest40: missing upstream status means your patch is missing an Upstream-Status tag
<rburton>
if you apply the patch in a bbappend in your layer instead of patching poky, you won't get that warning
<Guest40>
rburton I have created that patch through devshell, and adding this patch in my layer through bbappend
<rburton>
add Upstream-Status: Inappropriate to the top of the patch
<Guest40>
rburton I have seen syslog.conf in yocto's working directory. My changes are there, strangely enough I am still getting error. Can you guess?
rob_w has quit [Remote host closed the connection]
<Guest40>
rburton thank you very much that has seemed to work. I appreciate your help
<antoniovado>
hello, i'm trying to build python3 with sqlite3 module included, i see that the python3_3.12.8.bb already has sqlite3 among the depends. Am I missing something obvious?
Guest99 has joined #yocto
<rburton>
antoniovado: are you just not installing python3-sqlite3? we split out the sqlite3 module into a separate package.
Chaser has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<antoniovado>
So I was missing something obvious, my bad, I was looking for something it in the layer index and could not find anything. Thank you very much!
Guest99 has quit [Quit: Client closed]
<RP>
rburton: looking at the code, buildhistory and sstate look to be a nightmare :(
<mcfrisk>
are these issues with the vncserver running in CI?
<RP>
mcfrisk: not that I'm aware of and it seems odd it is just that platform
alessio has joined #yocto
<mcfrisk>
RP: ok, I was thinking if Xorg display issue could be linked to the psplash failures
<RP>
mcfrisk: I have wondered if those are linked
<mcfrisk>
but if it's only the meta-arm builds then issue could also be in driver stack there..
<RP>
mcfrisk: right, that would appear to be the case
<mcfrisk>
do the meta-arm builds really need graphics support? many of the meta-arm kas builds run tests without display (nographics novga for runqemu)
<JPEW>
RP: When bitbake hashes library code, does it has the actual function content to determine the hash, or just the variable dependencies?
<JPEW>
*hash the actual function content
<RP>
JPEW: the content of the function
<RP>
JPEW: I queued the hashserv API/clean script in master-next. I'm hoping you could review those...
<JPEW>
Ah, I think something is wrong in the detection of when it needs to rehash then; If I change a function, it doesn't rebuild (no hash change), but then when it does re-run for some reason it gets a takshash mismatch