similar to: Setting Gnu++11 when compiling R-devel on Windows

Hi, I was reading through the R extensions website and noticed that the example code at the end of the section makes references to CXX11XSTD and CXX11XFLAGS, shouldn?t these be CXX1XSTD and CXX1XFLAGS respectfully? (on the second and fourth line) CXX1X=`"${R_HOME}/bin/R" CMD config CXX11X` CXX1XSTD=`"${R_HOME}/bin/R" CMD config CXX11XSTD` CXX="$(CXX1X) $(CXX1XSTD)"

Was writing a short R script to modify compile flags and saw this typo: Index: config =================================================================== --- config (revision 68217) +++ config (working copy) @@ -61,7 +61,7 @@ CXX1X C++ compiler command for C++11 code CXX1XSTD flag used to enable C++11 support CXX1XFLAGS C++11 compiler flags - CXX1XXPICFLAGS +

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

Hi Avraham, I tried with the patched version. The same error message. gcc -std=gnu99 -m64 -shared -s -mwindows -o R.dll R.def console.o dynload.o editor.o embeddedR.o extra.o malloc.o opt.o pager.o preferences.o psignal.o rhome.o rt_complete.o rui.o run.o shext.o sys-win32.o system.o dos_wglob.o dllversion.o ../main/libmain.a ../appl/libappl.a ../nmath/libnmath.a getline/gl.a

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

Hi Avraham, A quick question - I realized I did not have *Perl* installed. So I installed *ActiveState Perl* right now. Also I see I need *texinfo* and *texi2any*. I was able to installed *texinfo* from here: http://gnuwin32.sourceforge.net/packages/texinfo.htm. But not sure where to get *texi2any*. Can you guide me in this step? Regards, Indrajit On Fri, Feb 9, 2018 at 11:58 AM, Indrajit Sen

Hi Avraham, What a coincidence, I have been following this post of yours: https://www.avrahamadler.com/2013/10/24/an-openblas-based-rblas-for-windows-64-step-by-step/ Looks like this post is slightly older than what you have shared previously. It is strange that you did not get the attachments. I am pasting the contents of the MkRules.local here:

On Wed, Mar 11, 2015 at 1:23 PM, Hsiu-Khuern Tang <tangoh at gmail.com> wrote: > On Tue, Mar 10, 2015 at 10:47 PM, Avraham Adler <avraham.adler at gmail.com> wrote: >> On Wed, Mar 11, 2015 at 1:40 AM, Hsiu-Khuern Tang <tangoh at gmail.com> wrote: >>> On Tue, Mar 10, 2015 at 8:54 PM, Avraham Adler <avraham.adler at gmail.com> wrote: >>>>

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

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

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

Hi All, I am trying to compile R from source on a 64 bit Windows. I have downloaded and installed all the third party software as per the R - documentation. The compilation starts fine and after a while it stops with the following error message: D:/Rtools/mingw_64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.3/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lRgraphapp collect2.exe: error: ld

As far as I can see, and even test, R COMPILE CXXFLAGS="..." foo.c works just fine and passes the desired options on to gcc/g++. I have not been able to find a way to do this with R INSTALL foo*.tar.gz, other than by edting $RHOME/etc/Makeconf. While editing Makeconf is probably good enough for most users, it is not something I can do during (automated, unattended) builds of Debian

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

>>>>> CanisMaior writes: > 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

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`

On Fri, Feb 9, 2018 at 9:29 AM, Kenny Bell <kmbell56 at gmail.com> wrote: > I suggest that you work off the build process in the rwinlib repository so > you are starting from something that you know works and already incorporates > the set of dependencies you need. Hello, Kenny. For what it's worth I've been successfully building R+OpenBLAS on Windows64 since 2013, which

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

>>>>> 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

On 03/06/2017 6:31 AM, Vivek Sutradhara wrote: > Hi all, > I am having some problems in updating some packages from source. I start > with : > install.packages("Boom",lib="C:/RownLib",type="source") > > I get the following error message : Do you have multiple copies of cygwin1.dll? Duncan Murdoch > > * installing *source* package