It's intentional: > Gnulib takes a different approach. Its components are intended to be shared at the source level, rather than being a library that gets buil

It's intentional: > Gnulib takes a different approach. Its components are intended to be shared at the source level, rather than being a library that gets built, installed, and linked against. Thus, there is no distribution tarball; the idea is to copy files from Gnulib into your own source tree. https://www.gnu.org/software/gnulib/ https://www.gnu.org/software/gnulib/ The musl FAQ has some, ah, choice words: https://wiki.musl-libc.org/faq.html#Q:-I'm-getting-a-gnulib-error https://wiki.musl-libc.org/faq.html#Q:-I'm-getting-a-gnulib-... gnulib is like the hellspawn retroactive offspring of autoconf and a vendored copy of jquery. The "portability" issues it solves are immediately invalidated when your code probably won't compile under a pre-C99 compiler unless you pay special attention anyway, and the kind of people who run those systems either know what they're getting into or aren't likely intending to be installing new software. Then it goes creating problems in otherwise perfectly fine environments. Don't use it.