similar to: alpha, portable use

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

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

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

Hi, I don't know if I'm sending this to the right place but I've looked throught tens and tens of topics on http://tolstoy.newcastle.edu.au/ and finally found that email address where I can maybe find some help. Well my main goal is to get to use the lapack library within my R package (which can be done using calls from C). But in order to do this I have to create a file src/Makevars

Hi, I don't know if I'm sending this to the right place but I've looked throught tens and tens of topics on http://tolstoy.newcastle.edu.au/ and finally found that email address where I can maybe find some help. Well my main goal is to get to use the lapack library within my R package (which can be done using calls from C). But in order to do this I have to create a file src/Makevars

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

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

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

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

Hi there, I'm having trouble to compile the R + C/C++ codes for this project from Yahoo folks on latent factor models: https://github.com/yahoo/Latent-Factor-Models#readme After downloading the package from the site, I could not successfully *make* the files. Here is the message: ====================================================================================== sh-4.1$ make R CMD

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;

Dear R-devel, I've written a numerical solver for SOCPs (second order cone programs) in R, and now I want to move most of the solver code into C for speed. I've written combined R/C packages before, but in this case I need to do matrix operations in my C code. As I have never done that before, I'm trying to write some simple examples to make sure I understand the basics. I am stuck

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 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

Prof Brian Ripley wrote: > 'library' in R has a different meaning: I've altered the subject to be > more accurate 'libR'. > > This is what R CMD SHLIB is for: it does all this for you in a portable way. > > But if you want to DIY, you can use R CMD config to find out the > appropriate linker incantation. Thank you for the clarification. I do not insist on

I am the guy who compiles the OpenMx binaries. We would be delighted to place our package on CRAN, once the project is stable enough so that we are comfortable releasing it to the larger public. Let's try to track down where I made a mistake. Our Makevars.in file contains the line: PKG_LIBS=$(FLIBS) $(BLAS_LIBS) $(LAPACK_LIBS) In addition, on the build machine I noticed that a copy of

Dear R experts, recently I started developing a Rcpp package "OpenMPTest". Within that package I want to use OpenMP, as in the following code example: // header file #include <omp.h> using namespace Rcpp ; RcppExport SEXP testOpenMP( SEXP nThreads ) ; // cpp file SEXP testOpenMP( SEXP nThreads ) { BEGIN_RCPP NumericVector numberThreads = NumericVector( nThreads );

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, I can not install packages from source which links to RcppArmadillo on Ubuntu 20.04 (after upgrading from 18.04). The following problem occurs: ** testing if installed package can be loaded from temporary location Error: package or namespace load failed for 'myPackage' in dyn.load(file, DLLpath = DLLpath, ...): unable to load shared object