From owner-cvs-all@FreeBSD.ORG Mon Aug 1 01:03:47 2005 Return-Path: X-Original-To: cvs-all@FreeBSD.org Delivered-To: cvs-all@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B55816A41F; Mon, 1 Aug 2005 01:03:47 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id B251B43D48; Mon, 1 Aug 2005 01:03:46 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j7110Lfp088270; Sun, 31 Jul 2005 19:00:21 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 31 Jul 2005 19:01:11 -0600 (MDT) Message-Id: <20050731.190111.96940184.imp@bsdimp.com> To: jeremie@le-hen.org From: "M. Warner Losh" In-Reply-To: <20050801000209.GZ68965@obiwan.tataz.chchile.org> References: <20050731185925.GU68965@obiwan.tataz.chchile.org> <20050731.164241.119877948.imp@bsdimp.com> <20050801000209.GZ68965@obiwan.tataz.chchile.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, netchild@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src Makefile.inc1 ObsoleteFiles.inc src/share/man/man7 build.7 X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Aug 2005 01:03:47 -0000 In message: <20050801000209.GZ68965@obiwan.tataz.chchile.org> Jeremie Le Hen writes: : However, if someone can provide me a list of all possible file(1) : output concerning the processor for which a binary has been compiled for, : I would be glad to provide a patch. TARGET_ARCH is what you want. Why won't that work again? Seems to me that it is exactly what you want. For non-cross builds, it is set automatically for you. For cross builds, you gotta set it anyway on each of the other steps, so it hardly sounds burdonsom to set it for the obsolete file check. However, when cross building, it is rare that you install, on the machine you are cross building from, to a DESTDIR that's likely to have obsolete files in it. DESTDIR is usually for installing images that you are going to later do something with. While one could export / and /usr via nfs, mount those and do the cross install that way, I'd say that's relatively rare. The file(1) thing is a kludge and should be avoided. You can't possibly tell TARGET=i386 from TARGET=pc98 since both are TARGET_ARCH=i386 and all binaries, modulo kernel ones, from one run unchanged on the other. Warner