rhelmer / emscripten-vagrant

This project will use http://vagrantup.com and http://puppetlabs.com to install a complete https://github.com/kripken/emscripten/ environment in a local http://virtualbox.org/ VM.

---

INSTALL

1. Install the latest Virtualbox from http://www.virtualbox.org/

2. Install vagrant from http://vagrantup.com/

3. build VM and provision with puppet

$ vagrant up

4. Enjoy your Emscripten environment!

Here are some common vagrant operations:

SSH into your VM (emscripten is checked out in ~vagrant/src/emscripten):

$ vagrant ssh

Re-run puppet

$ vagrant provision

Reboot VM and re-run puppet

$ vagrant reload

Destroy VM and rebuild from scratch

$ vagrant destroy

$ vagrant up

emscripten-vagrant's Issues

Included LLVM is dated by a version

Emscripten is using 3.1 now and the included version is 3.0. The bytecode format has changed and so some parts of emscripten are broken. I am downloading what I think is the correct version right now from this page: http://llvm.org/releases/download.html
Should be a easy fix via a change in static assets or url.

VM appears not to run without cpu VT

Hi rhelmer!

I tried running the vm with vagrant and was having problems connecting to the VM. I opened up VagrantFile and uncommented the gui configuration line to boot with a gui. Looks like virtualbox is giving a "VT-x/AMD-V hardware acceleration is not available on your system. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot."

Is the Ubuntu distro 64-bit? Is it possible to use a 32-bit Ubuntu for those with older cpus without VT or does a 64-bit Ubuntu provide any distinct advantage for use with emscripten?

old dependencies

Everything ran cleanly to install. Puppet is amazing.

When i run emcc to check the environment i get an error saying node version too old.

Is this ok to use with emscripten ? Its a very old version of nodejs.

upgrade ubuntu version

Ubuntu version is really old; upgrade it.

node version appears too old (seeing "v0.6.12", expected "v0.8.0")

Puppet fails

Puppet fails:

err: /Stage[main]/Emscripten/Package[python-software-properties]/ensure: change from purged to latest failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install python-software-properties' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
  unattended-upgrades
Suggested packages:
  bsd-mailx
The following NEW packages will be installed:
  python-software-properties unattended-upgrades
0 upgraded, 2 newly installed, 0 to remove and 2 not upgraded.
Need to get 20.4 kB/44.5 kB of archives.
After this operation, 438 kB of additional disk space will be used.
Err http://gb.archive.ubuntu.com/ubuntu/ oneiric-updates/main python-software-properties all 0.81.13.3
  404  Not Found [IP: 91.189.92.200 80]
Err http://security.ubuntu.com/ubuntu/ oneiric-security/main python-software-properties all 0.81.13.3
  404  Not Found [IP: 91.189.92.200 80]
Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/s/software-properties/python-software-properties_0.81.13.3_all.deb  404  Not Found [IP: 91.189.92.200 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
 at /tmp/vagrant-puppet/manifests/emscripten.pp:52

I've fixed it by switching to the us mirrors for packages. I don't know if this is a US thing or a busted mirror upstream or what.

For posterity this is how I switched mirrors:

sudo vim /etc/apt/sources.list

:%s/uk.archive/us.archive/
:wq

Failed to connect to VM!

[default] Waiting for VM to boot. This can take a few minutes.
[default] Failed to connect to VM!
Failed to connect to VM via SSH. Please verify the VM successfully booted
by looking at the VirtualBox GUI.

In the GUI : Changing the VM state from 'RESUMING' to 'RUNNING' It running fine there.

$ /opt/vagrant/bin/vagrant ssh
ssh_exchange_identification: Connection closed by remote host

$ uname -a
generic #65-Ubuntu SMP Tue Jan 24 13:48:14 UTC 2012 i686 GNU/Linux


$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 10.10
Release:    10.10
Codename:   maverick

Could it be due to :

Guest Additions Version: 4.1.8
VirtualBox Version: 4.1.10