search for: binpref64

...ingw_$(WIN)/bin/" > > I think this will do the job. Thanks, that indeed did the trick. May I suggest that this hint be also included in "REMAINING TASKS" section of the file Rtools.txt that is part of the Rtools distribution? The R installation manual does mention BINPREF and BINPREF64 but I missed that part... Peter

...>> I think this will do the job. > > Thanks, that indeed did the trick. May I suggest that this hint be > also included in "REMAINING TASKS" section of the file Rtools.txt that > is part of the Rtools distribution? The R installation manual does > mention BINPREF and BINPREF64 but I missed that part... Glad it worked. Actually BINPREF64 only exists when building R itself. For the R user there is no BINPREF64. There is only BINPREF which has to point to a 32bit gcc when R runs in 32bit, and a 64bit compiler when R runs in 64bit. But if you compile R packages you need bot...

Dear R People: Hope you're having a nice Saturday. I'm trying to compile R-2.13.1 from source on Windows 7 (64 bit). I've been able to compile on a 32 bit without any problems. I changed my BINPREF64, WIN, DEFS_W64 in MkRules.local and did the usual stuff with the jpeg, etc. But things are jogging along and I get the following: Makefile.win:28: ../../../../etc/x64/Makeconf: No such file or directory Has anyone run across this, please? Should I possibly just switch back to 32 bit, do you thi...

...e toolchain's bin directory is not in your path, set this to the path # (including the trailing /, and use / not \). # TOOL_PATH = # for other toolchains leave these empty and set the more detailed options below # With the recommended gcc 4.9.3 toolchain or another toolchain, set # BINPREF and BINPREF64 (below) to the respective bin directories. # Include the trailing /, and use / not \. # Do this in the more detailed options below # Set this to 32 or 64 WIN = 64 ### BEGIN more detailed options # Some of the toolchains have prefixes for e.g. ar, gcc. # This can also be used to give the full path...

...as I suppose according to uncorrect x32 - x64 configuration (it links 32bits external libs to 64bits object files) I would be very greatful if you could help me to compile R, please. Thank you very much !! ============== MkRules.local ============== G_FLAG=-gdwarf-2 LEA_MALLOC=YES USE_ATLAS=NO BINPREF64 = C:/Rtools/gcc-4.6.3/bin/ WIN = 64 BUILD_HTML = NO MIKTEX = TRUE EOPTS=-mtune=native OPENMP = -fopenmp PTHREAD = -pthread

...s.dist to MkRules.local and apply the following patch: -------------------------------------------------- --- MkRules.local 2015-03-02 13:57:38.601903500 -0800 +++ MkRules.local 2015-03-06 10:43:44.708581800 -0800 @@ -52,6 +52,7 @@ # BINPREF = # prefix for 64-bit: path or x86_64-w64-mingw32- # BINPREF64 = x86_64-w64-mingw32- +BINPREF64 = # Others use a -m64 or -m32 option to select architectures # M_ARCH = @@ -64,6 +65,7 @@ # 32- or 64-bit Windows? # WIN = 32 +WIN = 64 # The gcc 4.9.2 64 bit toolchain is set up for the 'medium code' model and needs # to remove the .refptr entries...

...in your path, set this to the > path > # (including the trailing /, and use / not \). > # TOOL_PATH = > # for other toolchains leave these empty and set the more detailed options > below > > # With the recommended gcc 4.9.3 toolchain or another toolchain, set > # BINPREF and BINPREF64 (below) to the respective bin directories. > # Include the trailing /, and use / not \. > # Do this in the more detailed options below > # Set this to 32 or 64 > WIN = 64 > > > ### BEGIN more detailed options > # Some of the toolchains have prefixes for e.g. ar, gcc. > #...

...ng patch: > > -------------------------------------------------- > > --- MkRules.local 2015-03-02 13:57:38.601903500 -0800 > +++ MkRules.local 2015-03-06 10:43:44.708581800 -0800 > @@ -52,6 +52,7 @@ > # BINPREF = > # prefix for 64-bit: path or x86_64-w64-mingw32- > # BINPREF64 = x86_64-w64-mingw32- > +BINPREF64 = > > # Others use a -m64 or -m32 option to select architectures > # M_ARCH = > @@ -64,6 +65,7 @@ > > # 32- or 64-bit Windows? > # WIN = 32 > +WIN = 64 > > # The gcc 4.9.2 64 bit toolchain is set up for the 'medium code...

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

...it Windows with the released R 2.12.1. The error is the same when using R-patched_2010-12-27_r53886. I'm sorry if this is something obvious, but I believe I've followed the instructions carefully and do not know what I might be doing wrong. As far as I can tell I should not need to modify BINPREF64 or SYMPAT64 if use Rtools 2.12. Is that correct? A description of the set up and build process follows. Best regards, Mike. ---------------------------------- Context ---------------------------------- Using Rtools212.exe, with MiKTeX, no static HTML help, and no installer build. Everything i...

...ptions below ### BEGIN more detailed options # Some of the toolchains have prefixes for e.g. ar, gcc. # This can also be used to give the full path to the compiler, # including a trailing / . # prefix for 32-bit: path or i686-w64-mingw32- BINPREF = # prefix for 64-bit: path or x86_64-w64-mingw32- BINPREF64 = x86_64-w64-mingw32- # Others use a -m64 or -m32 option to select architectures M_ARCH = # and for as (--32 or --64) AS_ARCH = # and for windres (-F pe-i386 or pe-x86-64) RC_ARCH = # and for dlltool ("-m i386 --as-flags --32" vs "-m i386:x86-64 --as-flags --64") DT_ARCH = # 3...

On Mon, Mar 9, 2015 at 3:50 AM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 08/03/2015 10:02 PM, Hsiu-Khuern Tang wrote: >> Hi, >> >> [This is a follow-up to the "New version of Rtools for Windows" thread >> in January, but I just subscribed and don't know how to reply to an >> old thread -- my apologies.] > > I am planning to

Hi all, I'm trying to set up the Windows Rtools toolset for building packages with compiled code. I installed for Windows R-3.4.3 from CRAN and installed Rtools-3.4 in a custom location M:\R\R-3.4.3 and M:\R\Rtools-3.4 Following the instructions, in shell, I set Path=M:\R\Rtools-3.4\bin;M:\R\Rtools-3.4\gcc-4.6.3\bin;M:\R\R-3.4.3\bin;... (the ... are other paths irrelevant for R/Rtools).

...code, as it should. >> >> yes, lto build's speed gain is very impressive. >> > > >I apologize for my ignorance, but how would I do that? I tried by >changing the following in src/gnuwin32/MkRules.local: > ># prefix for 64-bit: path or x86_64-w64-mingw32- >BINPREF64 = x86_64-w64-mingw32-gcc- > >I added the gcc- as the suffix there, but I guess that is insufficient >as I still get the following error using 4.9.2: > >windres -F pe-x86-64? -I../include -i dllversion.rc -o dllversion.o >gcc -std=gnu99 -m64 -shared -s -mwindows -o R.dll R.def cons...

...to optimizes away the stack probing code, as it should. > > yes, lto build's speed gain is very impressive. > > I apologize for my ignorance, but how would I do that? I tried by changing the following in src/gnuwin32/MkRules.local: # prefix for 64-bit: path or x86_64-w64-mingw32- BINPREF64 = x86_64-w64-mingw32-gcc- I added the gcc- as the suffix there, but I guess that is insufficient as I still get the following error using 4.9.2: windres -F pe-x86-64 -I../include -i dllversion.rc -o dllversion.o gcc -std=gnu99 -m64 -shared -s -mwindows -o R.dll R.def console.o dynload.o editor.o...

...t;> path >> # (including the trailing /, and use / not \). >> # TOOL_PATH = >> # for other toolchains leave these empty and set the more detailed options >> below >> >> # With the recommended gcc 4.9.3 toolchain or another toolchain, set >> # BINPREF and BINPREF64 (below) to the respective bin directories. >> # Include the trailing /, and use / not \. >> # Do this in the more detailed options below >> # Set this to 32 or 64 >> WIN = 64 >> >> >> ### BEGIN more detailed options >> # Some of the toolchains have pr...