Date: Sun, 14 Oct 2018 15:34:32 -0600 From: Cy Schubert <Cy.Schubert@cschubert.com> To: Graham Perrin <grahamperrin@gmail.com>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: RE: Problem compiling rust: observations on swap Message-ID: <20181014213422.3188BC1B@spqr.komquats.com>
next in thread | raw e-mail | index | archive | help
Set TAR in make.conf to gnu tar from ports. Some tarballs will cause bsdtar= to exhaust memory and swap. There was discussion a while ago suggesting th= is is a bug in vmm. --- Sent using a tiny phone keyboard. Apologies for any typos and autocorrect. Also, this old phone only supports top post. Apologies. Cy Schubert <Cy.Schubert@cschubert.com> or <cy@freebsd.org> The need of the many outweighs the greed of the few. --- -----Original Message----- From: Graham Perrin Sent: 14/10/2018 15:19 To: freebsd-current@freebsd.org Subject: Problem compiling rust: observations on swap On 06/10/2018 23:41, Rebecca Cran wrote:=0A= =0A= > On 10/6/18 6:40 AM, Greg V wrote:=0A= >=0A= >> BTW, this error message doesn't say much, but if cargo fails, you=0A= >> might be out of memory.=0A= >=0A= > I was going to suggest being out of memory too. I've seen the rust build= =0A= > cause my system to run out of all 32GB RAM and 2GB swap.=0A= =0A= Yeah, by coincidence I mentioned this yesterday in IRC:=0A= =0A= <https://imgsafe.org/image/1966398b68>=0A= =0A= =E2=80=93 whilst poudriere built both llvm and rust. Around 6 of 8 GB swap = used on a system with 16 GB real memory.=0A= =0A= (I allowed a larger than usual partition for swap when I first installed th= e system.)=0A= _______________________________________________=0A= freebsd-current@freebsd.org mailing list=0A= https://lists.freebsd.org/mailman/listinfo/freebsd-current=0A= To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"= =0A=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181014213422.3188BC1B>