**** BEGIN LOGGING AT Thu Oct 13 02:59:57 2022
Oct 13 07:43:47 <mckoan> good morning
Oct 13 09:14:51 <shoragan> Crofton, do you know if there will be an OE meeting close to FOSDEM next year?
Oct 13 10:45:10 <rburton> shoragan: the plan I heard was for a meeting the monday after
Oct 13 11:14:13 <hrw> like last time
Oct 13 11:22:31 <Crofton> this is the idea, I am hunting spaces now
Oct 13 11:23:02 <Crofton> the one we used last time closed, and anyone who knows anythinog about meetings spaces in Brussels chime in :)
Oct 13 11:29:26 <rburton> i can ask a dude I know from intel who is in brussels
Oct 13 17:44:24 <Crofton> WARNING: Your host glibc version (2.35) is newer than that in uninative (2.33). Disabling uninative so that sstate is not corrupted.
Oct 13 17:44:47 <Crofton> am I am seeing this because petalinux has locked sstate  sigs
Oct 13 17:45:08 <Crofton> disbaling uninative is likely casuing more pain
Oct 13 17:54:32 <Crofton> nope not locked sigs
Oct 13 17:56:15 <khem> What’s the problem @crofton I can’t see any context around
Oct 13 17:57:03 <Crofton> I think disbaling uninative then leads to build failures with older  petlinux on newer distro
Oct 13 17:57:26 <Crofton> I thought uninative was supposed to help with this (and buildtoolds extended
Oct 13 17:58:19 <Crofton> this is petalinux, so lots of stuff hidden and hard to sort out
Oct 13 17:59:47 <khem> Yeah use a container of that era and save yourselves
Oct 13 18:00:38 <khem> With yoe that’s one thing I really like you can build arcane releases with no issues
Oct 13 18:02:22 <Crofton> normally I would use pyrex, but not sure how to add that to petalinux
Oct 13 18:02:59 <JaMa> yes, petalinux is strange, use yoe instead :)
Oct 13 18:04:16 <Crofton> I wonder if I have a laptop containing a suitable distro
Oct 13 18:08:18 <khem> GitHub/gitsm/docker I love monorepos
Oct 13 18:55:31 <khem> yeah use yoe definitely is a good thing
Oct 13 20:22:48 <Crofton[m]> khem: does/can qemu/gcc in OE support risc-v vector extensions?
Oct 13 20:23:28 <khem> Crofton: rvv is still WIP
Oct 13 20:23:29 <khem> in upstream gcc
Oct 13 20:24:05 <Crofton[m]> inline asm?
Oct 13 20:24:33 <khem> so yes it can but you have to use a different gcc source https://github.com/riscv-collab/riscv-gcc/tree/riscv-gcc-rvv-next
Oct 13 20:25:10 <khem> inline asm might work havent checked binutils/gas support
Oct 13 20:25:43 <Crofton[m]> I'll poke arond, maybe check with Drew
Oct 13 20:28:10 <khem> depends what all you need
Oct 13 20:29:17 <Crofton[m]> mostly want to try some of the vector stuff out when I get bored
Oct 13 20:32:51 <khem> I see, I would say build a RV64 toolchain out of oe and try this example https://raw.githubusercontent.com/riscv-non-isa/rvv-intrinsic-doc/master/examples/rvv_sgemm.c
Oct 13 20:33:02 <khem> if it compiles then you are good to go atleast somewhat
Oct 13 20:33:34 <khem> but I think you need rv64gcv ABI so above gcc is perhaps needed
**** ENDING LOGGING AT Fri Oct 14 02:59:56 2022