Date: Tue, 17 Jun 2003 09:31:54 -0700 From: Joe Kelsey <joek@mail.flyingcroc.net> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: questions@freebsd.org Subject: Re: Tools to modify shared libraries Message-ID: <3EEF427A.1080106@mail.flyingcroc.net> In-Reply-To: <20030617162302.GC584@dhcp01.pn.xcllnt.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EEF427A.1080106>