similar to: LAPACK and BLAS libraries

Hi, I am working on a UNIX machine and I am interfacing R and C with the .C function. I am trying to call LAPACK and BLAS routines, but am running into a problem where, while I am able to run the BLAS routines, I cannot run the LAPACK routines. I compile my .c file (at end of email) in the following way: [mhitczen at jlogin2 ~/Cstuff]$ R CMD SHLIB testmore.c gcc -std=gnu99

Dear helpers, I am trying to create a library which uses some Fortran source files and Lapack and Blas subroutines. The Fortran source files from the original author contain subroutines isamax.f, sgefa.f and sgesl.f, which are part of BLAS subroutines on my Linux computer, but maybe different (old) versions. So in addition to these subroutines, there are other Lapack and Blas subroutines

Hello, I have a problem with the checking and building of R packages that contain C or FORTRAN code. I have implemented R 2.3.1 (2006-06-01) and the corresponding toolset under Windows XP and Windows 2000. The MinGW compiler components are (exactly as recommended for R 2.3.1) gcc-core-3.4.5-20051220-1.tar.gz gcc-g++-3.4.5-20051220-1.tar.gz gcc-g77-3.4.5-20051220-1.tar.gz

Hey Everyone, I'm running R 2.4.0 on Debian etch 4.0, and I'm trying to call some LAPACK functions from the C code in my package. Actually, to be honest I'm not really having trouble using commands such as La_dgesv from within my C code, but I do get warning when compiling the package saying: ***.c: In function '***': ***.c:37: warning: implicit declaration of function

Hello I'm trying to run a fortran code which use LAPACK subroutines. I think I should use some points shown in the manual 5.5 Creating shared objects but it is too technical for me :-(... Could anyone help me for the procedure to do: -which part of the manual is relevant for this type of question? actually I'm speaking from writing R extensions, should I read R admin? -point 1.2

I am interested in tapping into LAPACK functionality directly from R. Using R-2.4.1 for Windows, I was able to do so ala: dyn.load("bin/Rlapack.dll") is.loaded("dstebz") # returns TRUE N <- 100 NW <- 4 n.tapers <- 5 tpW <- (2 * pi * NW)/N otNmo <- 1:N D <- as.double(cos(tpW) * ((N - 1 - 2 * (0:(N - 1)))/2)^2) E <- as.double((otNmo * (N - otNmo))/2) z

Everyone, I'm running R CMD check on a package using the 2.6.0 alpha version: > sessionInfo() R version 2.6.0 alpha (2007-09-09 r42809) i386-pc-mingw32 locale: LC_COLLATE=English_United States.1252;LC_CTYPE=English_United States.1252;LC_MONETARY=English_United States.1252;LC_NUMERIC=C;LC_TIME=English_United States.1252 attached base packages: [1] stats graphics grDevices utils

Dirk, thank you a thousand times. Indeed, src/Makevars was wrong. I modified Makevars so that now looks like the below and the package now compiled and linked properly. CXX_STD = CXX11 PKG_LIBS += $(SHLIB_OPENMP_CXXFLAGS) $(LAPACK_LIBS) $(BLAS_LIBS) $(FLIBS) $(shell ${R_HOME}/bin/Rscript -e "RcppParallel::RcppParallelLibs()") PKG_CXXFLAGS = $(SHLIB_OPENMP_CXXFLAGS) -I../inst/include

Hello! I have some Fortran code that uses BLAS calls, and would like to compile it into a shared object to call it from R as per the "Writing R Extensions" manual. What needs to go into the "Makevars" file, so that running the R CMD SHLIB will work in Ubuntu? The code compiles properly on the Mac, with the Makevars line PKG_CFLAGS=-Wl,-framework -Wl,vecLib but of course

Hi everybody: I am writing a package that includes C code that uses the BLAS library. My Makevars looks like PKG_LIBS = $(LAPACK_LIBS) $(BLAS_LIBS) $(FLIBS). If I check and build the package under Linux on my own computer everything works fine. However, if I submit the package to win-builder I get the following error messages: g++ -shared -s -o bzipl.dll tmp.def ars.o bzipl.o cvm_arrays.o

Hi all, I have a C function, say Cfun, that calls Lapack's DGEMM routine and I need to create a shared library to use Cfun inside R. The C file is the following #include<stdio.h> #include<R.h> #include<R_ext/Lapack.h> void Cfun(double *res, double *X, int *n, int *q) { char *ptr_TRANSA, TRANSA='T', *ptr_TRANSB, TRANSB='N'; ptr_TRANSA=&TRANSA;

Hello List, I have create a small package with C code. In the C code, I call Fortran routines of Lapack. Here is the call in the C function: F77_CALL(dgesvd)(&jobu, &jobvt,&size, &size,A, &size, D,U,&size,V,&size,&work1, &lwork,&error); In the src directory, I have a Makevars File with: PKG_LIBS = $(LAPACK_LIBS) $(BLAS_LIBS) $(FLIBS) And in the

The following were the replies to my question about using R's LAPACK and other .h files in some of my C programs. From what was said, it appears that buying a ready-made library (MKL = $200, for example) or using CLapack according to the Shumway lecture notes are the best approaches: -------------------------------- >From Andy Liaw: (1) If you just want linear algebra routines in your C

Attached (and pasted in it entirety, although quite a few of the long lines are munched) is my rpm spec file for building the mingw cross-compiler as an rpm. It is more or less a wrapper which massages the cross-tool script and setting some of the directories in the "RPM" way and eventually everything is under /opt/mingw ; the only tricky part is telling rpm not to strip binaries. The

When I build one of my packages with alpha from yesterday I am getting * checking for portable use of $BLAS_LIBS ... WARNING apparently missing $(FLIBS) in 'PKG_LIBS=$(LAPACK_LIBS) $(BLAS_LIBS)' Is this something I should worry about? (Possibly I got this before and didn't notice.) Paul Gilbert ====================================================================================

Dear all, I have a problem to build a package on Windows XP while there is no problem on Linux. The Makefile is something like: ########### LIBNAME=cts PKG_LIBS = $(LAPACK_LIBS) $(BLAS_LIBS) $(FLIBS) OBJS=file1.o ... file20.o -llapack -lblas $(LIBNAME)$(SHLIB_EXT): $(OBJS) $(SHLIB_LD) $(SHLIB_LDFLAGS) -o $@ $(OBJS) $(FLIBS) clean: @rm -f *.o *.$(SHLIB_EXT) realclean: clean

When I install an R package with cpp codes such as rrcov via CRAN (under R 3.1.1, using no Makevars file and under Ubuntu 14.04 using GCC 4.8), the cpp code is compiled with the -o3 flag (in fact, looking at the Makeconf file this seem to again be the default since R 3.1.1) But when I install my own package via CRAN it is compiled with the -o2 flag. My questions are what is causing my

Hello. I am a Linux neophyte and know almost nothing ?about compiling, so I would appreciate any help and advice y'all would care to offer. I am trying to compile the 64 bit version of R using a tuned ATLAS and LAPACK (ATLAS 3.9.24). I am running Ubunto 10.04 LTS (through wubi, FWIW). The ATLAS and LAPACK files (atlas.so, f77blas.so, lapack.so, and cblas.so) are sitting in the folder

Dear all, I am running R : Copyright 2005, Version 2.2.1 (2005-12-20 r36812) ISBN 3-900051-07-0 On a mac 10.4.5 I am having trouble with my package. The trouble is the following: In my package I have integrated three files in my src folder. 1- simplematch.C a .C file 2- ordering.f a fortran file 3- Makevars : PKG_LIBS = $(LAPACK_LIBS) $(BLAS_LIBS) $(FLIBS) I am not sure if that last file is

Dear All, I am building R from source[1], following what is done in "rules" for building Debian's R. But the R I generate, in contrast to the standard Debian's R, will not change the BLAS and LAPACK libraries it uses when I change them via "update-alternatives". I have no idea what I am doing wrong (but, somehow, I've been quite capable of making the same