Closed r-o-b-b-y closed 5 months ago
Great find! @Parzival-3141 are you able to reproduce?
@robby-robby do you happen to possibly have multiple versions of Go installed?
ok, i see that this new GOTOOLCHAIN nonsense breaks some assumptions about determining what you have installed and where. so we'll update our code to accommodate this and report back
"I think I can just set GOTOOLCHAIN=local instead of 1.21.1 that should default to whatever version you have installed, i.e. your GOROOT" - Julian
@robby-robby do you happen to possibly have multiple versions of Go installed?
I DO, is that bad?
I blew all other go versions away and installed the latest (1.21.6), this fixes, it make
s without any special flags.
I am admittedly not a go packaging and versioning pro (sorry!)
Might I suggest adding a Dockerfile, to the repo (I will glady contribute) - That way there can be a fallback 'sanity check' for proper environment setups
Dockerfile is not a bad idea. Regardless, it looks like we just need to work out proper use of the new toolchain stuff. Then it shouldn't matter if you have multiple versions.
I am currently on go version 1.21.1 and it may be causing some issue with some of the packages. (you'll have to excuse me I am not an expert in go dep and version management at the moment)
make dev
is causing the error below. Runningmake dev
again, fixes it.Alternatively using
GOTOOLCHAIN=go1.21.1 make dev
makes it run on the first try, but this feature is only available in go1.21+ - Which I will assume is OK, since go.mod has this project at version 1.21.1