Rivet Trouble Shooting
If you are having trouble installing or running rivet, some of these tips might help. You might also want to check out the AGILe trouble shooting page. Also check the open tickets to see if your problem is already known.
Running on Mac OS X?
Check MacInstallationIssues
Can't find libCore.so
If you get an error like:
-bash-3.00$ rivetgun rivetgun: error while loading shared libraries: libCore.so: cannot open shared object file: No such file or directory
this probably means you are running a version of rivet built to include the root interface, but you have not got $ROOTSYS/lib in your $LD_LIBRARY_PATH
SELinux security warnings
If you are running a Security Enhanced Linux (SELinux) system, you may get warning messages in the SELinux troubleshooter when trying to run an executable which uses Rivet:
"SELinux is preventing <execname> from loading /usr/local/lib/libRivet.so.1.1.0 which requires text relocation."
This is referring to Rivet's use of binreloc to improve portability when reading the installed reference histogram files. It is not a real security issue. We recommend that you use the chcon command suggested by SELinux's troubleshooter to allow text relocation on libRivet (and libRivetAnalysisStd, as well as any user-written analysis libraries). Rivet should then run as it would on a non-SE Linux system.
Boost errors when compiling code that uses Rivet
There is a problem with Rivet's use of the Boost library - we compile against Boost headers distributed with Rivet, but don't install them. Hence, other tools which want to use Rivet as a library will get "header not found" errors when they try to compile against Rivet, because Rivet's own headers reference the Boost ones.
The long term solution to this problem is likely to be that we will require Boost as a system dependency in future. In the short term, we suggest that you copy the Boost headers from the include/boost directory of the expanded Rivet tarball to a standard include directory on your system, e.g. /usr/local/include/boost. Obviously, this is more of a problem for users without root access, so we will try to find a better solution as soon as possible.
AIDA errors when compiling code that uses Rivet
This is the same issue as above for Boost headers, but for the AIDA interface declarations. The solution is also the same. The next major version of Rivet will no longer use the AIDA interfaces, and so this problem will disappear.
