bonifartius 𒂼𒄄 @bonifartius@social.cleverlibre.org

@scathach ZFS if you install the drivers :P

@cameron i somewhere heard that you best apply opinions with the pointy side facing outwards/the blunt side inwards!

@Terry what a sad hill to choose to die on.

@niclas :D

@selea @kmj
see how nice it is! it even tells you what it expects :P

joke aside, i never had trouble with compiling go for supported architectures. i think it's a very nice compiler compared to other languages. i'm a bit partial because of it's plan9 heritage though :)

@niclas
sometimes i like to go on the federated timeline. i found many interesting people there, but you also do see some shit you'd rather not see. my choice is to stomach that, it's more good than evil in the end. i think that if you _can't_ stomach the federated timeline you either need a moderated server or maybe this is just not your medium. both are fine, the expectation that people stop voicing their thoughts isn't.

@selea @kmj
TL;DR:

GOROOT_BOOTSTRAP=path/to/go1.8 ./all.bash

should be your first try.

@selea @kmj
i'm not 100% sure the newer releases use no new features but in theory:

the last c release was 1.4, so you should be fine with using 1.8 to build 1.19. just make sure the tests are run as a sanity check, which happens automatically if you build with ./all.bash

otherwise you'd have to build multiple versions, which is quite fast though.

also you should be able to cross-compile as long as the architecture and os are supported, but i never done that :) it's usually done by just setting GOOS and GOARCH, but the whole compiler might need some extra flags.