Date: Thu, 4 Feb 1999 08:29:27 -0500 (EST) From: Matt Behrens <matt@zigg.com> To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com> Cc: Satoshi Asami <asami@FreeBSD.ORG>, myke@ees.com, stormy@futuresouth.com, freebsd-stable@FreeBSD.ORG Subject: Re: 3.0-19990202-SNAP a.out problem Message-ID: <Pine.BSF.4.05.9902040824590.57171-100000@megaweapon.zigg.com> In-Reply-To: <87115.918133531@zippy.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Will they still be buildable? (I use the XFree86 port, personally. I think it's because I'm masochistic.) I think that there's some confusion surrounding this. I think that most people think they're going to wake up and their old binaries are going to stop working. What I'm wondering is if 3.1 will do the following: 1. Not have any a.out libraries or binaries, only ELF, for 3.x-level stuff. (Generally a Good Thing, unless someone went on a building spree for 3.0-RELEASE, then died or something. Doubt this is much of anything to worry about though.) :) 2. Have compat1x and compat2[012], just like every other version of FreeBSD, able to run a.out binaries from those old releases. 3. Be able to build any a.out libraries when needed for compatibility's sake. (i.e. XFree86's old libs). On Thu, 4 Feb 1999, Jordan K. Hubbard wrote: : > What about XFree86 a.out libs? netscape needs those too. : : What about them? Those are bundled with XFree86, last I checked, and : not of any immediate concern. - Matt Behrens <matt@zigg.com> Network Administrator, zigg.com <http://www.zigg.com/>; Engineer, Nameless IRC Network <http://www.nameless.net/>; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9902040824590.57171-100000>