From owner-freebsd-ports@freebsd.org Sat Sep 28 23:55:56 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 A11DE132E2D for ; Sat, 28 Sep 2019 23:55:56 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (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 46glt43hHfz3GW8 for ; Sat, 28 Sep 2019 23:55:56 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id 77BA713A6B; Sat, 28 Sep 2019 23:55:56 +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> <20190928220050.GG49516@bastion.zyxst.net> <20190928224615.GH49516@bastion.zyxst.net> Date: Sun, 29 Sep 2019 01:55:53 +0200 In-Reply-To: <20190928224615.GH49516@bastion.zyxst.net> (tech-lists@zyxst.net's message of "Sat, 28 Sep 2019 23:46:15 +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 23:55:56 -0000 tech-lists writes: > On Sat, Sep 28, 2019 at 11:00:50PM +0100, tech-lists wrote: > > [...] > > in the meantime, for a test, I made a fresh poudriere jail, and tried to build > lang/python36 with CPUTYPE?=btver1 in its make.conf and it fais the same way Could be a compiler[1], kernel or hardware bug then. For compiler try using clang80 from devel/llvm80 or upgrade to the upcoming FreeBSD 12.1. For kernel try booting -CURRENT kernel (e.g., from snapshot) while keeping old world/base. For hardware try reproducing on another machine or virtual machine. Alternatively, track down which function returns unexpected result, disassemble and/or minimize then ask for feedback on toolchain@ list. To get debugging symbols build WITH_DEBUG=1. Or maybe someone has better ideas. -- [1] If the code uses instructions not supported by CPU then kernel should return SIGILL (and dump core) but maybe CPython catches the signal or similar.