In message <97680f3e-fb00-abc7-81d5-c61c9cae7...@gmail.com>, Graham
Perrin writ
es:
> On 14/10/2018 22:34, Cy Schubert wrote:
>
> > 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 this
> is a bu
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 this 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. Ap
On 10/6/18 6:40 AM, Greg V wrote:
>
> BTW, this error message doesn't say much, but if cargo fails, you
> might be out of memory.
I was going to suggest being out of memory too. I've seen the rust build
cause my system to run out of all 32GB RAM and 2GB swap.
--
Rebecca Cran
_
On Sat, Oct 6, 2018 at 3:26 PM, Filippo Moretti
wrote:
extracting
cargo-0.29.0-x86_64-unknown-freebsd/cargo/share/doc/cargo/README.md
extracting cargo-0.29.0-x86_64-unknown-freebsd/cargo/manifest.in
extracting
cargo-0.29.0-x86_64-unknown-freebsd/cargo/etc/bash_completion.d/cargo
ext
On 4/17/18 10:25 AM, Filippo Moretti wrote:
> I have the folloing error while compiling rust on i386 current of April the
> 9th
It looks like the normal bootstrap bug with the ino64 changes but is
fine on my amd64 system. Perhaps I missed something for i386 support.
Are you able to build lang/rus
