search for: shlib_openmp_cflags

...20.915 3 3.277 1.894 1.908 Comments on that? To me it seems clear that openblas (0, 2, 3) has nothing to offer me, as my C code stands now. Is the problem that openblas uses C versions of blas? I am using the Fortran version via F77_CALL(name) I tried adding PKG_CFLAGS = $(SHLIB_OPENMP_CFLAGS) PKG_LIBS = $(SHLIB_OPENMP_CFLAGS) to src/Makevars, but then I got ...undefined symbol: dsytri_ when compiling. G?ran

...d I comment? I do not know what code you ran. | To me it seems clear that openblas (0, 2, 3) has | nothing to offer me, as my C code stands now. Is the problem that | openblas uses C versions of blas? I am using the Fortran version via | | F77_CALL(name) | | I tried adding | | PKG_CFLAGS = $(SHLIB_OPENMP_CFLAGS) | PKG_LIBS = $(SHLIB_OPENMP_CFLAGS) This is missing LAPACK and BLAS so ... | | to src/Makevars, but then I got | | ...undefined symbol: dsytri_ ... so get a _linker error_ about missing symbols. | when compiling. You meant linking, not compiling. Dirk -- https://dirk.eddelbuettel.com | @...

...lse AC_MSG_ERROR([gsl-config not found, is GSL installed?]) fi # Now substitute these variables in src/Makevars.in to create src/Makevars AC_SUBST(GSL_CFLAGS) AC_SUBST(GSL_LIBS) AC_OUTPUT(src/Makevars) And here is Makevars.in: GSL_CFLAGS = @GSL_CFLAGS@ GSL_LIBS = @GSL_LIBS@ PKG_LIBS=$(GSL_LIBS) $(SHLIB_OPENMP_CFLAGS) $(SHLIB_OPENMP_CXXFLAGS) PKG_CFLAGS=$(GSL_CFLAGS) $(SHLIB_OPENMP_CFLAGS) PKG_CXXFLAGS=$(SHLIB_OPENMP_CXXFLAGS) Any help would be greatly appreciated. I don't have access to Solaris which makes the debugging rather hard. Best regards, Jouni Helske [[alternative HTML version deleted]]

.... > > | To me it seems clear that openblas (0, 2, 3) has > | nothing to offer me, as my C code stands now. Is the problem that > | openblas uses C versions of blas? I am using the Fortran version via > | > | F77_CALL(name) > | > | I tried adding > | > | PKG_CFLAGS = $(SHLIB_OPENMP_CFLAGS) > | PKG_LIBS = $(SHLIB_OPENMP_CFLAGS) > > This is missing LAPACK and BLAS so ... > | > | to src/Makevars, but then I got > | > | ...undefined symbol: dsytri_ > > ... so get a _linker error_ about missing symbols. > > | when compiling. > > You meant link...

Dear mac folks, I have started porting a large legacy toolset maintained in windows and heavily mpi laden so it can be used across platforms in R... so I am building a package out of it. On this note, I am noticing that almost all of the mpi dependent packages do not compile on the CRAN repositories.... with the basic issue that it appears it can not find mpi installed: configure: error:

Hi everybody, I'm trying to develop an R package with Fortran and OpenMP. I wrote a simple hello world but I'm not able to set the number of threads. I found this old email chain <http://r.789695.n4.nabble.com/Set-the-number-of-threads-using-openmp-with-C-td2284685.html> and I tried to set my compile instructions accordingly but i had no luck. *This is my makevars:*

...: > > > I was able to make some progress by using this > <https://github.com/bert9bert/ParallelForest/blob/master/src/Makevars> as > a reference. Now: > > *This is my makevars:* > ##### Compiler flags ##### > PKG_FCFLAGS = $(SHLIB_OPENMP_FFLAGS) > PKG_LIBS = $(SHLIB_OPENMP_CFLAGS) > > ##### Phony target for R's build system to invoke ##### > all: $(SHLIB) > > ##### Clean target ##### > clean: > rm -f *.o *.mod > > And when I run my hello world function all the threads are used > regardless of what i specify: > > > hello(ncores...

I was able to make some progress by using this <https://github.com/bert9bert/ParallelForest/blob/master/src/Makevars> as a reference. Now: *This is my makevars:* ##### Compiler flags ##### PKG_FCFLAGS = $(SHLIB_OPENMP_FFLAGS) PKG_LIBS = $(SHLIB_OPENMP_CFLAGS) ##### Phony target for R's build system to invoke ##### all: $(SHLIB) ##### Clean target ##### clean: rm -f *.o *.mod And when I run my hello world function all the threads are used regardless of what i specify: > hello(ncores = 2) Hello from 1 Hello from 3 Hel...

...or C++ compiler rather than the Fortran 9x compiler. This is consistent with fixed-form Fortran code and allows mixing of C++ and free-form Fortran on most platforms. Consequentially, a package which includes free-form Fortran 9x code which uses OpenMP should include SHLIB_OPENMP_CFLAGS (or the CXXFLAGS version if they also include C++ code) in PKG_LIBS rather than SHLIB_OPENMP_FCFLAGS - fortunately on almost all current platforms they are the same flag. * Macro PKG_FFLAGS will be used for the compilation of both fixed-form and free-form Fortran code u...

...or C++ compiler rather than the Fortran 9x compiler. This is consistent with fixed-form Fortran code and allows mixing of C++ and free-form Fortran on most platforms. Consequentially, a package which includes free-form Fortran 9x code which uses OpenMP should include SHLIB_OPENMP_CFLAGS (or the CXXFLAGS version if they also include C++ code) in PKG_LIBS rather than SHLIB_OPENMP_FCFLAGS - fortunately on almost all current platforms they are the same flag. * Macro PKG_FFLAGS will be used for the compilation of both fixed-form and free-form Fortran code u...

...or C++ compiler rather than the Fortran 9x compiler. This is consistent with fixed-form Fortran code and allows mixing of C++ and free-form Fortran on most platforms. Consequentially, a package which includes free-form Fortran 9x code which uses OpenMP should include SHLIB_OPENMP_CFLAGS (or the CXXFLAGS version if they also include C++ code) in PKG_LIBS rather than SHLIB_OPENMP_FCFLAGS - fortunately on almost all current platforms they are the same flag. * Macro PKG_FFLAGS will be used for the compilation of both fixed-form and free-form Fortran code u...