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.urba...@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@r-project.org mailing list >> https://stat.ethz.ch/mailman/listinfo/r-devel > > ______________________________________________ > R-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel