From rowe at muxspace.com  Wed Sep 11 07:29:29 2013
From: rowe at muxspace.com (Brian Lee Yung Rowe)
Date: Wed, 11 Sep 2013 06:29:29 +0100
Subject: [Rd] R CMD config for R >= 3.0.1
In-Reply-To: <A34BCB42-029B-4B79-9F9D-4D6FD9F3C64E@r-project.org>
References: <20130518145434.4194be90@bossiaea>
	<1378848279883-4675813.post@n4.nabble.com>
	<1378848656818-4675814.post@n4.nabble.com>
	<A34BCB42-029B-4B79-9F9D-4D6FD9F3C64E@r-project.org>
Message-ID: <6B24A1C4-586E-459D-9C4B-80E5596D22AF@muxspace.com>

As an alternative, you might consider installing a virtual machine in your user space and installing R from there. That way you don't have to do a bunch of one-off gymnastics to get R compiled. 



On Sep 11, 2013, at 1:40 AM, Simon Urbanek <simon.urbanek at r-project.org> wrote:

> On Sep 10, 2013, at 5:30 PM, crunch wrote:
> 
>> Also have no cooperation from the admin of the machine, so can't ask for a
>> yum install.
> 
> Please follow Brian's advice. If you don't have even Fortran on that machine, then you're really in a pickle: you can extract the gfortran rpm contents (and all dependencies you may need) by hand in any place that you have access to and adjust LD_LIBRARY_PATH for the runtime accordingly. However, it's not a trivial task - it particular if you're not very familiar with subtleties of Linux. (I had to do this fairly recently on a CentOS machine, so I know it's possible, but there are a few gotchas that may require a few symlinks created by hand).
> 
> Cheers,
> Simon
> 
> 
>> 
>> --
>> View this message in context: http://r.789695.n4.nabble.com/R-CMD-config-for-R-3-0-1-tp4667399p4675814.html
>> Sent from the R devel mailing list archive at Nabble.com.
>> 
>> ______________________________________________
>> R-devel at r-project.org mailing list
>> https://stat.ethz.ch/mailman/listinfo/r-devel
> 
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel



[Rd] R CMD config for R >= 3.0.1
Brian Lee Yung Rowe