Date: Mon, 2 Sep 2002 21:53:26 -0400 From: "Matthew Emmerton" <matt@gsicomp.on.ca> To: "Juli Mallett" <jmallett@FreeBSD.ORG>, <current@FreeBSD.ORG> Cc: "Bruce Evans" <bde@zeta.org.au>, "Peter Wemm" <peter@wemm.org>, "Jake Burkholder" <jake@locore.ca> Subject: Re: aout support broken in gcc3 Message-ID: <008501c252ec$b38320f0$1200a8c0@gsicomp.on.ca> References: <20020903005911.V3848-100000@gamplex.bde.org> <Pine.BSF.4.21.0209021323440.74201-100000@xena.gsicomp.on.ca> <20020902193842.GA49786@dragon.nuxi.com> <20020902130333.A60287@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> * De: David O'Brien <dev-null@NUXI.com> [ Data: 2002-09-02 ] > [ Subjecte: Re: aout support broken in gcc3 ] > > 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". > > I *hope* nobody is suggesting to rip out the ability to use compat22, let > alone the a.out execution facilities in the Kernel. Though maybe making > those optional would be good? Sorry, I didn't mean what I said. I meant what Juli suggested (support for compat2x) but removing native 5.x support for a.out, which will help "clean up" some things in the tools chain. -- Matt Emmerton 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?008501c252ec$b38320f0$1200a8c0>