glibc LGPL requirements a bit unclear

At the moment, our statically linked binaries use whatever distribution's glibc archive we have -- does that mean we need to provide sources for glibc (even though under the definition of the LGPL glibc is a standard system library)? The reason I ask is that it'd be impractical for us to download and compile glibc for every release build, so maybe we should instead just provide a copy of the source RPM or source deb we used during compilation? Or (in keeping with the LGPLv3) can we just provide a link to the glibc homepage as well as a link to the distribution used (to cover the case where the distribution applied patches not upstream)?

No file, test, or entry point is identified in the issue. Start by reviewing the static-linking and release process, then verify the applicable LGPL requirements for the glibc archive and distribution sources. Done means the project has a documented, agreed answer for what source or links each release must provide.