Installing the packages required by the Calice Reconstruction software:

The get_soft Script

Contents

• 1 Usage
• 2 Troubleshooting
  • 2.1 Desy Linux
  • 2.2 Red Hat 7.3

1 Usage

The script get_soft.sh can be used to grep all packages which are needed to compile the calice software. The script contains a long list with the needed packages, their location, their versions and check sums (The check sum verification can be disabled by replacing the check sum by - ). The check sum verification is a bit fragile.

The script will create one directory LC (can be changed with the option --prefix [dir_name]. The source packages will be installed in LC/src, the compiled libraries and executables will be installed in LC/lib, LC/extern/lib, LC/autotools/lib, LC/bin, LC/extern/bin, LC/autotools/bin. The directory LC/src/log contains information about the installed or to-be-installed packages. The files with the extension .level give some information about the compilation/installation progress of a package. The file contains a simple number with the meaning:

1. initial status
2. successfully downloaded
3. check sum is calculated and it matches the check sum specified in the get_soft.sh script. A md5 checksum is calculated from the total compound of all files listed in [name]-[version].files:

   checksum=$(cat $(cat [name]-[version].files) | md5sum )
   

4. the package is configured (ready for compilation).
5. the compilation was successful.
6. the package is installed.

2 Troubleshooting

• Running get_soft.sh again: gtk+-2.0 is required. You need at least version 2.2''. But, this version was installed and the compilation of all gtk packages worked fine.
  Solution: After running get_soft.sh, the tool pkg-config is installed. It can be used to get information about the linker and preprocessor flags (including dependencies), which are required for certain package. It gets the necessary information from .pc files which are usually located in the directory pkgconfig in the directories where the libraries are installed. When running get_soft.sh again the newly installed pkgconfig tool is used instead. The new tool will likely have a different default search path. This new search path will most likely not contain the file gtk+-2.0.pc which however is need to identify the installed version of the gtk+-2.0 libraries. The problem is solved by adding the path of the directory which contains gtk+-2.0.pc to the environment variable PKG_CONFIG_PATH. For example:

  PKG_CONFIG_PATH=${PKG_CONFIG_PATH}:/usr/lib/pkg-config
  

  Alternatively the compilation of the GUI code can be omitted by supplying the switch --without-gtkglext.
  The file gtk-2.0.pc is usually located in /usr/lib/pkgconfig. Unfortunately, on DESY Linux 5, the file is not installed by default. However, the get_soft.sh script will install the necessary files in [prefix]/extern/lib/pkgconfig. If the environment variable is set, then /usr/lib/pkgconfig should be appended (separated by a colon), since it is not added by default but may be needed to resolve the dependencies.

2.1 Desy Linux

The configure script of CLHEP identifies the compiler kxx and uses it instead of g++. I suppose that kxx will not produce code which is binary compatible with g++, i.e. it will be difficult to link CLHEP to other C++ libraries. Anyway the compilation fails on DYSS.
Solution: set the environment variable CXX:

CXX=g++ [....]/tools/get_soft.sh --prefix [install path] ... other options ...

Red Hat ships with an ancient GNU C/C++ compiler version (2.96) which may cause some problems. I experienced the following problems:

• During compilation: ``exit(int) not found.''
  Solution: add ``#include <stdlib.h> ``
• During compilation: ``std::atoll not found''. Or something similar.
  Solution: the function ``atoll'' is defined in the C-header file ``stdlib.h''. Add the ``#include <stdlib.h> `` to the complaining source file. You may also have to remove the compiler switch --ansi.
• During linking: ``undefined versioned symbol name __dynamic_cast@@CXXABI_1.2''
  Solution: the libtool which is used to build the shared libraries is probably trying to link against a library which is compiled by a different compiler or compiler version (like for example g++ 3.2). Presumably this problem occurs for packages which use libtool for compiling and linking. A copy of the libtool script should be located in the top level directory of the package. You can try to remove path names from the shell variable (defined in the libtool script): TODO.