similar to: Compiling R and packages with debug information?

Hello, I experienced a compiler error when I tried to compile the latest version of R i.e. R4.0.2 making iosupport.d from iosupport.c making lapack.d from lapack.c making list.d from list.c making localecharset.d from localecharset.c grep.c(74): catastrophic error: cannot open source file "pcre2.h" # include<pcre2.h> (The pcre2.h header file is actually present!) I used the

Hi Erik, I've found a middleground for the problem of setting default CFLAGS. I've gone back to setting them if {C,CXX,CPP,LD}FLAGS are unset at the onset of the configure script (i.e., the user hasn't specified anything) and then proceed to set them to the defaults as before. This has been suggested before: https://lists.gnu.org/archive/html/autoconf/2006-04/msg00022.html In

Bugs compiling R-1.7.1 with Intel compilers icc and ifc, on x86-computer (Pentium IV) and linux operating system Hello, as there aren't many reports about that issue, I'll give a little report here. (Hope I don't bother anyone) The best thing about using icc and ifc are the warnings, because it is said that the Intel compilers are stricter and give more precise warnings than gcc.

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

Dear FLAC devs, I would like to get some of our patches merged into master. Most of them deal with adhering to GNU conventions, respectively not overriding flags/variables that are up to the user to set. For instance, honoring $(htmldir) is important, as we have installation paths for the documentation that differ from what is currently coded in the various Makefile.am's. Regards David

I am encountering a make error on an AIX 5.2 with R-2.3.0 and R-patched_2006-05-10 after successfully configuring them using gcc-4.1.0, gnu make, and the following configure options CC=/usr/local/bin/gcc F77=/usr/local/bin/gfortran CXX=/usr/local/bin/g++ MAIN_LDFLAGS=-Wl,-brtl SHLIB_LDFLAGS=-Wl,-G CFLAGS='-g -O' FFLAGS='-O' CXXFLAGS='-g -O' bash-3.00$ ./configure

Full_Name: Karsten Tabelow Version: R-2.3.1 OS: AIX5.3 Submission from: (NULL) (62.141.176.2) Specification in config.site: CC=xlc_r CFLAGS='-O -qstrict' F77=xlf_r FFLAGS='-O -qstrict' SHLIB_LDFLAGS='-G' DYLIB_LDFLAGS='-G' LDFLAGS='-brtl' CXX=xlc++_r CXXFLAGS='-O -qstrict' Complilation error in src/main/printutils.c: "printutils.c",

Hi, I have been able to build R-2.9.2 on AIX 6.1 and AIX 5.2. However, I failed to build R-2.10.0 and later releases on these AIX platforms. The error messages I got are attached below: "connections.c", line 461.10: 1506-022 (S) "truncate64" is not a member of "struct Rconn". "connections.c", line 772.10: 1506-022 (S) "truncate64" is not a member

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

Dear all, after trying to compile R on our IBM Power3/AIX 5.1 machine I've been able to run it correctly. First of all I would thank all who responded my mails. I explain here how I've done it: First of all, it seems that configure and some shared libraries of AIX does not work at the same time. I tried to configure & make with the following environment vars CC=xlc F77=xlf CCC=xlC

Hi, I am compiling R2.8.1 on a Sun M4000 machine with Solaris 10. I am using Sun Studio 12. I get the following error: cc -xtarget=native64 -G -L/usr/sfw/lib/sparcv9 -L/opt/csw/lib/sparcv9 -o grDevices.so chull.o devNull.o devPicTeX.o devPS.o devQuartz.o init.o mkdir ../../../../library/grDevices/libs Warning in solve.default(rgb) : unable to load shared library

Hello, Is there a way to force through R the amount of the cpu's cores (or the cpu's utilization level) used under Windows 7 or Linux? Thanks, Costas

Hi, I'm a sysadmin who's been tasked with installing R on our 1000-node compute cluster. I have licences for the Intel C and FORTRAN compilers, so I'm using the following to compile: CFLAGS="-O2 -axWK" FFLAGS=$CFLAGS CXXFLAGS=$CFLAGS CC=icc F77=ifort CXX=icc FPICFLAGS=-fpic ./configure --without-x --without-tcltk The compilation seems to go OK, with a few warnings.

Hi list, I tried to install MCMCpack to R-2.12.0, got the following error, CC -m64 -library=stlport4 -I/apps/sparcv9/R-2.12.0/lib/R/include -DSCYTHE_COMPILE_DIRECT -DSCYTHE_DEBUG=0 -DHAVE_TRUNC -DHAVE_IEEEFP_H -I/opt/csw/include -KPIC -g -c MCMCSVDreg.cc -o MCMCSVDreg.o "error.h", line 598: Error: The function "abort" must have a prototype.

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`

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 14:48:48 +0200 Kurt Hornik <Kurt.Hornik at wu.ac.at> wrote: > I guess foer the CXXFLAGS we want dpkg-buildflags --get CXXFLAGS? It must be the case. It's both the documented option [1] and it currently differs from CFLAGS in the offending flag: root at 93e09ba5b6fb:/# diff -u <(dpkg-buildflags --get CFLAGS | sed 's/ /\n/g') <(dpkg-buildflags --get

Full_Name: Kelly Black Version: 2.0.1 OS: FreeBSD 5.3 on AMD64 Submission from: (NULL) (149.106.32.93) I downloaded R-2.0.1 from the R website, ran configure then make and got an error. I will paste a copy of the output from the makefile below. The problem was when the makefile tried to run the R binary. When I came across the error I reran configure, but this time with the following arguments:

After a few days of reading and headache, I finally gave a try at building R from source with Intel MKL and ICC. Documentation and posts on this topic are rather incomplete, sometime fantasist et do not give much explanations about configure options. As I am not sure if mine is correct, I would appreciate some advices and hints. OS: Fedora 22 parallel_studio_xe_2016 Hardware : 8 Thread(s) per