Troubleshooting the configuration process

Two common things to check for are:

1. Check the value of the LD_LIBRARY_PATH environment variable. This is used to tell your system where to look for libraries which are not installed in /usr/lib. Quite often packages which you install yourself will put library files in /usr/local/lib by default. If LD_LIBRARY_PATH doesn't point to this directory (or wherever else the library files are installed) then programs which depend on these libraries at run time will not be able to find them.

   To find out the value type:

      echo $LD_LIBRARY_PATH
   

   If the value is empty or doesn't contain /usr/local/lib or any of the paths where your libraries are located in its colon separated list of paths then you must amend it so that it does. To do this first find out which shell you use by typing:

      echo $SHELL
   

   If you're using the bash shell see section * below for details of how to amend the value. If you're using the tcsh shell see section *.

2. If you install Mesa, GLUT or audiofile via RPM binary distributions check that you have the appropriate development packages installed also. These include:
   • audiofile-devel-0.1.6-*
   • Mesa-devel-3.0.*
   • Mesa-glut-devel-3.0.*

   These packages provide header files and symbolic links to the libraries (e.g. libaudiofile.so linked to libaudiofile.so.0.0). Without these packages the libraries themselves may be installed but you still won't be able to compile and link programs with them.

If, after reading this section you are still baffled then take a look at the next section too, since there is a further tool you can use to help diagnose problems.