From owner-freebsd-hackers Tue Nov 17 07:40:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26310 for freebsd-hackers-outgoing; Tue, 17 Nov 1998 07:40:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26304 for ; Tue, 17 Nov 1998 07:40:56 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from o2.cs.rpi.edu (root@o2.cs.rpi.edu [128.113.96.156]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id KAA17683; Tue, 17 Nov 1998 10:40:31 -0500 (EST) Received: from localhost (crossd@localhost) by o2.cs.rpi.edu (8.9.1a/8.9.1) with ESMTP id KAA14266; Tue, 17 Nov 1998 10:40:31 -0500 (EST) X-Authentication-Warning: o2.cs.rpi.edu: crossd owned process doing -bs Date: Tue, 17 Nov 1998 10:40:30 -0500 From: "David E. Cross" To: "Kaleb S. KEITHLEY" cc: hackers@FreeBSD.ORG Subject: Re: First Impression of 3.0-RELEASE In-Reply-To: <36519613.52DA940@ics.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I will answer this one point with my experience on SGI IRIX 6.2+ machines that experience this same behaviour. If I link libpng.so with libz.so, I *still* need to link any binaries with both libpng.so and libz.so. > Third, transitive linking doesn't work. I.e if I link libXt with -lSM > -lICE, and then link a program with -lXt, I get unresolved externals for > libSM and libICE. Should I? The program does not make any calls to libSM > or libICE, so I don't think I should. Leastways I don't get them on all > the other systems that use ELF, and I'd wager that if I looked, I could > find something in the ELF specification (a.k.a. the SystemV ABI) that > speaks to this. Of the three things, I think this is far and away the > most serious shortcoming. Nothing's going to fix this for 3.0, so some > sort of kludgie work-around will have to be employed. I hope someone > will fix this for the next release. -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message