From owner-freebsd-current Mon Sep 2 16:31:35 2002 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id B992937B400; Mon, 2 Sep 2002 16:31:31 -0700 (PDT) Date: Mon, 2 Sep 2002 16:31:31 -0700 From: Juli Mallett To: Richard Tobin Cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: aout support broken in gcc3 Message-ID: <20020902163129.A75558@FreeBSD.org> References: <200209022310.AAA24142@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: <200209022310.AAA24142@rhymer.cogsci.ed.ac.uk>; from richard@cogsci.ed.ac.uk on Tue, Sep 03, 2002 at 12:10:03AM +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-02 ] [ Subjecte: Re: aout support broken in gcc3 ] > > I think you're extremeley confused. > > In what way? Or are you just being rude? 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, and read such, whether said object files be a.out or ELF or COFF or PECOFF or Mach-O or ... For example, Mono works with PECOFF32 images, and can read them in and out on Windows, NetBSD, OpenBSD, FreeBSD, Linnex, and probably QNX. And nothing says that '.o' or 'a.out' implies the image is in a.out or ELF or PECOFF or ... format. juli. -- 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