I have. In fact this thread follows one started yesterday of having encountered linking problems when compiling RGtk2, to which Simon suggested to use the Tiger binaries (I had not clarified that I was using the Leopard GUI). I also echo my gratitude to Simon for both his efforts with R for the Mac community and his availability to bring light to the clueless like me!
To summarise: 1. If you are using the Tiger binaries, life is nice and there are lots of binary packages that go with it. 2. If you are using the Leopard binaries life is not as rosy and attempting to piggy-ride on the Tiger package binaries is not recommended by Simon. 3. If you are using the Leopard binaries and feel courageous (or simply need a package that is not available as binary), then you can try to compile the packages from source. Note that this is most of the time OK (noting the trial and error approach highlighted by David below), but when linking to external libraries (such as the GTK+ or the Tcltk Frameworks) then care is needed in providing R GUI with the paths to the elements it needs (see thread on "GTK+ libraries can't be found"). A similar issue occurs when I try to compile "gWidgetstcltk", where 4. If you are even more courageous, then compiling all from the sources provided kindly by Simon is possibly the best approach, as then the environment against which R is compiled exactly matches that against which the packages are compiled. For an example of what I mean could go wrong, try loading the standard tcltk package. Best regards, Ivan On 6 Jan 2009, at 14:20, David Winsemius wrote: > > On Jan 5, 2009, at 8:09 PM, Simon Urbanek wrote: > >> >> On Jan 5, 2009, at 7:09 PM, Ivan Alves wrote: >> >>> Dear Simon, >>> >>> Many thanks for clarifying the confusion. Reading the MAC OS FAQ >>> I understand that I can _in principle_ use the Tiger binaries with >>> the leopard build. Is there a way to configure the default package >>> type of the leopard build from mac.binary.leopard to mac.binary so >>> that it looks in the universal folder? >>> >> >> You can simply set options(pkgType="mac.binary"). You can do that >> in your startup files if you desire. However, it could be (I'd have >> to check the sources) that the GUI still overrides this setting so >> you may want to use install.packages yourself. Again, I do NOT >> recommend this, since it defeats the purpose of the Leopard build >> (you won't have 64-bit binaries!), but you're free to do what you >> please ;). >> >> Cheers, >> Simon > > I am wondering if Ivan has yet tried building the missing packages > from sources using the R-GUI Package Installer. I was holding off on > using the 64-bit GUI until I discovered how wonderfully simple you > had designed that process. Sometimes the dependencies are not > properly listed in the packages, but the error messages are clear > (and highlighted in red) and installing the missing packages often > solves the problems. I am assuming the the reasons for some of the > binaries not automatically being created is the missing dependency > information, since they usually compile without error when that is > corrected. > > A thousand thanks, Simon. > > -- > David Winsemius >> >> >> >>> >>> Ivan >>> On 6 Jan 2009, at 00:03, Simon Urbanek wrote: >>> >>>> You are using the Leopard build of R - that one uses >>>> http://cran.us.r-project.org/bin/macosx/leopard/contrib/2.8/ >>>> instead (which has fewer package than the Tiger build since only >>>> those supporting 64-bit are represented). See also R for Mac FAQ. >>>> >>>> http://cran.us.r-project.org/bin/macosx/universal/contrib/2.8/ >>>> is for the CRAN (default) Tiger build. >>>> >>>> Cheers, >>>> Simon >>>> >>>> >>>> On Jan 5, 2009, at 17:42 , Ivan Alves wrote: >>>> >>>>> Dear all, >>>>> >>>>> For some reason, the binaries listed by R GUI's "Package >>>>> Installer" (using http://cran.us.r-project.org as mirror, as set >>>>> up in >>>>> the default CRAN mirror in the Startup preference Panel) is not >>>>> the >>>>> same as the listing of binaries available in >>>>> http://cran.us.r-project.org/bin/macosx/universal/contrib/2.8/ >>>>> . Notably the RGtk2 binary is not available in the listing >>>>> provided by >>>>> the Package Installer, but >>>>> RGtk2_2.12.7.tgz 24-Oct-2008 15:01 6.7M >>>>> is. Any suggestions of what is going wrong and how I could fix >>>>> this >>>>> (short of downloading the binary manually and installing it >>>>> locally or >>>>> installing it from source)? Many thanks in advance. >>>>> Best regards, >>>>> Ivan >>>>> The sessioInfo() for my R session gives the following: >>>>> >>>>> R version 2.8.1 Patched (2009-01-04 r47472) >>>>> i386-apple-darwin9.5.0 >>>>> >>>>> locale: >>>>> en_GB.UTF-8/en_GB.UTF-8/C/C/en_GB.UTF-8/en_GB.UTF-8 >>>>> >>>>> attached base packages: >>>>> [1] stats graphics grDevices utils datasets methods >>>>> base >>>>> >>>>> other attached packages: >>>>> [1] gWidgets_0.0-32 rattle_2.4.0 plyr_0.1.3 >>>>> >>>>> loaded via a namespace (and not attached): >>>>> [1] tools_2.8.1 >>>>> >>>>> >>>>> [[alternative HTML version deleted]] >>>>> >>>>> _______________________________________________ >>>>> 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 > [[alternative HTML version deleted]] _______________________________________________ R-SIG-Mac mailing list [email protected] https://stat.ethz.ch/mailman/listinfo/r-sig-mac
