Date: Sat, 26 Jun 2021 14:53:51 -0700 From: Mark Millard via freebsd-ports <freebsd-ports@freebsd.org> To: bob prohaska <fbsd@www.zefox.net> Cc: FreeBSD ports <freebsd-ports@freebsd.org>, freebsd-arm <freebsd-arm@freebsd.org>, FreeBSD Toolchain <freebsd-toolchain@freebsd.org> Subject: Re: llvm10 build failure on Rpi3 Message-ID: <43513842-6FC0-4A89-8F0C-9EB2B328A5ED@yahoo.com> In-Reply-To: <C64D1A3F-A42E-42E3-8491-4DE9F6A96CFB@yahoo.com> References: <6F0CF2F3-A298-4CEA-AA07-B79810F3E8CF@yahoo.com> <20210623222838.GA85566@www.zefox.net> <8E78EE69-44A2-429E-AB65-941537DE25A0@yahoo.com> <20210624043000.GA87740@www.zefox.net> <22B941CA-3AFF-42FD-98D1-D40EC2F6EC43@yahoo.com> <20210624160109.GB87740@www.zefox.net> <3B41633E-AAFC-422A-8D73-3B1B001023F0@yahoo.com> <20210625001651.GA98214@www.zefox.net> <D0845F74-A9A9-4588-910B-B55F9216C9C9@yahoo.com> <5A26965D-2DFD-4A46-A171-A382A61E3CFB@yahoo.com> <20210626035234.GA18893@www.zefox.net> <C64D1A3F-A42E-42E3-8491-4DE9F6A96CFB@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Jun-25, at 22:14, Mark Millard <marklmi at yahoo.com> wrote: > On 2021-Jun-25, at 20:52, bob prohaska <fbsd at www.zefox.net> wrote: >=20 >> If you replicate the problem I'll be very pleased. >> And just slightly relieved. >=20 >=20 > No luck on the 1st try: >=20 > [ 28% 1315/4575] cd /wrkdirs/usr/ports/devel/llvm10/work/.build && = /wrkdirs/usr/ports/devel/llvm10/work/.build/bin/llvm-tblgen = -gen-global-isel -I = /wrkdirs/usr/ports/devel/llvm10/work/llvm-10.0.1.src/ > lib/Target/AArch64 -I = /wrkdirs/usr/ports/devel/llvm10/work/llvm-10.0.1.src/include -I = /wrkdirs/usr/ports/devel/llvm10/work/llvm-10.0.1.src/lib/Target = /wrkdirs/usr/ports/devel/llvm10/work/llvm-10.0.1.s > rc/lib/Target/AArch64/AArch64.td --write-if-changed -o = lib/Target/AArch64/AArch64GenGlobalISel.inc -d = lib/Target/AArch64/AArch64GenGlobalISel.inc.d > . . . > [ 28% 1326/4575] cd /wrkdirs/usr/ports/devel/llvm10/work/.build && = /wrkdirs/usr/ports/devel/llvm10/work/.build/bin/llvm-tblgen = -gen-global-isel -I = /wrkdirs/usr/ports/devel/llvm10/work/llvm-10.0.1.src/lib/Target/AMDGPU = -I /wrkdirs/usr/ports/devel/llvm10/work/llvm-10.0.1.src/include -I = /wrkdirs/usr/ports/devel/llvm10/work/llvm-10.0.1.src/lib/Target = /wrkdirs/usr/ports/devel/llvm10/work/llvm-10.0.1.src/lib/Target/AMDGPU/AMD= GPUGISel.td --write-if-changed -o = lib/Target/AMDGPU/AMDGPUGenGlobalISel.inc -d = lib/Target/AMDGPU/AMDGPUGenGlobalISel.inc.d >=20 > Both finished just fine, indicating that the prior file generations = were > okay. >=20 > I'll put the options to be like you are using and try again. No failure. In a faster context with RAM such that there is no reported use of swap in top, I've tried a host kernel that is non-debug and a host kernel that is debug in combinations with host worlds that are non-debug vs. debug in combination with systems for the jail that are non-debug releng/13 based, non-debug main based, and debug main based. So far none of that has failed. On the RPi4B with total_mem=3D1024 I've only had the non-debug main host kernel and world and a world for jail use that was nondebug. But I've tried with and without junk:true. No failures. For the RPi4B, I've now got a debug host kernel and world and a debug world for jail use. So, by default, junk:true . We will see if it gets a failure or not. It is likely the last of the reproduction attempts based on the information so far. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43513842-6FC0-4A89-8F0C-9EB2B328A5ED>