Read section 2.2 [1]. Each package that uses Gnulib maintains a list of modules that its program(s) requires. I.e., each package has a different library built as libgnu.a.
Gnulib also doesn't make API stability guarantees like shared libraries do. If a distribution installs Gnulib as a shared (or even static) library, and then links programs to that instead of the vendored sources, they will likely end up with broken programs.
[1] https://www.gnu.org/software/gnulib/manual/gnulib.html#Libra...
Yeah, I've read the section of 2.2 in its entirety — nothing you said in your comment is in it.
Also, "Gnulib doesn't make API stability guarantees like shared libraries do" — a) do you mean ABI? b) why not? The gnulib seems like something that's perfectly suited to be a shared library, even more so than the glibc, since it's not a language runtime.