[Rd] make check fails when R_HOME env var set (PR#1284)

[Warnes, Gregory R]

Perhaps one solution would be to add an equivalent line to the top level
makefile ?

-Greg

> -----Original Message-----
> From: Liaw, Andy [mailto:andy_liaw@merck.com]
> Sent: Friday, January 25, 2002 4:16 PM
> To: 'gregory_r_warnes@groton.pfizer.com'; r-devel@stat.math.ethz.ch
> Cc: R-bugs@biostat.ku.dk
> Subject: RE: [Rd] make check fails when R_HOME env var set (PR#1284)
> 
> 
> I also fell into that trap a couple of times, but it doesn't 
> really bother
> me, since it's, IMHO, a real minor inconvenience.
> 
> (In bash, under Linux:)  Would the following work?  Haven't tried...
> 
>   R_HOME="" make check
> 
> Andy
> 
> > -----Original Message-----
> > From: gregory_r_warnes@groton.pfizer.com
> > [mailto:gregory_r_warnes@groton.pfizer.com]
> > Sent: Friday, January 25, 2002 3:11 PM
> > To: r-devel@stat.math.ethz.ch
> > Cc: R-bugs@biostat.ku.dk
> > Subject: [Rd] make check fails when R_HOME env var set (PR#1284)
> > 
> > 
> > 	
> > When the R_HOME environment variable is set, R issues a 
> > warning messages
> > when it starts up.  When doing 'make check' this causes the 
> check for
> > eval-etc.R to fail:
> > 	
> > 	[...]
> > 	make[3]: Leaving directory
> > `/Volumes/app/R/src/R-1.4.0_patched_2002-01-24/tests'
> > 	running strict specific tests
> > 	make[3]: Entering directory
> > `/Volumes/app/R/src/R-1.4.0_patched_2002-01-24/tests'
> > 	running code in `eval-etc.R' ... OK
> > 	comparing `eval-etc.Rout' to `./eval-etc.Rout.save' ...1d0
> > 	< WARNING: ignoring environment value of R_HOME
> > 	make[3]: *** [eval-etc.Rout] Error 1
> > 	make[3]: Leaving directory
> > `/Volumes/app/R/src/R-1.4.0_patched_2002-01-24/tests'
> > 	make[2]: *** [test-Specific] Error 2
> > 	make[2]: Leaving directory
> > `/Volumes/app/R/src/R-1.4.0_patched_2002-01-24/tests'
> > 	make[1]: *** [test-all-basics] Error 1
> > 	make[1]: Leaving directory
> > `/Volumes/app/R/src/R-1.4.0_patched_2002-01-24/tests'
> > 	make: *** [check] Error 2
> > 
> > This is, of course easily worked around by unsetting R_HOME 
> > and removing it
> > from the shell startup scripts, but this is incovienient when 
> > R_HOME needs
> > to be set for other reasons (e.g. to allow the Python interface to R
> > 'RSPython' to find the R code it needs).
> > 
> > It already appears that the version strings are filtered out 
> > when testing
> > for difference between the versions.  Is it possible to 
> filter out the
> > environment variable warning message as well? 
> > 
> > -Greg
> > 
> > 
> > LEGAL NOTICE
> > Unless expressly stated otherwise, this message is 
> > confidential and may be privileged. It is intended for the 
> > addressee(s) only. Access to this E-mail by anyone else is 
> > unauthorized. If you are not an addressee, any disclosure or 
> > copying of the contents of this E-mail or any action taken 
> > (or not taken) in reliance on it is unauthorized and may be 
> > unlawful. If you are not an addressee, please inform the 
> > sender immediately.
> > 
> > -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.
> > -.-.-.-.-.-.-.-.-
> > r-devel mailing list -- Read 
> > http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
> > Send "info", "help", or "[un]subscribe"
> > (in the "body", not the subject !)  To: 
> > r-devel-request@stat.math.ethz.ch
> > _._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._.
> > _._._._._._._._._
> > 
> 
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: r-devel-request@stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._