From owner-freebsd-ports@freebsd.org Mon Jan 30 12:56:03 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5BDA0CC74EB for ; Mon, 30 Jan 2017 12:56:03 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [185.24.122.233]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F2ED3615; Mon, 30 Jan 2017 12:56:02 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from crayon2.yoonka.com (crayon2.yoonka.com [10.70.7.20]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v0UCtxfr023532 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 30 Jan 2017 12:55:59 GMT (envelope-from list1@gjunka.com) Subject: Re: poudriere and CPUTYPE To: Mathieu Arnold , freebsd-ports@freebsd.org References: <9df9eff0-aae9-18b8-641f-2f5209faad79@gjunka.com> <07e5ed6f-97be-5977-017e-18ee1de3ff36@FreeBSD.org> From: Grzegorz Junka Message-ID: <2631d1a5-b150-eec4-eba3-01acf40a9bc6@gjunka.com> Date: Mon, 30 Jan 2017 12:55:59 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <07e5ed6f-97be-5977-017e-18ee1de3ff36@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2017 12:56:03 -0000 On 30/01/2017 09:14, Mathieu Arnold wrote: > Le 29/01/2017 à 18:17, Grzegorz Junka a écrit : >> When building packages for a different machine it's possible to >> specify CPU target, e.g.: >> >> CPUTYPE?=core2 >> >> However, when building packages that depend on other packages >> poudriere will install the already build dependencies in order to >> build the new packages. That will fail if the CPU on the build machine >> doesn't execute instructions specified in the CPUTYPE for the target >> machine. For example, on amdfam10 build machine pkg build for core2 >> fails to install and as a result none of the packages can be build >> since pkg is required to install any dependency. >> >> How this CPUTYPE should be used then when building for different >> machines? Bhyve? > You should use the oldest CPUTYPE that any machine that will use those > packages has. If the host does not support core2, don't use it, use some > older one. Also, if it does not support it, bhyve won't work there as it > is too old. > > (As a rule of the thumb, don't use CPUTYPE, at best you will win a few > cycles here and there, but it will more generally be more painful when > you discover you need to use the packages some place where that CPUTYPE > is to recent.) I understand. Does it mean that poudriere can't be used to build packages for a completely different architecture, e.g. ARM using an amd64 build machine? I think that's called crosscompiling?