[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Guile
From: |
Thien-Thi Nguyen |
Subject: |
Re: Guile |
Date: |
Thu, 08 Sep 2005 07:59:38 -0400 |
From: Jon Wilson <address@hidden>
Date: Wed, 07 Sep 2005 15:50:50 -0500
Run configure and make as an unprivileged user, and then run make
install as root, IF necessary. (which it probably is, but give it a
shot as unprivileged first.)
this advice can be extended also to "make install", if the installation
directories are not "system directories". the approach is to create
"~/local" (in my case, this resolves to "/home/ttn/local") and configure
for, install into, and evaluate safely, software under that directory.
"safely" because you need not worry about damaging the system dirs due
to the fact that you can completely avoid being root.
one-time setup (suitable for ~/.bashrc or the like):
export LD_LIBRARY_PATH=$HOME/local/lib:$LD_LIBRARY_PATH
export PATH=$HOME/local/bin:$PATH
building software:
cd [directory where source is expanded from the tarball]
./configure --prefix ~/local [other configure options...]
make
make check
make install
make installcheck
note: in the one-time setup, there is $HOME instead of ~, but the idea
is the same. of course there is a downside: software that presumes to
be installed in a system directory. hopefully, those will be few.
thi
- Guile, Angelyn V. Dilim, 2005/09/07
- Re: Guile, Jon Wilson, 2005/09/07
- Re: Guile, Jon Wilson, 2005/09/07
- Re: Guile,
Thien-Thi Nguyen <=