similar to: Windows fixed/etc/Makeconf SHELL incorrect?

I am trying to build R under 64bit Windows7. I am using a fresh install of Rtools34 and R-patched_2016-07-05. I am getting the following error: C:/Rtools/mingw_64/bin/gcc -shared -s -static-libgcc -o tcltk.dll tmp.def init.o tcltk.o tcltk_win.o ../../../gnuwin32/dllversion.o -L../../../../Tcl/bin64 -ltc l85 -ltk85 -LC:/R/RLocalSoft/lib/x64 -LC:/R/RLocalSoft/lib -L../../../../bin/x64 -lR

As the build process, especially for Windows, is changing significantly for R 3.2.0, I am trying to build R-devel in preparation. When running `make rinstaller`, I get the following error: cp -p ../../../etc/x64/Makeconf R-devel/etc/x64 mkdir -p R-devel/doc cp -p ../../../doc/CRAN_mirrors.csv R-devel/doc mkdir -p R-devel/doc/manual/images cp -pR ../../../doc/html R-devel/doc

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?

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

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?

Hello all, I'm trying to build R 32bit from source in a Windows 64 machine. I have followed the steps in "R Installation and Adiministration" ( http://cran.r-project.org/doc/manuals/R-admin.html#Getting-the-source-files) or at least I think I did everything described. I am not sure if I have installed the libjpeg, libtiff and libpng files though. I have upzipped them in the

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

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:

Colleagues, I am trying to understand how R (2.12.1) obtains the PATH environment variable in Windows (7 or Vista). Startup {base} directs one to: "R_ENVIRON" -- which equals "" in my systems R_HOME/etc/Renviron.site -- which does not exist Next, it directs to: R_HOME/etc/Rprofile.site -- which also does not exist (the expected behavior in a "factory-fresh"

Hi, I can't seem to install R from source. I've downloaded the latest Rtools211.exe from http://www.murdoch-sutherland.com/Rtools/ & done a full installation of that and Inno Setup. I have set R_HOME as C:\R (and also tried using C:\R\R-2.11.1) After successfully running 'tar xf R-2.11.1.tar.gz' the modifications I have made and saved as MkRules.local are: BUILD_HTML =

I'm going to using RInside on windows enviroment. I installed all tools and packages according to Dirk's instruction. My R installation reside in d:\hli\programfiles\R-3.2.2. There's no problems with folders with spaces. The rtools is installed in d:\hli\programfiles\Rtools and MinGW in d: \hli\programfiles\MinGW. The R_HOME is set to d:\hli\programfiles\R-3.2.2. I

Hello all, I'm trying hard to make R CMD SHLIB work on Windows XP (32-bit) - please note that I don't have the admin rights on the computer. In terms of setup, I have followed the procedure : => installed Rtools 2.14 => changed my path : PATH=C:\Trading\R\RTools\bin;C:\Trading\R\RTools\MinGW\bin;C:\Trading\R\R-2.14.1\bin\i386;C:\WINDOWS\system32;%OTHER_PATHS% But when I try R CMD

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-devel at r-project.org

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

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.

On 26/01/2015 5:12 PM, Avraham Adler wrote: > As the build process, especially for Windows, is changing > significantly for R 3.2.0, I am trying to build R-devel in > preparation. When running `make rinstaller`, I get the following > error: > > cp -p ../../../etc/x64/Makeconf R-devel/etc/x64 > mkdir -p R-devel/doc > cp -p ../../../doc/CRAN_mirrors.csv

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 07/07/2016 5:47 PM, Avraham Adler wrote: > I am trying to build R under 64bit Windows7. I am using a fresh > install of Rtools34 and R-patched_2016-07-05. I am getting the > following error: > > C:/Rtools/mingw_64/bin/gcc -shared -s -static-libgcc -o tcltk.dll tmp.def init.o > tcltk.o tcltk_win.o ../../../gnuwin32/dllversion.o -L../../../../Tcl/bin64 -ltc > l85 -ltk85

Jiefei, you did not commit all files into the example package - your example has things like RcppExports.cpp as well as additional flags which are not in your GH project. I suspect the issue is with the extra flags you're adding - those don't come from R. Please make sure you can replicate the issue with the GH package you created. Cheers, Simon * installing *source* package

Hi, After uninstalling Rtools 2.14.0, I have installed the latest version of Rtools 2.15.0 which gives the two folders C:\Rtools\bin C:\Rtools\gcc-4.6.3 R is installed in the directory C:\R\R-2.15.0 I have set the Environment Variable PATH=c:\Rtools\bin;c:\Rtools\gcc-4.6.3\bin;c:\R\R-2.15.0\bin;<others> I am trying to install a custom package (BMEA_0.2.1) which is exactly