Unable to compile rustc on ubuntu 12.04 vm (osx host machine)

[brycefisher]

Apologies if this is the wrong repo to file an issue on! Is it possible to compile rustc on a virtual machine? Here's what happened when I tried:

My host machine:

• Mac Book Pro, OSX 10.8
• 8 GB ram
• 64bit architecture.

Virtual Machine:

• Running on VirtualBox 4.3.8
• 64bit Ubuntu 12.04
• 2 GB Ram
• 20 GB harddrive (VDI with fixed storage allocation)
• Additional Details:
  

Steps to Reproduce:

1. Boot up the new instance and select "Try Ubuntu" (same problem exists when installing as well)
2. Open terminal and sudo apt-get install g++ clang curl and git
3. curl -O http://static.rust-lang.org/dist/rust-0.9.tar.gz
4. tar -xzf rust-0.9.tar.gz
5. cd rust-0.9
6. ./configure
7. make && sudo make install

Expected outcome

rustc and rustdoc should compile and install after about 20 minutes.

Actual Outcome

The virtual harddrive is completely filled up. The complete error message I received was:

> error: ar rS x86_64-unknown-linux-gnu/stage0/lib/rustlib/x86_64-unknown-linux-gnu/lib/libsyntax-9be99726-0.9.rlib x86_64-unknown-linux-gnu/stage0/lib/rustlib/x86_64-unknown-linux-gnu/lib/syntax.bc failed with: exit code: 1
> note: stdout ---
>
> note: stderr ---
> ar:x86_64-unknown-linux-gnu/stage0/lib/rustlib/x86_64-unknown-linux-gnu/lib/libsyntax-9be99726-0.9.rlib: No space left on device
>
> error: aborting due to previous error
> task 'rustc' failed at 'explicit failure', /home/rustbuild/src/rust-buildbot/slave/snap3-linux/build/src/libsyntax/diagnostic.rs:75
> task '<main>' failed at 'explicit failure', /home/rustbuild/src/rust-buildbot/slace/snap3-linux/build/src/librustc/lib.rs:440
> make: *** [x86_64-unknown-linux-gnu/stage0/lib/rustlib/x86_64-unknown-linux-gnu/lib/libstanx.so] Error 101

[alexcrichton]

That error, plus the output of df (as you have noticed) means that your hardrive is full.

A rust build directory should be on the order of ~2.4 GB (that's what mine is right now), so you may want to explore where the extra space is going in the rest of the system.

[brycefisher]

The space is empty when I started the process. I newly provisioned the whole harddrive. I had the same outcome with a newly created VM on 8 GB virtual hardrive, so I ramped it up to 20 GB. I'm inclined to think that there's an issue with the build process on the VM, or there's an issue with VirtualBox.

[alexcrichton]

Can you investigate to see where all the space is going? "the build directory is > 20GB" is tough to debug when we can't reproduce it.

[brycefisher]

Arg! Sorry, my bad. When running Ubuntu in "Try" mode, I only had access to the available RAM. Ubuntu wasn't accessing my virtual harddrive at all (which I didn't realize at first). Installing Ubuntu and restarting the VM resolved this issue. Thanks for the speedy support!!