You can statically link your apps just fine as long as you follow the license for the libraries you're linking (in the case of libc, the LGPL.) Before you get upset about this Windows does the same thing with their C runtime (although the license terms are different.) Ever seen the installer for it when you install another app? That's exactly what's going on.
Go nearly always does this for example (although in some version they switched to dynamically linking to glibc for the stub resolver) and you can take statically linked go binaries and copy them to totally different OSes as long as the architecture is compatible. I remember taking a copy of syncthing and copying it between my Android and a Raspberry pi at one point (or maybe it was a kindle and a raspberry pi) which run totally different OSes and it worked just fine (ignoring the Android stupidity of course.)
Go nearly always does this for example (although in some version they switched to dynamically linking to glibc for the stub resolver) and you can take statically linked go binaries and copy them to totally different OSes as long as the architecture is compatible. I remember taking a copy of syncthing and copying it between my Android and a Raspberry pi at one point (or maybe it was a kindle and a raspberry pi) which run totally different OSes and it worked just fine (ignoring the Android stupidity of course.)