Skip to content

Updated Windows toolchain

6 messages · Brian Ripley, Dan Tenenbaum, Uwe Ligges +1 more

#
CRAN Windows binary packages built for R-devel are now online, and Uwe's 
winbuilder has gained the ability to check source packages under R-devel.

Windows check results are available from
http://cran.r-project.org/bin/windows/contrib/checkSummaryWin.html
and in due course from the main CRAN check page.

There have been a few updates to the toolchain:

(i) It is now based on a beta of gcc 4.6.3, and so reports almost the 
same compilation warnings/errors as the CRAN check machines.

(ii) There are various bug-fixes to the toolchain: notably x^n and 
exp(x) use gradual underflow to denormal numbers rather than abrubtly 
underflowing to zero.

(iii) This is a 'multilib' toolchain: the compiler is named 'gcc.exe' 
for both architectures, selected by flag -m32 (the default) and -m64.
On 29/11/2011 07:56, Prof Brian Ripley wrote:

  
    
8 days later
#
Hello,

On Mon, Jan 9, 2012 at 12:28 AM, Prof Brian Ripley
<ripley at stats.ox.ac.uk> wrote:
Is the binary R-devel provided by CRAN built against this toolchain?
If it is, should I expect "R --arch x64 CMD config CC" to report
"gcc"? It still reports "x86_64-w64-mingw32-gcc" (R-devel 58077).

Also, I have the latest Rtools installed (VERSION.txt reads "Rtools
version 2.15.0.1911") and it is first on my PATH.

I expect "gcc --version" to report 4.6.3 but it still says 4.5.0.

"x86_64-w64-mingw32-gcc --version" reports 4.5.2.
"which gcc" reports "/cygdrive/c/Rtools215/MinGW/bin/gcc".

"which x86_64-w64-mingw32-gcc" reports
"/cygdrive/c/Rtools215/MinGW64/bin/x86_64-w64-mingw32-gcc".
Looks like to check gcc versions I should (instead of what I do above)
do simply "gcc --version". I imagine that "gcc -m32 --version" would
report the same thing as "gcc -m64 --version".

Thanks,
Dan
#
On 18.01.2012 01:09, Dan Tenenbaum wrote:
Actually "gcc -m64" and that is also the case when I just tried 
yesterday's CRAN version (which is 58125). I guess you have an older 
version of R in your PATH?
Yes, these are the version you need for old versions of R that are 
included in the Rtools, but it has a third gcc in subdir gcc-4.6.3 which 
is the one you should have first in the path in order to use the new 
toolchain.

Uwe Ligges
#
On 12-01-17 7:09 PM, Dan Tenenbaum wrote:
This is a temporary problem:  you want a different path for R-devel 
builds (one that puts the new compiler first) than for R 2.14.x builds.

I think Rtools should default to offering the path for 2.14.x, but 
perhaps it should offer the newer one as well.

What I do is have a bash alias that resets the path when I choose to 
work in a particular version, but Rtools doesn't include anything like this.

Duncan Murdoch
#
Hi Uwe,

2012/1/18 Uwe Ligges <ligges at statistik.tu-dortmund.de>:
I can't seem to download the latest R-devel. When I try and download this file:
http://cran.r-project.org/bin/windows/base/R-devel-win.exe

and install that, it turns out to be r58077. I've tried with two
different browsers and with curl, and with another CRAN mirror. I
tried this on a fresh machine with no previous R installations or
installer .exes lying around.

The web page
http://cran.r-project.org/bin/windows/base/rdevel.html
says I should be downloading r58133 but that doesn't seem to be the
case....can you look into this?
Good, I did not know about this directory. I will put it first in my
PATH after I am able to get a recent R-devel binary.
Thanks,
Dan
#
For the records: This rsync infelicity has been solved in the meantime.

Uwe Ligges
On 19.01.2012 02:03, Dan Tenenbaum wrote: