qschulz has quit [Remote host closed the connection]
qschulz has joined #yocto
tgamblin has joined #yocto
tgamblin has quit [Ping timeout: 272 seconds]
Xagen has joined #yocto
tgamblin has joined #yocto
tr4gic_3rr0r has quit [Ping timeout: 276 seconds]
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jclsn has quit [Ping timeout: 272 seconds]
jclsn has joined #yocto
<khem>
RP:rust build with clang + gcc15 failed with the same error musl-qemuarm64
<khem>
so most likely its happening with gcc15
frgo has joined #yocto
frgo has quit [Ping timeout: 248 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 252 seconds]
sakman has quit [Quit: Leaving]
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #yocto
frgo has joined #yocto
frgo has quit [Ping timeout: 276 seconds]
kanavin has quit [Remote host closed the connection]
kanavin has joined #yocto
frgo has joined #yocto
frgo has quit [Ping timeout: 244 seconds]
ablu has quit [Ping timeout: 265 seconds]
ablu has joined #yocto
vthor has joined #yocto
vthor has quit [Changing host]
vthor has joined #yocto
vthor_ has quit [Ping timeout: 252 seconds]
rob_w has joined #yocto
frieder has joined #yocto
alessio has joined #yocto
frgo has joined #yocto
goliath has joined #yocto
zeddii has joined #yocto
rfuentess has joined #yocto
Kubu_work has quit [Ping timeout: 252 seconds]
JPEW_ has joined #yocto
ello- has joined #yocto
olani- has joined #yocto
JaMa has quit [Killed (mercury.libera.chat (Nickname regained by services))]
JaMa has joined #yocto
dmoseley_ has joined #yocto
pidge_ has joined #yocto
JPEW has quit [Ping timeout: 260 seconds]
olani has quit [Ping timeout: 260 seconds]
dmoseley has quit [Ping timeout: 260 seconds]
pidge has quit [Ping timeout: 260 seconds]
ello has quit [Ping timeout: 260 seconds]
JPEW_ is now known as JPEW
zeemate has joined #yocto
enok has joined #yocto
Kubu_work has joined #yocto
grma has quit []
grma has joined #yocto
mckoan|away is now known as mckoan
leon-anavi has joined #yocto
enok has quit [Ping timeout: 252 seconds]
<RP>
khem: it works with gcc 15 reverted, so yes, looks like gcc 15
alessio has quit [Quit: alessio]
alessio has joined #yocto
LainIwakura has joined #yocto
ptsneves has joined #yocto
enok has joined #yocto
florian has joined #yocto
Jones42 has joined #yocto
grma has quit []
grma has joined #yocto
LainIwakura has quit [Ping timeout: 240 seconds]
av has joined #yocto
florian_kc has quit [Quit: Ex-Chat]
vthor_ has joined #yocto
vthor has quit [Ping timeout: 272 seconds]
rob_w has quit [Remote host closed the connection]
Jones42 has quit [Ping timeout: 260 seconds]
Jones42 has joined #yocto
ptsneves has quit [Ping timeout: 260 seconds]
dmoseley has joined #yocto
dmoseley_ has quit [Ping timeout: 276 seconds]
dmoseley has quit [Ping timeout: 245 seconds]
dmoseley has joined #yocto
enok has quit [Ping timeout: 265 seconds]
enok has joined #yocto
kanavin_ has joined #yocto
av has quit [Quit: Client closed]
kanavin has quit [Ping timeout: 252 seconds]
frgo has quit [Remote host closed the connection]
frgo has joined #yocto
frgo has quit [Read error: Connection reset by peer]
frgo_ has joined #yocto
florian has quit [Ping timeout: 265 seconds]
frgo_ has quit [Read error: Connection reset by peer]
enok has quit [Quit: enok]
enok has joined #yocto
pbiel has joined #yocto
bielpa_ has joined #yocto
<bielpa_>
How can I update sources while working with devtoop? Suppose I want to make some changes in the source code, so I use devtool modify to extract recipe's source code, then I modify it, commit and call devtool update-recipe... Next I change the branch of my layer, and would like to modify the source code again, however on this particular layer branch, some patches should be added for the source code before I modify it. The only solution I
<bielpa_>
see currently is to remove / reset soruce code and call devtool modify once again
<bielpa_>
Any other ideas?
enok has quit [Ping timeout: 260 seconds]
frgo has joined #yocto
frgo has quit [Remote host closed the connection]
enok has joined #yocto
bielpa_ has quit [Remote host closed the connection]
bielpa_ has joined #yocto
enok has quit [Ping timeout: 248 seconds]
enok has joined #yocto
Articulus5 has joined #yocto
Articulus has quit [Ping timeout: 276 seconds]
Vonter has quit [Ping timeout: 244 seconds]
babb0 has quit [Quit: Leaving]
Vonter has joined #yocto
lexano has joined #yocto
enok has quit [Ping timeout: 276 seconds]
<kanavin_>
bielpa_, I don't think there's a way to update the sources in a devtool workspace that way
<rburton>
RP: so... esdk testing. if i fix the manifest generation so its not empty then it thinks the esdk has meson in, but the esdk doesn't - there was just meson available in the sstate. should esdk tests check that eg meson is in the manifest and then devtool sdk-install to be _sure_?
<RP>
rburton: really good question. I guess it should try and install it
<RP>
rburton: how interested are you in an arm specific gcc15 failure on musl in rust?
<RP>
rburton: unwind related :/
* RP
feels it is like a bingo card
grma has quit []
grma has joined #yocto
alessio has quit [Quit: alessio]
alessio has joined #yocto
<Saur>
RP: Is there any situation where it makes sense for a native recipe to depend on a target recipe, or could this be discovered and trigger an error? The reason I ask is because I realized the other day that pipewire-native unintentionally depended on pipewire (see 9f17bf73d7 in meta-openembedded).
<KanjiMonster>
the moment you decide "no", a bsp will pop into existence with a recipe doing that
<rburton>
RP: all my favourites! share a log and i'll spread it around internally.
<RP>
Saur: no, that never makes sense and the sstatetests in selftest in core are meant to detect things like that
<RP>
rburton: that patch probably makes sense...
<Saur>
RP: Any way it could be detected by bitbake itself? Relying on the selftests does not seem reliable for layers outside of core.
enok has quit [Ping timeout: 252 seconds]
Vonter has quit [Ping timeout: 244 seconds]
Vonter has joined #yocto
Xagen has joined #yocto
Jones42 has quit [Ping timeout: 260 seconds]
<RP>
Saur: the selftests should work outside core. Bitbake itself has no knowledge of "native"
Jones42 has joined #yocto
cyxae has joined #yocto
cyxae has quit [Remote host closed the connection]
rty has joined #yocto
psi has joined #yocto
enok has joined #yocto
savolla has quit [Quit: WeeChat 4.4.3]
<psi>
If anybody was wondering, I managed to solve the issue with the sstate hash and stamp invalidation. I had to call bb.parse.mark_dependency for the file that I generate the hash from in an anonymous python function and then append the hash to DESCRIPTION += " (myhash: ${MYHASH})"
psi has quit [Client Quit]
enok has quit [Ping timeout: 272 seconds]
mbulut has joined #yocto
rty has quit [Ping timeout: 240 seconds]
<RP>
khem: looks like gdb now breaks in readline on mingw with gcc 15 (we disable extrernal readline so it uses the internal one)
Jones42 has quit [Ping timeout: 248 seconds]
<smurray>
vmeson: I'm currently testing backporting the scarthgap level of setuptools-rust & setuptools to fix building python3-cryptography with kirkstone/rust, I'm curious if WR's use of kirkstone/rust is such that it'd always be in the layer stack or not (since there'll be non-trivial sstate impact)
alessio has quit [Quit: alessio]
<smurray>
vmeson: I have a rough idea what specific changes would need to be backported in setuptools-rust, but I'm a little wary of how much effort it might be to make that happen
arisut has quit [Quit: install gentoo]
arisut has joined #yocto
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Xagen has joined #yocto
<vmeson>
smurray: the goal is to always have it in the layer list. We did a world build but oddly, py-crypto didn't show up as an issue. I'll check with Soumya after May Day holiday.
<smurray>
vmeson: note this is with my local tree with Rust 1.85.1 backported, you'd not have seen the issue yet
<vmeson>
smurray: ah.
<smurray>
vmeson: I'll spend a little time this aft seeing if I can extract just the required fix(es) from newer setuptools-rust, but the full backport will be my fallback since it's working and atm doesn't seem to be impacting oe-selftest
<vmeson>
smurray: thanks. I don't object to the full-backport, especially given that you've done and tested it!
bielpa_ has quit [Remote host closed the connection]
pbiel has quit [Remote host closed the connection]
Vonter has joined #yocto
pbiel has joined #yocto
bielpa_ has joined #yocto
tr4gic_3rr0r has quit [Ping timeout: 248 seconds]
davidinux has joined #yocto
<khem>
RP: yeah the rust one looks like its due to gcc-15, but the code its complaining about fails with gcc-14 too, so my guess is that somehow llvm libunwind is not being built when gcc-14 is in use
Kubu_work has quit [Quit: Leaving.]
frieder has quit [Remote host closed the connection]
Articulus5 has quit [Remote host closed the connection]
ptsneves has joined #yocto
druppy has joined #yocto
KanjiMonster has quit [Read error: Connection reset by peer]
KanjiMonster_ has joined #yocto
KanjiMonster_ is now known as KanjiMonster
mckoan is now known as mckoan|away
leon-anavi has quit [Quit: Leaving]
jero has joined #yocto
<RP>
khem, JPEW: I stared long and hard at readline in gdb under mingw and I have no idea how it can ever work :/
<RP>
One of you will probably need to fix that failure