Skip to content

Latest commit

 

History

History
88 lines (62 loc) · 3.42 KB

README.md

File metadata and controls

88 lines (62 loc) · 3.42 KB
Raw

This is a collection of Vagrantfiles for testing GENIE builds on various OS's.

READ ME FIRST!

This version of Wayfarer is meant to work with GENIE R-2_10_2 and later. If you would like to use an older version of GENIE, you will need to edit the provision.sh scripts found in each package.

Also, users should be aware that there are some issues using ROOT5 with very new versions of the GCC compiler. The versions used here have been found to work, but if you would like to use a different version of ROOT5 than the ones specified, be aware you may need to add scripting to update ROOT's configuration scripts and/or install a different version of the C compiler and use it throughout the build.

Tags and versioning

Versions of Wayfarer are specified by git tags (as opposed to branches). When first checking out this package, you will have the HEAD version of the master branch. You can get a specifc tagged release by checking out the tag into a branch like so

git checkout -b R-2_10_4.0-br R-2_10_4.0

This will checkout tag R-2_10_4.0 into branch R-2_10_4.0-br. You want to checkout into a branch to avoid being in a "detached HEAD" state (although depending on your needs, this is not actually a major problem).

Check the releases page for information about the available tagged versions.

Basic usage

Wayfarer relies on Vagrant being installed. Additionally, it assumes VirtualBox, but other virtualization engines may be used (the example commands below would need to be updated).

To use, e.g., for Ubuntu 15.10 (and assuming you are using VirtualBox):

cd Ubuntu/u15_10
vagrant up --provider virtualbox

Currently supported:

  • Ubuntu/u14_04 ("trusty64")
  • Ubuntu/u15_10 ("wiley64")
  • Centos/Centos7 ("bento/centos-7.1")

Note that what is actually supported is trusty64 and wiley64, and the specific numeric tags of Ubuntu that corresponds to that specification, etc.

Some useful commands:

  • vagrant reload: reload the VM with changes to the Vagrantfile
  • vagrant destroy: clear out the VM

Much more is available on the Vagrant webpage and in other various tutorials available online.

Troubleshooting

The original Pythia storage addresses at CERN changed and some of the various installation scripts used by GENIE have appropriately reacted, but older, tagged versions are likely pointing to the wrong place (older than Spring 2016). If you are having installation troubles, be sure to check the location of the Pythia6 tar balls is correct in the scripts you are using.

Vagrant Errors

  • You may get the error message: "Failed to mount folders in Linux guest. This is usually beacuse the 'vboxsf' file system is not available. Please verify that the guest additions are properly installed in the guest and can work properly." In this case, we need to be sure guest additions are installed. For virtual box:

    $ vagrant plugin install vagrant-vbguest

After this, if still having trouble, you may need

$ vagrant vbguest
$ vagrant reload default

If still having trouble (possible), then you may need to log into the newly created guest and hack away. It isn't clear to me how to fix these problems with VirtualBox Guest Additions from inside the Vagrantfile - you have to stop halfway fix these things inside the host before proceeding with the installation.