From owner-freebsd-current Tue Aug 22 9:43:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 9606037B42C; Tue, 22 Aug 2000 09:43:31 -0700 (PDT) Received: from grimreaper.grondar.za ([196.7.18.138] ident=root) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13RH96-0000qM-00; Tue, 22 Aug 2000 18:43:29 +0200 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e7MGiJe01520; Tue, 22 Aug 2000 18:44:19 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200008221644.e7MGiJe01520@grimreaper.grondar.za> To: Paul Richards Cc: Jeroen Ruigrok van der Werven , Ollivier Robert , "FreeBSD Current Users' list" , green@FreeBSD.ORG Subject: Re: make buildworld br0ken in libutil References: <39A2A98E.EC1D33C4@originative.co.uk> In-Reply-To: <39A2A98E.EC1D33C4@originative.co.uk> ; from Paul Richards "Tue, 22 Aug 2000 17:25:50 +0100." Date: Tue, 22 Aug 2000 18:44:19 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A growing libc makes static binaries grow and makes it more difficult to > strip out unneeded functionality from a minimalist system install. I'd > been inclined to try and move things the other way and strip stuff out > of libc into separate libraries but that's obviously not in vogue at the > moment. Static binaries don't pull in the whole of libc; they just pull in what they need, be it from libc or libcrypt, so size should not change. The _shared_ libc will get bigger, but we'll lose the shared libcrypto. > Why does crypt need to be in libc? Not even a significant fraction of > applications need crypt? Goes for very many libc components. Quite a lot of userland needs libcrypt (not much as a proportion, but a non-insignificant number). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message