...
If there is an error running the slic binary using this script, then check your build log (starting at the top) for error messages.
Troubleshooting Common Build Problems
The most common problems are related to configuration of Geant4, because it is a large, complex package. And it has no standard configure script. Make sure that the options generated by SimDist at packages/geant4/env.gmk make sense for your platform. For instance, if you don't have the OpenGL headers and libraries, then all the GL variables should not have a value. A blank variable means that the corresponding option will not be enabled. These variables are basically passed directly to Geant4's build system. Refer to the Geant4 documentation of these settings for more details.
Commands to the slic package only can be used to debug problems that occur with other dependencies. For instance, if the slic build complains about missing LCIO headers, then the LCIO library build probably failed. Or if there are a bunch of error messages about linking against Geant4, then part of Geant4 likely did not compile correctly.
If all of the above fails to get a working SimDist, then send email to jeremym AT slac DOT stanford DOT EDU with the following.
- OS variety and kernel version e.g. for Linux
No Format cat /etc/redhat-release; uname -a - gcc version
No Format gcc -v - 32 or 64 bit
No Format uname -m - log of global configure command
No Format cd SimDist; ./configure &> myconfig.log
Please attach or inline the snippets containing build errors from your logs. I don't want full log files, if possible. Usually, the first error in the log is the most relevant.
Advanced Instructions
The SimDist build system is based on GNU Autoconf and Make. Individual packages can be manipulated using make commands from their appropriate package directories.
...