Re: building LLVM threads gets killed

2018-08-22 Thread Dimitry Andric
On 22 Aug 2018, at 04:01, Mark Millard wrote: > > Brooks Davis brooks at freebsd.org wrote on > Tue Aug 21 20:29:45 UTC 2018 : > >> On Mon, Aug 20, 2018 at 07:33:32PM +0200, Dimitry Andric wrote: >>> . . . >>> >>> I have attached a patch for most of the llvm ports, which sets the >>>

Re: building LLVM threads gets killed

2018-08-22 Thread Samy Mahmoudi
> That's exactly why I keep the following in my /boot/loader.rc: I meant "in my /boot/loader.conf"... ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Re: building LLVM threads gets killed

2018-08-21 Thread Mark Millard
Brooks Davis brooks at freebsd.org wrote on Tue Aug 21 20:29:45 UTC 2018 : > On Mon, Aug 20, 2018 at 07:33:32PM +0200, Dimitry Andric wrote: > > . . . > > > > I have attached a patch for most of the llvm ports, which sets the > > LLVM_PARALLEL_LINK_JOBS CMake flag during the configure phase. >

Re: building LLVM threads gets killed

2018-08-21 Thread Samy Mahmoudi
> And probably running ZFS, which ate all your memory and > put you in a memory contrained environment. That's exactly why I keep the following in my /boot/loader.rc: # vfs.zfs.arc_max=1073741824 vfs.zfs.arc_max=2147483648 # vfs.zfs.arc_max=4294967296

Re: building LLVM threads gets killed

2018-08-21 Thread Brooks Davis
On Mon, Aug 20, 2018 at 07:33:32PM +0200, Dimitry Andric wrote: > On 20 Aug 2018, at 16:26, Rodney W. Grimes > wrote: > > > >> 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

Re: building LLVM threads gets killed

2018-08-21 Thread Mark Millard
When I discovered that you were building debug versions of devel/llvm60 that also meant that my Pine64+ 2GB specifics do not make a useful comparison (do not show how small an environment can be for a build). Last I tried such a debug build was on a powerpc64 with 16 MiBytes RAM and it took

Re: building LLVM threads gets killed

2018-08-20 Thread Rodney W. Grimes
> On Mon, Aug 20, 2018 at 11:04 PM Mark Millard wrote: > > > Rodney W. Grimes freebsd-rwg at pdx.rh.CN85.dnsmgr.net wrote on > > Mon Aug 20 14:26:55 UTC 2018 : > > > > > > On 20 Aug 2018, at 05:01, blubee blubeeme > > wrote: > > > > > > > > > > I am running current compiling LLVM60 and when it

Re: building LLVM threads gets killed

2018-08-20 Thread blubee blubeeme
On Mon, Aug 20, 2018 at 11:04 PM Mark Millard wrote: > Rodney W. Grimes freebsd-rwg at pdx.rh.CN85.dnsmgr.net wrote on > Mon Aug 20 14:26:55 UTC 2018 : > > > > On 20 Aug 2018, at 05:01, blubee blubeeme > wrote: > > > > > > > > I am running current compiling LLVM60 and when it comes to linking >

Re: building LLVM threads gets killed

2018-08-20 Thread bob prohaska
On Mon, Aug 20, 2018 at 07:33:32PM +0200, Dimitry Andric wrote: > On 20 Aug 2018, at 16:26, Rodney W. Grimes > wrote: > > > >> 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.

Re: building LLVM threads gets killed

2018-08-20 Thread Dimitry Andric
On 20 Aug 2018, at 16:26, Rodney W. Grimes wrote: > >> 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

Re: building LLVM threads gets killed

2018-08-20 Thread Mark Millard
Rodney W. Grimes freebsd-rwg at pdx.rh.CN85.dnsmgr.net wrote on Mon Aug 20 14:26:55 UTC 2018 : > > 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;

Re: building LLVM threads gets killed

2018-08-20 Thread blubee blubeeme
On Mon, Aug 20, 2018 at 10:26 PM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > 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,

Re: building LLVM threads gets killed

2018-08-20 Thread Rodney W. Grimes
> 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]

Re: building LLVM threads gets killed

2018-08-20 Thread Dimitry Andric
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

Re: building LLVM threads gets killed

2018-08-20 Thread Mark Millard
blubee blubeeme gurenchan at gmail.com wrote on Mon Aug 20 03:02:01 UTC 2018 : > 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 > . . . > last pid: 20965; load

Re: building LLVM threads gets killed

2018-08-20 Thread Mark Millard
[In part a resend from the right Email account. In part adding a note about another Mark Johnston patch for reporting information.] On 2018-Aug-19, at 11:25 PM, Mark Millard wrote: > blubee blubeeme gurenchan at gmail.com wrote on > Mon Aug 20 03:02:01 UTC 2018 : > >> I am running current

building LLVM threads gets killed

2018-08-19 Thread blubee blubeeme
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 I am using ninja which is a little better but gmake or make are a lot worse. uname -a: FreeBSD blubee 12.0-CURRENT