I can no longer postpone upgrading my Macs from OS X 10.6.8 to 10.7. I am very dependent on R, Eclipse, and the Eclipse plugins StatET for R development and MercurialEclipse for support for distributed versioning repositories. Are there any "gotchas" to which I should pay special attention? I am not running the latest versions of these programs, but of course would upgrade to the "latest/safest" versions after upgrading the OS. Here are the versions:
R:
Version: R-2.12-branch-leopard 2011-03-18
Eclipse:
Version: 1.3.2.20110301-1807 (Helios)
Build id: 20110301-1815
StatET:
Version: 1.3.2.20110301-1807 (Helios)
Build id: 20110301-1815
StatET:
Version: 0.10.0.b201106190930E36sw
MercurialEclipse:
Version: 1.8.2.v201107291920 mercurialeclipse.feature.group
I am particularly concerned about two things:
1. Compiling R packages from source. I find myself building both 32- and 64-bit versions, simply because scripts that don't need a lot of memory run faster in 32-bit mode. Sometime near the end of 2010 Apple removed the Java 1.5.0 SDK and all its headers, so thereafter I have had to execute
JAVA_CPPFLAGS=-I/Developer/SDKs/MacOSX10.6.sdk/System/Library/Frameworks/JavaVM.framework/Headers
export JAVA_CPPFLAGS
before
R --arch=i386 CMD INSTALL ...
R --arch=x86_64 CMD INSTALL --libs-only ...
2. Incompatibilities between versions of Eclipse, StatET and R. What is the "latest/safest" version of all three such that they are all compatible with each other?
I will also post this to the StatET mail list.
Thanks for any help/suggestions that might avoid some weeping and gnashing of teeth on part.
Richard
Richard R. Liu
[email protected]
_______________________________________________ R-SIG-Mac mailing list [email protected] https://stat.ethz.ch/mailman/listinfo/r-sig-mac
