<manuel1985>
Ad0, is that directed at me? Not looking for something to run on Yocto. I'm looking for an NTP server that's running on my development host and that I can use to test the NTP client on my target.
florian has quit [Ping timeout: 252 seconds]
<RP>
zeddii, khem: I'm leaning to merging the go upgrade to 1.21, any objections?
simonew has quit [Ping timeout: 256 seconds]
kpo has quit [Ping timeout: 252 seconds]
jmd has quit [Remote host closed the connection]
GNUmoon has quit [Ping timeout: 260 seconds]
GNUmoon has joined #yocto
manuel1985 has quit [Quit: Leaving]
jmd has joined #yocto
alessioigor has joined #yocto
<zeddii>
nope. I'll fix what breaks in meta-virt. do you plan on merging it today ? I'll get ahead and rebuild against it shortly. I assume it is in master-next right now ?
<zeddii>
I see it i master next, testing now.
<RP>
zeddii: yes, it is master-next right now
<khem>
there are 3 apps in meta-oe and all of them are breaking with 1.21, I will disable them and let ayone needing them fix them and enable again
Dr_Who has quit [Quit: ZZZzzz…]
<RP>
khem: ok thanks
<RP>
zeddi, khem: I've merged it since I think this helps get us in a better place for the LTS
<khem>
I started playing with poky-bleeding nothing concrete yet
<khem>
RP: I have fixed the failing go recipes in meta-oe
<khem>
GOPROXY needs to be handled I think somehow
florian has joined #yocto
<khem>
for now I have added it to the concerning recipes
kpo has joined #yocto
alessioigor has quit [Quit: alessioigor]
vladest has quit [Remote host closed the connection]
amitk_ has quit [Ping timeout: 240 seconds]
<RP>
khem: oh, for 1.21 maybe, yes. I was looking at 1.22
<RP>
khem: I didn't have a chance to think about that patch yet
<khem>
yeah for 1.21
<khem>
for 1.22 I think I know whats going on, sadly this will need fixing the go compiler unless there is some way to inject it from env
<RP>
khem: care to give me a hint? :)
<Ad0>
manuel_, you can still use the first link
<Ad0>
or use chrony
<khem>
RP: go runtime is having new C code trying to be compiled and tooling can detect it. So maybe a tweak to prove this theory is enable CGO when building the failing apps
<RP>
khem: it isn't even building the compiler itself though :/
jmiehe has joined #yocto
jmiehe has quit [Client Quit]
kpo has quit [Ping timeout: 256 seconds]
<Crofton>
Groups.io is listed by spamcop ... I'm not getting any email from oe/yocto lists
vladest has joined #yocto
ptsneves has quit [Ping timeout: 264 seconds]
<RP>
Crofton: :(
<Crofton>
Very annoying. Next time I am at the laptop I need to report to groups.io ... I am wondering how many others are using email devices that check spamcop
<jmd>
I thought spamcop stopped operating 20 years ago.
tangofoxtrot has quit [Remote host closed the connection]
tangofoxtrot has joined #yocto
<rbox>
in the build/tmp/work directory things are separated out by the machine and the architecture... how does it know which one to use?
Vonter has quit [Ping timeout: 272 seconds]
Vonter has joined #yocto
<Ad0>
machine I suppose
<Ad0>
that decides the arch
<rbox>
but like how does it decide which directory to put each pcakge in
jmd has quit [Remote host closed the connection]
ptsneves has joined #yocto
<RP>
rbox: in rough terms recipes are machine specific or target tuning specific or "allarch" or native or sdk
<rbox>
is it somethign thats calculated by the build system or is it a setting in the receipe?
<RP>
rbox: machine/target/all is set in the recipe
<RP>
PACKAGE_ARCH = xxx
<rbox>
okay, i see that
ptsneves has quit [Ping timeout: 272 seconds]
Vonter has quit [Ping timeout: 264 seconds]
Vonter has joined #yocto
kpo has joined #yocto
prabhakalad has quit [Quit: Konversation terminated!]