Skip to content
Prev 7874 / 15075 Next

Here's what Steve said

On Sun, 20 Mar 2011, Berend Hasselman wrote:

            
I don't think that is necessary.  Provided you have a reasonable C 
compiler to start from, you can always build and install your own GNU 
toolchain and build R with that.  And that is what fink, MacPorts, ... 
do, as I understand it.  Simon rightly warns that they give you other 
things you do not want, but that's not stopping a simple solution.

There are two relevant things which I know of which are special to the 
Apple toolchain.

1) Support (or level of support) for Objective C(++).  That's not an 
issue for R nor for any of the packages: it is for R.app.  However, 
the latter is compiled separately and 'should' link to a libR.dylib 
compiled under a non-Apple toolchain.

2) The ability to make 'fat binaries' by things like

gcc -arch i386 -arch x86_64

and more generally to select the architecture in this way.  However, 
we hardly use fat binaries in R (only Rscript, AFAIR) and once ppc is 
no longer supported, the standard -m32 and -m64 flags will work with 
the standard GCC toolchain.

I would be staggered if the task of producing a suitable toolchain for 
Mac OS X was 50% of the work needed for Windows.  But of course 
someone would need to be prepared to do it, and I suspect that the 
volume of Mac users of R is less than 10% of that for Windows.