From owner-freebsd-arch@FreeBSD.ORG Tue May 6 11:08:53 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 656F237B401 for ; Tue, 6 May 2003 11:08:53 -0700 (PDT) Received: from gw.nectar.cc (gw.nectar.cc [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6E0843F85 for ; Tue, 6 May 2003 11:08:52 -0700 (PDT) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.nectar.cc (Postfix) with ESMTP id 0E97166; Tue, 6 May 2003 13:08:52 -0500 (CDT) Received: by madman.celabo.org (Postfix, from userid 1001) id A2C8C78C66; Tue, 6 May 2003 13:08:53 -0500 (CDT) Date: Tue, 6 May 2003 13:08:53 -0500 From: "Jacques A. Vidrine" To: Julian Elischer Message-ID: <20030506180853.GH79167@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , Julian Elischer , freebsd-arch@FreeBSD.org References: <20030506175557.GE79167@madman.celabo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.3i-ja.1 cc: freebsd-arch@FreeBSD.org Subject: Re: Re: `Hiding' libc symbols X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2003 18:08:53 -0000 On Tue, May 06, 2003 at 11:02:24AM -0700, Julian Elischer wrote: > If you could do your census again but this time showing which symbols > clash we would have a better idea of what we are talking about.. Uh, that is the list I posted. Yes, that long list included clashing symbols only. > Probably most of these packages have these function 'in case' the system > does not. It's a pretty good mix of those that do it `in case' and those that do it for their own reasons. > You can also bet that if compiled on Linux they don't include > these functions if Linux has them, so I'm willing to bet that many of > them have ways to turn off much of the excess stuff. You would lose the bet. These applications compile and run fine on FreeBSD _now_, also. Whether or not something in libc will change in the future to break it is the question (as in the qpopper example). Or maybe the `bad' code path hasn't yet been hit. Cheers, -- Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal nectar@celabo.org . jvidrine@verio.net . nectar@freebsd.org . nectar@kth.se