Date: Wed, 23 Sep 1998 06:13:31 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: peter@netplex.com.au (Peter Wemm) Cc: tlambert@primenet.com, jkh@time.cdrom.com, chuckr@mat.net, freebsd-current@FreeBSD.ORG Subject: Re: elf & compat Message-ID: <199809230613.XAA12526@usr09.primenet.com> In-Reply-To: <199809230552.NAA12900@spinner.netplex.com.au> from "Peter Wemm" at Sep 23, 98 01:52:56 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809230613.XAA12526>