Skip to content

RGL

7 messages · Duncan Murdoch, David Winsemius, Guillaume Meurice +2 more

#
On 12-07-26 7:46 AM, Guillaume Meurice wrote:
I don't know the solution, but if you don't get one from someone else, 
you might have more luck on the R-sig-mac list.

Duncan Murdoch
#
On Jul 26, 2012, at 4:46 AM, Guillaume Meurice wrote:

            
The error messages in the"sources" install dialog suggests a problem  
with your system installation of freetype. I was running rgl v0.92.861  
on Leopard without problems. I just tried installing the current  
version offered to the GUI installer, v0.92.880, restarting and got an  
error on attempting to load while in version 2.14.2,

  After updating R to the current version I am able to install  
rgl_0.92.892 from binary using the GUI Package Installer and then  
load  and run code in either R64 or 32-bit R.

 >  sessionInfo()
R version 2.15.1 (2012-06-22)
Platform: x86_64-apple-darwin9.8.0/x86_64 (64-bit)

locale:
[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8

attached base packages:
[1] stats     grDevices utils     datasets  graphics  methods   base

other attached packages:
[1] rgl_0.92.892   lattice_0.20-6

loaded via a namespace (and not attached):
[1] grid_2.15.1  tools_2.15.1


You have a fairly full system. I wonder if you should restart and try  
with a few less packages?

And as Duncan suggested, you _should_ be posting on the R-SIG-Mac list.

--
David.
David Winsemius, MD
West Hartford, CT
#
On Jul 27, 2012, at 03:48 , David Winsemius wrote:

            
[snip]
Yes. The new CRAN binaries work for me too (and are in the non-X11 version if run from the R app). For source compiles, I think you need to follow the hint about libraries for dependencies at the bottom of http://cran.r-project.org/bin/macosx/.

I believe we have seen the R_decompress1 error before, though. If you can reproduce it, it might be worth digging deeper --- over on R-sig-Mac.
#
On 27/07/2012 09:14, peter dalgaard wrote:
It almost always indicates a corrupted lazyload database.  One way to 
corrupt it is to update the package whilst it is in use (which corrupts 
it for the running session, at least).
#
On Jul 27, 2012, at 11:05 , Prof Brian Ripley wrote:

            
Or, as I just found out, upgrading and then installing from a running copy of the previous version... (Yes, it is hot in .dk today, why do you ask?)

-pd