search for: makeconf

.../LC_MESSAGES/%N.cat:/usr/ccs/bin/../../lib/locale/C/LC_MESSAGES/%N.cat VIRTUAL_ROOT= / MFLAGS= -dd MAKEFLAGS= -dd stat(Makefile) doname(Makefile) Looking for % rule for Makefile find_double_suffix_rule(Makefile) find_suffix_rule(Makefile,Makefile,) srcdir= . top_srcdir= . top_builddir= . stat(./Makeconf) doname(./Makeconf) Looking for % rule for ./Makeconf find_double_suffix_rule(./Makeconf) find_suffix_rule(./Makeconf,./Makeconf,) PACKAGE= R VERSION= 0.63.0 AR= ar BLAS= blas.o CC= gcc CFLAGS= -g -O2 CPICFLAGS= -fPIC CPPFLAGS= -I../include -I$(top_srcdir)/src/include DLLFLAGS = DVIPS= /apps/res...

http://cran.r-project.org/doc/manuals/R-exts.html#Configure-and-cleanup near the start of 1.2.1 Using Makevars says > There are some macros which are set whilst configuring the building of > R itself and are stored in R_HOME/etcR_ARCH/Makeconf. That makefile is > included as a Makefile after Makevars[.win], and the macros it defines > can be used in macro assignments and make command lines in the latter. > I'm confused. If Makeconf is included after Makevars, then how can Makevars use macros defined in Makeconf? Or is the...

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. Here are the results of the check command: c:\PROGRA~1\R\R-3.0.1\bin\i386>R CMD check cudasize R CMD check cudasize...

I sent the message below to r-sig-mac yesterday, but having no reply I decided to explore a bit myself and found that editing: /Library/Frameworks/R.framework/Versions/2.3/Resources/share/make/ shlib.mk yzzy: diff shlib.mk shlib.mk~ 3c3 < include $(R_HOME)/etc/Makeconf --- > include $(R_HOME)/etc${R_ARCH}/Makeconf restored the functionality of R CMD INSTALL. Is this a known issue? url: www.econ.uiuc.edu/~roger Roger Koenker email rkoenker at uiuc.edu Department of Economics vox: 217-333-4558 University of Ill...

...st(0) dyn.unload("./OrthoFunctions.dll") then R crashes. If I compile with the default flags (no extern "C", no __cdecl) I get an error message about an undefined reference to "__gxx_personality_v0": C:\...>R CMD SHLIB OrthoFunctions.c C:/Programme/R/R-2.10.1/etc/Makeconf:151: warning: overriding commands for target `.c.o' C:/Programme/R/R-2.10.1/etc/Makeconf:142: warning: ignoring old commands for target `.c.o' C:/Programme/R/R-2.10.1/etc/Makeconf:159: warning: overriding commands for target `.c.d' C:/Programme/R/R-2.10.1/etc/Makeconf:144: warning: igno...

...WS\system32;%OTHER_PATHS% But when I try R CMD SHLIB *.* I have litterally nothing, no output at all. (and R CMD INSTALL debug tells me, of course that the operation failed while calling R CMD SHLIB) I tried the command R CMD SHLIB -n, which gives me : make -f "C:/Trading/R/R-2.14.1/etc/i386/Makeconf" -f "C:/Trading/R/R-2.14.1/share/make/winshlib.mk" SHLIB= OBJECTS= So I had a closer look at these two files, and found some strange things in Makeconf, for example a variable LOCAL_SOFT with a d: path which has nothing to do with my configuration : LOCAL_SOFT = d:/RCompile/CRANpkg...

Read in the Windows release notes for 2.4.0 that: There is a new file etc/Makeconf that provides an approximation to the Unix version and may help with src/Makefile's. Yet when I look at the CRAN binary I have for 2.4.1patched, there are five files in the $R_HOME/etc directory, but no Makeconf. Is the file only available with custom installs? ---------------------------...

R developers, On windows, it seems like R_HOME/etc/Makeconf has SHELL = /bin/sh instead of the location of Rtools' sh. I think this is because R_HOME/src/gnuwin32/fixed/etc/Makeconf needs to define SHELL as just sh (since Rtools/bin has to be on the PATH). This is of consequence with R CMD config. R version 2.7.0 Under development (unstable) (2007-...

Full_Name: Tim Middelkoop Version: 0.64.0 OS: IRIX 6.3 on O2 Submission from: (NULL) (128.119.88.192) Various IRIX complile issues src/nmath/pnt.c IRIX cc does not like double negatives Makeconf,config.site,etc/Makeconf f77 pic hack, should change Makeconf.in or other... change -PIC with -KPIC enjoy, tim... === diff -ru orig/R-0.64.0/src/nmath/pnt.c R-0.64.0/src/nmath/pnt.c --- orig/R-0.64.0/src/nmath/pnt.c Wed Apr 7 02:45:48 1999 +++ R-0.64.0/src/nmath/pnt.c Sat Apr 10 13:02:4...

I get an error when trying to compile a FORTRAN source file for use in a package that I am developing. The error, reported in 00install.out is below. * installing *source* package 'USGSstats' ... ** libs *** arch - i386 C:/PROGRA~1/R/R-214~1.1/etc/i386/Makeconf:194: warning: overriding recipe for target `.m.o' C:/PROGRA~1/R/R-214~1.1/etc/i386/Makeconf:187: warning: ignoring old recipe for target `.m.o' gfortran -O3 -mtune=core2 -c seakenF.f -o seakenF.o "zseakenF.o" was unexpected at this time. make: *** [USGSstats.dll] Error 255...

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 can be overridden by the environment variable MAKEFLAGS (at least for systems using GNU make), as in (Bourne shell sy...

R 3.4 has 'experimental' support for setting CXX_STD to CXX98 / CXX11 / CXX14 / CXX17. However on most platforms, the R configuration seems to leave the CXX1Y and CXX1Z fields blank in "${R_HOME}/etc/Makeconf" (rather than falling back on default CXX). Therefore specifying e.g CXX_STD= CXX14 will fail build with cryptic errors (due to compiling with CXX="") I don't think this is intended? Some examples from r-devel on Windows: CXX11: https://win-builder.r-project.org/R8gg703OQSq5/ C...

...-O2 -Wall -c file6d55374d.cpp -o file6d55374d.o g++ -shared -s -static-libgcc -o file6d55374d.dll tmp.def file6d55374d.o C:/Program Files/R/R-2.13.0/library/Rcpp/lib/i386/libRcpp.a -LC:/PROGRA~1/R/R-213~1.0/bin/i386 -lR cygwin warning: MS-DOS style path detected: C:/PROGRA~1/R/R-213~1.0/etc/i386/Makeconf Preferred POSIX equivalent is: /cygdrive/c/PROGRA~1/R/R-213~1.0/etc/i386/Makeconf CYGWIN environment variable option "nodosfilewarning" turns off this warning. Consult the user's guide for more details about POSIX paths: http://cygwin.com/cygwin-ug-net/using.html#using-pathn...

...where to look for it and if you know all the manuals inside out. Looking at the help for R CMD config, it's not actually clear that these relate to the options specified on configure, and it doesn't tell you things like --enable-R-shlib, or --prefix etc. Anyway, thanks for the info. The Makeconf file is what I want. At least on Linux, doesn't appear to exist on our OSX installation, but we probably installed that from a pre-built package. Ditto Windows. -----Original Message----- From: Dirk Eddelbuettel [mailto:edd at debian.org] Sent: 22 January 2016 12:07 To: Tom Quarendon <tom....

In trying to compile a package with c code using Rtools, -O3 is added by default. This comes from Makeconf? Compiler flags (CFLAGS="-O0 -g" ) set in src/Makevars.win or src/Makevars appear before this. nm pkg.dll reveals no symbols! How can I compile a Windows package with "-O2 -g"? Thanks, RT -- View this message in context: http://r.789695.n4.nabble.com/Cannot-override-def...

So in English what you are saying is that there's a file called Makeconf in the etc directory under the R_HOME that contains the information. That certainly seems to be true for Linux. Thanks. -----Original Message----- From: G?bor Cs?rdi [mailto:csardi.gabor at gmail.com] Sent: 22 January 2016 11:37 To: Tom Quarendon <tom.quarendon at teamwpc.co.uk> Cc: r-deve...

...c and i386 in the path. I am on Windows Vista and am using R version 2.12.1 Patched (2010-12-16 r53864) and just downloaded Rtools 2.12 today. Is this a bug in R? How can I resolve this? C:\tmp2>Rcmd SHLIB myprog.c cygwin warning: MS-DOS style path detected: C:/PROGRA~1/R/R-212~1.X/etci386/Makeconf Preferred POSIX equivalent is: /cygdrive/c/PROGRA~1/R/R-212~1.X/etci386/Makeco nf CYGWIN environment variable option "nodosfilewarning" turns off this warning. Consult the user's guide for more details about POSIX paths: http://cygwin.com/cygwin-ug-net/using.html#using-pathn...

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 './configure'. Here is the output: ---------------------------------------------- pauling 1% ./configure loading cache ./config.cache checking host system type... mips-sgi-irix6.5 loading site script ./conf...

Hello, I'm writing an R package that is mainly written in C++. By default, R CMD INSTALL creates C/C++ flags as follows: -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -g However, my package is fairly large. With debug info compiled into the library, the generated .so file is over 200MB. Without debug info, it's about 30MB. I hope

Thanks. I have now CXX = g++ -std=c++98 in my /etc/R/Makeconf, it's picked up properly. I can only assume that the last -std= option wins if more than one are given on the same command line [1]. -Kirill [1] http://stackoverflow.com/q/40563269/946850 On 12.11.2016 03:01, Dirk Eddelbuettel wrote: > On 11 November 2016 at 23:48, Kirill M?ller wro...