Shortest possible answer: Failing to install ggplot2 won't affect any package's ability to correctly perform statistical calculations. It only limits the ability to present them through the nifty
If you select the
n option, you can *still install
the usually only slightly outdatedbinary` version.
There are two install issues
There are binary versions available but the source versions are later:
binary source needs_compilation
rlang 0.1.6 0.4.5 TRUE
ggplot2 2.2.1 3.3.0 FALSE
Do you want to install from sources the package which needs compilation?
Package which is only available in source form, and may need compilation of C/C++/Fortran:
ggplot2 depends on
rlang depends on
isoband, which needs to be installed from source, but it, again, relies a different resource,
xrun and it on
xcrun which is not a package, but a compiler tool. Here's mine
$ 569: l /usr/bin/xcrun
-rwxr-xr-x 1 root wheel 30K Jan 23 05:59 /usr/bin/xcrun*
which is in a different location than the one that yours is looking for,
Ok, hang in there.
The reason it's not there is that the
xcrun in that directory is not there, because, in turn the directory itself isn't there and needs to be.
And the reason that it is missing is because the
CommandLine\Tools directory itself isn't there. That isn't there because of two possibilities
- the command line tools haven't been installed or
- the free Xcode app from the App Store (yes, I used my magical powers to see you are on macOS and also not yet on Catalina*)
Depending on the macOS version, here' the backstory and the fix (unless you are on a waaay old macOS version.)
On macOS, packages sometimes fail to install, often with a non-zero exit status message. This is due to Apple's idiosyncratic compiler. The same packages will install on most Linux systems without trouble. Saint Simon Urbanek of the
R Core Development Team takes on the brain damage required to recode the source to get around macOS's peculiar worldview for those in CRAN, but he can't bestow the same mercy on those still in development.
Some packages will successfully install through compilation from source, but many won't.
When installing if you are offered the option to install from source, it makes sense to try it once. But, if at first it doesn't succeed, in all likelihood it never will. It's usually only 7-10 days until a macOS binary is available, but for some reason it's been a year and it hasn't yet been.
And THEREFORE, it doesn't need to be because it readily compiles, so installing the command line utilities SHOULD work.