From owner-freebsd-current Sat Sep 26 18:19:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16840 for freebsd-current-outgoing; Sat, 26 Sep 1998 18:19:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16830 for ; Sat, 26 Sep 1998 18:19:17 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id TAA18218; Sat, 26 Sep 1998 19:18:53 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id TAA11889; Sat, 26 Sep 1998 19:18:52 -0600 Date: Sat, 26 Sep 1998 19:18:52 -0600 Message-Id: <199809270118.TAA11889@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: obrien@NUXI.com Cc: dawes@rf900.physics.usyd.edu.au, current@FreeBSD.ORG Subject: Re: Finding a.out shared libraries (was: Netscape no longer works with ELF system) In-Reply-To: <19980926175320.A22450@nuxi.com> References: <19980926130720.C20205@freebie.lemis.com> <15680.906795121@time.cdrom.com> <19980926153028.B22040@nuxi.com> <19980927104934.W22169@rf900.physics.usyd.edu.au> <19980926175320.A22450@nuxi.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > An X3323alib.tgz tarball could be added with the a.out libraries > > (should it contain static libs as well as shared libs?). > > > > Or should the current a.out binaries in the FreeBSD-3.0 directory simply > > be replaced with ELF ones? > > alib should only be a.out shared libs. Once the move to ELF is made, we > don't support building an a.out binary any longer. Thus no need for > a.out static libs. Except for the 2.2 branch, which will be around for a while longer.... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message