From owner-freebsd-current Tue Aug 22 20: 1: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 120D437B423; Tue, 22 Aug 2000 20:00:57 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id NAA16811; Wed, 23 Aug 2000 13:00:23 +1000 Date: Wed, 23 Aug 2000 13:00:14 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Garrett Wollman Cc: Jeroen Ruigrok van der Werven , Ollivier Robert , "FreeBSD Current Users' list" , green@FreeBSD.ORG Subject: Re: make buildworld br0ken in libutil In-Reply-To: <200008221705.NAA12505@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 22 Aug 2000, Garrett Wollman wrote: > > -On [20000822 17:30], Ollivier Robert (roberto@eurocontrol.fr) wrote: > >> Brian, I'm afraid you broke libutil... Every program using libutil now must > >> depend on libcrypt too. > > No. This is precisely why shared libraries have dependencies. For > static linking, what Brian has done Just Works. For dynamic linking, > libutil needs to depend on libcrypt to get its symbols resolved. > (Alternatively you might be able to do it with weak symbols.) Actually, the change breaks static linking for most programs that use one of the functions described in login_cap(3). This is because it adds login_setcrypt() to the existing spam in login_cap.c. This breaks limits, cron, crontab, inetd and sendmail in /usr/src alone. For dynamic linking, it only wastes time and space for the rarely actually used library. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message