I’m trying to understand what is going on with the following: we have a simulation code that uses specially-built paraview libraries for in-situ processing. The executable finds its libraries using
On the same machine, there is also ParaView installed (same version, 5.8, installed as pre-built binaries), that has built-in RPATH definition for finding its libraries:
The problem we’re facing is that when paraview executable is started, while the in-situ libraries are on the LD_LIBRARY_PATH, paraview crashes.
From my limited understanding of RPATH, I thought that RPATH takes precedence over LD_LIBRARY_PATH, but that does not seem to be happening here.
Do you have any advice on how to resolve this? One thing we could do, I suppose, is to also use RPATH in the executable of the simulation. But if there is a simpler way to convince the loader to first use RPATH that would be great.