On 12/10/06, Yann E. MORIN <<a href="mailto:yann.morin.1998@anciens.enib.fr">yann.morin.1998@anciens.enib.fr</a>> wrote:<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Denis, all, On Sunday 10 December 2006 040, Denis Vlasenko wrote: > Static glibc cannot do name resolution. Forget "ping <hostname>" - > it won't work. (Didn't check recently - maybe fixed now). Yes it does. *But* you have to have at least one of those:    libnss_{compat,dns,files,hesiod,nis{,plus}}*.so And, yes, those are shared libraries, and you need them to be present even if your binary was statically linked. NSS stands for Name Service Switch, and is configured via /etc/nsswitch.conf. And those libraries are linked against libc.so and ld-linux.so, then you'll have to have the shared C library and the dynamic loader as well! Thus, compiling static binaries, which require name services (eg. DNS), with glibc anyway sucks in libc.so and at least one of the libnss libraries... So, stay away from static linking with glibc. Use uClibc. Regards, Yann E. MORIN.</blockquote><div> Well said.  There really isn't much of a reason to statically link with glibc.  If you do, you can live with seeing Busybox spit out some warnings. </div> </div>