On Aug 26, 2009, at 10:43 , pleyd...@supagro.inra.fr wrote:
^^-- 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
^^-- 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 -
insta
On Aug 26, 2009, at 6:47 , pleyd...@supagro.inra.fr wrote:
You're confusing rhome and arch - the above makes no sense. Let
rhome alone and you should be fine. (And make sure you're not
building in the source tree - you should be using something like
mkdir obj_vg0 && cd obj_vg0 && ../R-2
is suspect installing to seperate _vg0, _vg1 and _vg2 directories
could be the problem. I'll retry and post the results.
Well, the following script didn't work
cd /usr/local/lib
sudo mkdir R
cd /usr/local/lib/R
sudo /usr/local/src/R-2.9.2/configure --enable-memory-profiling
--with-valgrind-inst
You're confusing rhome and arch - the above makes no sense. Let rhome
alone and you should be fine. (And make sure you're not building in
the source tree - you should be using something like mkdir obj_vg0 &&
cd obj_vg0 && ../R-2.9.1/configure ...)
Thanks Simon. I'd already tried various var
On Aug 25, 2009, at 12:31 PM, pleyd...@supagro.inra.fr wrote:
"R Installation and Administration", section 2.5 "Sub-architectures"
describes
calling specific builds of R using the call "R --arch=name". I am
trying to
build and install three versions of R-2.9.1, each configured with a
diffe
"R Installation and Administration", section 2.5 "Sub-architectures" describes
calling specific builds of R using the call "R --arch=name". I am trying to
build and install three versions of R-2.9.1, each configured with a different
valgrind-instrumentation level ("Writing R Extensions", section 4.
