And yes, I've built #ziglang too, but it fails to produce binaries even for the hello_world type of programs, I have no idea what the problem might be, but as it depends on LLVM (and even comes with LLVM 18 for bootstrapping), it could be literally anything.

Good news is — it's possible to make #golang work on a relatively up-to-date #powerpc system, even though it's really dated: gccgo that comes with gcc 8.5.0 provides go 1.10.3… Yeah-yeah, but even this is one hell of an achievement, at least programs that only depend on the standard library work reliably.
Thanks to Adelie Linux maintainers and their set of patches: https://cgit.adelielinux.org/packages/tree/system/gcc?id=b7807f42fbd231b0783eb0d26fd60b63153ca6d9

I've also had to update libbacktrace to the one from gcc 10.5 — my system seems pro produce binaries with dwarf-5, but older libbacktrace does not support that and adding "-gdwarf-4" to CFLAGS somehow failed to fix that for me.
This go toolchain still fails to produce fully statically linked binaries as normal go toolchain does — this is probably related to libucontext in Void only exporting prefixed symbols. But that's a relatively minor problem, statically linking libgo works fine.

@awilfox Thanks for all your patches and for keeping PowerPC alive!
Did you manage to advance any further in making newer Go work on 32-bit machines? I see that Adelie got updated with GCC 13 about 10 days ago? Does gccgo in that one get built properly? I think I've tried those patches when they were still in the experimental branch and it didn't work for me.

@awilfox
There is also a branch with an attempt to port newer libgo to older gccgo in the Adelie tree — that one failed to build on my machine too, but my experimenting with it is somewhat hindered by the fact that complete rebuild of gcc on this MacMini takes forever😅 So I might've missed something.

So, Zig indeed appears to be broken on Big Endian machines, even 0.12: https://github.com/ziglang/zig/issues/18100
The issue is rather old, but on the other hand, they don't have the resources of Google and even that of those who work on Rust, so hopefully there'd be a fix sooner or later.

zig hurts my brain.

Can you build go on ppc?

I'm not even sure. I lack a ppc to even try it.

Oh I was talking to m0xee but wanted you included in the conversation because I like talking with you

@tyler
Turns out you can!
I'm still updating the thread: https://social.librem.one/@m0xee/112983810359104857
TL; DR it's REALLY old — backporting to that would take a significant effort, but it works! I've managed to get BloatFE running matively on the same PowerPC machine my Pelorma instance runs on. It has very few dependencies, but it still took me a couple of hours yesterday.
@pyrate

Nice!

@pyrate
Why though? I've never used it for anything serious myself, but it looks like a nice language in its own way, not having the shortcomings of Go and not as complex as Rust — at the very least it appears to be easier to read, the code looks cleaner 😂
I don't like the reliance on LLVM and the fact that it's currently broken on PowerPC, but at least there is no Google-style "Haha, get new hardware" attitude here.

@m0xee never update, retvrn to gcc4 and golang 1

@romin
Ackshually yeah — correct! I had to deal with this older go yesterday and it appeared to be way less broken than it is today 😂
E.g. the way it handles the dependencies: just issuing "go build" and seeing it retrieve all the dependencies itself is fine and dandy, but having them saved in a particular directory locally and not depending on… 🤬 GOPROXY is preferable to me.

@romin
I've already forgotten that GOPROXY simply didn't exist then, you don't even have to do "go env -w GOPROXY=direct" — that might be related to "go env" simply not supporting the "-w" parameter in this version though 🤣

@m0xee can't you just vendor 'em

@romin
You can now! I'm not even sure when they have added it — this version doesn't support it either. A directory named "vendor" is handled in some special way, but it only seems to affect the namespace visibility and nothing else, it doesn't look for dependencies in this dir.
But you can always put everything under src/ and point GOROOT to the current directory — very straightforward!

@romin
Minor downside: you have to put local modules into src/ too — obviously (it's in the name) GO111MODULE didn't exist in this version either.