From owner-freebsd-current Tue Sep 3 12:52:20 2002 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id B5FC437B400; Tue, 3 Sep 2002 12:52:17 -0700 (PDT) Date: Tue, 3 Sep 2002 12:52:17 -0700 From: Juli Mallett To: Richard Tobin Cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: aout support broken in gcc3 Message-ID: <20020903125217.A56616@FreeBSD.org> References: <200209030827.JAA04147@rhymer.cogsci.ed.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200209030827.JAA04147@rhymer.cogsci.ed.ac.uk>; from richard@cogsci.ed.ac.uk on Tue, Sep 03, 2002 at 09:27:34AM +0100 Organisation: The FreeBSD Project X-Alternate-Addresses: , , , , X-Towel: Yes X-LiveJournal: flata, jmallett X-Negacore: Yes 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 * De: Richard Tobin [ Data: 2002-09-03 ] [ Subjecte: Re: aout support broken in gcc3 ] > > 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. Where exactly does GCC fit into the mix, making this impossible? -- Juli Mallett | FreeBSD: The Power To Serve Will break world for fulltime employment. | finger jmallett@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message