It is a bug, and we will fix it, but keep in mind the scope - this is something that affects old versions of glibc. Newer versions of glibc are not affected, and neither is musl libc (often preferable for cross compiling to Linux).
You can target a newer glibc like this: -target x86_64-linux-gnu.2.28
You can target musl libc like this: -target x86_64-linux-musl
You can target a newer glibc like this: -target x86_64-linux-gnu.2.28
You can target musl libc like this: -target x86_64-linux-musl