sites

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs

commit 356e7fddbc9b1c35da5dfa9b2a74c9fa95dd71d3
parent 5c0ba78d17b507ae510b2d617a50bcf3bdcfa7a3
Author: Anselm R Garbe <garbeam@gmail.com>
Date:   Mon,  2 Nov 2009 11:43:17 +0000

thanks to pancake for the typo fix
Diffstat:
Msta.li/faq.md | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sta.li/faq.md b/sta.li/faq.md @@ -23,7 +23,7 @@ What's wrong with glibc? We think nearly everything is wrong with it. Its enormous complexity, its lack of good structure and well separated object files (otherwise linking trivial programs wouldn't result in 600kb oberhead) and -even worse than that, its design decision to use ldopen for certain +even worse than that, its design decision to use dlopen for certain "separated" library features (NSS, locales, IDN, ...), which makes it nearly impossible to use glibc for static linking in non-trivial programs. Unfortunately, for certain tools we will ship glibc for pragmatic reasons. Of