Date: Sun, 29 Sep 2019 15:46:34 +0200 From: Jan Beich <jbeich@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: make.conf for a poudriere jail and CPUTYPE Message-ID: <v9tb-43lx-wny@FreeBSD.org> In-Reply-To: <20190929095732.GA38643@bastion.zyxst.net> (tech-lists@zyxst.net's message of "Sun, 29 Sep 2019 10:57:32 %2B0100") References: <20190928135343.GE49516@bastion.zyxst.net> <r240-cxo8-wny@FreeBSD.org> <20190928145055.GF49516@bastion.zyxst.net> <y2y8-bcuc-wny@FreeBSD.org> <20190928220050.GG49516@bastion.zyxst.net> <20190928224615.GH49516@bastion.zyxst.net> <pnjk-7z7a-wny@FreeBSD.org> <20190929010925.GJ49516@bastion.zyxst.net> <v9tb-6f2i-wny@FreeBSD.org> <20190929022242.GK49516@bastion.zyxst.net> <20190929095732.GA38643@bastion.zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
tech-lists <tech-lists@zyxst.net> writes: > On Sun, Sep 29, 2019 at 03:22:42AM +0100, tech-lists wrote: > >>On Sun, Sep 29, 2019 at 03:56:05AM +0200, Jan Beich wrote: >> >>>Is that for host or after upgrade? Your build logs had the following: >>> >>>> _CCVERSION_921dbbb2=FreeBSD clang version 6.0.1 >>> (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1) Target: >>> x86_64-unknown-freebsd12.0 Thread model: posix InstalledDir: >>> /usr/bin >>> >>>FreeBSD 11.2/12.0 have Clang 6, FreeBSD 11.3/12.1 have Clang 8. >> >>That's the host (recent 12-stable). The build log was the poudriere jail which is 12.0-p10. I >>made a 13-current poudriere jail a short while ago and the same error happens. >> >>Now building a 12,0-p10 jail on desktop hardware > > Well, that was interesting! build of python36 and lzo2 succeeds on desktop host !!!!! > > this machine succeeds: > > Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz / 32Gb RAM > FreeBSD 12.1-PRERELEASE r352514 > poudriere jail is 12.0-RELEASE-p10 1200086 r351263 amd64 > > this one fails: > > Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz x2 / 192Gb RAM > FreeBSD 12.1-PRERELEASE #0 r352507 > poudriere jail is 13.0-CURRENT 1300048 r352860 amd64 > also failed on 12.0-RELEASE-p10 1200086 r351263 amd64 > > what do you think? A CPU bug in a SIMD instruction? Did you apply microcode update? Maybe older Intel CPUs have trouble with code optimized for AMD CPUs. For one, try CPUTYPE?=native on the failing CPU to check if Clang knows about Intel quirks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?v9tb-43lx-wny>