From owner-freebsd-arch@FreeBSD.ORG Thu May 1 11:05:49 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 A492E37B407 for ; Thu, 1 May 2003 11:05:49 -0700 (PDT) Received: from mail.speakeasy.net (mail13.speakeasy.net [216.254.0.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF2EA43FB1 for ; Thu, 1 May 2003 11:05:47 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 29148 invoked from network); 1 May 2003 18:05:53 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 1 May 2003 18:05:53 -0000 Received: from laptop.baldwin.cx ([216.133.140.1]) by server.baldwin.cx (8.12.8/8.12.8) with ESMTP id h41I5iOv026327; Thu, 1 May 2003 14:05:45 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 01 May 2003 14:05:49 -0400 (EDT) From: John Baldwin To: Julian Elischer cc: "Jacques A. Vidrine" cc: freebsd-arch@FreeBSD.org Subject: Re: Re: `Hiding' libc symbols (was Re: cvs commit: src/lib/libc/gen ...) 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: Thu, 01 May 2003 18:05:50 -0000 On 01-May-2003 Julian Elischer wrote: > > > On Thu, 1 May 2003, Paul Richards wrote: > >> On Thu, May 01, 2003 at 09:30:32AM -0500, Jacques A. Vidrine wrote: >> > On Thu, May 01, 2003 at 03:02:55PM +0100, Paul Richards wrote: >> > > On Wed, Apr 30, 2003 at 11:41:35AM -0500, Jacques A. Vidrine wrote: >> > > > [Trimmed cc:list; moving to freebsd-arch] >> > > > >> > > > >> > > > First, has something been broken by making strlcpy/strlcat into a weak >> > > > reference? >> > > >> > > Yes, deliberately overloading it from an application now no longer >> > > works. >> > >> > Give me a break. Good, it should not work by accident. An >> > application might define strlcpy for its own use, but we should NEVER >> > use the application's strlcpy. [1] >> >> An application doesn't have any business defining a strlcpy, since >> str* is reserved. The qpopper application is just broken and we >> shouldn't be "fixing" our libc to work around that. > > > > Exactly.. > This is why we have ports > It is also th king of thing that "configure" is supposed to fix.. > The port should be altered to fix this and teh maintainers contected and > told of the problem. > > I don't see why the libc needs to be changed at all. Agreed. Somebody just needs to sit down and fix the qpopper port and then the argument for this change goes away and it can be reverted. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/