go: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found

see #57328

here is my case may help others Stackoverflow

Thank you both.

I’ve re-run the golang-releaser build with 1.19 and it ends up with CGO_ENABLED=1, too. With 1.19 that doesn’t hurt apparently, with 1.20 it does. I’m not a compiler person and totally fail to make the connection from the Go release notes to the problem observed. I do understand that dynamic linking requires the link targets to be available at runtime. What I don’t get is what has changed between 1.19 and 1.20 that makes it behave differently with regards to runtime behaviour.

Happy to not get an answer, solved by forcing the build to CGO_ENABLED=0 which I suspected to be the default all the time. I could imagine though that the change in behaviour will confuse other devs, too.

@Pim-Infuzed This issue is closed. If you are having trouble I suggest that you ask on a forum, with full details about what you are doing. See https://go.dev/wiki/Questions. Thanks.

if you build your code in docker for arm, with arm64v8/golang:1.20 image. There is a change that upgrade the base OS from bullseye to bookworm. So the version of glibc was changed.

CGO_ENABLED=1 is the default and always has been. It’s true that in 1.19 if you built the tools with CGO_ENABLED=0, then the tools would in turn default to building programs with CGO_ENABLED=0. I believe that that is no longer true in 1.20.

More specifically, when the CGO_ENABLED environment variable is unset, the CC environment variable is unset, and the default C compiler (typically clang or gcc) is not found in the path, CGO_ENABLED defaults to 0. As always, you can override the default by setting CGO_ENABLED explicitly.

I have CGO_ENABLED unset in the build environment. It’s confusing that the build would end with CGO_ENABLED=1? Seems this wasn’t the case with Go 1.19.

Looking at the evcc issue, it’s your nightly ubuntu builds. These are linked against glibc.

As we no longer ship precompiled archives for the standard library, it’s up to you to ensure glibc linking (if you use it, eg using net) works. https://go.dev/doc/go1.20#go-command

root@c737fabce3a0:/# go version -m /usr/bin/evcc
/usr/bin/evcc: go1.20
	path	command-line-arguments
	...
	build	-buildmode=exe
	build	-compiler=gc
	build	-ldflags="-X github.com/evcc-io/evcc/server.Version=0.112.5 -X github.com/evcc-io/evcc/server.Commit=99595b72 -s -w"
	build	-tags=release
	build	CGO_ENABLED=1
	build	CGO_CFLAGS=
	build	CGO_CPPFLAGS=
	build	CGO_CXXFLAGS=
	build	CGO_LDFLAGS=
	build	GOARCH=amd64
	build	GOOS=linux
	build	GOAMD64=v1
root@c737fabce3a0:/# ldd /usr/bin/evcc 
	linux-vdso.so.1 (0x00007fffde69b000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f943b894000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f943bac1000)

Closing as working as intended.