similar to: Can one set CFLAGS/CXXFLAGS during R INSTALL ?

Why is it that R places CFLAGS after PKG_CFLAGS and not before when compiling a package (e.g. through R CMD build pkg)? This can be problematic if, for instance, you want to use -O3, but -O2 is in R_HOME/etc/Makeconf. If -O2 (in CFLAGS) appears after -O3 (in PKG_CFLAGS), you are left with what you didn't want: -O2. In R-exts, it says that "Flags which are set in file etc/Makeconf

On 21 May 2024 at 13:01, Jeroen Ooms wrote: | Compiling packages with C++ code using the default r-base-dev | configuration on debian:sid shows a lot of: | | cc1plus: warning: '-Werror=' argument | '-Werror=implicit-function-declaration' is not valid for C++ | | Can this flag be removed from R CMD config CXXFLAGS? "No." That was quoting Simon Urbanek from a few

On Tue, 21 May 2024 07:08:02 -0500 Dirk Eddelbuettel <edd at debian.org> wrote: > You cannot undo what it is in R's own /etc/R/Makeconf via a > programmatic way via some sort of option or alike. I think this is about the following line in debian/rules: optimflags = `DEB_BUILD_MAINT_OPTIONS=optimize=-lto dpkg-buildflags --get CFLAGS`

The following patch uses INSTALL_SCRIPT to install scripts, as opposed to directly using INSTALL. It is relative to R-1.0.1 source. -- Johnny C. Lam <lamj@stat.cmu.edu> Department of Statistics, Carnegie Mellon University http://www.stat.cmu.edu/~lamj/ --- Makeconf.in.orig Sat Jan 22 15:10:00 2000 +++ Makeconf.in Mon Apr 17 16:04:58 2000 @@ -23,6 +23,7 @@ INSTALL =

Compiling packages with C++ code using the default r-base-dev configuration on debian:sid shows a lot of: cc1plus: warning: '-Werror=' argument '-Werror=implicit-function-declaration' is not valid for C++ Can this flag be removed from R CMD config CXXFLAGS?

>>>>> Ivan Krylov writes: > On Tue, 21 May 2024 07:08:02 -0500 > Dirk Eddelbuettel <edd at debian.org> wrote: >> You cannot undo what it is in R's own /etc/R/Makeconf via a >> programmatic way via some sort of option or alike. > I think this is about the following line in debian/rules: Without having looked in much detail, I guess foer the CXXFLAGS

Hello, I'm tring to install a Rpackage that holds some C//C++ code as far as I understood the R library generic compilation mechanism, compilation of C//C++ sources is controled 1) at system level by the ocntentos RHOME/etc/Makeconf 2) at user level by the content of ~/.R/Makevars 3) at package level by the content of src/Makevars Problem I have is that src/Makevars is ignored see

I shouldn't try to do this on Monday morning. Can anyone suggest why the make for R 0.63 is failing for me under Solaris (SunOS 5.6). Paul Gilbert ... creating src/scripts/html2dos creating tests/Makefile creating tests/Examples/Makefile creating src/include/Platform.h R is now configured for sparc-sun-solaris2.6 Source directory: . Installation directory: /usr/local C

retitle 925358 qemu-user-static: mis-emulates something to do with process/signal handling (m68k, s390x, ?) affects 925358 klibc-dev thanks This still happens. (And retitling because I almost filed a bug against klibc again? oops?) Look for ?mtest-external? (second occurrence) in: https://buildd.debian.org/status/fetch.php?pkg=mksh&arch=m68k&ver=59c-16&stamp=1643675884&raw=0

Le 27/09/16 ? 13:31, Dirk Eddelbuettel a ?crit : > > On 27 September 2016 at 09:37, Eric Deveaud wrote: > | Hello, > | > | I'm tring to install a Rpackage that holds some C//C++ code > | > | as far as I understood the R library generic compilation mechanism, > | compilation of C//C++ sources is controled > | > | 1) at system level by the ocntentos

I have been trying to compile R. I downloaded R-1.0.1.tgz(I think; the original tar file was untarred) and unpacked it with gzip. Now all the R files are in a directory named R-1.0.1. The source files (.c) are in R-1.0.1/src. There are files in R-1.0.1 named 'Makefile.in', 'Makeconf.in', and 'Makeconf'. I followed the instructions in INSTALL by typing

{message bounced because it has "$$$" in it. manually approved by list maintainer -- MM} > Date: Tue, 22 Feb 2000 13:03:35 +0100 > From: jens <jniesch at gwdg.de> > > I have trouble to install R on Sparc Sun Solaris 2.6. > make returns the error message: > Undefined symbol first referenced in file > d_lg10 ../appl/libappl.a(uncmin.o) > d_sign

For various reasons, it suits our workplace to have a cygwin version of R. I am pretty sure that cygwin is still not a supported environment for R, but we have managed to compile R-2.5.1 under cygwin without too many dramas. Our procedure is described below. We still have a few problems compiling libraries without manually changing files from .so to .dll, but it seems ok. I was wondering

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

Hi, I am trying to package some code to use with R and wanted to call Rscript from within the Makevars file (I am trying to automate the setting of the location of a third party library depending on what is available / the system the package is being installed on). If I just have a simple Makevars containing PKG_LIBS= -lnag_nag -L/fserver/nagprod/FL22/fll6a22df/lib the package is built

Hello, I am writing you about the GNU R-Project, as part of by effort to help GNU projects provide a better, more consistent build system. Currently, your project does not support the DESTDIR variable in generated Makefiles (marked as optional in the GNU coding policies, make and automake manual). In my opinion, DESTDIR support can be very helpful for the user, the distribution-specific

Hi, I have built a library that consists of a piece of C code and some R functions. To build it into a library that I can load using library() command, I have followed "Writing R Extensions" and made sub-directories such as mylib/R and mylib/src. But when I run R CMD INSTALL mylib, nothing seems to be happening with src directory, i.e., no C compiling. I have probably missed some key

Hi, I have built a library that consists of a piece of C code and some R functions. To build it into a library that I can load using library() command, I have followed "Writing R Extensions" and made sub-directories such as mylib/R and mylib/src. But when I run R CMD INSTALL mylib, nothing seems to be happening with src directory, i.e., no C compiling. I have probably missed some key

Greetings, I am trying to call simple C-code from R. I am on Windows XP with RTools installed. The C-function is #include <R.h> #include <Rinternals.h> #include <Rmath.h> #include <Rdefines.h> // prevent name mangling extern "C" { SEXP __cdecl test(SEXP s){ SEXP result; PROTECT(result = NEW_NUMERIC(1)); double* ptr=NUMERIC_POINTER(result); double t =

Dear R development: I'm not sure if this is the appropriate list, but it's a start. I would like to put together a package which contains a CUDA program on Windows 7. I believe that it has to do with the Makeconf file in the etc directory. But when I just use the nvcc with the shared option, I can use the dyn.load command, but when I use the is.loaded function, it shows FALSE.