From owner-freebsd-current Mon Nov 23 13:05:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16966 for freebsd-current-outgoing; Mon, 23 Nov 1998 13:05:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16957 for ; Mon, 23 Nov 1998 13:05:45 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id IAA05834; Tue, 24 Nov 1998 08:10:35 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199811232110.IAA05834@cimlogic.com.au> Subject: Re: Elf linker question. In-Reply-To: from Julian Elischer at "Nov 23, 98 12:41:25 pm" To: julian@whistle.com (Julian Elischer) Date: Tue, 24 Nov 1998 08:10:35 +1100 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > > I'm doing some work in a 3.0 system using the elf linker. > It seems that the new linker is insisting on me including libraries > that I never needed before.. In other words, I thin it's trying to resolve > symbols in functions I'm not using. Does anyone have comments on this? I guess you are linking against shared libraries? A static link should work as previously. > The old aout linker didn't need me to specify libraries that were not in > my call-graph. THe new one seems to need them. We now have standard binutils behaviour, like it or not. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message