On 19/10/2012 8:51 AM, Alexander Shenkin wrote:
Thanks Duncan. Here's what I come up with. Anything obviously missing? I'd think there'd be more incompatibilities than just these few...
If you are on Windows, packages need to pass tests on both 32 and 64 bits to make it onto CRAN. So it's not really such a big surprise after all...
But I would check those lists against the packages you already have installed, in case those are not on CRAN.
Duncan Murdoch
In 32-bit: > pkgs32 = available.packages(type="win.binary") In 64-bit: > pkgs64 = available.packages(type="win.binary") > pkgnames32 = pkgs32[,"Package"] > pkgnames64 = pkgs64[,"Package"] > as.character(pkgnames32[which(is.na(match(pkgnames32, pkgnames64)))]) [1] "RSVGTipsDevice" "RSvgDevice" "eco" "rcqp" "sparsenet" "hdf5" On 10/19/2012 8:22 AM, Duncan Murdoch wrote: > On 19/10/2012 8:10 AM, Alexander Shenkin wrote: >> Hi folks, >> >> Despite the pain of migrating to 64-bit R (I have to install 64-bit >> Office also due to RODBC), I'm considering making the leap due to >> memory issues. Is there any place that lists packages that are 64-bit >> incompatible? Or, will I just have to march through all my packages >> and check them one-by-one on CRAN? > > An approximation to that is to call > available.packages(type="win.binary") on both versions, and compare the > lists. Packages may fail to appear for reasons other than > incompatibility, but incompatible packages won't be available in binary > versions. > > Duncan Murdoch
______________________________________________ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
