rany2
rany2
P.S. this is very similar to my issue on PPC64LE (cfarm120). The fix is also the same as what I described in this comment: https://github.com/ziglang/zig/issues/20087#issuecomment-2133867069 ``` rany@cfarm203:~/zig-linux-powerpc-0.11.0$ uname -a Linux...
Explicitly specifying the `-mcpu` fixes the problem, it turns out the problem is that `-mcpu` defaults to `pwr10` which is the toolchain default. ``` $ ./zig build-exe -mcpu=pwr10 hello-world.zig error:...
@MementoRC Your machine is PPC64le, so it should be `-mcpu=ppc64le`. See https://github.com/ziglang/zig/issues/20087#issuecomment-2133867069. There is also a similar issue with PPC64 with a similar solution: https://github.com/ziglang/zig/issues/18100#issuecomment-2133894184 Note that this only works...
I'm not sure what you're trying to do. Are you attempting to build Zig from source with your patches to include `-mcpu=...`?
I don't know, sorry.
@alexrp I confirm this issue is fixed as of fbcb00fbb. Thanks!
I'll have to research it, I don't know what this is
I doubt that that cookie is used to obtain a WG config. I'll have a look myself but my assumption is that everything is going to be different in terms...
@GaryChicago Do you know how to MITM it? warp-svc on Linux seems to embed the trusted certificates into the binary itself so it's not trivial to modify it. If you...
@AnimMouse how does WARP Connector differ from WARP teams? Is there any advantage to using it over Teams auth? I'm asking because currently Teams has the advantage of not reporting...