From owner-freebsd-current Tue Sep 3 1:27:39 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 4287F37B400; Tue, 3 Sep 2002 01:27:37 -0700 (PDT) Received: from rhymer.cogsci.ed.ac.uk (rhymer.cogsci.ed.ac.uk [129.215.144.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDC4C43E65; Tue, 3 Sep 2002 01:27:35 -0700 (PDT) (envelope-from richard@cogsci.ed.ac.uk) Received: (from richard@localhost) by rhymer.cogsci.ed.ac.uk (8.9.3/8.9.3) id JAA04147; Tue, 3 Sep 2002 09:27:34 +0100 (BST) Date: Tue, 3 Sep 2002 09:27:34 +0100 (BST) Message-Id: <200209030827.JAA04147@rhymer.cogsci.ed.ac.uk> From: Richard Tobin Subject: Re: aout support broken in gcc3 To: Juli Mallett In-Reply-To: Juli Mallett's message of Mon, 2 Sep 2002 16:31:31 -0700 Organization: just say no Cc: Julian Elischer , current@FreeBSD.ORG 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 > GCC being able to produce a.out format binaries has nothing to do with > the ability of a Lisp or Prolog to compile to object files, Correct. > and read such, whether said object files be a.out or ELF or COFF or PECOFF or > Mach-O or ... False. As I said, I have systems that read a.out format object files and they would need to be ported to read ELF object files instead. Furthermore, they write themselves out (after loading object files) in a.out format, and would need to be ported to write themselves out in ELF format. -- Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message