Daniel Jacobowitz wrote:
On Thu, Jul 31, 2003 at 01:14:33AM +0100, Philip Blundell wrote:
On Sun, 2003-07-27 at 02:41, Gianluigi Tiesi wrote:
This makes impossible to statically link a program usingDoesn't --enable-static-nss actually disable the normal NSS mechanism? This switch is really just a hack to allow you to complete a libc build
gethostname/byname etc. since it uses dlopen and
need .so files, ld-so and libc.so.
before you have dynamic linking operational. I would be reluctant to
turn it on in production.
The static nss libraries are also documented not to work in a number of cases, if I remember right. The glibc maintainers just really, really want you to link dynamically.
Compiling glibc without --enable-static-nss produces these .a files: flender:/usr/src/work/glibc/2/glibc-2.2.5# find . -name libnss\*.a ./i386-linux/obj/resolv/libnss_dns_pic.a ./i386-linux/obj/nss/libnss_files_pic.a ./i386-linux/obj/hesiod/libnss_hesiod_pic.a ./i386-linux/obj/nis/libnss_nis_pic.a ./i386-linux/obj/nis/libnss_nisplus_pic.a ./i386-linux/obj/nis/libnss_compat_pic.a
but they are collected by no one of glibc packages, I think here it's enough to include all of these .a files lib libc6-dev without
modifing compile-time options....

