Details
-
Bug
-
Status: Open (View Workflow)
-
Medium
-
Resolution: Unresolved
-
6.20/04
-
None
-
None
-
Linux (at least)
Description
It seems that "make install" creates misbehaving ROOT installations when some linked shared libraries come from non-trivial directories.
This has been shown for the ROOTR (ROOT R interface) where three ROOT shared libraries are broken ("libRInterface.so", "libRMVA.so", "libRtools.so"), even though the missing "/usr/lib/R/site-library/RInside/lib/libRInside.so" library comes from the default system package:
https://root-forum.cern.ch/t/issues-when-building-root-with-r-statistics-rootr/39267/9
Another report shows the same erratic behaviour for the "fitsio" feature ("libFITSIO.so"), where the missing "/usr/local/cfitsio-3.47/lib64/libcfitsio.so.8" was built and installed by the user:
Yet another report for the "libGLEW" built by ROOT. However, this problem may be different from the above ones. It is possible that the "libGLEW" is simply copied into improper place ("/opt/root/lib/" instead of "/opt/root/lib/root/"), which may also depend if "-Dgnuinstall=ON" was used or not:
https://root-forum.cern.ch/t/python3-and-root-6-23-01/39877/8
Attachments
Issue Links
- relates to
-
ROOT-9758 Installed ROOT cannot find its libraries
-
- Reopened
-