How do I manually remove ESyS-Particle?

In the event that "make uninstall" and "make distclean" are not run before rebuilding ESyS-Particle (with "configure", "make" and "make install"), a manual removal of installed files may be necessary to avoid new simulations attempting to use the incorrect versions of files. For instance, if Python was upgraded after ESyS-Particle was installed, failure to "make uninstall" and "make distclean" before rebuilding ESyS-Particle will result in two sets of installed Python libraries. Or if ESyS-Particle is rebuilt with a different installation location specified on the "configure" command line, executables and libraries will appear in different locations. Depending on the state of the $PATH, $LD_LIBRARY_PATH, $LIBRARY_PATH and $PYTHONPATH environment variables, the system may not know where to look for the new installation, or it may find an old installation before it reaches the new installation directory in its path list. Here are the steps to manually remove installed files.

If the earlier installation of ESyS-Particle (version 2.0) was to the default /usr/local/, using Python 2.6, check for the existence of:

  /usr/local/share/doc/esys-particle-2.0/pythonapi/,

  ESyS-Particle libraries and scripts under /usr/local/lib/python2.6/dist-packages/,

  ESyS-Particle libraries in /usr/local/lib/, and

  ESyS-Particle executables in /usr/local/bin/.

(Use your version number of ESyS-Particle in place of "2.0" and your version number of Python in place of "2.6". Depending on your installation, you may need to replace "dist" with "site". If you used the "--prefix" switch in the "configure" command line, use the argument that you supplied in place of /usr/local/. You may do well to run the "find" utility to locate directories containing existing files in case you have used different arguments for the "--prefix" installation switch when running "configure" in the past; for example:

  sudo find / -name esys.lsm-module.html
  sudo find / -name libLsmPy*
  sudo find / -name libParallel*
  sudo find / -name mpipython
)

Remove /usr/local/share/doc/esys-particle-2.0/pythonapi/ and all directories underneath if not already deleted.

Remove /usr/local/lib/python2.6/dist-packages/esys/ and all directories underneath if there are scripts or libraries in them.

If the ESyS-Particle libraries

  libBoostPythonUtil*
  libFields*
  libFoundation*
  libGgGeometry*
  libMacroFrictionCalc*
  libModel*
  libntable*
  libParallel*
  libppa*
  libStressCalculator*
  libTmlComm*
  libTmlMessage*
  libTmlType*

have not already been deleted from /usr/local/lib/, remove them also.

Likewise, remove the ESyS-Particle executables

  dump2pov
  dump2vtk
  ESySParticleBEWorker
  fcconv
  forcetofric
  fracextract
  grainextract
  lamexecLsm
  lsmpython
  mesh2pov
  mpipython
  mptrunLsm
  mptrunLsmFile
  pfc2geo
  profextract
  raw2tostress
  rotextract
  slip2vtk
  strainextract

from /usr/local/bin/ if they still exist.

Update the paths in $PATH, $LD_LIBRARY_PATH, $LIBRARY_PATH and $PYTHONPATH to reflect the new installation location (specified with the "--prefix" switch on the "configure" command line) and Python version (determined by "python --version").