Re: hardcoded shared library path

B Thomas wrote: Hi, I am trying to understand what causes the search path for a shared library to be hardcoded in to an dynamically linked executable. Also how can one avoid this, so that a user may run the executable with say processor optimised libraries, in a non-standard location. Any pointer

hardcoded shared library path

Hi, I am trying to understand what causes the search path for a shared library to be hardcoded in to an dynamically linked executable. Also how can one avoid this, so that a user may run the executable with say processor optimised libraries, in a non-standard location. Any pointer to information