From owner-freebsd-arch@FreeBSD.ORG  Wed Jul  7 13:19:32 2010
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id C8A1D106566B
	for <freebsd-arch@freebsd.org>; Wed,  7 Jul 2010 13:19:32 +0000 (UTC)
	(envelope-from nwhitehorn@freebsd.org)
Received: from mail.icecube.wisc.edu (trout.icecube.wisc.edu [128.104.255.119])
	by mx1.freebsd.org (Postfix) with ESMTP id 9FC598FC0A
	for <freebsd-arch@freebsd.org>; Wed,  7 Jul 2010 13:19:32 +0000 (UTC)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mail.icecube.wisc.edu (Postfix) with ESMTP id CFC9F582C9
	for <freebsd-arch@freebsd.org>; Wed,  7 Jul 2010 08:19:31 -0500 (CDT)
X-Virus-Scanned: amavisd-new at icecube.wisc.edu
Received: from mail.icecube.wisc.edu ([127.0.0.1])
	by localhost (trout.icecube.wisc.edu [127.0.0.1]) (amavisd-new,
	port 10030)
	with ESMTP id 44zw0946ywgM for <freebsd-arch@freebsd.org>;
	Wed,  7 Jul 2010 08:19:31 -0500 (CDT)
Received: from wanderer.tachypleus.net
	(adsl-76-208-69-179.dsl.mdsnwi.sbcglobal.net [76.208.69.179])
	by mail.icecube.wisc.edu (Postfix) with ESMTP id 81E33582C5
	for <freebsd-arch@freebsd.org>; Wed,  7 Jul 2010 08:19:31 -0500 (CDT)
Message-ID: <4C347EE2.6080301@freebsd.org>
Date: Wed, 07 Jul 2010 08:19:30 -0500
From: Nathan Whitehorn <nwhitehorn@freebsd.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
	rv:1.9.1.10) Gecko/20100627 Thunderbird/3.0.5
MIME-Version: 1.0
To: freebsd-arch@freebsd.org
References: <20100706.174919.29649800801850.imp@bsdimp.com>
In-Reply-To: <20100706.174919.29649800801850.imp@bsdimp.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: ObsoleteFiles and TARGET_ARCH
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jul 2010 13:19:32 -0000

On 07/06/10 18:49, M. Warner Losh wrote:
> I'm wondering...
>
> Why do we use TARGET_ARCH so much inside of ObsoleteFiles?  It seems
> like it should be used only when we obsolete files on some
> architectures, but retain them on others.  Instead, it seems to be
> used to obsolete files that normally exist on a specific
> architecture.  This seems backwards.
>
> Also, we need to change this, but I don't (yet) define a
> TARGET_CPUARCH.
>
> Also, why is this TARGET_ARCH and not MACHINE_ARCH?  That suggests
> we're invoking it wrong if this is "needed" for the cross build case
> to "work".
>    

It mostly seems to be used to remove things from /usr/include/machine, 
in which case it should also probably be TARGET, not TARGET_ARCH or 
TARGET_CPUARCH.
-Nathan