Re: building LLVM threads gets killed

On 20 Aug 2018, at 16:26, Rodney W. Grimes <freebsd-rwg_at_pdx.rh.CN85.dnsmgr.net> wrote:
> 
>> On 20 Aug 2018, at 05:01, blubee blubeeme <gurenchan_at_gmail.com> wrote:
>>> 
>>> I am running current compiling LLVM60 and when it comes to linking
>>> basically all the processes on my computer gets killed; Chrome, Firefox and
>>> some of the LLVM threads as well
...
> 
>> It is running out of RAM while running multiple parallel link jobs.  If
>> you are building using WITH_DEBUG, turn that off, it consumes large
>> amounts of memory.  If you must have debug info, try adding the
>> following flag to the CMake command line:
>> 
>> -D LLVM_PARALLEL_LINK_JOBS:STRING="1"
>> 
>> That will limit the amount of parallel link jobs to 1, even if you
>> specify -j 8 to gmake or ninja.
>> 
>> Brooks, it would not be a bad idea to always use this CMake flag in the
>> llvm ports. :)
> 
> And this may also fix the issues that all the small
> memory (aka, RPI*) buliders are facing when trying
> to do -j4?

Possibly, as linking is usually the most memory-consuming part of the
build process (and more so, if debugging is enabled).  Are there build
logs available somewhere for those RPI builders?

I have attached a patch for most of the llvm ports, which sets the
LLVM_PARALLEL_LINK_JOBS CMake flag during the configure phase.

-Dimitry