These messages are generated by the R shared library as it attempts
to load the fundimental R packages it needs. This usually means
that your installation of R is lacking properly installed versions of
these packages. Does R start up and run properly when run directly?
-G
On Nov 2, 200
I don't get any error messages when I start up R by itself. And methods and
grDevices are both listed when I do the library() command. I don't actually
use R independently of rpy, so I'm not sure of how to test that they are
working correctly other than that. Is there something I can run to test
What do you get when you type
R RHOME
on the command line?
-G
On Nov 5, 2007, at 11:01AM , Andrew Jones wrote:
I don't get any error messages when I start up R by itself. And
methods and grDevices are both listed when I do the library()
command. I don't actually use R independe
Typing R RHOME gave me
/usr/local/lib/R
which is the correct installation directory. Thanks a lot for your time
helping me out by the way,
Andrew
On 11/5/07, Gregory Warnes <[EMAIL PROTECTED]> wrote:
>
>
> What do you get when you type
>
> R RHOME
>
> on the command line?
>
> -G
>
> On Nov
On 5 November 2007 at 18:40, Toby Dylan Hocking wrote:
| I am trying to compile RPy SVN release 361 on Ubuntu dapper using gcc
| v.4.0.3. I have an identical software setup (I think) on a different
| machine, so I'm really confused as to why it I can get it to compile on
| the other machine but
