Found a workaround (or perhaps solution): Move the variable setting to ~./.bashrc:
~/.profile: if [ -d "$HOME/lib" ] ; then export LIBRARY_PATH="$HOME/lib" fi
~/.bashrc: if [ -d "$HOME/lib" ] ; then export LD_LIBRARY_PATH="$HOME/lib" fi
sperlis said that LD_LIBRARY_PATH may be deleted for security reasons in certain situations. Is this the case here?
Declaring variables in ~/.bashrc is less efficient according to https://help.ubuntu.com/community/EnvironmentVariables:
"However, performance-wise this may not be the best thing to do since it will cause values to be unnecessarily set many times".
If LD_LIBRARY_PATH is blocked for security reasons it is not a bug. There should however be more information on this.
Found a workaround (or perhaps solution):
Move the variable setting to ~./.bashrc:
~/.profile: PATH="$ HOME/lib"
if [ -d "$HOME/lib" ] ; then
export LIBRARY_
fi
~/.bashrc: PATH="$ HOME/lib"
if [ -d "$HOME/lib" ] ; then
export LD_LIBRARY_
fi
sperlis said that LD_LIBRARY_PATH may be deleted for security reasons in certain situations. Is this the case here?
Declaring variables in ~/.bashrc is less efficient according to https:/ /help.ubuntu. com/community/ EnvironmentVari ables:
"However, performance-wise this may not be the best thing to do since it will cause values to be unnecessarily set many times".
If LD_LIBRARY_PATH is blocked for security reasons it is not a bug. There should however be more information on this.