Sorry, one more: on OSX, I deleted my old 2.9.2 R.app, and installed the 64
bit version of 2.9.0. I then did an
"install.packages("car")" under my new
2.9.0. It seems to have worked, but alas, I still get an error that package
'car' was built under R version 2.9.2 . Where exactly does R under OSX
install its packages? (is it a bug that another car is loaded?)
PS: do I need to install the car packages under the 64-bit version, or will
it be seen by the 64 bit version if I do a 32-bit install? Or do I need to
do a double install? for safety, I did it under the command line version,
which I presume is still 32-bit, and the 64 bit GUI.
PPS: how do I learn which version of R is running?
regards, /iaw
--
Ivo Welch (ivo.welch@brown.edu, ivo.welch@gmail.com)
[[alternative HTML version deleted]]
iaw4 wrote:> > Sorry, one more: on OSX, I deleted my old 2.9.2 R.app, and installed the > 64 > bit version of 2.9.0. I then did an "install.packages("car")" under my > new > 2.9.0. It seems to have worked, but alas, I still get an error that > package > 'car' was built under R version 2.9.2 . Where exactly does R under OSX > install its packages? (is it a bug that another car is loaded?) >If you are using the standard install on OSX, then packages are kept in: /Library/Frameworks/R.framework/Resources/library If you installed the package from CRAN then I think the warning may be related to CRAN using the most recent version of R to build packages. i.e. you are running R 2.9.0, but the CRAN server was the actual builder of the package you are using and it was running R 2.9.2. iaw4 wrote:> > > PS: do I need to install the car packages under the 64-bit version, or > will > it be seen by the 64 bit version if I do a 32-bit install? Or do I need > to > do a double install? for safety, I did it under the command line version, > which I presume is still 32-bit, and the 64 bit GUI. > >If you installed a distribution that includes both i386 and x86_64 versions then R will be able to run in both modes, depending on the situation. Check the folder names in: /Library/Frameworks/R.framework/Resources/bin/exec To see which versions you have available. With the 64 bit GUI from: http://r.research.att.com You will be running the 64-bit R binaries whenever you start the GUI. For R on the command line, you can specify which version gets used by setting the environment variable R_ARCH to either i386 or x86_64 iaw4 wrote:> > > PPS: how do I learn which version of R is running? > >Try sessioninfo() Hope this helps! -Charlie ----- Charlie Sharpsteen Undergraduate Environmental Resources Engineering Humboldt State University -- View this message in context: http://www.nabble.com/Location-of-Packages--tp25438651p25438849.html Sent from the R help mailing list archive at Nabble.com.
>>>>> "iw" == ivo welch <ivo_welch at brown.edu> >>>>> on Mon, 14 Sep 2009 12:03:59 -0400 writes:iw> Sorry, one more: on OSX, I deleted my old 2.9.2 R.app, and installed the 64 iw> bit version of 2.9.0. I then did an "install.packages("car")" under my new iw> 2.9.0. It seems to have worked, but alas, I still get an error that package iw> 'car' was built under R version 2.9.2 . Where exactly does R under OSX iw> install its packages? (is it a bug that another car is loaded?) Don't know. But in R, you can always see (and also change if you want) in which libraries R is looking for packages, either by ll <- library() str(ll) ## or ll or -- more quickly but with less "adjoint" info -- by .libPaths() iw> PS: do I need to install the car packages under the 64-bit version, or will iw> it be seen by the 64 bit version if I do a 32-bit install? Or do I need to iw> do a double install? for safety, I did it under the command line version, iw> which I presume is still 32-bit, and the 64 bit GUI. iw> PPS: how do I learn which version of R is running? sessionInfo() iw> regards, /iaw Regards, Martin iw> -- iw> Ivo Welch (ivo.welch at brown.edu, ivo.welch at gmail.com) iw> [[alternative HTML version deleted]] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ hmm....
iaw4 wrote:> > > PS: do I need to install the car packages under the 64-bit version, or > will > it be seen by the 64 bit version if I do a 32-bit install? Or do I need > to > do a double install? for safety, I did it under the command line version, > which I presume is still 32-bit, and the 64 bit GUI. > >Ooops, there was one point I wanted to clarify related to this. The architecture of your machine only matters if the package contains code that needs to be compiled-- i.e. Fortran or C routines. When installing packages, R will automatically attempt build separate libraries with versions of these routines for every architecture listed in: /Library/Frameworks/R.framework/Resources/bin/exec So you shouldn't need to worry about "double installing" or "dual building"-- it should be taken care of for you. P.S I have had some problems building ppc64 binaries from source on OS X when installing packages. Since I am running an x86_64 machine, I have no need for these binaries, so I simply removed the ppc64 folder from /Library/Frameworks/R.framework/Resources/bin/exec to stop the builds. ----- Charlie Sharpsteen Undergraduate Environmental Resources Engineering Humboldt State University -- View this message in context: http://www.nabble.com/Location-of-Packages--tp25438651p25438910.html Sent from the R help mailing list archive at Nabble.com.
Hi, On Sep 14, 2009, at 12:03 PM, ivo welch wrote:> Sorry, one more: on OSX, I deleted my old 2.9.2 R.app, and installed > the 64 > bit version of 2.9.0. I then did an "install.packages("car")" under > my new > 2.9.0. It seems to have worked, but alas, I still get an error that > package > 'car' was built under R version 2.9.2 . Where exactly does R under > OSX > install its packages? (is it a bug that another car is loaded?)/Library/Frameworks/R.framework/Resources/library/ You'll see that the Resources folder is actually a symlink to the current version's Resources folder: $ ls -l /Library/Frameworks/R.framework/Resources /Library/Frameworks/R.framework/Resources -> Versions/Current/Resources And that the "Current" folder (in Versions/Current) is actually a symlink to the current version (answering your PPS question below). $ ls -l /Library/Frameworks/R.framework/Versions/Current /Library/Frameworks/R.framework/Versions/Current -> 2.10 (2.10 because I'm running R-devel)> PS: do I need to install the car packages under the 64-bit version, > or will > it be seen by the 64 bit version if I do a 32-bit install?If you are running R in 64 bit mode, you need a 64 bit install of the package (if it uses compiled code). Note that just because you downloaded a 64 bit version of R, you might not be running it in 64 bit mode by default.> for safety, I did it under the command line version, > which I presume is still 32-bit, and the 64 bit GUI.I don't understand what you're trying to say here. Assuming you have a 64 bit version of R, you can launch it in 64 bit mode from the terminal like so: $ R --arch x86_64 (That's on the http://r.research.att.com/ page, btw).> PPS: how do I learn which version of R is running?Along with chasing down the symlinks to the "Current" version of (as stated above), when you start R, it will tell you in the preamble before the prompt is up. If you want to know if the version of R that's currently running is 64 vs. 32 bit, look at the size of the pointer: R> .Machine$sizeof.pointer [1] 8 8 means 64 bit, 4 means 32 bit. -steve -- Steve Lianoglou Graduate Student: Computational Systems Biology | Memorial Sloan-Kettering Cancer Center | Weill Medical College of Cornell University Contact Info: http://cbio.mskcc.org/~lianos/contact