Date: Tue, 3 Sep 2002 12:52:17 -0700 From: Juli Mallett <jmallett@FreeBSD.org> To: Richard Tobin <richard@cogsci.ed.ac.uk> Cc: Julian Elischer <julian@elischer.org>, current@FreeBSD.ORG Subject: Re: aout support broken in gcc3 Message-ID: <20020903125217.A56616@FreeBSD.org> 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 %2B0100 References: <200209030827.JAA04147@rhymer.cogsci.ed.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
* De: Richard Tobin <richard@cogsci.ed.ac.uk> [ 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 <jmallett@FreeBSD.org> | 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020903125217.A56616>