When you build a package from source (one that uses
configure in the package source directory), the default behavior is to install in the
/usr/local tree -- and this is a "good thing" because anything you install as an "extra" does not interfere with system software. You can, by using arguments to
configure, install the package in
/bin,
/usr/bin,
/usr/lib and so on, but it's usually a better idea to install in
/usr/local (and there will be some arguments about this). The downside of this is that you may need to add path information to your system so it looks in
/usr/local for libraries, executables and the like.
You can add
/usr/local/lib to the
LD_LIBRARY_PATH environment variable; system-wide, edit
/etc/profile and, down toward the end of that file put
Code:
export LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:/usr/local/lib"
You must log out an log back in for this to take effect;
/etc/profile is read once at log in.
If you prefer to have user-by-user, edit the
.profile (Bourne, BASH or Korn shell),
.bashrc (BASH) or
.chsrc (C-shell) adding the above using the syntax appropriate for that shell; the example shown is for Bourne, BASH or Korn shells but not C-shell.
You should log out and log back in for the addition to take effect.
Consider, as a general rule, that you install additional software in the default
/usr/local tree and that you install "package" software (such as
OpenOffice.org) in
/opt. Doing this keeps system software and add-on software segregated; you may need to add path information to your
/etc/profile (or some other file; check your system documentation).
Hope this helps some.