olani has quit [Remote host closed the connection]
frgo has quit [Ping timeout: 252 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 240 seconds]
frgo has joined #yocto
sgw has joined #yocto
frgo has quit [Ping timeout: 240 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 248 seconds]
Xagen has joined #yocto
frgo has joined #yocto
jmd has joined #yocto
ray-san3 has joined #yocto
frgo has quit [Ping timeout: 252 seconds]
Jones42 has quit [Ping timeout: 252 seconds]
Jones42 has joined #yocto
ray-san2 has quit [Ping timeout: 260 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 252 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 276 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 252 seconds]
frgo has joined #yocto
<khem>
rburton: I am seeing a new build failure for meta-python, python3-httptools is failing wierdly, I wonder if its something to do with setuptools3 cleanups you did
<khem>
bitbake python3-httptools will reproduce it
<khem>
if I inherit setuptools_legacy then it works
<khem>
but it worked ok with setuptools3 until now
<rburton>
khem: also some cython buildpaths warnings, are they new or have they always been there?
savolla has joined #yocto
Articulus has quit [Quit: Leaving]
dmoseley has quit [Ping timeout: 240 seconds]
dmoseley has joined #yocto
sugarbeet has quit [Ping timeout: 248 seconds]
sugarbeet has joined #yocto
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #yocto
litb has joined #yocto
chep has quit [Ping timeout: 244 seconds]
<mcfrisk>
How to fix/work around this in a bbappend when changing original layer is not possible? "do_unpack: Recipes that set S = "${WORKDIR}/git" or S = "${UNPACKDIR}/git" should remove that assignment, as S set by bitbake.conf in oe-core now works"
<mcfrisk>
setting S in a bbappend does not help
<rburton>
mcfrisk: unset S might work
<rburton>
though i'd contest the assertion that you cannot change the original layer. the original layer isn't compatible with master if it gets that warning :)
wmills_ has joined #yocto
<mcfrisk>
well I will not fix meta-xilinx (yet) in this build setup
chep has joined #yocto
<mcfrisk>
neither "S = ''" nor "unset S" works from a bbappend. And the qa check does not seem to be easy to remove since it's a postfunc
<rburton>
surprised unset doesn't work
<mcfrisk>
or my bbappend is not applied at all, will double check
RyanEatmon has quit [Remote host closed the connection]
RyanEatmon has joined #yocto
Chaser has quit [Ping timeout: 260 seconds]
Chaser has joined #yocto
stern has joined #yocto
stern is now known as stern1
stern1 has quit [Client Quit]
stern445647 has joined #yocto
stern445647 has quit [Client Quit]
ptsneves has quit [Ping timeout: 260 seconds]
Chaser has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<RP>
yocton: did you try your changes with something like "bitbake core-image-minimal -c testimage"? I've tried that on the autobuilder but even with various tweaks it isn't quite working as yet :/
jclsn has joined #yocto
Chaser has joined #yocto
jpuhlman has quit [Ping timeout: 240 seconds]
Chaser has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
jerrycash has quit [Ping timeout: 248 seconds]
ptsneves has joined #yocto
<yocton>
RP : no, I did not try that :-\
ptsneves has quit [Ping timeout: 276 seconds]
goliath has quit [Quit: SIGSEGV]
<RP>
yocton: np, I'll see if I can work out what is going on
<RP>
yocton: it is finding the rootfs but not the qemuboot conf files and throwing an fstype "maybe wrong" warning too
<RP>
yocton: I think a bad assumption about how to convert the rootfs name into a qemuboot file
zwelch has joined #yocto
jpuhlman has joined #yocto
<RP>
yocton: found the issue
<khem>
rburton: yes rust 1.88.0 has more diagnostics, I have sent a patch for radeon to fix it
<khem>
rburton: I guess we can use setuptools3_legacy for now, if it does not get fixed by end of this year then punt the recipe
<khem>
that for httptools py3 recipe
<rburton>
yeah, that works
<rburton>
there's a slew of recipes that all use a packaging/pep_517 shim class to do the build instead of proper setuptools and they're all terrible, with build paths and other non-reproducible strings in
<khem>
stated at same time, nativesdk-libclc build finished on my tiny puny VM, but its still running on the 64core machine. Hail ccache
<khem>
We have added almost 100+ new recipes in meta-openembedded this year and deleted < 10