From owner-freebsd-arch@FreeBSD.ORG Mon Jan 10 18:11:05 2005 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E4B6E16A4CE; Mon, 10 Jan 2005 18:11:05 +0000 (GMT) Received: from pittgoth.com (14.zlnp1.xdsl.nauticom.net [209.195.149.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67D0943D31; Mon, 10 Jan 2005 18:11:05 +0000 (GMT) (envelope-from trhodes@FreeBSD.org) Received: from mobile.pittgoth.com (64-144-75-100.client.dsl.net [64.144.75.100]) (authenticated bits=0) by pittgoth.com (8.12.10/8.12.10) with ESMTP id j0AIB3oa042686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 10 Jan 2005 13:11:04 -0500 (EST) (envelope-from trhodes@FreeBSD.org) Date: Mon, 10 Jan 2005 13:11:11 -0500 From: Tom Rhodes To: Ruslan Ermilov Message-ID: <20050110131111.6446bd24@mobile.pittgoth.com> In-Reply-To: <20050110180649.GA45481@ip.net.ua> References: <20050110103332.7dbc2f72@mobile.pittgoth.com> <20050110180649.GA45481@ip.net.ua> X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: arch@FreeBSD.org Subject: Re: Removing rtld-aout X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jan 2005 18:11:06 -0000 On Mon, 10 Jan 2005 20:06:49 +0200 Ruslan Ermilov wrote: > On Mon, Jan 10, 2005 at 10:33:32AM -0500, Tom Rhodes wrote: > > Hi, > > > > Would anyone care if I removed rtld-aout in CURRENT and eventually > > in RELENG_5? It was unhooked over two years ago during the removal > > of a.out support by peter. Reviewing the Makefile, it doesn't seem > > to be built for any architecture. Patch URL is listed below but it > > review shouldn't be needed. > > > > Comments? Yes/no/Tom go away? > > > Rumours were to make it (and a bunch of other a.out remnants) a > port first, then remove. Yep, I recall. And we see how that happened eh? :) Note to whoever makes it a port: this is broken -- Tom Rhodes