Date: Wed, 30 Oct 2002 23:54:44 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: David Schultz <dschultz@uclink.berkeley.edu> Cc: Doug Rabson <dfr@nlsystems.com>, Peter Wemm <peter@wemm.org>, Nate Lawson <nate@root.org>, current@FreeBSD.ORG Subject: Re: libc size Message-ID: <3DC0E1C4.2C20D263@mindspring.com> References: <20021030214158.CB6EA2A88D@canning.wemm.org> <20021030221417.J22480-100000@herring.nlsystems.com> <20021031053202.GA26280@HAL9000.homeunix.com> <3DC0D9C9.CC889413@mindspring.com> <20021031074236.GA27185@HAL9000.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David Schultz wrote:
> At least in the case of the base system, it should be easy to link
> all programs that actually use the resolver with -lresolv. Is
> there some standard that says that the resolver is an integral
> part of the C library, such that separating the two would break
> compatibility beyond comprehension?
It is a historical matter of pride in BSD-land that the resolver
is both available merely by linking libc ("BSD is a true networking
OS"), and that the resolver code is perpetually out of datem
relative to the ISC BIND distribution version of the resolver
code.
> If you wanted to be really evil, I suppose you could have a libc.a
> that included the resolver and a libc.so that didn't. ;-)
It's a lot easier to just have universal rules, and ignore the
fact that ELF lets you do these things, if you want to ignore the
fact that ELF was never written for static libraries in the first
place, and let people link things static. 8-) 8-).
-- Terry
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DC0E1C4.2C20D263>