Re: [R-SIG-Mac] R.app Packages file to load: Cannot find library objects

2015-06-19 Thread Gregory Sawyer

 On Jun 19, 2015, at 1:10 PM, David Winsemius dwinsem...@comcast.net wrote:
 
 If you installed the frameworks version of R 3.2, then R should be looking 
 for the package library in 
 
   /Library/Frameworks/R.framework/Versions/3.2/Resources/
 
 How did you migrate you packages to 3.2. The usual method is to make copies 
 and move them to the 3.2 .../library/ directory and then execute:
 
   update.packages(checkBuilt-TRUE, # and I usually need to do this because I 
 have a lot of packages
   ask=FALSE)  # the default is TRUE
 
 What does this show?
 
   .libPaths()
 
 It should show at least this:
 
 1] /Library/Frameworks/R.framework/Versions/3.2/Resources/library
 
 ... but if you have a User/.../library then that will also appear
 
 On Jun 19, 2015, at 11:20 AM, Gregory Sawyer wrote:
 
 Hello,
 
 I�m having a problem with R 3.2 on the Mac under R.app, and the Internets 
 have failed to provide an answer, so I was wondering if there might be 
 someone here that can help me.
 
 Whenever I try to load a package I get the following error:
 
 library(dplyr)
 Error in dyn.load(file, DLLpath = DLLpath, ...) : 
 unable to load shared object 
 '/Library/Frameworks/R.framework/PackageLib/dplyr/libs/dplyr.so':
 dlopen(/Library/Frameworks/R.framework/PackageLib/dplyr/libs/dplyr.so, 6): 
 Library not loaded: 
 /Library/Frameworks/R.framework/Versions/3.1/Resources/lib/libR.dylib
 Referenced from: 
 /Library/Frameworks/R.framework/PackageLib/dplyr/libs/dplyr.so
 Reason: image not found
 Error: package or namespace load failed for �dplyr�
 
 (1)  The specific library referenced in the dlopen() function may differ � 
 here it is libR.dylib, but for markovchain it�s libgfortran.
 
 (2)  I�m running (just installed) R 3.2.1 World Famous Astronaut, but this 
 happened with 3.2.0 as well;
  Mac OS 10.10.3
  32 GB Core
 
 (3)  This only happens using R.app.  Everything works fine when I fire up R 
 in R-Studio or at the command line.
 
 (4)  I have noted that it seems to be trying to access the 3.1 Resources.  
 There are some 3.1 things out in /Library/Frameworks/R.framework, but all 
 the major directories, particularly those that are links, appear to be 
 pointing to 3.2.  I don�t know how to tell R.app that we�ve moved on in life 
 and need to be looking in the new neighborhood.
 
 
 Thanks,
 
 �Gregory
 
 Gregory D. Sawyer
 Sr. Data Architect (Business Intelligence)
 GreaterGood.com http://greatergood.com/ http://greatergood.com/ 
 http://greatergood.com/
 
 
 
 
 
 
  [[alternative HTML version deleted]]
 
 ___
 R-SIG-Mac mailing list
 R-SIG-Mac@r-project.org mailto:R-SIG-Mac@r-project.org
 https://stat.ethz.ch/mailman/listinfo/r-sig-mac 
 https://stat.ethz.ch/mailman/listinfo/r-sig-mac
 
 David Winsemius
 Alameda, CA, USA

Thank you, David, executing the update.packages() command seems to have cured 
it.

This was perplexing because it only failed in the R.app, and not in R Studio or 
the command line R � since I mainly use R Studio, I didn�t really notice the 
R.app behavior.  

�Gregory


[[alternative HTML version deleted]]

___
R-SIG-Mac mailing list
R-SIG-Mac@r-project.org
https://stat.ethz.ch/mailman/listinfo/r-sig-mac


[R-SIG-Mac] R.app Packages file to load: Cannot find library objects

2015-06-19 Thread Gregory Sawyer
Hello,

I’m having a problem with R 3.2 on the Mac under R.app, and the Internets have 
failed to provide an answer, so I was wondering if there might be someone here 
that can help me.

Whenever I try to load a package I get the following error:

 library(dplyr)
Error in dyn.load(file, DLLpath = DLLpath, ...) : 
  unable to load shared object 
'/Library/Frameworks/R.framework/PackageLib/dplyr/libs/dplyr.so':
  dlopen(/Library/Frameworks/R.framework/PackageLib/dplyr/libs/dplyr.so, 6): 
Library not loaded: 
/Library/Frameworks/R.framework/Versions/3.1/Resources/lib/libR.dylib
  Referenced from: 
/Library/Frameworks/R.framework/PackageLib/dplyr/libs/dplyr.so
  Reason: image not found
Error: package or namespace load failed for ‘dplyr’

(1) The specific library referenced in the dlopen() function may differ — 
here it is libR.dylib, but for markovchain it’s libgfortran.

(2) I’m running (just installed) R 3.2.1 World Famous Astronaut, but this 
happened with 3.2.0 as well;
Mac OS 10.10.3
32 GB Core

(3) This only happens using R.app.  Everything works fine when I fire up R 
in R-Studio or at the command line.

(4) I have noted that it seems to be trying to access the 3.1 Resources.  
There are some 3.1 things out in /Library/Frameworks/R.framework, but all the 
major directories, particularly those that are links, appear to be pointing to 
3.2.  I don’t know how to tell R.app that we’ve moved on in life and need to be 
looking in the new neighborhood.


Thanks,

—Gregory

Gregory D. Sawyer
Sr. Data Architect (Business Intelligence)
GreaterGood.com http://greatergood.com/






[[alternative HTML version deleted]]

___
R-SIG-Mac mailing list
R-SIG-Mac@r-project.org
https://stat.ethz.ch/mailman/listinfo/r-sig-mac


Re: [R-SIG-Mac] Yosemite and R

2014-10-17 Thread Gregory Sawyer

 On Oct 17, 2014, at 1:49 PM, Marc Schwartz marc_schwa...@me.com wrote:
 
 
 On Oct 17, 2014, at 2:17 PM, Spencer Mass ma...@newpaltz.edu wrote:
 
 Has anyone had issues installing/running  R3.1.1 2014-07-11, R.app 1.65 on 
 Yosemite?
 
 Thanks,
 
 - SM
 
 
 I upgraded (over Mavericks) to Yosemite last night. R was already installed 
 and I have had no issues at this point.
 
 I don't normally use R.app and use Emacs with ESS, however, R.app appears to 
 be running without issue with the limited use that I attempted.
 
 Regards,
 
 Marc Schwartz
 
 ___
 R-SIG-Mac mailing list
 R-SIG-Mac@r-project.org
 https://stat.ethz.ch/mailman/listinfo/r-sig-mac

I upgraded to 10.10 Yosemite this morning; R.app seems to be having some 
problems launching, but not all the time.  It's crashed twice on startup, but 
the second attempt (e.g. clicking 'Re-open' on the crash stack trace panel) 
seems to work.(running a very recent 27-inch iMac w/ 32Gib core, a 1tb 
drive, and a second 27-inch Apple LED cinema display, and I suspect it might be 
that second display that's causing the problems, but that's just speculation 
right now.)

___
R-SIG-Mac mailing list
R-SIG-Mac@r-project.org
https://stat.ethz.ch/mailman/listinfo/r-sig-mac