Error reading R script (),system error 2 when trying to run R Studio on Mac - macos

I installed R Studio desktop in my MacBook air running on Big Sur. Unfortunately, it cannot run due to the error below:
Error reading R script (),system error 2 (No such file or directory);
Unable to find libR.dylib in expected locationswithin R Home directory
/Library/Frameworks/R.framework/Resources

Running brew install R solves the problem for me.

A similar question was asked on the R Studio community.
You need to first download base R:
Choose the latest version from here, under the Latest release header. For example, R-4.1.0.pkg.
Then download R Studio for MacOS from here.

You have probably installed Rstudio before installing R. What you can do is to first install R using brew install R and then reinstalling Rstudio using brew reinstall rstudio.

To add to all above info, with recent releases of MacOS we will have to install XQuartz before installing R. After these installations, proceed with RStudio installation.

Related

Problems installing and opening Anaconda3 on macOS Sierra

I am using a MacBook Pro (early-2011) with macOS Sierra v10.12.6. I can not install and run Anaconda3. I have downloaded the pkg file from the Anaconda webpage. First day, it took overnight to finish installing. After which it said installation failed. I tried to delete all files and reinstall all over again serval times, but this hasn't worked. I made sure the /opt folder was empty before I reinstall again, but even like that didn't work.
Any ideas how to make it work?
Had a similiar problem with a geriatric iMac mid 2010 running OSX 10.13.16. The GUI installer for Anaconda 3 takes an age, then reports there was a problem.
I downloaded the install script and ran, "bash Anaconda3-2022.05-MacOSX-x86_64.sh" in a terminal.
Answered questions, and after some time, have Anaconda installed in my personal space. Now to figure out how to use the latest LTS Julia.
No Anaconda support. Current Anaconda (and likely Miniconda) distribution declares a minimum system requirement of macOS v10.13+. One could try scraping back through the archive to find an older distribution that will install, but I wouldn't recommend that.
Conda Forge supports macOS 10.9+. Conda Forge still builds all osx-64 packages with a macOS 10.9 target. Hence, you should be fine using instead a Miniforge variant for the base Conda installation. I strongly recommend Mambaforge, and using mamba instead of conda.

error while installing Python 2.7.12 "There is a problem with this window installer package"

I want to install Python 2.7.12 but It shows following error.
There is a problem with this window installer package. A program required for this install to complete could not be run.
I saw one youtube video (https://www.youtube.com/watch?v=KikshWVWhzg) and so I provide full access to system and User. Even then, the same problem occurs.
How to solve this problem?
I solved this problem by my own.
Actually what happens is: In past, I installed Python 2.7.10 and by mistake, I deleted python27 file from C drive. But python remains installed in computer and when I tried to uninstall it, It shows the same error as above. So to uninstall this,
first I download similar python file (python2.7.10ci) version and try to install it. And you see it got installed. Due to this a file get generated in C drive with name python27 and now I can uninstalled python which I installed a long time back.
After uninstalling old python2.7.10, I right click on python 2.7.10ci (in control panel ) and choose repair. Due to this again a file generated with python27 and now I uninstalled this too easily.
After doing all this, I downloaded python 2.7.12 and try to install. And I able to install this without any error.

Installing Wxpython on mac

I am trying to install wxpython on mac os. I have already tried following solution. I have already enables software installation from all sources
a) Downloaded the binary for mac and tried to install it. It says no software found to install at the last step.
b) I tried using brew to install. The brew command works find but when when I tried import wx it says no module found.
Can you specify how to get rid of this error? My mac version is 10.11.5 I am using python 2.7
Try using the installer found here: https://wxpython.org/snapshots/. It is a current (as of 2 weeks ago) snapshot of the code, modified to use the newer Installer Package format.

Error installing control v3.0.0 package on El Capitan for Octave

I recently installed Octave using the binary installer found on this site: http://wiki.octave.org/Octave_for_MacOS_X
I then tried to install the control package using 'pkg install -forge control' but it gave me the error 'pkg: error running `make' for the control package.'. I have gone through most of the threads regarding this error but with no success.
I then tried to use MacPorts to install the control package, I followed the instructions on the wiki page above with some help from this thread: Installing general package in octave has error. I believe I succeeded installing the packages because I can see them in the folder tree for Octave and MacPorts says it is installed when using the console.
The problem is that when i run some code in Octave it cannot build as it doesn't know that I have installed any additional packages. Using 'pkg list' in Octave it says that no additional packages installed. I feel like I need to link the two together but I don't know how?
I'll happily explain more if I need to and I hope you can help me out.
Many Thanks,
Sam.
You cannot "link the two together" (assuming you mean the binary version of octave and the MacPorts version).
If you have packages installed via MacPorts for the MacPorts version of octave, then they will only be available from the the MacPorts version of octave, so make sure you are running that.
Otherwise, figure out how to install the package with the octave binary version. It seems you require a build environment for this, but installing the command line tools (which you must have done for MacPorts to work) might have already solved this problem.
It seems to be a problem with gfortan compiler built-in with Octave. To solve this you should install an external fortran compiler.
Try this:
Install Xcode and command line tools for Xcode
Download and install a fortran compiler for MacOS, for example: http://coudert.name/software/gfortran-6.1-ElCapitan.dmg
Change the fortran compiler path in your octave, to this if you installed the compiler that I suggested in point number 2 you only must to open Octave and type: setenv('F77', '/usr/local/gfortran/bin/gfortran').
And Enjoy Octave for MacOS
Octave with control package 3.0.0 on MacOS
You haven't provided enough information for a precise diagnostic, but I had the same error message (and a few more), and re-installing octave from source solved it; see this link for more info, but essentially you can do it by running brew reinstall --build-from-source octave.

Solving install issues with Python 3.4 on Windows

I have recently tried to install Python 3.4 as an alternative installation on my system in an attempt to familiarise myself before migrating code. My main Python installation is 2.7.6.
I tried the 64 bit installer for Windows, but it came up with an error message
There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.
After this the install is rolled back (from the point shown below):
I have eventually found a solution to this posted below and decided to share in case anyone else was having the same issue.
After some looking online I found (here) that the issue was related to conflicting pip installs (I have a version already installed for Python 2.7 and apparently this is not compatible with the version that ships with Python 3.4.
To get around this issue I simply de-selected pip from the install options shown below and the install went ahead smoothly:
Run installer again and select PIP installation.
If the PIP fails to install with the same error, you may want to check environmental variables using a tool like http://eveditor.com/ which enables to check whether they are valid. If you had another version installed before, you most likely have wrong PYTHONHOME and PYTHONPATH variables. Fix them by setting them to relevant paths. e.g. PYTHONHOME=C:\python27 and PYTHONPATH=c:\python27\Lib
You will then be able to run and install PIP.
My issue was that I had a PYTHON_HOME or PYTHON_SOMETHING environment variable set. After removing the environment variable, the installation worked perfectly.
What worked for me, strangely enough, was the "Microsoft Program Install and Uninstall troubleshooter"
The "deselect pip" solution did not work for me.
My Python 3.4.1 install was failing with the same "A program run as part of the setup did not finish as expected" error. I tried both installing it on top of Python 3.4.0 and installing it in a new folder, but got the same error. I tried uninstalling Python 3.4.0 first, but got the error during the uninstall, as well.
I ran that Microsoft utility, which helped me uninstall 3.4.0, and was then able to install 3.4.1 cleanly. The utility has options for both problematic installs and uninstalls, so it may help even if you're doing a new install, not an upgrade.
I'm running 64-bit Windows 7, but was working with 32-bit Python versions.
I had similar issues with Python 3.4x on Windows 8.1. Even after a successful install, the uninstaller would fail in the same way. Ultimately, "Method 1" at the MS forum solved this for me when I ran Microsoft's (Un)installer Fix It.
I also had the problem that pip couldn't be installed like #ChrisPosser.
So I deselected pip and the installation went fine. afterwards I restarted the setup, chose "change python" and installed pip. now everything worked like expected.
If you have any problems with windows installers I recommend activating the verbose log like this:
msiexec /i python-2.7.10-1.609.2.msi /lv install-python.log
From the logs I could see that it was the pip install, which was not working.
Yes, I faced the same issue, and was working on this for the past one hour. Was trying to uninstall the Python 3.4.1 from the control panel -> uinstall program -> add/remove program, but was facing issues.
This trick worked for me:
Manually deleted the 3.4.1 folder, which was present in my C folders after I installed the 3.4.1
Then I followed these steps:
-> Went to Regedit.exe, checked in both HKEY_CURRENT_USER, HKEY_LOCAL SOFTWARE Folder, and deleted the Python folders there.
-> windows 8 -> Downloads -> 3.4.1 msi setup (Glad I never deleted it)
-> Right clicked on the msi setup and choose the repair option
-> The repair would re install the Python 3.4.1
-> After this, I un-installed the Python 3.4.1
-> Then I deleted the 3.4.1 msi setup.
Rebooted the system, and now, there is no instance of Python 3.4.1 in my system.
According to me when environment variables containing name 'Python' are created they somehow becomes related with python. I was unable to open idle (GUI PUTHON) and to uninstall it . Deleting a variable named 'PYTHON PATH' solved my all python related problems.
I had 3.7.4 and wanted to move to 2.7.13.
I uninstalled 3.7.4
Tried to install 2.7.13 but got the same error.
There was a 2.7.10 installer(not msi) also present, uninstalling which gave the same error.
So I downloaded 2.7.10 msi, installed it, and then just installed 2.7.13 from the downloaded msi and it worked fine. This overwriting worked because the major version i.e. 2.7 was same for both.
I don't know if this is helpful but after the hours I spent on this, I wanted to write out what worked for me.
Yup, I have already installed another version of python. I have uninstalled them using Program features. But still the same issue persisted because of the folder which was present in my C: drive. After deleting them manually, the installation got completed without errors
I faced this issue because of 2 conflicting versions of 7zip. Removing them both and installing just one fixed this issue.
I had python3.4 installed, then added 3.5, and deleted 3.4. That was a mistake. In trying to get a library to work, I had to go back to 3.4. I uninstalled 3.5, but couldn't uninstall 3.4 (folder deleted).
I ended up searching the registry in rededt32 for "python". There was a Guid folder with a number of entries that had c:\python34 and one more related to the same folder that I deleted. After this, the install worked correctly.
Windows 10.
Mine was linked to having installed an older version in the past, only for my own user account. I got around it by telling the installer to install Python for all users.
For me none of the suggested fixes worked for me. However checking the option "Install just for me" instead of "Install for all users" (Windows 10) worked for me. So this might be another option to try.

Resources