Hi Dirk,

> I would venture that you upgraded R and replaced a build using
> shared libraries with one containing static libraries --- thereby
> breaking r.

I did make R recently, 2.9.0, with shared library,
which is how I got little r to work at all.  There are
more than one R on the machine, however, and judging
from what you mention, my little r must be using "wrong"
R (the one without shared library).

I do have the PATH variable set correctly so that the big
brother R gets run is in fact the correct R (2.9.0).
Is there any way for little r to be assured to use the R
and not others?

Regards,

Tena Sakai
tsa...@gallo.ucsf.edu



-----Original Message-----
From: Dirk Eddelbuettel [mailto:e...@debian.org]
Sent: Mon 6/1/2009 5:29 PM
To: Tena Sakai
Cc: r-help@r-project.org
Subject: Re: [R] my little r is sick
 

Tena,

On 1 June 2009 at 17:02, Tena Sakai wrote:
| Suddenly, I find my little r is sick.
| 
| Given:
| 
|   #! /usr/bin/env r
| 
|   library (hwriter)
| 
|   unlink ('tmp.html')
| 
|   p = openPage ('tmp.html')
|   hwrite ("Hello World", p)
|   closePage (p)
| 
|   browseURL ('tmp.html')
| 
| It worked fine a few days ago, but now it says:
| 
|   r: error while loading shared libraries: libR.so: cannot open shared object 
file: No such file or directory
| 
| The big brother (R) has no problem.
| 
| Can somebody please tell me what's going on?

As stated in the documentation, littl r require R to be built as a shared
library. I would venture that you upgraded R and replaced a build using
shared libraries with one containing static libraries --- thereby breaking r.

You may need reverse that if you want to continue using r.

Dirk

-- 
Three out of two people have difficulties with fractions.


        [[alternative HTML version deleted]]

______________________________________________
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.

Reply via email to