Showing posts with label ecce 6.4. Show all posts
Showing posts with label ecce 6.4. Show all posts

30 May 2013

434. ECCE 6.4 in a 32 bit Debian 7 Virtual Machine by compiling, or in a 64 bit Debian 7 Virtual Machine by using pre-built binaries

ECCE is only available prebuilt for 64 bit OS. You will NOT be able to install the binaries from EMSL on a 32 bit OS in your virtual machine.

!NOTE2! I use localhost in the set-up below. Be aware that this will block outside access:

This post shows how to
1. compile ECCE for a 32 bit system
2. install the pre-built EMSL 64 bit binaries for a 64 bit system.

The reason why I show both is that if you are running a 32 bit host system you might not be able to run a 64 bit client OS.


This is essentially an update of an older post ( which describes how to install ECCE 6.3 on Debian 6.

Part of the reason for updating is this comment:

If you are running a debian or redhat based linux distribution you should be able to install ecce natively without issue (e.g.

However, if you are using Windows or OS X you will probably want to install ecce inside a virtual machine, hence this post:

0. Install virtualbox
How you install virtualbox depends on your host system. I'm running debian wheezy AMD 64, so I did
cd ~/Downloads
sudo dpkg -i virtualbox-4.2_4.2.12-84980~Debian~wheezy_amd64.deb

Note that you are in no way obliged to download the Oracle packaged version of virtualbox. I'm using it because I've had issues with the debian packages in the past when using kernels that are very new (and that I've compiled myself). See e.g.

See here for other versions of virtualbox:

1. Download the Debian 7 installation CD
If you are on a unix-like system you should be able to do something along the lines of
mkdir ~/tmp
cd ~/tmp
to download the 32 bit iso and

to download the 64 bit version. Please read the introduction to this post to learn about the consequences of installing a 32 bit system.

2.Set up the virtual machine
(in this example I'm using the i386 version of debian, but the steps are identical for the amd64 version)

Start virtualbox and click on New:

Mount the CD

3. Install Debian 7 on the virtual machine
Click Start and the installation should start. (the steps are the same for the i386 and the amd64 versions)

Debian 7 (wheezy) is now installed. Log in.

At this point you can install whatever you want. I suggest installing the

  • LXDE desktop environment (I know that it's a tautology). 
  • openjdk-7-jdk (you might be able to get away with -jre)


4a. 32 bit Virtual machine: Compile ECCE v 6.4
Note: you might have to go to and download the source in a browser if wget doesn't work.

mkdir ~/tmp
cd ~/tmp
tar xvf ecce-v6.4-src.tar.bz2
sudo apt-get install bzip2 build-essential autoconf libtool ant pkg-config gtk+-2.0-dev libxt-dev csh gfortran openjdk-6-jdk python-dev libjpeg-dev imagemagick xterm
cd ecce-v6.4/
export ECCE_HOME=`pwd`
cd build/

At this point you'll be going through the same steps as shown in this post: (yesterday's testing is today's stable)
Checking prerequisites for building ECCE... If any of the following tools aren't found or aren't the right version, hit -c at the prompt and either find or install the tool before re-running this script. The whereis command is useful for finding tools not in your path. Found gcc in: /usr/bin/gcc ECCE requires gcc 3.2.x or 4.x.x This version: gcc (Debian 4.7.2-5) 4.7.2 Hit return if this gcc is OK... [..] This works fine unless your site needs support for multiple platforms. Finished checking prerequisites for building ECCE. Do you want to skip these checks for future build_ecce invocations (y/n)? y
Xerxes built
Mesa OpenGL built
wxWidgets built
wxPython built
Apache HTTP server built
ECCE built and distribution created in /home/verahill/tmp/ecce-v6.4
cd ../ ./install_ecce.v6.4.csh

and continue to section 5.

4b. 64 bit Virtual machine: Download ECCE v 6.4

mkdir ~/tmp
cd ~/tmp
sudo apt-get install csh
csh install_ecce.v6.4.rhel5-gcc4.1.2-m64.csh

and continue to section 5.

5. Install ECCE
Main ECCE installation menu =========================== 1) Help on main menu options 2) Prerequisite software check 3) Full install 4) Full upgrade 5) Application software install 6) Application software upgrade 7) Server install 8) Server upgrade IMPORTANT: If you are uncertain about any aspect of installing or running ECCE at your site, please refer to the detailed ECCE Installation and Administration Guide at Hit at prompts to accept the default value in brackets. Selection: [1] 3 Host name: [eccehost] localhost Application installation directory: [/home/verahill/tmp/ecce-v6.4/ecce-v6.4/apps] /home/verahill/.ecce/apps Server installation directory: [/home/verahill/.ecce/server] ECCE v6.4 will be installed using the settings: Installation type: [full install] Host name: [localhost] Application installation directory: [/home/verahill/.ecce/apps] Server installation directory: [/home/verahill/.ecce/server] Are these choices correct (yes/no/quit)? [yes] Installing ECCE application software in /home/verahill/.ecce/apps... Extracting application distribution... Extracting NWChem binary distribution... Extracting NWChem common distribution... Extracting client WebHelp distribution... Configuring application software... Configuring NWChem... Installing ECCE server in /home/verahill/.ecce/server... Extracting data server in /home/verahill/.ecce/server/httpd... Extracting data libraries in /home/verahill/.ecce/server/data... Extracting Java Messaging Server in /home/verahill/.ecce/server/activemq... Configuring ECCE server... ECCE installation succeeded. *************************************************************** !! You MUST perform the following steps in order to use ECCE !! -- Unless only the user 'verahill' will be running ECCE, start the ECCE server as 'verahill' with: /home/verahill/.ecce/server/ecce-admin/start_ecce_server -- To register machines to run computational codes, please see the installation and compute resource registration manuals at -- Before running ECCE each user must source an environment setup script. For csh/tcsh users add this to ~/.cshrc: if ( -e /home/verahill/.ecce/apps/scripts/runtime_setup ) then source /home/verahill/.ecce/apps/scripts/runtime_setup endif For sh/bash users, add this to ~/.profile or ~/.bashrc: if [ -e /home/verahill/.ecce/apps/scripts/ ]; then . /home/verahill/.ecce/apps/scripts/ fi ***************************************************************
echo 'export ECCE_HOME=/home/verahill/.ecce/apps' >> ~/.bashrc
echo 'PATH=$PATH:/home/verahill/.ecce/server/ecce-admin/:/home/verahill/.ecce/apps/scripts/' >> ~/.bashrc
source ~/.bashrc
/home/verahill/.ecce/server/httpd/bin/apachectl start: httpd started [1] 4137 INFO BrokerService - ActiveMQ 5.1.0 JMS Message Broker (localhost) is starting INFO BrokerService - ActiveMQ JMS Message Broker (localhost, ID:ecce64bit-35450-1369895708602-0:0) started

Note that this is just the beginning. You should now compile nwchem and set up ecce to work with nwchem either locally or remotely.

This post shows one type of configuration:

But read the documentation and search this site and you'll find more examples.