^^-- this is really bad form - you should never build/compile
software as root. The location of the build directory is irrelevant
so use /tmp or you home or something like that ... (usualy the
fastest disk ;))
OK, thanks for the tip, although I don't understand the configure - make -
install cycle enough to see how compiling as non-root and installing as
root is
any safer than just doing both as root.
Why would you do all that?
Well, when you've been trying for hours to get something to work and it
doesn't
and there are no workable examples on the net... is it too much to ask that a
workable example be placed in the documentation? Finally I have a script that
has worked for me (writen before I saw Simon's comment about root)
cd /usr/local/lib
umask 022
mkdir R-2.9.2
mkdir build_vg0
mkdir build_vg1
mkdir build_vg2
cd /usr/local/lib/build_vg2
sudo /usr/local/src/R-2.9.2/configure --enable-memory-profiling
--with-valgrind-instrumentation=2 r_arch=vg2
sudo make
sudo make prefix=/usr/local/lib/R-2.9.2 install
cd /usr/local/lib/build_vg1
sudo /usr/local/src/R-2.9.2/configure --enable-memory-profiling
--with-valgrind-instrumentation=1 r_arch=vg1
sudo make
sudo make prefix=/usr/local/lib/R-2.9.2 install
cd /usr/local/lib/build_vg0
sudo /usr/local/src/R-2.9.2/configure --enable-memory-profiling
--with-valgrind-instrumentation=0 r_arch=vg0
sudo make
sudo make latex
sudo make dvi
sudo make pdf
sudo make info
sudo make help
sudo make html
sudo make prefix=/usr/local/lib/R-2.9.2 install
sudo cp /usr/local/lib/R-2.9.2/bin/R /usr/local/bin/R
IMHO, if the surpless newbie chaff was whittled off this example might
be useful
to others in the official documentation.
David
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
