From owner-freebsd-arch@FreeBSD.ORG Mon May 5 14:20:30 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 D6D3737B401; Mon, 5 May 2003 14:20:30 -0700 (PDT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA0DA43FBD; Mon, 5 May 2003 14:20:28 -0700 (PDT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.9/8.12.9) with ESMTP id h45LKRMr041521; Tue, 6 May 2003 01:20:28 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.9/8.12.9/Submit) id h45LKRKK041520; Tue, 6 May 2003 01:20:27 +0400 (MSD) Date: Tue, 6 May 2003 01:20:27 +0400 From: "Andrey A. Chernov" To: Dag-Erling Smorgrav Message-ID: <20030505212027.GA41263@nagual.pp.ru> References: <20030501182820.GA53641@madman.celabo.org> <20030501191027.GA53801@madman.celabo.org> <20030505110601.H53365@beagle.fokus.fraunhofer.de> <20030505175426.GA19352@madman.celabo.org> <20030505205051.GA40572@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i cc: freebsd-arch@freebsd.org 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 21:20:31 -0000 On Mon, May 05, 2003 at 23:05:15 +0200, Dag-Erling Smorgrav wrote: > "Andrey A. Chernov" writes: > > Better reject such error automatically at the linkage stage. Programmers > > are always free to redefine their functions in case of conflict. > > There must be something wrong with my MUA, as I can't see a patch > attached to your message. Could you please resend it? Which one do you mean? If one for affected ports, it is corresponding maintainers task. If one for libc, it is difficult (for me). The problem is that threads people do all that hiding in first place for their own needs. To simple unhide it, breaks threads. I think they must change replacement they need for functions to be truely internal, it makes all unhiding automatically.