Skip to content

Rcmdr package

7 messages · İbrahim Mutlay, Peter Dalgaard, Dirk Eddelbuettel

Peter Dalgaard
#
?brahim Mutlay wrote:
That is not clear. I believe it normally would. Did you compile R 
yourself or did it come with Quantian? Did you perchance forget to 
install the tcl/tk libraries (including devel packages if you did the 
compile)?
Dirk Eddelbuettel
#
On 9 December 2006 at 16:02, ?brahim Mutlay wrote:
| Dear R users,
| 
| I want to install the Rcmdr package in a Quantian linux machine, but, when i
| tried that, following commands appeared:

Well, Quantian should already contain Rcmdr, albeit an older version given
that there hasn't been a Quantian release in a while.
 
| ** building package indices ...
| * DONE (Rcmdr)
| 
| The downloaded packages are in
|         /tmp/RtmpuOikyk/downloaded_packages
| > library("Rcmdr")
| Loading required package: tcltk
| Error in firstlib(which.lib.loc, package) :
|         Tcl/Tk support is not available on this system
| Error: package 'tcltk' could not be loaded
| > library("tcltk")
| Error in firstlib(which.lib.loc, package) :
|         Tcl/Tk support is not available on this system
| Error in library("tcltk") : .First.lib failed for 'tcltk'
| 
| I do not know why my OS does not support the Tcl/Tk.

Neitehr do I, and Quantian 'as shipped' obviously contains working R, tcltk,
Rcmdr and a number of other applications. 

Did you rebuild R and not build tcl/tk support with it?  What does this
command show on your box?  tcltk is indicated by the third element:

edd at basebud:~> echo "capabilities()" | R --no-save | tail -6
jpeg      png    tcltk      X11 http/ftp  sockets   libxml     fifo
    TRUE     TRUE     TRUE     TRUE     TRUE     TRUE     TRUE     TRUE
  cledit    iconv      NLS
   FALSE     TRUE     TRUE
Hth, Dirk
Dirk Eddelbuettel
#
On 9 December 2006 at 17:09, ?brahim Mutlay wrote:
| Dear Mr. Eddelbuettel,

[ Well if you want to be formal, Dr Eddelbuettel is more appropriate.  But
Dirk is easier on your keyboard ... ]

| in R, i wrote the command of capabilities(), and the result was such like:
| 
| > capabilities()
| Xlib: connection to ":0.0" refused by server
| Xlib: No protocol specified
| 
|     jpeg      png    tcltk      X11 http/ftp  sockets   libxml     fifo
|    FALSE    FALSE    FALSE    FALSE     TRUE     TRUE     TRUE     TRUE
|   cledit    iconv      NLS
|     TRUE     TRUE     TRUE
| 
| My R version is 2.4.0, so, the version was compiled by me but i do not know
| about building the Tcl/Tk support. In fact, i followed the directions in the
| "INSTALL" file. Now i can't remember problems, if exist, at the installation
| process.

So you chose to build your own R instead of using the package I maintain for
Debian, and which I install onto Quantian.  No problem so far --- but you
happened to build R without jpeg, png, tcltk, or x11. There is a clear
message that configure prints at the end of its run that you probably
overlooked.  Maybe you want to revisit the extensive documentation
in the various READMEs and in the 'R Administration' manual?

As Peter told you, you need to make sure that you have all the required
development packages.  On a Debian system such as Quantian, this is easily
achieved via 'apt-get build-dep r-base' which would install all potentially
missing build-dependencies for the r-base package.  Eg on a Ubuntu 'edgy'
system I have here, a 'simulated' run (ie not actually installing it) starts
at

root at joe:~ # apt-get -s build-dep r-base
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  bison gfortran gfortran-4.1 libgfortran1-dev libmpfr1 libreadline5-dev
  refblas3-dev tcl8.4-dev texi2html tk8.4-dev
0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded.

so the system can figure out itself what it needs. For comparison. on my
Debian box all pieces are present:

basebud:~# apt-get -s build-dep r-base
Reading package lists... Done
Building dependency tree... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded

Good luck,  Dirk
Dirk Eddelbuettel
#
On 9 December 2006 at 18:29, ?brahim Mutlay wrote:
| My intent in installing a newer R version is just an approach that "newer is
| better". So, i'm a "teenager" statistician and R user, thus, i can not
| discriminate a newer tar.gz package from stable debian packages. But you're
| right about that i should use R coming from Quantian or maintained for
| Debian.
| 
| I tried "apt-get...." command, so, i faced to the words:
| 
| root at quantian:/home/mutlay/r# apt-get -s build-dep r-base
| Reading package lists... Done
| Building dependency tree... Done
| W: Couldn't stat source package list http://ndiswrapper.sourceforge.net ./
| Packages (/var/lib/apt/lists/ndiswrapper.sourceforge.net_debian_._Packages)
| - stat (2 No such file or directory)
| W: Couldn't stat source package list http://kanotix.com ./ Packages
| (/var/lib/apt/lists/kanotix.com_files_debian_._Packages) - stat (2 No such
| file or directory)
| W: You may want to run apt-get update to correct these problems
| E: You must put some 'source' URIs in your sources.list

It's the package manager telling you that two entries are not responding. You
should comment them out.

If all that is too complicated for you then ... maybe you should just run
Quantian "as is" ?  

There is a reason why there are more than six gigabytes of *installed* and
*configured* software ready to run -- installation can be tricky and tedious.
Quantian already has R, it has Rcmdr, and it has thousands more packages.
Why not use Quantian as-is if you can't get the newer stuff installed?

Regards, Dirk