В 10:23 +0200 на 05.10.2011 (ср), lluvia_listas[@nospam] написа:

> 
> for compiling, and
> 
>    sudo make install

I would not recommend this step. It could override system files and
usually the installed files are not easy to remove. It is not a good
idea to manually install software in the same place where the package
manager does (/usr, /usr/bin, /usr/lib, /lib, /bin ...).

Some packages do not provide "make uninstall", which prevents their
removal. A better way is to set the DESTDIR variable. This will install
all files in the path specified by DESTDIR. For example:

DESTIDR=$HOME/binaries/ make install

Of course not every project respects the DESTDIR variable. Packages
using GNU Autotools do.

For testing the step could be executed without sudo. It will fail, but
it will be possible to see where it will install.

It is always a good idea to execute ./configure with
--prefix=/usr/local.

A useful tool is GNU Stow, which manages software installed
in /usr/local (mostly compiled locally) by providing symbolic links
in /usr/local/bin, /usr/local/lib etc. etc. to the actual path where the
package files are. This is
usually /usr/local/stow/locally_compiled_package_name.

Oh, and for configure, make, gcc and other commands to be available one
should install the build-essential package.

Reply via email to