Re: Problem compiling rust: observations on swap: GNU tar

2018-10-15 Thread Cy Schubert 
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 bug in vmm.
>
> Thanks!
>
> My make.conf for poudriere:
>
> root@momh167-gjp4-hpelitebook8570p-freebsd:~ # cat /usr/local/etc/poudriere.d
> /make.conf
> ICA_CERTS=/usr/ports/distfiles/QuoVadisRootCA2.crt
> DEFAULT_VERSIONS+= samba=4.8
> GNUTAR=on
> root@momh167-gjp4-hpelitebook8570p-freebsd:~ #
>
> – like so (the third line of the file), yes?

No, like this.

TAR=/usr/local/bin/gtar


-- 
Cheers,
Cy Schubert 
FreeBSD UNIX: Web:  http://www.FreeBSD.org

The need of the many outweighs the greed of the few.


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Problem compiling rust: observations on swap: GNU tar

2018-10-15 Thread Graham Perrin 
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 bug in vmm.

Thanks!

My make.conf for poudriere:

root@momh167-gjp4-hpelitebook8570p-freebsd:~ # cat 
/usr/local/etc/poudriere.d/make.conf
ICA_CERTS=/usr/ports/distfiles/QuoVadisRootCA2.crt
DEFAULT_VERSIONS+= samba=4.8
GNUTAR=on
root@momh167-gjp4-hpelitebook8570p-freebsd:~ #

– like so (the third line of the file), yes?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

RE: Problem compiling rust: observations on swap

2018-10-14 Thread Cy Schubert 
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. Apologies.

Cy Schubert
 or 
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:

> 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.

Yeah, by coincidence I mentioned this yesterday in IRC:

<https://imgsafe.org/image/1966398b68>

– whilst poudriere built both llvm and rust. Around 6 of 8 GB swap used on a 
system with 16 GB real memory.

(I allowed a larger than usual partition for swap when I first installed the 
system.)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Problem compiling rust: observations on swap

2018-10-14 Thread Graham Perrin 
On 06/10/2018 23:41, Rebecca Cran wrote:

> 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.

Yeah, by coincidence I mentioned this yesterday in IRC:



– whilst poudriere built both llvm and rust. Around 6 of 8 GB swap used on a 
system with 16 GB real memory.

(I allowed a larger than usual partition for swap when I first installed the 
system.)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Problem compiling rust

2018-10-06 Thread Rebecca Cran 
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

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Problem compiling rust

2018-10-06 Thread Greg V 




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 
 extracting cargo-0.29.0-x86_64-unknown-freebsd/cargo/bin/cargo  
extracting 
cargo-0.29.0-x86_64-unknown-freebsd/cargo/share/zsh/site-functions/_cargorunning: 
/usr/ports/lang/rust/work/rustc-1.29.1-src/build/x86_64-unknown-freebsd/stage0/bin/cargo 
build --manifest-path 
/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/Cargo.toml 
--frozenTraceback (most recent call last):  File 
"/usr/ports/lang/rust/work/rustc-1.29.1-src/x.py", line 20, in 
bootstrap.main()  File 
"/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/bootstrap.py", 
line 843, in mainbootstrap(help_triggered)  File 
"/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/bootstrap.py", 
line 819, in bootstrapbuild.build_bootstrap()  File 
"/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/bootstrap.py", 
line 646, in build_bootstraprun(args, env=env, 
verbose=self.verbose)  File 
"/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/bootstrap.py", 
line 148, in runraise RuntimeError(err)RuntimeError: failed to 
run: 
/usr/ports/lang/rust/work/rustc-1.29.1-src/build/x86_64-unknown-freebsd/stage0/bin/cargo 
build --manifest-path 
/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/Cargo.toml 
--frozen*** Error code 1

Stop.make[1]: stopped in /usr/ports/lang/rust*** Error code 1
Stop.make: stopped in /usr/ports/lang/rust[root@sting 
/usr/ports/lang/rust]# I always had this problem trying to compiling 
rust (amd64 alpha3),as I only need it to compile firefox I wonder if 
it is possible to disable its building.Thanks Filippo


You don't need to compile Rust from source to compile Firefox.
You can just 'pkg install rust' to get Rust from a binary package.

BTW, this error message doesn't say much, but if cargo fails, you might 
be out of memory.


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Problem compiling rust

2018-10-06 Thread Filippo Moretti 
  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  
extracting cargo-0.29.0-x86_64-unknown-freebsd/cargo/bin/cargo  extracting 
cargo-0.29.0-x86_64-unknown-freebsd/cargo/share/zsh/site-functions/_cargorunning:
 
/usr/ports/lang/rust/work/rustc-1.29.1-src/build/x86_64-unknown-freebsd/stage0/bin/cargo
 build --manifest-path 
/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/Cargo.toml 
--frozenTraceback (most recent call last):  File 
"/usr/ports/lang/rust/work/rustc-1.29.1-src/x.py", line 20, in     
bootstrap.main()  File 
"/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/bootstrap.py", line 
843, in main    bootstrap(help_triggered)  File 
"/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/bootstrap.py", line 
819, in bootstrap    build.build_bootstrap()  File 
"/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/bootstrap.py", line 
646, in build_bootstrap    run(args, env=env, verbose=self.verbose)  File 
"/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/bootstrap.py", line 
148, in run    raise RuntimeError(err)RuntimeError: failed to run: 
/usr/ports/lang/rust/work/rustc-1.29.1-src/build/x86_64-unknown-freebsd/stage0/bin/cargo
 build --manifest-path 
/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/Cargo.toml --frozen*** 
Error code 1
Stop.make[1]: stopped in /usr/ports/lang/rust*** Error code 1
Stop.make: stopped in /usr/ports/lang/rust[root@sting /usr/ports/lang/rust]# I 
always had this problem trying to compiling rust (amd64 alpha3),as I only need 
it to compile firefox I wonder if it is possible to disable its building.Thanks 
Filippo
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Problem compiling rust

2018-04-19 Thread Bryan Drewery 
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/rust-nightly?


-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

Problem compiling rust

2018-04-17 Thread Filippo Moretti 
I have the folloing error while compiling rust on i386 current of April the 9th


rust_error
Description: Binary data
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"