3 ms·
> which was solved by linking it statically You could also have linked against glibc 2.23 or 2.22 or older instead of bloating your binary.
by account42 6y ago
> which was solved by linking it statically
You could also have linked against glibc 2.23 or 2.22 or older instead of bloating your binary.
- arp242 6y agoBut that's a lot more effort, and who knows if someone is still using a CentOS or whatnot with an even older version. And it still won't work for other libc implementations. Adding an extra megabyte or so is a reasonable trade-off, with no real other downsides. It's not that large – smaller than many websites.