Hi I am using program the needs to have R 2.11.x installed on my Mac with El Capitan. However, when I try to install this I get an error message saying that R.2.11 version is not supported in Leopard or previous versions of OS. Please let me know if there is a get around to this problem. Thank you.
R 2.11 is ancient. No wonder you can’t install it.
If you really need this old version, the only recourse is to use a different PC or a virtual machine with another operating system installed on it.
But chances are you should use a much newer version of R.
Related
According to cran.r-project.org, I should be using R 4.2.1 binary for macOS 11. The only thing is, I'm concerned about compatibility issues due to a mismatch between operating system and machine specs. I'm running macOS 11.5 on a mid-2012 MBP via a patcher (PatchedSur) which works quite nicely with most apps. However, the Cran Project website specifically states that R 4.2.1 binary for macOS 11 will not work on older Intel-based Macs.
Any idea on which version of R I should install if any? I'm beginning to think that perhaps I'm better off using RStudio Cloud (or even better--a newer machine).
Thanks!
https://cran.r-project.org/bin/macosx/
As in R documentation:
The last version known to run on Windows 2000 was 2.12.2. Windows XP is no longer supported.
I tried to install R 3.4.3 on windows xp , but i faced problems when installing packages that i didn't face when installing them on Windows 7 system. I think it is safe to assume that R 2.12.2 runs on Windows xp as windows 2000, but does a version later than R 2.12.2 runs on windows xp also? what is the highest version ?
The latest version officially supported on XP was one version below, 3.4.2. Nevertheless, R as high as 3.6.0 installs and runs well on XP (though is not officially QA tested).
Starting from v.3.6.1, R is packed with InnoSetup v.6.0.0 (that means, installing on WinXP will not succeed and end up with an error "not valid Win32 application"). However, one may try to unpack the installer and deploy the files manually (still may help to launch R itself). Another option which may be useful is One Core API.
But... All this stuff is relevant if one is going to use plain R or integrated R environment in some old application. Many 3rd-party R packages require the most up-to-date versions of R, what will cause inconveniences on WinXP.
I have been unable to run R from within QGIS on my Macbook. I have R version 3.4.0 installed and QGIS 2.18.9 on macOSX Sierra.
"The error message I receive is
Missing dependency.This algorithm cannot be run :-(
This algorithm requires R to be run.Unfortunately, it seems that R is not installed
in your system, or it is not correctly configured to be used from QGIS
Click here to know more about how to install and configure R to be used with QGIS"
Error Image...
I get the same thing on my MAC. Researching discovered that the MacOS X from El Capitan and later (Sierra is later) implemented some stringent sandboxing security that doesn't allow R to be seen from the QGIS location. Hence the error. So far I have not discovered a workable solution. The solutions suggested for El Capitan do not work for Sierra.
I have an R script that was written by someone else that I need to run. This script depends on another library (written by yet another person) that generates an error when the script is run. This all began after I updated my desktop to the newest Mac OSX, and subsequently updated to the newest R (and newer versions of these dependencies). I'm unable to compile this older version due to some compilers errors (error: unsupported directive '.stabs'), so a binary version seems like the easier way to go than to start digging deep into OPC as a novice R programmer. Is there a way to force R to install older versions of a binary library like there is for package managers for languages like Python and Ruby?
So, what I ended up doing that worked fine was rsyncing my old installation from an old computer that had those libraries already installed. Both were Mac OSX, but the older computer was still on the previous OS and R was compatible and the scripts do run now.
Also, I did find that if you don't reinstall R after you upgrade OS X, the installation is still valid, you just have to recreate the sym links or add the binary to your PATH.
I have been having some weird issues with R (3.1.1) and RStudio (0.98.1079) and I suspect that it is due to the fact that these programs are not longer referencing the right places after I upgraded to Mac OSX 10.10.
In particular, I cannot seem to find packages that I know I have installed on my computer to run using the system command in the R console. That is, running man pdflatex in a Terminal window yields the help manual for PDFLATEX. However running system('man pdflatex') from the R console yields the error message No manual entry for pdflatex.
The issue persists even though I reinstalled R, RStudio and MacTex since I upgraded to Mac OSX 10.10. Any help would be appreciated!
Yosemite has a bug wherein some environment variables, including PATH, appear twice in a program's environment with different values. For instance, you might notice that Sys.getenv("PATH") will show you one PATH, and system("echo $PATH") will show you an entirely different one.
I expect that most of your problems are due to this bug.
There are a few workarounds you can try immediately:
You can manually forward PATH yourself. Try this:
> system2("man", "pdflatex", env=paste0("PATH=", Sys.getenv("PATH")))
Or, you can start RStudio from Terminal:
$ open /Applications/RStudio.app
Both the R and RStudio engineers have implemented workarounds in the last few days. R (as of 3.1.2) and RStudio (as of 0.98.1087) should behave as you'd expect.
There are a host of questions about similar problems. All of them appear to come up when you update OS X to either Yosemite or Sierra with an older version of R already installed.
The easiest solution is to completely uninstall R (note the comments about using which R !), and then to install it again.
This also solves problems such as R showing different version numbers in terminal and the GUI.