Skip to content

Compiling R-packages on Mac

2 messages · R. Michael Weylandt, Simon Urbanek

#
Let's keep this on list.

(And if you can, please do reply in plain text -- I've had to
re-format things more or less manually to make it legible)

On Sat, Mar 30, 2013 at 11:50 AM, Petar Milin
<petar.milin at uni-tuebingen.de> wrote:
But where did the local binaries come from if you can't build them?
Perhaps a $PATH issue, but I'd be quite surprised if R.app had a
different path than the plain R executable.

Perhaps the following will help

echo $PATH

from the terminal and Sys.getenv("PATH") from within R. If you can
narrow it down to what tool in particular is failing, comparing the
output of `which` and Sys.which() might be more direct.

Finally, the traceback of the failed build perhaps and the exact
install.packages() command you used.
Yes, sorry if that wasn't clear. Simon is the official R-on-Mac "guy"
(though certainly not the only one of R Core to use it) and provides
the official binaries. You can probably get away with using Mac Ports
or Homebrew or whatnot, but if it doesn't work and you need help, be
prepared to be told to use the officially supported tools.

Michael
#
On Mar 30, 2013, at 7:59 AM, R. Michael Weylandt wrote:

            
No you can't (at least not for HPC, Fink, MacPorts) - they don't have Apple compiler drivers. If you want to use those, you'll have to compile R yourself using their tools.  (I'm not 100% about Homebrew, because they apparently use our compilers as I learden from the storm of e-mails when we had server issues ;)) You'll have to pick the world you want to live in - either native OS X + CRAN (supported by us) or one of the parallel universes like MacPorts, Fink etc. (supported by them, not us). But as Brian, said, reading the manuals is a good start (and FWIW, if you downloaded R from CRAN, you did see the link pointing you to the tools).

Cheers,
Simon