ederibaucourt has quit [Ping timeout: 256 seconds]
ak77 has quit [Read error: Connection reset by peer]
ak77 has joined #yocto
mbulut has quit [Ping timeout: 252 seconds]
prabhakalad has quit [Ping timeout: 256 seconds]
prabhakalad has joined #yocto
starblue has quit [Ping timeout: 244 seconds]
starblue has joined #yocto
jclsn has quit [Ping timeout: 272 seconds]
jclsn has joined #yocto
ablu has quit [Ping timeout: 244 seconds]
ablu has joined #yocto
dvergatal has quit [Read error: Connection reset by peer]
dvergatal has joined #yocto
pita has quit [Remote host closed the connection]
dgriego has quit [Quit: Bye]
Daanct12 has joined #yocto
florian_kc has quit [Ping timeout: 260 seconds]
florian_kc has joined #yocto
nerdboy has quit [Ping timeout: 260 seconds]
nerdboy has joined #yocto
nerdboy has quit [Changing host]
nerdboy has joined #yocto
Xagen has quit [Ping timeout: 256 seconds]
Xagen has joined #yocto
dmoseley_ has quit [Ping timeout: 260 seconds]
dmoseley has joined #yocto
vladest has quit [Remote host closed the connection]
olani- has joined #yocto
leon-anavi has joined #yocto
florian_kc has quit [Ping timeout: 272 seconds]
Jones42 has joined #yocto
ederibaucourt has joined #yocto
vladest has joined #yocto
leon-anavi has quit [Quit: Leaving]
leon-anavi has joined #yocto
<olani>
khem: Your comment on glibc and kernel 5.7 was from July 4th. It was a slow day, so it's easy to find in the logs :) I'm curious because we do have a few products still that uses an older kernel and cannot be upgraded. But I guess we'll just have to wait and se as it does not seem like anyone knows anything more about it.
<KanjiMonster>
olani: and it says it's a build-time (i.e. kernel-headers) requirement. So if you use Yocto (which I presume you do, being in this channel ;-) you likely just need to update the kernel-headers recipe, not the kernel itself
florian has joined #yocto
<olani>
KanjiMonster: Thank you, that looks like exactly the information I was looking for.
mbulut has joined #yocto
vthor_ has quit [Excess Flood]
vthor_ has joined #yocto
Xagen has quit [Ping timeout: 256 seconds]
Xagen has joined #yocto
Wouter01007 has joined #yocto
Wouter0100 has quit [Ping timeout: 252 seconds]
Wouter01007 is now known as Wouter0100
tnovotny has joined #yocto
demirok has quit [Server closed connection]
demirok has joined #yocto
prabhakalad has quit [Ping timeout: 255 seconds]
prabhakalad has joined #yocto
sunkist has quit [Server closed connection]
sunkist has joined #yocto
tlwoerner_ has joined #yocto
rgolledge has joined #yocto
tlwoerner has quit [Ping timeout: 260 seconds]
bantu has quit [Server closed connection]
bantu has joined #yocto
goliath has joined #yocto
<rburton>
RP: i think the blocker for genericarm64-qemu was the idea of running it with kvm on the altras
|Xagen has joined #yocto
Xagen has quit [Ping timeout: 260 seconds]
olani_ has joined #yocto
sohbzudlb has joined #yocto
olani has quit [Remote host closed the connection]
olani_ has quit [Remote host closed the connection]
sohbzudlb has quit [Remote host closed the connection]
dvergatal has quit [Remote host closed the connection]
<walter>
I've managed to build and install a golang CLI application onto an RK3399, and I'm now trying to build a GUI application that has CGO dependencies and it is giving me some headakes. I don't see any error, I just get an exit code of 1 for this command: https://bpa.st/RBVJR5HEIPUR2O2GQJQJMNYKMQ
<walter>
I get tons of output, but there's no warning or error of any kind, I'm assuming the error is swallowed by the subcommand `go_list_packages`. Any ideas how to get more output out of this?
<walter>
I've managed to get past the first hurdle of installing go dependencies and I'm thinking that I'm missing some C header files, but there's nothing in the logs to indicate any issue. Just a listing of build hashes for each dependency and that's about it.
warthog9 has quit [Ping timeout: 252 seconds]
<walter>
The log looks like this: https://bpa.st/YENESWBPWJYN6D6GNQZAC4A4ZA -- I've had to remove a lot of lines, but they were basically the same thing as what's left in there.
<walter>
Is it normal for people to build outside of yocto and then just install the built file?
florian has quit [Ping timeout: 248 seconds]
mbulut has joined #yocto
florian has joined #yocto
mbulut has quit [Ping timeout: 256 seconds]
<khem>
walter:as an intermediate step for go apps its feasible to ensure it works
<khem>
especially if they are statically linked and dont use CGO its easy step
<khem>
but in long run you want to yocto'ize the build for it
<walter>
Yeah, that's the line I've saw, but as you can see, nothing extra is there. The apps actually do use CGO, I'm playing around with https://gioui.org/ apps right now. I've built and opensource Material v3 widgets library for it -- https://git.sr.ht/~schnwalter/gio-mw -- and I want to try the library in Yocto. So far nobody seems to had success running Gio apps in Yocto or Buildroot
<walter>
*I've seen,
<walter>
The Gio apps are using openGL so there's a big chance the library kitchen sink will work directly in the Weston image without a problem. Here's a WASM build for the kitchen sink: https://schnwalter.eu/wasm/kitchen/ -- it works like a charm.