similar to: R-0.99 installation on UNIX

Displaying 20 results from an estimated 800 matches similar to: "R-0.99 installation on UNIX"

2000 Jun 19
1
Trying to compile R on Unix
I have been trying to compile R. I downloaded R-1.0.1.tgz(I think; the original tar file was untarred) and unpacked it with gzip. Now all the R files are in a directory named R-1.0.1. The source files (.c) are in R-1.0.1/src. There are files in R-1.0.1 named 'Makefile.in', 'Makeconf.in', and 'Makeconf'. I followed the instructions in INSTALL by typing
1999 Sep 02
1
unresolved symbols in growth and repeated libraries
I am having trouble using Jim Lindsey's libraries because of unresolved symbols. I am currently using R 0.65.0, but had this problem in earlier releases as well. I have a RedHat 6.0 Linux on i386 and use egcs (upgraded to that distributed with rawhide, after first failures with the libraries): egcs-g77-1.1.2-19 egcs-1.1.2-19 Installation of the libraries works but on loading >
2001 Jul 06
4
How to build R-1.3.0 under HP-UX 11.00
Hello, I am new in R and I am delighted with it, so I am trying to bulid R-1.3.0 from sources under HP-UX 11.00 using f2c and X11 support. Configuration phase is OK but using make I have errors: gcc -Wl,-E -o R.bin CConverters.o Rdynload.o RNG.o apply.o arithmetic.o array.o attrib.o bind.o builtin.o charac ter.o coerce.o colors.o complex.o connections.o context.o cov.o cum.o dcf.o
2001 Jul 06
4
How to build R-1.3.0 under HP-UX 11.00
Hello, I am new in R and I am delighted with it, so I am trying to bulid R-1.3.0 from sources under HP-UX 11.00 using f2c and X11 support. Configuration phase is OK but using make I have errors: gcc -Wl,-E -o R.bin CConverters.o Rdynload.o RNG.o apply.o arithmetic.o array.o attrib.o bind.o builtin.o charac ter.o coerce.o colors.o complex.o connections.o context.o cov.o cum.o dcf.o
2001 Jul 09
0
ODP: Re: How to build R-1.3.0 under HP-UX 11.00
Thank you for advice. I my case RPC nedd to be linked with libnsl, so I used "-lnsl" option to link it, but i have still problem: /usr/bin/ld: Unsatisfied symbols: i_len (code) d_sign (code) collect2: ld returned 1 exit status Can you suggest something? Kris
1999 Nov 13
0
patches for alpha
Recently I reviewed my RPM spec files for DU 4.0, and noticed that I forgot to post some problems + patches: 1. ./configure fails to choose a PIC flag, I simply removed the AC_MSG_ERROR and it works. There is actually no PIC flag for DEC cc (with DU 4.0E) --- ./configure.in.alpha-patch Mon Aug 23 06:36:28 1999 +++ ./configure.in Sun Sep 12 17:38:27 1999 @@ -541,7 +541,9 @@
1999 Jul 07
1
Almost succesfull build on AIX
Hi, Kurt Hornik and myself have an almost successful build of R on AIX including dynamic loading of libraries ... which fails make check :-( Anyway, as we have no AIX experience at all, maybe somebody else knows what's going on. Here's the problem: > 1/0 [1]INF > is.finite(1/0) [1] TRUE R was built using the flags included below, gcc version is 2.7.2. Does anybody with
2008 Jul 10
4
[LLVMdev] Including svn version number in --version output
It is very useful to have svn version number encoded in llvm-gcc's -- version output. Here is one approach. Anyone has a better patch ? - Devang Index: Makefile.in =================================================================== --- Makefile.in (revision 53385) +++ Makefile.in (working copy) @@ -802,6 +802,9 @@ DEVPHASE_s := "\"$(if $(DEVPHASE_c),
2008 Jul 10
0
[LLVMdev] Including svn version number in --version output
Why not set the VERSUFFIX to be " (Based on Apple Inc. build 5555) (LLVM rXXXX)" Where you set the revision number? We currently use LLVM_VERSION_INFO to set this sort of information and to me it makes more sense to have the svn rev number there instead of just saying LLVM build like it does now. -Tanya On Wed, 9 Jul 2008, Devang Patel wrote: > It is very useful to have svn
2004 Sep 08
1
Problems loading Lapack library
I have just installed R 1.9.1 on an old Sun Sparc with the following specs: version Machine hardware: sun4u OS version: 5.6 Processor type: sparc Hardware: SUNW,Ultra-4 The following components are installed on your system: Sun Visual WorkShop C++ 3.0 Sun WorkShop Compiler C 4.2 Sun WorkShop Compiler C++ 4.2 Sun WorkShop Tools.h++ 7.0
1998 Oct 28
1
Request for help with compiling R on a DEC Alpha
I am currently attempting to install R (v0.62.3) on our DEC Alpha computer, and have solved one problem but now am having another: When issuing the 'make' (after ./configure), I get the error shown at the end of this output: ============================================================================ ======= cd main; make make[3]: Entering directory `/usr/local/src/R-0.62.3/src/main'
1998 Apr 17
1
development mda package
NEW: CRAN/src/contrib/devel/mda_0.1-1.tar.gz I have made a first shot at porting the Hastie & Tibshirani mda package t= o R ... this is almost not tested at all ... but it works for the iris data and what else could a statistician be possibly interested in anyway = :-) All BRUTO stuff is missing because there are some unresolved symbols: R.binary: can't resolve symbol
2004 Nov 02
0
how to call function in ../src/main
Hi, This is Kotien Wu from NIH/NCI. We want to use R function for our web: http://cgap.nci.nih.gov It works for functions in R/R-1.9.1/src/nmath/standalone very well. We have function GetPvalueForT.c which has #define MATHLIB_STANDALONE 1 #include <Rmath.h> double GetPvalueForT ( double t, double deg ) { return 2 * pt(t, deg, 0, 0); } We create GetPvalueForT.i, which has /* File :
2008 Jul 10
4
[LLVMdev] Including svn version number in --version output
On Jul 9, 2008, at 6:13 PM, Tanya M. Lattner wrote: > > Why not set the VERSUFFIX to be " (Based on Apple Inc. build 5555) > (LLVM > rXXXX)" > > Where you set the revision number? I do not want to set the revision number in a source file every time I do 'svn update' :) > We currently use LLVM_VERSION_INFO to set this sort of information > and to
2009 Jul 23
1
problem building R 2.9.1 from source on RHEL 4 (x86_64)
I am building from source on RHEL 4 and have run into a problem while running "make check": running code in 'lapack.R' ...make[3]: *** [lapack.Rout] Error 1 make[3]: Leaving directory `/opt/R/R-2.9.1/tests' make[2]: *** [test-Specific] Error 2 make[2]: Leaving directory `/opt/R/R-2.9.1/tests' make[1]: *** [test-all-basics] Error 1 make[1]: Leaving
2008 Jul 10
0
[LLVMdev] Including svn version number in --version output
On Jul 9, 2008, at 6:13 PM, Devang Patel wrote: > > On Jul 9, 2008, at 6:13 PM, Tanya M. Lattner wrote: > >> >> Why not set the VERSUFFIX to be " (Based on Apple Inc. build 5555) >> (LLVM >> rXXXX)" >> >> Where you set the revision number? > > I do not want to set the revision number in a source file every time I > do 'svn
2001 Jan 25
1
problems compiling R under digital unix 4.0d (PR#826)
Dear Sirs, I am trying to compile R v1.2.1 under Digital Unix 4.0D. The configure-script runs without any problems but during 'make' I receive the following error-message: [......] g77 -mieee -g -O2 -c dtrco.f -o dtrco.o g77 -mieee -g -O2 -c dtrsl.f -o dtrsl.o g77 -mieee -g -O2 -c eigen.f -o eigen.o g77 -mieee -g -O2 -c lminfl.f -o lminfl.o ar cr libappl.a Rsock.o approx.o bakslv.o
2006 Feb 07
0
[R] R compile on AIX 5.2
Professor Ripley, Following your advice, I am now using an updated version of gcc (4.0.2 to be exact) as well as a true fortran compiler (XL Fortran Compiler v10.1.0.0 from IBM). I am still experiencing difficulty in running "make" after a successful "configure". Any additional insight you could provide would be greatly appreciated. Output of make is as follows: Running
2005 Mar 29
1
final stages of installing R - please help?
Hello, This morning I downloaded, unzipped, and compiled the latest version of R for unix, in my HOME/APPLICATIONS directory. My current unix machine is a sparc-sun-solaris2.9, running SunOS 5.9. Here are the last few lines of the output following ./configure: R is now configured for sparc-sun-solaris2.9 Source directory: . Installation directory: /usr/local C compiler:
2017 Feb 09
3
Ancient C /Fortran code linpack error
In my package 'glmmML' I'm using old C code and linpack in the optimizing procedure. Specifically, one part of the code looks like this: F77_CALL(dpoco)(*hessian, &bdim, &bdim, &rcond, work, info); if (*info == 0){ F77_CALL(dpodi)(*hessian, &bdim, &bdim, det, &job); ........ This usually works OK, but with an ill-conditioned data