With XCode 5.0, clang is now the default compiler toolchain supplied,
and llvm-gcc-4.2 is no longer available.
FWIW, I and many others have had a lot of success compiling packages
with the version of clang supplied with XCode. The only requirement
(at this point) is that you set your own ~/.R/Makevars settings, as
discussed in the SO posts -- in particular, you need
CC=clang
CXX=clang++
You may need to reinstall packages from source that your packages link
to (e.g., Rcpp) and compile them with the new set of compilers for
them to play nicely together, but in general this should work.
However, hopefully others can give advice on the 'recommended'
compiler toolchain now for R and Mavericks.
-Kevin
On Thu, Oct 24, 2013 at 3:00 PM, David Winsemius <[email protected]> wrote:
> From comments made on the thread regarding the segfault in the R.app GUI
> following the error from TRUE <- FALSE, I'm inferring that at least three
> people ( Prof. Ripley, S. Urbanek, and T. Bates) have installed R 3.0.2 on
> Mavericks. I have R version 3.0.2 (2013-09-25) -- "Frisbee Sailing" with
> R.app GUI 1.60 (6475) and XCode Version 3.2.6 in OSX 10.7.5 and have
> installed the Command Line Tools, so at the moment I'm generally succeeding
> when compiling from source. (I see I am rather behind the current GUI version
> although that was not my intention when I updated to 3.0.2.) Are there any
> specific steps one needs to take (or avoid taking) in order to preserve
> access to (or gain updated access to) tools for compiling packages from
> source?
>
> (I've seen people posting problems on SO where the error after updating to
> Mavericks was a missing copy of llvm-gcc-4.2.)
>
> --
> David Winsemius
> Alameda, CA, USA
>
> _______________________________________________
> R-SIG-Mac mailing list
> [email protected]
> https://stat.ethz.ch/mailman/listinfo/r-sig-mac
_______________________________________________
R-SIG-Mac mailing list
[email protected]
https://stat.ethz.ch/mailman/listinfo/r-sig-mac
