Re: Problem building NetBSD-8 for rpi (evbarm)

[maya%NetBSD.org@localhost]

On Tue, Oct 22, 2019 at 12:32:02AM -0700, pimin inwa wrote:
> Running NetBSD:
> NetBSD toy.wan.vpn 8.99.26 NetBSD 8.99.26 (GEMINI) #0: Sun Nov 25 11:06:09
> PST 2018  root%toy.wan.vpn@localhost:/usr/src/BUILD_OBJ/sys/arch/i386/compile/GEMINI
> i386
> 
> Source is located at /usr/src/rpi/(src|xsrc)
> 
> Respository tag:
> Tnetbsd-8
> 
> Build command:
> 
> (rm -fr ./RPI_OBJ/* ./RPI_TOOL/* & wait & cvs update -Pd & pushd ../xsrc &&
> cvs update -Pd & pushd external && cvs update -Pd & pwd& wait) &&
> ./build.sh -m evbarm -O RPI_OBJ -T RPI_TOOL -V
> TOOLDIR=/usr/src/rpi/RPI_TOOL -V X11SRCDIR=/usr/src/rpi/xsrc -R
> /usr/src/rpi/xreleasedir -o -x -X /usr/src/rpi/xsrc cleandir tools build
> distribution release kernel=GENERIC | tee /tmp/bld.out 2>/tmp/rpi,bld.err
> 
> 
> Where Have I gone wrong?
> 
> 
> #    create  libLLVMMC/ConstantPools.d
> CC=/usr/src/rpi/RPI_TOOL/bin/aarch64--netbsd-clang++
> /usr/src/rpi/RPI_TOOL/bin/nbmkdep -f ConstantPools.d.tmp  --   -std=c++11
>  --sysroot=/usr/src/rpi/src/RPI_OBJ/destdir.evbarm64 -I.
> -I/usr/src/rpi/src/external/bsd/llvm/lib/libLLVMMC/../../dist/clang/include
> -I/usr/src/rpi/src/external/bsd/llvm/lib/libLLVMMC/../../dist/lld/include
> -I/usr/src/rpi/src/external/bsd/llvm/lib/libLLVMMC/../../dist/llvm/include
> -I/usr/src/rpi/src/external/bsd/llvm/lib/libLLVMMC/../../dist/mclinker/include
> -I/usr/src/rpi/src/external/bsd/llvm/lib/libLLVMMC/../../dist/lldb/include
> -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS
> -DCLANG_ENABLE_STATIC_ANALYZER
> -I/usr/src/rpi/src/RPI_OBJ/external/bsd/llvm/include
> -I/usr/src/rpi/src/external/bsd/llvm/lib/libLLVMMC/../../config
> -I/usr/src/rpi/src/external/bsd/llvm/lib/libLLVMMC/../../config
> -I/usr/src/rpi/src/external/bsd/llvm/lib/libLLVMMC/../../config/mclinker
>  /usr/src/rpi/src/external/bsd/llvm/lib/libLLVMMC/../../dist/llvm/lib/MC/ConstantPools.cpp
> &&  mv ConstantPools.d.tmp ConstantPools.d
> *** Error code 1
> 

I suspect if you look at "dmesg", you'll find that a process was killed
due to running out of RAM.