From owner-freebsd-ports@freebsd.org Sat Sep 28 16:33:03 2019 Return-Path: Delivered-To: freebsd-ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9AB7012AF7B for ; Sat, 28 Sep 2019 16:33:03 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46gZ333LJ1z4NP1 for ; Sat, 28 Sep 2019 16:33:03 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id 6A982F2D8; Sat, 28 Sep 2019 16:33:03 +0000 (UTC) From: Jan Beich To: freebsd-ports@freebsd.org Subject: Re: make.conf for a poudriere jail and CPUTYPE References: <20190928135343.GE49516@bastion.zyxst.net> <20190928145055.GF49516@bastion.zyxst.net> Date: Sat, 28 Sep 2019 18:32:59 +0200 In-Reply-To: <20190928145055.GF49516@bastion.zyxst.net> (tech-lists@zyxst.net's message of "Sat, 28 Sep 2019 15:50:55 +0100") Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Sep 2019 16:33:03 -0000 tech-lists writes: > On Sat, Sep 28, 2019 at 04:17:43PM +0200, Jan Beich wrote: > >>tech-lists writes: >> >>> On Fri, Sep 27, 2019 at 12:33:36PM +0100, tech-lists wrote: >>> >>>> Hi, >>>> >>>> If I'm building ports on a poudriere and the jail I'm building for has say >>>> Host CPU: btver1 and the host running poudriere is Host CPU: sandybridge, is >>>> there any benefit or advantage in defining CPUTYPE?= in the jail's make.conf? >>>> >>>> If yes, which programs does it benefit? I guess maybe openssl >>> >>> thought I'd experiment. Seems setting CPUTYPE?=btver1 causes some ports to >>> fail at the configure or build stage. python36 and lzo2 for example. Unsure >>> why that should be (or where to ask???) >> >>I can't reproduce. Provide poudriere log which documents FreeBSD >>version, compiler type/version/flags, port options, make.conf, etc. > > Ok, for archivers/lzo2: > https://cloud.zyxst.net/~john/FreeBSD/ports/buildfailures/lzo2-2.10_1.log Compare with http://beefy6.nyi.freebsd.org/data/latest-per-pkg/lzo2/2.10_1/120amd64-default.log or mine with CPUTYPE https://reviews.freebsd.org/P325 > for python36: > https://cloud.zyxst.net/~john/FreeBSD/ports/buildfailures/python36-3.6.9.log Compare with http://beefy6.nyi.freebsd.org/data/latest-per-pkg/python36/3.6.9/120amd64-default.log or mine with CPUTYPE https://reviews.freebsd.org/P324 > both of these will build if CPUTYPE?= is commented out [...] > #### /usr/local/etc/poudriere.d/12R-bastion-make.conf #### > OPTIONS_UNSET+=DEBUG > OPTIONS_SET+=OPTIMIZED_CFLAGS > OPTIONS_SET+=ICONV > CPUTYPE?=btver1 > USE_LOCALE=en_GB.UTF-8 > LICENSES_ACCEPTED+=GPLv2+ MSPAT > WITH_CCACHE_BUILD=yes > CCACHE_DIR=/root/.ccache > NO_CCACHE_DEPEND=1 > CCACHE_WRAPPER_PATH= /ccache/libexec/ccache Can you try with *CCACHE* stuff commented out?