From owner-freebsd-arm@FreeBSD.ORG Thu Feb 12 05:57:35 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CBFBE9C8 for ; Thu, 12 Feb 2015 05:57:35 +0000 (UTC) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B01B7BD9 for ; Thu, 12 Feb 2015 05:57:35 +0000 (UTC) Received: from comporellon.tachypleus.net (polaris.tachypleus.net [75.101.50.44]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t1C5vWsW003083 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 11 Feb 2015 21:57:33 -0800 Message-ID: <54DC40CC.2090103@freebsd.org> Date: Wed, 11 Feb 2015 21:57:32 -0800 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: freebsd-arm@freebsd.org Subject: Re: FreeBSD/arm64 MACHINE/MACHINE_ARCH identification References: <607BF592-A09B-4DB4-9872-C9E63066AB57@bsdimp.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVbCxzNvb4nHgxgwBJCNA4cNo8DpUoZPYlHeuVYWxMtVBPABw3/gzM78kt7ROTeSR656SzC+I8NeoZVJCBhbBj++ruNpu/ilQ38= X-Sonic-ID: C;dKwgCXyy5BGIYOTWjn0JFw== M;dNKkCXyy5BGIYOTWjn0JFw== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2015 05:57:35 -0000 On 02/11/15 19:46, Ed Maste wrote: > On 11 February 2015 at 19:20, Warner Losh wrote: >> Linux used the original aarch64, but later changed to arm64. > Are you sure? As far as I can tell Linux reports "aarch64" for uname > -m (i.e., hw.machine) and that is what config.guess / autoconf > expects. > >> I suggest >> that we follow this carefully. We botched the naming of amd64 and have >> dozens of warts in our build system because of it. > Indeed. We have to be sure that this is correct before it makes it to HEAD. > >> I strongly object to the MACHINE change for reasons stated above, but the MACHINE_ARCH >> is likely a very good change since it aligns with the expected values for configuring things like >> clang, gcc, bintuils, etc. > As far as I can tell it's uname -m / sysctl hw.machine that's used by > autoconf. Uname -p is hw.machine_arch and doesn't seem to be used. > _______________________________________________ It usually uses uname -p. For example, on powerpc64: $ uname -m powerpc $ uname -p powerpc64 $ ./configure checking build system type... powerpc64-portbld-freebsd11.0 checking host system type... powerpc64-portbld-freebsd11.0 Most software does the right thing here, with the exception of a few rare custom build systems I've run into. -Nathan