tammranil has quit [Remote host closed the connection]
tammranil has joined #yocto
Daanct12 has joined #yocto
enok has joined #yocto
savolla has joined #yocto
enok has quit [Quit: enok]
enok has joined #yocto
enok has quit [Ping timeout: 248 seconds]
davidinux has joined #yocto
enok has joined #yocto
marka has quit [Ping timeout: 276 seconds]
enok has quit [Ping timeout: 260 seconds]
paulg has quit [Ping timeout: 252 seconds]
alessio has joined #yocto
vmeson has quit [Ping timeout: 260 seconds]
enok has joined #yocto
enok has quit [Read error: Connection reset by peer]
enok has joined #yocto
enok has quit [Remote host closed the connection]
vmeson has joined #yocto
eduter has joined #yocto
enok has joined #yocto
enok has quit [Ping timeout: 245 seconds]
frgo has joined #yocto
frgo has quit [Quit: Leaving...]
enok has joined #yocto
enok has quit [Client Quit]
enok has joined #yocto
rfuentess has joined #yocto
rob_w has joined #yocto
leon-anavi has joined #yocto
enok has quit [Ping timeout: 265 seconds]
frgo has joined #yocto
florian has joined #yocto
Tyaku has joined #yocto
enok has joined #yocto
vbpieter has joined #yocto
vbpieter has quit [Client Quit]
florian_kc has joined #yocto
pietervb has quit [Quit: WeeChat 4.1.1]
miau_miau has joined #yocto
JerryM has joined #yocto
alcroito has joined #yocto
florian has quit [Ping timeout: 260 seconds]
florian_kc has quit [Ping timeout: 244 seconds]
enok has quit [Ping timeout: 260 seconds]
<RP>
agodard: We may need to clarify the docs on spdx 2.2 vs 3, see above from ebassi
alcroito has left #yocto [#yocto]
enok has joined #yocto
olani has joined #yocto
<agodard>
RP: thanks, took note of that
enok has quit [Ping timeout: 260 seconds]
enok has joined #yocto
miau_miau has quit [Ping timeout: 240 seconds]
florian has joined #yocto
florian_kc has joined #yocto
enok has quit [Client Quit]
enok71 has joined #yocto
enok71 is now known as enok
florian_kc has quit [Ping timeout: 265 seconds]
florian_kc has joined #yocto
enok has quit [Quit: enok]
enok71 has joined #yocto
enok71 has quit [Ping timeout: 244 seconds]
Tyaku has quit [Ping timeout: 260 seconds]
<ebassi>
RP, agodard: Thanks; I spent a bit too much on that particular rabbithole, and I thought I was going insane :-)
Tyaku has joined #yocto
eduter has quit [Quit: Client closed]
<agodard>
ebassi: yeah, I was looking at the docs and it is indeed out-of-sync on most branches... so thanks for reporting that. I'll try to clear that up
olani- has joined #yocto
goliath has joined #yocto
eduter has joined #yocto
marka has joined #yocto
<dvergatal>
hi is there a way to generate some sort of graph showing which packages depend on my package?
<mcfrisk>
dvergatal: bitbake -g build-target, will generate dot files with build time dependencies. For runtime dependencies I recommend checking output of INHERIT += "buildhistory"
<dvergatal>
mcfrisk: build-target is my image?
frgo has quit [Ping timeout: 248 seconds]
<mcfrisk>
dvergatal: yes
<dvergatal>
mcfrisk: thx
<dvergatal>
mcfrisk: btw. how can i read this buildhistory? i mean generation of some graph to see what is depending on my package?
alessio has quit [Read error: Connection reset by peer]
reatmon_ has quit [Remote host closed the connection]
alessio_ is now known as alessio
reatmon_ has joined #yocto
Xagen has joined #yocto
eduter55 has joined #yocto
Guest79 has joined #yocto
<Guest79>
hello all, is there a way to display all cross compiler warnings of a yocto build?
<Guest79>
I mean not the bitbake warnings, but the compiler ones inside do_compile
<Guest79>
I supose we could parse all log.do_compile files
<Guest79>
but I was wondering if there is some way of printing this via the bitbake command
<rburton>
Guest79: just opening the full compile log is the easiest solution
<rburton>
Guest79: a neat solution would be to get gcc to write the warnings in a machine readable format to a separate file so you can extract those and show them. https://git.yoctoproject.org/poky-contrib/commit/?h=ross/sarif&id=19c32a8244512905d8537074358f2cfd0e6fbb32 was the start of this but the tooling to display it was lacking.
<Guest79>
Thanks! rburton
<agodard>
rburton: ok, thanks
Guest35 has joined #yocto
Guest35 has quit [Client Quit]
MQueiros has joined #yocto
<derRichard>
leon-anavi: FYI, i found the root cause of the problem with my rpi5. fdt_addr and other addresses come from the rpi firmware and show up in the uboot env. as soon you save the uboot env once. these addresses override what the rpi firmware gives you
<derRichard>
e.g. you boot the rpi 5, run saveenv, fdt_addr is stored as X. this works fine
<derRichard>
but when you plug in the rpi camera and boot again, the rpi firmware places the fdt into a different location, sets it to fdt_addr, but the u-boot env sets it back to the old (now wrong) address
<derRichard>
same happens also when you boot once on the 4gb version, run saveenv and try to boot the very same sdcard on the 8gb version
Daanct12 has quit [Quit: WeeChat 4.6.0]
<leon-anavi>
derRichard, this is a let's say "interesting" behavior. Have you found any similar issue in the meta-raspberrypi github repo? If not probably it is worth opening an issue so that other people can have it in mind.
<leon-anavi>
well done for debugging the root cause.
Guest79 has quit [Quit: Client closed]
tangofoxtrot has quit [Remote host closed the connection]
tangofoxtrot has joined #yocto
rob_w has quit [Remote host closed the connection]
<derRichard>
leon-anavi: well, this is a pure u-boot issue
<derRichard>
not related to meta-raspberrypi
<derRichard>
i'll post to u-boot mailinglist soon
<leon-anavi>
yes, you are right. Probably the U-Boot mailing list is the right place.
<derRichard>
if you want i can cc you :)
<leon-anavi>
yes, sure. I am subscribed the U-Boot mailing list.
alessio has quit [Quit: alessio]
alessio has joined #yocto
eduter55 has quit [Ping timeout: 240 seconds]
ciao has joined #yocto
ciao has quit [Write error: Connection reset by peer]