[218/4552] /usr/bin/c++ -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Ilib/CodeGen/SelectionDAG -I/usr/ports/devel/llvm60/work/llvm-6.0.1.src/lib/CodeGen/SelectionDAG -Iinclude -I/usr/ports/devel/llvm60/work/llvm-6.0.1.src/include -isystem /usr/local/include -O2 -pipe -isystem /usr/local/include -fno-strict-aliasing -isystem /usr/local/include -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -std=c++11 -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -fcolor-diagnostics -ffunction-sections -fdata-sections -O2 -pipe -isystem /usr/local/include -fno-strict-aliasing -isystem /usr/local/include -fno-exceptions -MD -MT lib/CodeGen/SelectionDAG/CMakeFiles/LLVMSelectionDAG.dir/SelectionDAGISel.cpp.o -MF lib/CodeGen/SelectionDAG/CMakeFiles/LLVMSelectionDAG.dir/SelectionDAGISel.cpp.o.d -o lib/CodeGen/SelectionDAG/CMakeFiles/LLVMSelectionDAG.dir/SelectionDAGISel.cpp.o -c /usr/ports/devel/llvm60/work/llvm-6.0.1.src/lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp ninja: build stopped: subcommand failed. ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make[1]: stopped in /usr/ports/devel/llvm60 *** Error code 1 Stop. make: stopped in /usr/ports/devel/llvm60 ===>>> make build failed for devel/llvm60 ===>>> Aborting update # uname -a FreeBSD rp3.local 13.0-CURRENT FreeBSD 13.0-CURRENT r340361 GENERIC arm64 root@rp3:/usr/ports/devel/ninja # pkg info | grep ninja ninja-1.8.2,2 Ninja is a small build system closest in spirit to Make I also have a "portmaster -fR devel/llvm60" tested, without success.
(In reply to Jochen Neumeister from comment #0) Is there any errors above; Sometimes I have seen ninja error and makes one think it is because of 'ninja' but there was an error above
Try building with MAKE_JOBS_UNSAFE=yes as the message say to have a better chance of capturing the actual error. Without that there's nothing I can do (and I don't have hardware to test so even with it my options are limited). You might also check dmesg to see if the process was killed due to lack of memory. The 1GB of ram on a Raspberry Pi 3 is pretty marginal for building LLVM unless you have swap configured.
Closing this due to lack of followup.