similar to: Build Portland Group Compiler

Hi, Can anyone advise me on how to compile R with Portland Group compiler on a Opeteron machine with Red Hat Enterprise Linux WS release 4 installed? I've edit config.site file to pick portland group compilers instead of gcc. Here is the list of modified flags: CC=/usr/pgi/linux86-64/6.0/bin/pgcc CFLAGS='-g -O2' CPPFLAGS='-I/usr/pgi/linux86-64/6.0/include

Hi All, While attempting to build R-patched using the Portland Group compiler suite on our dual Opteron 250 box running Scyld 29cz5 (based on RH, kernel 2.4.29), I get: make[5]: Leaving directory `/home/andy/Rbuild/R221-pgi/src/library/tools/src' make[5]: Entering directory `/home/andy/Rbuild/R221-pgi/src/library/tools/src' pgcc -I../../../../include -I/include -I/include/CC -fpic

Dear R-devel, [I'm not sure if this is appropriate for R-devel. If not, I'm more than happy to move it to R-help.] As those of you who saw my post on R-help know, I've been trying to build R-patched on a dual Opteron box running Scyld Beowulf, using the PGI 6.1 compilers. The build went fine, but I couldn't get it to pass make check-all. Jennifer Lai, who reported success with

I am working on a SLES 10 cluster with R available on it. To better use my resources, I want to use Rmpi, but I am having a difficult time installing it. I have set the $R_LIBS variable correctly. The MPI libraries are available through the PGI compiler, but this R instance was compiled with GCC. The Rmpi package can be compiled and installed with %R CMD INSTALL Rmpi_0.5-5.tar.gz

I am trying to compile R-devel (R-devel_2006-05-17.tar.gz) on Red Hat Enterprise Linux AS release 3 (Taroon Update 7) using the Portland Group compiler 6.0. (I have not yet successful compiled R on this configuration, so I don't know if this is a new problem.) I get an error pgcc -L/usr/local/pgi/linux86-64/6.0/libso -L/usr/lib64 -o dftables dftables.o ../dftables chartables.h

Hi, I followed this message, https://stat.ethz.ch/pipermail/r-devel/2004-February/028942.html, to compile ATLAS with gcc and g77 on AMD Opteron. I then followed the instructions on this message, https://stat.ethz.ch/pipermail/r-devel/2004-February/028966.html, to convert static libraries to dynamic libraries. However, when I tried to configure R-devel, I got the following error

Dear R-users, Has any one compiled R-1.9.1 successfully with Portland pgcc pgCC and pgf77? I can not configurate it with ./configure since it told me checking for Fortran name-mangling scheme... configure: error: cannot compile a simple Fortran program Can any one give me some advice. Thank you. My platform: Linux-2.4.26, pentium4, portland compiler 5.1

Full_Name: Mike Pacey Version: 2.6.0 OS: SuSe Linux 9.3 x86_64 Submission from: (NULL) (194.80.32.10) A "vanilla" version of R configures and compiles without a problem on my system. Switching to using the PGI compiler configures correctly (see the values at the bottom fo thismessage), but compilation aborts with: pgcc -I../../src/extra/zlib -I../../src/extra/bzip2

I am trying to compile R-2.3.0 (both first release and patched 2006-05-10) on Red Hat Enterprise Linux AS release 3 (Taroon Update 7) using the Portland Group compiler version 6.1 and the notes from Jennifer Lai on p33 of "R Installation and Administration" version 2.3.0 (2006-04-24). I have not used this compiler before, so it is possible things are messed up more than usual, even

Hi, Has anyone had any luck in using portland group compiler to build R(-devel) with AMD's pgi compiled ACML library? I've downloaded the packages and set LD_LIBRARY_PATH, and run configuration script as follow: % ./configure --prefix=/usr/local/R.pgcc --with-blas='-lacml' However, it failed to pick up double complex BLAS, checking for sgemm_ in -lacml... yes checking

Hi, we have installed R-2.8.1 using the current pgi compiler (8.0.2) for AMD64 on a SLES9 system. When I try to install "Matrix" everything is fine until the last step. make[1]: Leaving directory `/tmp/R.INSTALL.TW3399/Matrix/src/AMD' pgCC -L/usr/lib64 -L/usr/X11R6/lib64 -pgf90libs -o Matrix.so CHMfactor.o Csparse.o TMatrix_as.o Tsparse.o init.o Mutils.o chm_common.o

This may be a tad O.T., but I have to ask somebody. In compiling WRF model, everything seems to build but at runtime, I get this error message: real.exe: /usr/pgi/linux86-64/6.0/lib/libpthread.so.0: version `GLIBC_2.3.3' not found (required by /lib64/tls/librt.so.1) There appears to be something missing from the library, but not being smart enough to know what each one provides, nor know

Hi all, I'm using my own front-end that generates LLVM debug info metadata. I was using LLVM 2.9 debug version and I'm moving to LLVM 3.2 debug version of metadata. On my example I got llc 3.2 to fail on following assertion: llc: /work1/tools/llvm/3.2/sources/lib/CodeGen/AsmPrinter/DwarfDebug.cpp:1471: void llvm::DwarfDebug::endFunction(const llvm::MachineFunction*): Assertion `TheCU

For those interested: I compiled R-1.9.0beta_2004-04-02 with pgf77/gcc/g++ and g77/gcc/g++, both _without_ fast BLAS. Both passed make check-all. Simple crossprod(m) for fairly large `m' shows that the version compiled with pgf77 is about 15% faster: [andy@leo:scratch]% echo "set.seed(1); m <- matrix(runif(5e7), 1e4); gc(); system.time(crossprod(m))" | R-1.9.0-PGI/bin/R

> From: Prof Brian Ripley [mailto:ripley@stats.ox.ac.uk] > > On Fri, 2 Apr 2004, Liaw, Andy wrote: > > > Dear R-devel, > > > > I'm trying to compile R-1.9.0beta (2004-03-31) with the PGI > compilers > > (15-day free evaluation: after the 15 days the binaries > will stop working). > > I'm running into some problems, that I hope some can

Hello! I am updating to the R-devel version as of 2/28 and recompiling with OpenBLAS. I got that to compile nicely. I am now updating a package that uses the OpenBLAS and the PGI compiler, which has changed too. I just changed the path names in Makevars. Here is the Makevars file. FC= d:/PGI/win64/18.10/bin/pgf90 F77= d:/PGI/win64/18.10/bin/pgf90 CC = d:/PGI/win64/18.10/bin/pgcc FFLAGS=

Hi List, I've run into a library problem I believe might be related to the portland group compiler, and / or the libs on CentOS. Essentially what is happening is the primary executable I'm trying to run is failing under mpi. Here's the output from the command (which would be the same as the script calling it) $ /usr/local/mpich/bin/mpirun -machinefile machines.LINUX -np 2

----- Original Message ----- > From: "Alex Bradbury" <asb at asbradbury.org> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "LLVM Dev" <llvm-dev at lists.llvm.org>, "flang-dev" <flang-dev at googlegroups.com>, "Rob Neely" <neely4 at llnl.gov>, > "douglas miles (PGI)" <douglas.miles at

Hi everyone, I have some very good news for everyone interested a production-quality Fortran frontend for LLVM: The U.S. Department of Energy’s National Nuclear Security Administration and its three national labs have reached an agreement with NVIDIA's PGI division to adapt and open-source PGI's Fortran frontend, and associated Fortran runtime library, for contribution to the LLVM

Chad, et al, In addition to Doug’s excellent technical update, I’ll note that we are starting to have some discussions on the DOE side with PGI about establishing a more formal review team made up of some key LLVM stakeholders to help smooth the way for a broader public rollout of the Flang code base and eventual integration. We’ll probably rely on Hal and others here to help us figure out who