From owner-freebsd-arch@FreeBSD.ORG Tue May 6 22:59:22 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 0DD9037B401 for ; Tue, 6 May 2003 22:59:22 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 681E143FA3 for ; Tue, 6 May 2003 22:59:21 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0555.cvx40-bradley.dialup.earthlink.net ([216.244.44.45] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19DHxO-0002iZ-00; Tue, 06 May 2003 22:59:10 -0700 Message-ID: <3EB8A058.E3F1D452@mindspring.com> Date: Tue, 06 May 2003 22:57:44 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dag-Erling Smorgrav References: <20030501191027.GA53801@madman.celabo.org> <20030505110601.H53365@beagle.fokus.fraunhofer.de> <20030505175426.GA19352@madman.celabo.org> <20030505205051.GA40572@nagual.pp.ru> <20030505231135.GA21953@madman.celabo.org> <20030505231837.GA44533@nagual.pp.ru> <20030506170823.GI83663@lucky.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4e71fce681e859ea296e5ccdb6407c607387f7b89c61deb1d350badd9bab72f9c350badd9bab72f9c cc: "Andrey A. Chernov" 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: Wed, 07 May 2003 05:59:22 -0000 Dag-Erling Smorgrav wrote: > "Andrey A. Chernov" writes: > > There is no problem. Each *.h function prototype can be accompanied with > > some assembler instruction making it strong reference. The same thing can > > be conditionalized at the header level using _POSIX_SOURCE or other > > defines. So, linker will know, what headers are included. > > I would like to draw your attention to points b) and c) above and ask > how you plan to address them. Forget that, I want to see his "make it a strong reference in the header file for multiple object files in the same binary"-foo! -- Terry