From owner-freebsd-current Tue Sep 3 0: 7:58 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83D1037B400 for ; Tue, 3 Sep 2002 00:07:56 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E3F943E42 for ; Tue, 3 Sep 2002 00:07:56 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.6/8.12.2) with ESMTP id g8377qfO054124; Tue, 3 Sep 2002 00:07:52 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.6/8.12.5/Submit) id g8377qot054123; Tue, 3 Sep 2002 00:07:52 -0700 (PDT) Date: Tue, 3 Sep 2002 00:07:52 -0700 From: "David O'Brien" To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: aout support broken in gcc3 Message-ID: <20020903070752.GA54037@dragon.nuxi.com> Reply-To: current@FreeBSD.ORG Mail-Followup-To: David O'Brien , Julian Elischer , current@FreeBSD.ORG References: <20020902193842.GA49786@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 02, 2002 at 12:42:47PM -0700, Julian Elischer wrote: > > On Mon, Sep 02, 2002 at 01:24:19PM -0400, Matthew Emmerton wrote: > > > I thought it was part of the plan to drop all traces of a.out support in > > > 5.x. Am I wrong? > > > > We should be *very* careful to accurately describe what is being > > suggested. > > > > I believe it is that 5.x a.out binaries not be supported. However, 2.x > > a.out binaries will be supported. This is different thatn "drop all > > traces of a.out support". > > yes binary support will remain.. if you need to generate new ones (?) > unpack a 2.2.6 system into a chroot tree (jail?) and make it there :-) *sigh* This *still* isn't clear what is being suggested. (also seen in other emails in this thread, just picked this one to repond to) This is what BDE said: Actually, I agree. Not having a clean break in FreeBSD-3 was very expensive. Support for running aout binaries and compatibility cruft to support old binaries should have been dropped too. This is NOT a toolchain issue he is talking about, but a kernel one. Please forget all about the toolchain issue. It is a non-issue. I and kan are the only ones that it has inconvinced. Everyone else has been able to totally ignore it. I'll probably do something about it next week. _The_ issue is to understand exactly what is being discussed about "compatibility cruft to support old binaries should have been dropped too"Q. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message