Re: aarch64 native context, devel/llvm14 build via poudriere-devel: build fails during "Building package for llvm14-14.0.0.r2" (armv7 too)

From: Simon Wright <simon.wright_at_gmx.net> wrote on
Date: Thu, 17 Mar 2022 08:49:44 +0800 :

> On 17/03/2022 08:01, Mark Millard wrote:
> 
> <snipped>
> 
> >
> > The armv7 style build failed with:
> >
> > ===>  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/libLLVMVEAsmParser.a:No such file or directory
> > pkg-static: Unable to access file /wrkdirs/usr/ports/devel/llvm14/work/stage/usr/local/llvm14/lib/libLLVMVECodeGen.a:No such file or directory
> > pkg-static: Unable to access file /wrkdirs/usr/ports/devel/llvm14/work/stage/usr/local/llvm14/lib/libLLVMVEDesc.a:No such file or directory
> > pkg-static: Unable to access file /wrkdirs/usr/ports/devel/llvm14/work/stage/usr/local/llvm14/lib/libLLVMVEDisassembler.a:No such file or directory
> > pkg-static: Unable to access file /wrkdirs/usr/ports/devel/llvm14/work/stage/usr/local/llvm14/lib/libLLVMVEInfo.a:No such file or directory
> > *** Error code 1
> >
> 
> Mark:
> 
> 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.

Hello Simon.

> Are you seeing swap issues during the build?

Nope.

[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

64 GiBytes of RAM, about 246 GiBytes of swap, for 16 Cortex-A72
cores.

(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.)

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.


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.

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 .

===
Mark Millard
marklmi at yahoo.com