similar to: BLAS and the Sun Performance Library

Hi, I am trying to compile R 1.9.1 and 2.0.0 on Solaris 2.8 with Sun Studio Fortran 95 compiler but I have obtained some errors which I enclose. I have compiled R with g77 GNU compiler and it was OK. Does anyone know if R 2.0.0 has been successfully built on Solaris 2.8 with Sun Studio Fortran 95 compiler? or at least, How could I achieve this? The R installation manual does not have any

Full_Name: Bob Bownes Version: 2.9.2 OS: Solaris 10 Submission from: (NULL) (164.55.254.106) The sed lines in src/unix/Makefile confuse the grep distributed with Solaris that gets configured by ./configure. Switching from a separator of ':' to a separator of ',' fixes the problem. 76,77c76,77 < @$(SED) -e "s:@rhome:$(rhome):" -e

64-bit R-2.12.0 was installed on Sun SPARC Solaris 10. Compiler used is solstudio12.2. Attached is the configure script. I then tried to install a recommended package called Matrix. The compilation failed with the following messages, ....... CC -library=stlport4 -G -L/opt/csw/lib/sparcv9 -L/opt/solstudio12.2/prod/lib/v9 -o Matrix.so CHMfactor.o Csparse.o TMatrix_as.o Tsparse.o init.o Mutils.o

Hmnnn... This is the third version of R I have installed and I am stumped on this one. There is some unresolved external I cannot find... /opt/SUNWspro/bin/cc -v -o R.bin CConverters.o Rdynload.o RNG.o apply.o arithmetic.o array.o attrib.o bind.o builtin.o character.o coerce.o colors.o complex.o connections.o context.o cov.o cum.o dcf.o datetime.o debug.o devPS.o devPicTeX.o deparse.o

System details: -------------- Sun Blade 1000, Solaris 8, Sun ONE Compiler Suite (rebranded Forte 7), R versions 1.6.0 and 1.6.2 - suspect others are affected, too Problem description: ------------------- Using the recommended env var setting from p.15 of the Admin Guide, the configure script fails the sgemm sunperf test, even though the sunperf libraries are available Not linking with

Hello R Help, I am attempting to install/build a 64-bit version of R to hopefully resolve some memory.limit problems for a user who is running a simulation. The 'configure' runs fine and the compilation (make) runs fine until the very last part (see below). I have libiconv in /usr/local/lib (no sure why I am getting the referencing error). The config.site file is attached. ANY HELP YOU

Doh! turns out I was using a newer feature of S-PLUS that is not supported in R, or at least was generating the parse error. replace all a = b with a <- b (except in arguments, naturally ...) Sorry to bother anyone ... smooth sailing ahead. > Date: Mon, 4 Jun 2001 10:03:56 -0600 (MDT) > From: Tim Hoar <thoar at cgd.ucar.edu> > Reply-To: Tim Hoar <thoar at ucar.edu>

I hope this is enough information to determine the problem. Thanks in advance for any help. Configure goes ok (I think) ./configure --prefix=$HOME --without-iconv R is now configured for sparc-sun-solaris2.9 Source directory: . Installation directory: /home/dpowers C compiler: gcc -g -O2 Fortran 77 compiler: f95 -g C++ compiler: g++

Hi All, This question was brought up some time ago but I never saw a reply so I'd like to bring it up again. When using ROracle package (version 0.5-5), I am unable to run any queries that are greater than 4000 characters in length. If I do, I get the following message: Error in oraPrepareStatement(con, statement, bind=NULL) : RS-DBI driver: (too long a statement -- it must has less than

Dear Developers, motivated by the new Sun Studio checks I compiled R-devel and several of our packages with Sun Studio 12 on Fedora x64. Everything worked fine and R-devel runs, with the exception of package Matrix where compilation crashes with the following message. The error occurs during building of the recommended packages and also if Matrix is compiled separately: [...] CC -G -lCstd

To all. I need your help. The big question is: How do I make an R library with Fortran 95 files? You may assume that I am a pretty decent programmer in both R and Fortran. I lay out a scenario and need your help! I know how to make an ordinary R package and have dabbled with R + Fortran 95 *.dll linking. I do not have a great handle on the whole Makevars file and whatever else I might need

Hello, I tried to compile v2.3.1 on Solaris x86 with SUN Pro compilers. I had an error while stats libarary was being compiled and I notice that "-xtarget=generic64" was not passed to f95 while cc used it. Could you tell me how to fix this problem? f95 -PIC -O -I/mounts/devel/SUNWspro/prod/include -c sgram.f -o sgram.o f95 -PIC -O -I/mounts/devel/SUNWspro/prod/include -c

On 30 Aug 2006, at 23:04, Chris Lattner wrote: > On Wed, 30 Aug 2006, Kenneth Hoste wrote: >>> I use NAG with llvm-gcc4. What sort of errors do you get? Did >>> you configure llvm-test with the appropriate flags to find it? >> Yes, I did. llvm-test is configured as follows: (in /work/LLVM/ >> 1.8/ llvm/project/llvm-test): >> ./configure

On Thu, 31 Aug 2006, Kenneth Hoste wrote: >> $ grep F95 .../projects/llvm-test/Makefile.config > > -bash-3.00$ grep F95 projects/llvm-test/Makefile.config > # F95: Enable LLVM to run Fortran benchmarks without a Fortran front-end > USE_F95=1 > F95_DIR := > F95 := /work/NAG_f95/bin/f95 > F95_INC := /work/NAG_f95/lib > F95_LIB := /work/NAG_f95/lib > > Looks

R Help List: Just curious if anyone has successfully built R on a SPARC platform running Sun Solaris 10 using the latest Sun Studio 12 set of compilers. If so, I would be interested in the compile flags that you used. I have tried several different builds of version 2.5.1, 2.6.0, and 2.6.1 using various different compile flags and I am able to compile and check, but for whatever reason, the

On 01 Sep 2006, at 10:05, Kenneth Hoste wrote: > >> >>> Also, it is possible to tell make only to compile benchmark X? How >>> can I >>> enforce this? >> >> Go into the directory for that benchmark, then run 'make' or >> whatever. > I tried tom compile each of the SPEC CPU2000 benchmarks using the make command is each respective

On 25 Nov 2006, at 09:02, Reid Spencer wrote: > Anyone know what to do about this: > > make[4]: Leaving directory `/proj/llvm/llvm-test-1/External/SPEC/ > CFP2000/173.applu' > make[4]: Entering directory `/proj/llvm/llvm-test-1/External/SPEC/ > CFP2000/178.galgel' > /usr/bin/f95 -w -S -O2 /opt/spec/CPU2000v1.3.1/benchspec// > CFP2000/178.galgel/src/modules.f90

On Oct 30, 2008, at 11:02 PM, Chris Lattner wrote: > On Oct 30, 2008, at 5:23 PM, Jack Howarth wrote: >> ps We do have one oddity left in llvm-gfortran from current llvm >> svn. I find everytime I compile something with llvm-gfortran that >> I get a series of warning messages... >> >> f951: warning: command line option "-Wformat" is valid for C/C++/

Hi all, I'm preparing a package which uses .Fortran to interface a Fortran 95 function. This F95 function simply receives the name of a file from R, opens this file and forwards its content to a F95 module, which, in turn, makes the real computation. The F95 module is a pre-existing one and I'm trying to use it in its actual state. Thus, data transfer between R and this F95 module is

Hi Kenneth, On Sat, 2006-11-25 at 10:12 +0100, Kenneth Hoste wrote: > > > > ? > > > > This man page: > > http://www.die.net/doc/linux/man/man1/gfortran.1.html > > > > says there's no such option as -kind > > > > Do I need some special version of f95 to run the SPEC2K tests? > > If I'm correct, f95 has nothing to do with GCC. As