[R-SIG-Mac] [R] How to install rpy under mac os x?
Stefan Evert
stefan.evert at uos.de
Thu Sep 11 12:41:05 CEST 2008
[This should probably go to R-SIG-Mac, so I'm moving the thread there.]
> I'm tryin' to install Rpy under Mac Os X but I receive the following
> message:
I suppose you're talking about the alpha releases of RPy2 rather than
the stable 1.0 series?
I have no idea what's going wrong here, but for what it's worth, I
have no problems building both RPy-1.0.3 and RPy-2.0.0-a3 on my
system, which seems to have the same setup as you (Mac OS X 10.5.4
Intel, CRAN R 2.7.2, Apple-supplied Python 2.5.1).
> host46-209-dynamic:rpy usernone$ python setup.py install
> running install
> running build
> running build_py
> running build_ext
> building 'rpy2.rinterface.rinterface' extension
> gcc -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -
> fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd -
> fno-common -dynamic -DNDEBUG -g -O3 -DR_INTERFACE_PTRS=1 -
> DCSTACK_DEFNS=1 -DRIF_HAS_RSIGHAND=1 -I/Library/Frameworks/
> R.framework/
> Resources/include -Irpy/rinterface -I/Library/Frameworks/
> Python.framework/Versions/2.5/include/python2.5 -c rpy/rinterface/
> array.c -o build/temp.macosx-10.3-fat-2.5/rpy/rinterface/array.o
I'm getting quite a different gcc call at this point, though:
gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-
madd -fno-common -dynamic -DNDEBUG -g -Os -Wall -Wstrict-prototypes -
DMACOSX -I/usr/include/ffi -DENABLE_DTRACE -arch i386 -arch ppc -pipe -
DR_INTERFACE_PTRS=1 -DCSTACK_DEFNS=1 -DRIF_HAS_RSIGHAND=1 -I/Library/
Frameworks/R.framework/Resources/include -Irpy/rinterface -I/System/
Library/Frameworks/Python.framework/Versions/2.5/include/python2.5 -c
rpy/rinterface/array.c -o build/temp.macosx-10.5-i386-2.5/rpy/
rinterface/array.o
Actually, this part of your log
> -o build/temp.macosx-10.3-fat-2.5/rpy/rinterface/array.o
suggests that RPy (or Python) thinks it's compiling on OS X 10.3, and
it uses
> -isysroot /Developer/SDKs/MacOSX10.4u.sdk
instead of the proper OS X 10.5 SDK.
Perhaps something is wrong with your configuration (is you XCode up to
date?) or you're using a non-standard Python binary?
Best regards,
Stefan Evert
[ stefan.evert at uos.de | http://purl.org/stefan.evert ]
More information about the R-SIG-Mac
mailing list