From owner-freebsd-current Tue Sep 22 23:14:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14735 for freebsd-current-outgoing; Tue, 22 Sep 1998 23:14:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14694 for ; Tue, 22 Sep 1998 23:13:51 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id XAA10713; Tue, 22 Sep 1998 23:13:46 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp01.primenet.com, id smtpd010698; Tue Sep 22 23:13:42 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id XAA12526; Tue, 22 Sep 1998 23:13:32 -0700 (MST) From: Terry Lambert Message-Id: <199809230613.XAA12526@usr09.primenet.com> Subject: Re: elf & compat To: peter@netplex.com.au (Peter Wemm) Date: Wed, 23 Sep 1998 06:13:31 +0000 (GMT) Cc: tlambert@primenet.com, jkh@time.cdrom.com, chuckr@mat.net, freebsd-current@FreeBSD.ORG In-Reply-To: <199809230552.NAA12900@spinner.netplex.com.au> from "Peter Wemm" at Sep 23, 98 01:52:56 pm X-Mailer: ELM [version 2.4 PL25] 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 > > So a program which, when build a.out, require an a.out libgnumalloc, > > will, when built ELF, *not* require an ELF libgnumalloc? > > > > How does that work? > > They were provided for link-time compatability with old a.out binaries. > We have not been providing gnumalloc at all for some time. > > The presense of the ELF libgnumalloc stub is just an oversight. > > The reason for /usr/lib/compat in the first place was so that ld and > autoconfig wouldn't "find" -lgnumalloc or -lresolv etc, but without > busting backwards compatability with "old" binaries. Ah. So it's a shared library backward compatability thing, not a "compatability library for linking code that expects those libraries" thing. This is very confusing. I initially thought it was referring to "libcompat", which as we all know implements source compatability routines not specified by standards; it was only after reading through the entire thread that I surmised (wrongly) that it was for programs that expected to be able to link with certain third party libraries... This type of thing needs a bit less assumed context. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message