From owner-freebsd-current@freebsd.org Mon Aug 20 14:26:55 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 96EE6106F95E for ; Mon, 20 Aug 2018 14:26:55 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 03E588F62D; Mon, 20 Aug 2018 14:26:54 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w7KEQoGV074810; Mon, 20 Aug 2018 07:26:50 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w7KEQo9j074809; Mon, 20 Aug 2018 07:26:50 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201808201426.w7KEQo9j074809@pdx.rh.CN85.dnsmgr.net> Subject: Re: building LLVM threads gets killed In-Reply-To: To: Dimitry Andric Date: Mon, 20 Aug 2018 07:26:50 -0700 (PDT) CC: blubee blubeeme , FreeBSD Current , Brooks Davis X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2018 14:26:55 -0000 > On 20 Aug 2018, at 05:01, blubee blubeeme 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 > ... > > llvm/build % ninja -j8 > > [2408/2473] Building CXX object > > lib/Passes/CMakeFiles/LLVMPasses.dir/PassBuilder.cpp.o > > FAILED: lib/Passes/CMakeFiles/LLVMPasses.dir/PassBuilder.cpp.o > > /usr/bin/c++ -DGTEST_HAS_RTTI=0 -D_DEBUG -D__STDC_CONSTANT_MACROS > > -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Ilib/Passes -I../lib/Passes > > -Iinclude -I../include -isystem /usr/local/include -fPIC > > -fvisibility-inlines-hidden -Werror=date-time > > -Werror=unguarded-availability-new -std=c++11 -Wall -Wextra > > -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 -fdiagnostics-color -g -fno-exceptions -fno-rtti -MD > > -MT lib/Passes/CMakeFiles/LLVMPasses.dir/PassBuilder.cpp.o -MF > > lib/Passes/CMakeFiles/LLVMPasses.dir/PassBuilder.cpp.o.d -o > > lib/Passes/CMakeFiles/LLVMPasses.dir/PassBuilder.cpp.o -c > > ../lib/Passes/PassBuilder.cpp > > c++: error: unable to execute command: Killed > > 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? -- Rod Grimes rgrimes@freebsd.org