similar to: trouble compiling R-patched from source on Windows 64 bit

Dear R People: I'm trying to compile R-2.15.0 on a 64 bit Windows machine. However, I'm getting the following error: c:\R64\R-2.15.0\src\gnuwin32>set TMPDIR=c:\temp set TMPDIR=c:\temp c:\R64\R-2.15.0\src\gnuwin32>make all recommended make all recommended make[1]: `MkRules' is up to date. make[4]: Nothing to be done for `svnonly'. installing C headers make[2]: Nothing to

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

Dear R People: I'm installing R 2-.15.1 on a Windows 32 bit machine from source. I'm getting a strange error about init.win (please see below) Does this look familiar to anyone, please? Thanks, Erin Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. c:\R\R-2.15.1\src\gnuwin32>make all recommended make all recommended make[1]:

On Thu Jan 9 2014 03:47 Henrik Bengtsson wrote: > This is is an issue that bugged me for a while. I encountered a year > ago (April 2012) when I first tried to build R from source on Windows. > I never figured out what the solution is or if I'm doing something > wrong myself (but I have found a tedious workaround). I'm still on > the same Windows 7 Ultimate machine with

This is is an issue that bugged me for a while. I encountered a year ago (April 2012) when I first tried to build R from source on Windows. I never figured out what the solution is or if I'm doing something wrong myself (but I have found a tedious workaround). I'm still on the same Windows 7 Ultimate machine with NTFS, but I now made sure I started from scratch so I have a completely

> Yes, the nightly build is broken in a similar, but different way. See below. > Both seem to be readline related, so Frederick Eaton's patches, which Martin committed yesterday are the likely culprit. I had actually tested them and things seemed to work, but it was on a different machine and not a completely clean build. Indeed a problem. I'm pretty sure that RL_UNSETSTATE()

Oh, I forgot to mention that besides setting AR, RANLIB and the stack probing fix, you also need a very up to date binutils. 2.25 was out in december. Even with that , if you linker's default is not what you are compiling for (i.e. a multiarch toolchain), you need to set GNUTARGET also, i.e. -m32/-m64 is not enough. Some fix to autodetect non-default targets went in after christmas before the

Very timely, as this is how I got into the problem I posted about earlier; maybe some of the problems I ran into will mean more to the you and the experts on this thread, Dr. Murdoch.For reference, I run Windows 7 64bit, and I am trying to build a 64 bit version of R-3.1.2. As we discussed offline, Dr. Murdoch, I've been trying to build R using more recent tools than GCC4.6.3 prerelease.

Dear R-devel, The latest version of R-devel (05-17) is throwing an error for me when building on OS X (v 10.11.4): making Rembedded.d from Rembedded.c making dynload.d from dynload.c making system.d from system.c making sys-unix.d from sys-unix.c making sys-std.d from sys-std.c making X11.d from X11.c clang -I. -I../../src/include -I../../src/include -I/usr/local/include -DHAVE_CONFIG_H

On Thu, Jan 8, 2015 at 10:48 AM, Hin-Tak Leung <htl10 at users.sourceforge.net> wrote: > > The r.dll crash is easy - you need to be using gcc-ar for ar, and gcc-ranlib for ranlib. I also posted a patch to fix the check failure for stack probing, as lto optimizes away the stack probing code, as it should. > > yes, lto build's speed gain is very impressive. > > I

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

Dear All, I have been trying to compile a package for windows that we have written. Since R version 3.0.0 the package doesn't compile any more. (On Linux the package compiles without errors). The error specifically says: gcc -m32 -I"C:/PROGRA~1/R/R-30~1.0/include" -DNDEBUG -I"d:/RCompile/CRANpkg/extralibs64/local/include" -O3 -Wall -std=gnu99 -mtune=core2 -c

The r.dll crash is easy - you need to be using gcc-ar for ar, and gcc-ranlib for ranlib. I also posted a patch to fix the check failure for stack probing, as lto optimizes away the stack probing code, as it should. yes, lto build's speed gain is very impressive. ------------------------------ On Thu, Jan 8, 2015 2:01 PM GMT Henric Winell wrote: >On 2015-01-08 14:18, Avraham Adler

> On 18 May 2016, at 18:54 , Martin Maechler <maechler at stat.math.ethz.ch> wrote: > > >> Yes, the nightly build is broken in a similar, but different way. See below. >> Both seem to be readline related, so Frederick Eaton's patches, which Martin committed yesterday are the likely culprit. I had actually tested them and things seemed to work, but it was on a

On Wed, 2015-09-02 at 20:49 +0200, arnaud gaboury wrote: > On Wed, Sep 2, 2015 at 7:35 PM, arnaud gaboury <arnaud.gaboury at gmail.com> wrote: > > 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 > >

Hello, I was trying to build R from source on Windows XP. I installed software which are mentioned from the follow web page http://www.murdoch-sutherland.com/Rtools/ (Last accessed on Nov. 13th, 2006) . Unfortunately, I got error messages whenever I run 'make all recommended' without modifying 'MkRules' file. I have removed software and reinstalled them several times but I still

Yes, the nightly build is broken in a similar, but different way. See below. Both seem to be readline related, so Frederick Eaton's patches, which Martin committed yesterday are the likely culprit. I had actually tested them and things seemed to work, but it was on a different machine and not a completely clean build. -pd ..... ranlib: file: libR.a(printf.o) has no symbols gcc

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

Hi, I tried to compile R-2.10.0 src on 64 bit window. After install Rtools and wingw-w64 compiler and put it the first of my PATH variable, but i got the following error when i tried to compile. Anything I missed? thank you. x86_64-w64-mingw32-gcc -std=gnu99 -I../include -I. -I../extra -DHAVE_CONFIG_H -D R_DLL_BUILD -O3 -Wall -pedantic -DR_ARCH='"x64"' -c malloc.c -o

On Tue, Feb 13, 2018 at 12:22 PM, Indrajit Sen Gupta <indrajitsg at gmail.com> wrote: > 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