From owner-freebsd-stable@FreeBSD.ORG Tue Jun 17 09:31:55 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D1F6037B401; Tue, 17 Jun 2003 09:31:55 -0700 (PDT) Received: from gilliam.users.flyingcroc.net (gilliam.users.flyingcroc.net [207.246.128.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43AD743F3F; Tue, 17 Jun 2003 09:31:55 -0700 (PDT) (envelope-from joek@mail.flyingcroc.net) Received: from mail.flyingcroc.net (zircon.staff.flyingcroc.net [207.246.150.92])h5HGVsAv012131; Tue, 17 Jun 2003 09:31:55 -0700 (PDT) Message-ID: <3EEF427A.1080106@mail.flyingcroc.net> Date: Tue, 17 Jun 2003 09:31:54 -0700 From: Joe Kelsey User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030515 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marcel Moolenaar References: <3EEE4717.2090409@mail.flyingcroc.net> <1055804020.79093.2.camel@rushlight.kf8nh.apk.net> <3EEF19D5.9040706@mail.flyingcroc.net> <20030617154208.GA584@dhcp01.pn.xcllnt.net> <3EEF3883.1080500@mail.flyingcroc.net> <20030617160141.GB584@dhcp01.pn.xcllnt.net> <3EEF3E10.8030205@mail.flyingcroc.net> <20030617162302.GC584@dhcp01.pn.xcllnt.net> In-Reply-To: <20030617162302.GC584@dhcp01.pn.xcllnt.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: stable@freebsd.org cc: questions@freebsd.org Subject: Re: Tools to modify shared libraries X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2003 16:31:56 -0000 Marcel Moolenaar wrote: > Yes it can. Symbol resolution is a fundamental part in linking. > Hence, the linker has all the information it needs to filter the > gratuitously long list of libraries programmers tend to give it > and keep the libraries that actually contributed to the link. > I know of no way to do this in the case of shared libraries. When linking shared libraries, the linker *cannot* resolve any references to other shared libraries other than list them in the .dynamic section with some sort of tag such as DT_NEEDED. Please explain to me how the linker can prune the shared library list at link time. Sorry that this has veered off into a dead-end. I promise to cut the mailing list from any further discussions on this dead-end thread. /Joe