GlastRelease User Guide:  Installing GlastRelease

Public Installations

UW Windows Server

The University of Washington Windows Server is provided for GLAST collaborators.  The terminal server provides shared access to GLAST software.  For information concerning the UW Windows Server, see:  http://glast.phys.washington.edu/

To use the installed version of GlastRelease, start up VCMT and set your CMTPATH to:
    d:\ground\GlastRelease_release
where release is the currently release version. 

If you want to make modifications, you should check out individual packages in your own area, and prepend that path to your CMTPATH.

SLAC Linux

GLAST software is available via the SLAC central linux system.  With a SLAC linux account, you can access the shared software.  For more information, please see the GLAST SLAC Linux home page:  http://www-glast.slac.stanford.edu/software/GLASTatSLAC/public_linux_at_slac.htm

You can set your CMTPATH to point to the release of your choice from

/nfs/farm/g/glast/u05/builds

Binary Distribution 

Coming Soon..

Full Installation on Local Machine from Source

Installing GlastRelease using the source code, requires three steps:  Check your version of CMT, install the latest external libraries, and install GlastRelease.

Install CMT:

Check to see that you have CMT v1r12p20021129 installed on your machine.
If not, please see the CodeHowTo pages for directions concerning CMT installation.

On Windows:  Check that you have VCMT v15 or later installed. It can be used to update CMT.

Install the External Libraries:

The following is the list of external libraries required to use GlastRelease, this applies to both Windows and Linux systems:
[Note: it is now out of date: we have added and changed a few things.

Interface Package, in IExternal native
 version		 Path to libs/includes
Name Version Windows Linux
AIDA v3r221p0 2.2.1 AIDA/2.2.1 AIDA/2.2.1
CLHEP v2r1800p1 1.8.0.0 CLHEP/1.8.0.0 CLHEP/1.8.0.0
HTL v2r1311p1 1.3.1.1 HTL/1.3.1.1 HTL/1.3.2.1
ROOT v2r30402p0 v3.04.02 ROOT/v3.04.02 ROOT/v3.04.02
Geant4Runtime v2r50p0 5.0 geant4/5.0 geant4/5.0
XMLEXT v3r152p2 c1_5_2 xerces-c1_5_2-win32 xerces/1.5.2
cfitsio v1r2410p0 v2410 cfitsio_v2410 cfitsio/v2410
GaudiInterface v0r114p0 v11r4 gaudi/v11r4p0 gaudi/v11r4p0
MYSQLEXT v0r32349p0 3.23.49 mysql/3.23.49 mysql/3.23.49

Windows:

  1. Retrieve the actual external libraries from SLAC FTP by doing either
    1. ftp ftp-glast.slac.stanford.edu
      login as anonymous
      cd glast.u05/extlib/full_dist
      bin
      get full_dist_GlastRelease_vi_win.tar
      quit
      OR, if you would rather just click a few times:
    2. Visit the site  ftp://ftp-glast.slac.stanford.edu/glast.u05/extlib/full_dist
      and download the appropriate file to your machine
  2. Unzip the tar file into your GLAST_EXT directory
  3. You now have a series of zip files, one for each external library - you may unpack each one into your GLAST_EXT, noting that you may already have some of these external libraries already installed.  If your extraction program prompts you about over-writing an existing file, check to see if you already have a particular external library installed.

Linux:

  1. Using either ftp or Netscape, download  the external libraries from.
    ftp://ftp-glast.slac.stanford.edu/glast.u05/extlib/full_dist/full_dist_GlastRelease_v0_linux.tar.gz
  2. Extract the tar files into your local GLAST_EXT directory

Install IExternal package

One checks out the lot with the cmt command,
     

cmt co -R IExternal 

Alternatively you can use vcmt, and recursively checkout IExternal. See the method below for GlastRelease itself.

Install GlastRelease:

Windows:

  1. Obtain the GlastRelease code:

    With vcmt v15:

    1. Create a new directory to contain the GlastRelease and all of its associated packages,
    2. Using the Windows command line, enter the new directory (for example) GlastRelease_v1r0 and do the following:
      cmt co -R -r v1r0 GlastRelease
    3. Start up VCMT and update the CMTPATH to point to GlastRelease directory

    Or, if you get vcmt v16 or greater:

    1. Click on the checkout button
    2. In the dialog box, enter name=GlastRelease, cvs revision=v1r0, cmt version blank
    3. Select the entry in the Directory listbox that you want all the packages to be checked out to
    4. Click  the Recursive check box
  2. Highlight Gleam in the vcmt package list.
  3. Under the Project drop-down list, check the configuration you want to use for the build:
        vsnet Debug or Release, to use Visual Studio .Net with the vc7 compiler; (if it is installed) or
        msdev Debug or Release to use Visual Studio 6 with the vc6 compiler
     
  4. Click the broadcast local checkbox and click the setup button
  5. Click the make button (you don't need to broadcast it).
  6. When the build finishes, click run to run the gui program, or select the test_Gleam project to run the batch test program. [Note: this does not build packages, such as ntupleWriterSvc, that Gleam does not need. They must be built separately.]


Linux: 

The instructions vary depending upon whether or not you are installing on a local SLAC machine or on a machine at another institution.

At SLAC

Using glastpack.pl

    These instructions are reflected in Alex's message to the core list:. If you wish to use the central installations of GlastRelease, you can find them at /nfs/farm/g/glast/u05/builds/.

Using standard CMT commands (using a csh-style shell) path path and v1r0 should reflect your choice of path and version

$ mkdir path/GlastRelease; cd path/GlastRelease
$ setenv CMTPATH $PWD
$ setenv CMTCONFIG rh72_gcc2953
$ setenv GLAST_EXT $GLASTROOT/ground/externalPackages/rh72_gcc2953
$ cmt co -R -r v1r0 GlastRelease 
$ cd Gleam/*/cmt
$ cmt broadcast gmake
$ source setup.csh
$ ../rh72_gcc2953/test_Gleam.exe

 

On Other Non-SLAC Machines:
This recipe was tested for:

a) RH72 kernel-2.4.9-13.i686 glibc-2.2.4-19.3 compat-glibc-6.2-2.1.3.2
b) RH80 kernel-2.4.18-14 glibc-2.2.93-5 no compat-glibc

Recipe:

Preliminary setup - first note whether or not you have ROOT privileges on your machine.

For non-root users:

  1. Follow the directions in the CodeHowTo to be sure your system is setup:
    http://www-glast.slac.stanford.edu/software/CodeHowTo/default.htm
  2. Locate gcc 2.95.3 on your system, if it is not available, things will be much more difficult.  
    If it is available, create the links to gcc295 and g++295 in $HOME/bin, and make sure it's in your PATH.
    If gcc 2.95.3 is not available - ask your sysadmin to install the gcc 2.95.3 rpms (see step 2 for root Linux users)
  3. Once you have gcc 2.95.3 available, proceed to step 3 for root users.

If you have ROOT privileges:

  1. Follow the direction in the CodeHowTo 
    http://www-glast.slac.stanford.edu/software/CodeHowTo/default.htm
  2. Install the gcc295-2.95.3 and gcc295-c++-2.95.3 rpms from the redhat contribs.  You can find them, e.g., at
    /afs/cern.ch/project/linux/redhat/mirror/contrib/libc6/i386 
    (or search for them at http://www.redhat.com).  In order to not enforce an edit of the GaudiPolicy requirements file, you should also create sym links to the "proper" executable name.
    as root:
    cd /afs/cern.ch/project/linux/redhat/mirror/contrib/libc6/i386
    rpm -Uvh gcc295-2.95.3-0.i386.rpm gcc295-c++-2.95.3-0.i386.rpm
    cd /usr/bin
    ln -s g++295 g++-2.95.3
    ln -s gcc295 gcc-2.95.3

    Comment: there should be no conflicts, as none of these files exist on any standard installation.
  3. The libGaudiKernel.so in the extlib tarball depends on libstdc++-libc6.1-2.so.3 .  The safest way is to copy it from SLAC, and to put it into a directory which is in your (system default) ld library path.

    as root:
    cd /usr/lib
    scp -p user@noric.slac.stanford.edu:/usr/local/lib/libstdc++-3-libc6.1-2-2.10.0.so .
    ln -s libstdc++-3-libc6.1-2-2.10.0.so libstdc++-libc6.1-2.so.3

    Comment: You should check first to see if you have these libs installed (locate <filename>), but it would be surprising.  At http://rpmfind.net, you can find libstdc++-2.95.1_2.10.0-3.i386.rpm, which contains these libc6.1-2 versions.  But a few files in the rpm conflict with files from compat-libstdc++.  On RH80, it his highly recommended not to install this package, as many applications depend on compat-libstdc++.  On RH7x, you may check.  For the tested RH72 system, there is Netscape (obsolete, there is mozilla), compat-egcs (very obsolete), and some qt packages.  You can try yourself with rpm -e --test compat-libstdc++, and may decide to remove all the conflicting packages and install the above mentioned rpm.
  4. Now proceed to the directions for Compilation and Running GlastRelease.

Compilation and Running GlastRelease

Using glastpack.pl

 

H. Kelly Last Modified:  2003-03-24 17:36:21 -0800