Skip to content

installing R-2.1.0 from source on Fedora Core 3 with tclt k

4 messages · Liaw, Andy, Brian Ripley, Jonathan Baron +1 more

#
On my FC3 for x86_64 (Athlon64 3000+) at home, R-patched from today compiled
just fine, and tcltk works.  The version of tcl, tcl-devel, tk and tk-devel
are all 8.4.7-2.

Cheers,
Andy
http://www.murdoch-sutherland.com/Rtools/R_Tcl.zip

(even though it is supposedly for Windows), unzip it in the
R-2.0.0/ directory (where the tar file put itself), and also
install rpms for tcl-devel and tk-devel, which I did not have.
When I did both of these things, it worked.  Either one of them
alone (the ..devel rpms or the R_Tcl.zip) did not suffice.
(However, it isn't clear that a single trial experiment is
sufficient to determine what works.)

My own problem is solved for the moment.  But others may benefit
from this report, and it may be that the installation
documentation needs minor tweaking.  (Or it may be that I did
something else wrong, but right now I doubt that.)

Jon
1 day later
#
On Sun, 24 Apr 2005, Liaw, Andy wrote:

            
Indeed.  Since FC3 is the platform used by two (at least) of R-core and 
both have 64-bit machines, it would be surprising if there were a problem 
there.
You need the non-devel rpms as well, and that is what I think you are 
picking up from the R_Tcl.zip (which is Tcl pre-compiled for Windows).

  
    
#
I was able to compile R-2.0.0 successfully on another fc3
computer, theoretically identical to the first three.  I'm sorry
for starting this thread.

It does seem that I had a problem that resulted from having only
tk and tcl, but not tk-devel and tcl-devel.  Perhaps after I
installed these I forgot to log out and log in again, so they
weren't found.

When I did it successfully, I installed the devel versions first, 
then logged in as root and did everything as root.  (Initially I
had done only the very last step - make install - as root.)
Probably this doesn't matter either.

Jon
#
On Tue, 2005-04-26 at 09:05 -0400, Jonathan Baron wrote:
Logging in and out should not be needed. The header files (installed
from the 'devel' RPMS) are installed in standard locations on Linux
(ie. /usr/include) as are the libraries (ie. /usr/lib) and these are
usually picked up by the configure script.

There is really nothing in terms of "environment" variables for example,
that would need to get updated via a logout/login cycle. Unlike Windows,
which for example can require a full re-boot when certain components get
installed, about the only time Linux needs a re-boot is to utilize a new
kernel. Otherwise the majority of system updates are done "hot".

When building from source, I do it all as a regular user and as you
reference above, then 'su' to root for the installation.

Best regards,

Marc Schwartz