Date: Wed, 16 Mar 2022 19:02:30 -0700 From: Mark Millard <marklmi@yahoo.com> To: simon.wright@gmx.net, freebsd-ports@freebsd.org Subject: Re: aarch64 native context, devel/llvm14 build via poudriere-devel: build fails during "Building package for llvm14-14.0.0.r2" (armv7 too) Message-ID: <BB8BDDA3-BAB8-43CB-81A5-F7B9DEF8CFDC@yahoo.com> In-Reply-To: <EBCFD756-987C-470C-A65D-7F6FEFF1DB14@yahoo.com> References: <EBCFD756-987C-470C-A65D-7F6FEFF1DB14@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Mar-16, at 18:46, Mark Millard <marklmi@yahoo.com> wrote: > From: Simon Wright <simon.wright_at_gmx.net> wrote on > Date: Thu, 17 Mar 2022 08:49:44 +0800 : >=20 >> On 17/03/2022 08:01, Mark Millard wrote: >>=20 >> <snipped> >>=20 >>>=20 >>> The armv7 style build failed with: >>>=20 >>> =3D=3D=3D> Building package for llvm14-14.0.0.r2 >>> pkg-static: Unable to access file = /wrkdirs/usr/ports/devel/llvm14/work/stage/usr/local/llvm14/lib/clang/14.0= .0/include/riscv_vector.h:No such file or directory >>> pkg-static: Unable to access file = /wrkdirs/usr/ports/devel/llvm14/work/stage/usr/local/llvm14/lib/libLLVMVEA= smParser.a:No such file or directory >>> pkg-static: Unable to access file = /wrkdirs/usr/ports/devel/llvm14/work/stage/usr/local/llvm14/lib/libLLVMVEC= odeGen.a:No such file or directory >>> pkg-static: Unable to access file = /wrkdirs/usr/ports/devel/llvm14/work/stage/usr/local/llvm14/lib/libLLVMVED= esc.a:No such file or directory >>> pkg-static: Unable to access file = /wrkdirs/usr/ports/devel/llvm14/work/stage/usr/local/llvm14/lib/libLLVMVED= isassembler.a:No such file or directory >>> pkg-static: Unable to access file = /wrkdirs/usr/ports/devel/llvm14/work/stage/usr/local/llvm14/lib/libLLVMVEI= nfo.a:No such file or directory >>> *** Error code 1 >>>=20 >>=20 >> Mark: >>=20 >> Please forgive me if I'm missing your point but I used to get very >> similar errors at the later stages of the build process for large >> packages and my issue was actually running out of swap space. For >> building rust I had to add a 20GB swap partition then the build would >> (eventually) complete. >=20 > Hello Simon. >=20 >> Are you seeing swap issues during the build? >=20 > Nope. >=20 > [04:29:43] [03] [03:48:58] Finished devel/llvm13 | llvm13-13.0.1: = Success > . . . > [04:42:14] [10] [04:01:29] Finished lang/rust | rust-1.59.0: Success >=20 > 64 GiBytes of RAM, about 246 GiBytes of swap, for 16 Cortex-A72 > cores. >=20 > (Of course, individual armv7 processes are limited to the memory > space they can use, just based on addressing-related considerations. > But the aarch64 failures did not have that kind of limitation.) >=20 > No OOM kill notices. No swap space messages. No memory allocation > failure notices. No console messages at all, other than for my > logging in another time over ssh. >=20 >=20 > I'd selected to not build for riscv (and others), so the = riscv_vector.h > notice is an example of something that pkg should not have been told > to include. >=20 > I'm not sure what the lib/libLLVMVE*.a would be for. But it might be > that the OPTIONS I'm using might mean that pkg should not have been > told to include them, just like for riscv_vector.h . Hmm. Looks like lib/libLLVMVE*.a are for targeting NEC Vector Engines, a type of PCIe accelerator card. My OPTIONS selections excluded tareting such and so pkg should not have been told to include them, just like for riscv_vector.h . =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BB8BDDA3-BAB8-43CB-81A5-F7B9DEF8CFDC>