ROOT Version: 6.20.04
Platform: openSUSE 15.1 / x86_64
Compiler: gcc 7.5.0
Dear ROOT Users & Developers,
Further investigation of the issues I reported with regards to building ROOT with R statistics (ROOTR),
see Issues when building ROOT with R statistics (ROOTR)
did show that the steps I took to successfully build against R lead to ROOTR working from the bin directory of the build tree, while installing ROOT to a user-defined prefix and then executing it from the installation directory resulted in ROOTR failing.
This behavior was confirmed by @wile_e_coyote who also pointed out that this finding was caused by the libraries
libRInterface.so libRMVA.so libRtools.so
being broken by (or at least after) installation to a user-defined prefix. Following his approach, I can now confirm that this not only happens on my system for the libraries named above, but it also happens for
All libraries that are broken by installation of ROOT share one common feature: They relate to external packages (R, cfitsio) that I have built and installed (to user-defined prefixes) from source. As these are the only two packages this situation applies to, I cannot tell whether this is a systematic “feature” (bug?) of installing ROOT, but it might hint at an approach for solving this issue.
For the time being, I ended up with a brute-force fix that probably should not be taken: Replacing the named libraries in the installation directory by the ones from the build tree does result in an apparently working installation…
If I had any decent knowledge of CMake and its install procedure, I would try propose a clean fix, but unfortunately I am lacking the necessary knowledge. I would be happy to hear someone is able to come up with a systematic fix.
Thank you as always, and stay safe,