From simon.urbanek at r-project.org  Wed Aug 26 16:11:11 2009
From: simon.urbanek at r-project.org (Simon Urbanek)
Date: Wed, 26 Aug 2009 10:11:11 -0400
Subject: [Rd] Cannot make 3 different R installations for 3 different
	valgrind-instrumentation levels
In-Reply-To: <20090826124729.ad1ilt691u880w0w@web.supagro.inra.fr>
References: <20090825183131.19kjcomatupco0wg@web.supagro.inra.fr>
	<D30ADD33-3339-409D-B2E2-9090B4E14CD8@r-project.org>
	<20090826124729.ad1ilt691u880w0w@web.supagro.inra.fr>
Message-ID: <1AC73CC3-67A9-4800-9B9C-E65525D35152@r-project.org>


On Aug 26, 2009, at 6:47 , pleydell at 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.9.1/configure ...)
>
> Thanks Simon. I'd already tried various variations with rhome and  
> arch, but I
> think my biggest error was that I was always compiling from within  
> the source
> tree. However, the following script still doesn't quite do the job
>
> cd /usr/local/lib
> mkdir R-2.9.2_vg0
> mkdir R-2.9.2_vg1
> mkdir R-2.9.2_vg2
> cd /usr/local/lib/R-2.9.2_vg2
> sudo /usr/local/src/R-2.9.2/configure --enable-memory-profiling
> --with-valgrind-instrumentation=2 r_arch=vg2

^^-- 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 ;))


> sudo make
> sudo make install
> cd /usr/local/lib/R-2.9.2_vg1
> sudo /usr/local/src/R-2.9.2/configure --enable-memory-profiling
> --with-valgrind-instrumentation=1 r_arch=vg1
> sudo make
> sudo make install
> cd /usr/local/lib/R-2.9.2_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 uninstall
> sudo make install
>

Why would you do all that? It should work if you do just make && make  
install on the subsequent archs. Note that docs etc. are all shared so  
it's sufficient to build them in the first arch.

Cheers,
Simon

PS: the config.log entry you sent is entirely irrelevant - it's header  
handling test


> Now the command "R --arch=vg0" executes fine, but...
>
> david at david > R --arch=vg1
> /usr/local/bin/R: line 230: /usr/local/lib/R/bin/exec/vg1/R: No such  
> file or
> directory
> /usr/local/bin/R: line 230: exec: /usr/local/lib/R/bin/exec/vg1/R:  
> cannot
> execute: No such file or directory
>
> david at david > R --arch=vg2
> /usr/local/bin/R: line 230: /usr/local/lib/R/bin/exec/vg2/R: No such  
> file or
> directory
> /usr/local/bin/R: line 230: exec: /usr/local/lib/R/bin/exec/vg2/R:  
> cannot
> execute: No such file or directory
>
> is suspect installing to seperate _vg0, _vg1 and _vg2 directories  
> could be the
> problem. I'll retry and post the results.
>
> David
>
>
>



[Rd] Cannot make 3 different R installations for 3 different valgrind-instrumentation levels
Simon Urbanek