Hacker News Reader

Comment by edwintorok | Hacker News Reader

Its also useful for creating statically linked executables, which is usually not possible with glibc if you use certain functions (getaddrinfo?).

View on HN

I always thought you could statically link glibc - but your executable will be huge as it needs to pull in the entire plus extras.

Regardless - I'm glad I'm not the only one who is concerned about binary sizes.

IME you can statically link glibc, but your statically linked binary will still call ld.so.

The NSS stuff? And something else?

There's some specific things that are supposed to be modular library-wise.

I think you usually get a warning at link-time if you try to statically link GCC and use a function that requires matching libc version at runtime, getaddrinfo was the one I remembered but there are certainly more functions like that:

  x.c:(.text+0x85): warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking

Reply on news.ycombinator.com