From owner-freebsd-arch@FreeBSD.ORG Mon May 5 15:14:47 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 A2A2F37B401 for ; Mon, 5 May 2003 15:14:47 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8F0D43F93 for ; Mon, 5 May 2003 15:14:46 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from pcnet1.pcnet.com (localhost [127.0.0.1]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h45MEkBg003625; Mon, 5 May 2003 18:14:46 -0400 (EDT) Received: from localhost (eischen@localhost)h45MEjVP003622; Mon, 5 May 2003 18:14:45 -0400 (EDT) Date: Mon, 5 May 2003 18:14:45 -0400 (EDT) From: Daniel Eischen To: "Andrey A. Chernov" In-Reply-To: <20030505214605.GA41803@nagual.pp.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-arch@freebsd.org cc: Dag-Erling Smorgrav Subject: 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: Mon, 05 May 2003 22:14:47 -0000 On Tue, 6 May 2003, Andrey A. Chernov wrote: > On Mon, May 05, 2003 at 23:25:46 +0200, Dag-Erling Smorgrav wrote: > > > > The patch that makes the linker produce warnings or errors like you > > suggested. You seemed so convinced it was the best solution that I > > figured you had to have a patch ready to commit. > > I don't write one yet (since some functions are still hidden by threads). > From first look, it will be based on ".protected" gas instruction or > something like. As the person who went through libc and added most of the weak symbols in order to satisfy the needs of the threads library and to separate libc_r from libc, I would kindly suggest that you leave things alone. But if want to change things, please make sure they work with all the threads libraries that we currently have. I don't want the burden of doing this nor have it impact our current efforts. -- Dan Eischen