Updated Windows toolchain

[Prof Brian Ripley]

An updated toolchain is now being used for Windows' builds of R-devel:
details are in the R-admin manual and at
http://www.murdoch-sutherland.com/Rtools/ and
http://www.stats.ox.ac.uk/pub/Rtools/

Both 32- and 64-bit parts of the toolchain use v2.0.1 of the Mingw-w64
project's runtime and a beta of gcc 4.5.4: the Mingw.org project's
builds are no longer used.  This should mean that code which compiles
for 64-bit Windows also compiles for 32-bit Windows, and v.v. unless
code makes (incorrect but common) assumptions that pointers fit into
longs.

A very few packages will need modifications because they contain
declarations which clash with the headers in this toolchain: where we
are aware of problems the maintainers have been informed.

At DLL level different Windows' toolchains should be compatible: at C
level they mostly are but at C++ level they are pretty much
incompatible (so that for example GDAL has to be re-compiled for every
toolchain: and Rcpp users need to be careful to use only one toolchain
for Rcpp and their packages).  All the external software previously
made available (and more) is made available at
http://www.stats.ox.ac.uk/pub/Rtools .

The toolchain has support for OpenMP and pthreads: however OpenMP
support is not enabled by default in R (it is too slow to be much
use).  If you do make use of it in your packages, be aware that you
will need to ship the appropriate pthreads DLL(s).

It is expected that there will be several further minor updates prior
to the release of 2.15.0 in ca 4 months, but this step is the major
one.

--
Brian D. Ripley,                  [hidden email]
Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
University of Oxford,             Tel:  [phone] (self)
1 South Parks Road,                     [phone] (PA)
Oxford OX1 3TG, UK                Fax:  [phone]

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

[Prof Brian Ripley]

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:

> An updated toolchain is now being used for Windows' builds of R-devel:
> details are in the R-admin manual and at
> http://www.murdoch-sutherland.com/Rtools/ and
> http://www.stats.ox.ac.uk/pub/Rtools/
>
> Both 32- and 64-bit parts of the toolchain use v2.0.1 of the Mingw-w64
> project's runtime and a beta of gcc 4.5.4: the Mingw.org project's
> builds are no longer used. This should mean that code which compiles for
> 64-bit Windows also compiles for 32-bit Windows, and v.v. unless code
> makes (incorrect but common) assumptions that pointers fit into longs.
>
> A very few packages will need modifications because they contain
> declarations which clash with the headers in this toolchain: where we
> are aware of problems the maintainers have been informed.
>
> At DLL level different Windows' toolchains should be compatible: at C
> level they mostly are but at C++ level they are pretty much incompatible
> (so that for example GDAL has to be re-compiled for every toolchain: and
> Rcpp users need to be careful to use only one toolchain for Rcpp and
> their packages). All the external software previously made available
> (and more) is made available at http://www.stats.ox.ac.uk/pub/Rtools .
>
> The toolchain has support for OpenMP and pthreads: however OpenMP
> support is not enabled by default in R (it is too slow to be much use).
> If you do make use of it in your packages, be aware that you will need
> to ship the appropriate pthreads DLL(s).
>
> It is expected that there will be several further minor updates prior to
> the release of 2.15.0 in ca 4 months, but this step is the major one.
>

--
Brian D. Ripley,                  [hidden email]
Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
University of Oxford,             Tel:  [phone] (self)
1 South Parks Road,                     [phone] (PA)
Oxford OX1 3TG, UK                Fax:  [phone]

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

[Dan Tenenbaum]

On Mon, Nov 28, 2011 at 11:56 PM, Prof Brian Ripley
<[hidden email]> wrote:
> An updated toolchain is now being used for Windows' builds of R-devel:
> details are in the R-admin manual and at
> http://www.murdoch-sutherland.com/Rtools/ and
> http://www.stats.ox.ac.uk/pub/Rtools/
>

Thanks for the update.
I saw that
http://cran.r-project.org/bin/windows/Rtools/VERSION.txt
had the following contents:
Rtools version 2.15.0.1911

So I downloaded Rtools215.exe but when I installed it, the VERSION.txt
that was extracted read:
Rtools version 2.15.0.1908

...which is the same version I previously had installed.

Has the new version not propagated yet or is there some other issue?
Thanks,
Dan

> Both 32- and 64-bit parts of the toolchain use v2.0.1 of the Mingw-w64
> project's runtime and a beta of gcc 4.5.4: the Mingw.org project's builds
> are no longer used.  This should mean that code which compiles for 64-bit
> Windows also compiles for 32-bit Windows, and v.v. unless code makes
> (incorrect but common) assumptions that pointers fit into longs.
>
> A very few packages will need modifications because they contain
> declarations which clash with the headers in this toolchain: where we are
> aware of problems the maintainers have been informed.
>
> At DLL level different Windows' toolchains should be compatible: at C level
> they mostly are but at C++ level they are pretty much incompatible (so that
> for example GDAL has to be re-compiled for every toolchain: and Rcpp users
> need to be careful to use only one toolchain for Rcpp and their packages).
>  All the external software previously made available (and more) is made
> available at http://www.stats.ox.ac.uk/pub/Rtools .
>
> The toolchain has support for OpenMP and pthreads: however OpenMP support is
> not enabled by default in R (it is too slow to be much use).  If you do make
> use of it in your packages, be aware that you will need to ship the
> appropriate pthreads DLL(s).
>
> It is expected that there will be several further minor updates prior to the
> release of 2.15.0 in ca 4 months, but this step is the major one.
>
> --
> Brian D. Ripley,                  [hidden email]
> Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
> University of Oxford,             Tel:  [phone] (self)
> 1 South Parks Road,                     [phone] (PA)
> Oxford OX1 3TG, UK                Fax:  [phone]
>
> ______________________________________________
> [hidden email] mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

[Uwe Ligges-3]

On 10.01.2012 18:51, Dan Tenenbaum wrote:

> On Mon, Nov 28, 2011 at 11:56 PM, Prof Brian Ripley
> <[hidden email]>  wrote:
>> An updated toolchain is now being used for Windows' builds of R-devel:
>> details are in the R-admin manual and at
>> http://www.murdoch-sutherland.com/Rtools/ and
>> http://www.stats.ox.ac.uk/pub/Rtools/
>>
>
> Thanks for the update.
> I saw that
> http://cran.r-project.org/bin/windows/Rtools/VERSION.txt
> had the following contents:
> Rtools version 2.15.0.1911
>
> So I downloaded Rtools215.exe but when I installed it, the VERSION.txt
> that was extracted read:
> Rtools version 2.15.0.1908
>
> ...which is the same version I previously had installed.
>
> Has the new version not propagated yet or is there some other issue?

Looks like it failed. I just checked the original sources and CRAN and
the versions differ. We will take care soon.

Uwe

> Thanks,
> Dan
>
>
>> Both 32- and 64-bit parts of the toolchain use v2.0.1 of the Mingw-w64
>> project's runtime and a beta of gcc 4.5.4: the Mingw.org project's builds
>> are no longer used.  This should mean that code which compiles for 64-bit
>> Windows also compiles for 32-bit Windows, and v.v. unless code makes
>> (incorrect but common) assumptions that pointers fit into longs.
>>
>> A very few packages will need modifications because they contain
>> declarations which clash with the headers in this toolchain: where we are
>> aware of problems the maintainers have been informed.
>>
>> At DLL level different Windows' toolchains should be compatible: at C level
>> they mostly are but at C++ level they are pretty much incompatible (so that
>> for example GDAL has to be re-compiled for every toolchain: and Rcpp users
>> need to be careful to use only one toolchain for Rcpp and their packages).
>>   All the external software previously made available (and more) is made
>> available at http://www.stats.ox.ac.uk/pub/Rtools .
>>
>> The toolchain has support for OpenMP and pthreads: however OpenMP support is
>> not enabled by default in R (it is too slow to be much use).  If you do make
>> use of it in your packages, be aware that you will need to ship the
>> appropriate pthreads DLL(s).
>>
>> It is expected that there will be several further minor updates prior to the
>> release of 2.15.0 in ca 4 months, but this step is the major one.
>>
>> --
>> Brian D. Ripley,                  [hidden email]
>> Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
>> University of Oxford,             Tel:  [phone] (self)
>> 1 South Parks Road,                     [phone] (PA)
>> Oxford OX1 3TG, UK                Fax:  [phone]
>>
>> ______________________________________________
>> [hidden email] mailing list
>> https://stat.ethz.ch/mailman/listinfo/r-devel
>
> ______________________________________________
> [hidden email] mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

[Duncan Murdoch-2]

On 10/01/2012 12:51 PM, Dan Tenenbaum wrote:

> On Mon, Nov 28, 2011 at 11:56 PM, Prof Brian Ripley
> <[hidden email]>  wrote:
> >  An updated toolchain is now being used for Windows' builds of R-devel:
> >  details are in the R-admin manual and at
> >  http://www.murdoch-sutherland.com/Rtools/ and
> >  http://www.stats.ox.ac.uk/pub/Rtools/
> >
>
> Thanks for the update.
> I saw that
> http://cran.r-project.org/bin/windows/Rtools/VERSION.txt
> had the following contents:
> Rtools version 2.15.0.1911
>
> So I downloaded Rtools215.exe but when I installed it, the VERSION.txt
> that was extracted read:
> Rtools version 2.15.0.1908
>
> ...which is the same version I previously had installed.
>
> Has the new version not propagated yet or is there some other issue?

I see 2.15.0.1911 in the original of that file, but the file on the
Canadian mirror is the 1908 version (not current).  Not sure how that
happened; it might just be really bad luck in the update timing.

I'll wait until tomorrow to see if things clear themselves up automatically.

Duncan Murdoch

> Thanks,
> Dan
>
>
> >  Both 32- and 64-bit parts of the toolchain use v2.0.1 of the Mingw-w64
> >  project's runtime and a beta of gcc 4.5.4: the Mingw.org project's builds
> >  are no longer used.  This should mean that code which compiles for 64-bit
> >  Windows also compiles for 32-bit Windows, and v.v. unless code makes
> >  (incorrect but common) assumptions that pointers fit into longs.
> >
> >  A very few packages will need modifications because they contain
> >  declarations which clash with the headers in this toolchain: where we are
> >  aware of problems the maintainers have been informed.
> >
> >  At DLL level different Windows' toolchains should be compatible: at C level
> >  they mostly are but at C++ level they are pretty much incompatible (so that
> >  for example GDAL has to be re-compiled for every toolchain: and Rcpp users
> >  need to be careful to use only one toolchain for Rcpp and their packages).
> >    All the external software previously made available (and more) is made
> >  available at http://www.stats.ox.ac.uk/pub/Rtools .
> >
> >  The toolchain has support for OpenMP and pthreads: however OpenMP support is
> >  not enabled by default in R (it is too slow to be much use).  If you do make
> >  use of it in your packages, be aware that you will need to ship the
> >  appropriate pthreads DLL(s).
> >
> >  It is expected that there will be several further minor updates prior to the
> >  release of 2.15.0 in ca 4 months, but this step is the major one.
> >
> >  --
> >  Brian D. Ripley,                  [hidden email]
> >  Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
> >  University of Oxford,             Tel:  [phone] (self)
> >  1 South Parks Road,                     [phone] (PA)
> >  Oxford OX1 3TG, UK                Fax:  [phone]
> >
> >  ______________________________________________
> >  [hidden email] mailing list
> >  https://stat.ethz.ch/mailman/listinfo/r-devel
>
> ______________________________________________
> [hidden email] mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

[Dan Tenenbaum]

Hello,

On Mon, Jan 9, 2012 at 12:28 AM, Prof Brian Ripley
<[hidden email]> wrote:

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

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

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

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 29/11/2011 07:56, Prof Brian Ripley wrote:
>>
>> An updated toolchain is now being used for Windows' builds of R-devel:
>> details are in the R-admin manual and at
>> http://www.murdoch-sutherland.com/Rtools/ and
>> http://www.stats.ox.ac.uk/pub/Rtools/
>>
>> Both 32- and 64-bit parts of the toolchain use v2.0.1 of the Mingw-w64
>> project's runtime and a beta of gcc 4.5.4: the Mingw.org project's
>> builds are no longer used. This should mean that code which compiles for
>> 64-bit Windows also compiles for 32-bit Windows, and v.v. unless code
>> makes (incorrect but common) assumptions that pointers fit into longs.
>>
>> A very few packages will need modifications because they contain
>> declarations which clash with the headers in this toolchain: where we
>> are aware of problems the maintainers have been informed.
>>
>> At DLL level different Windows' toolchains should be compatible: at C
>> level they mostly are but at C++ level they are pretty much incompatible
>> (so that for example GDAL has to be re-compiled for every toolchain: and
>> Rcpp users need to be careful to use only one toolchain for Rcpp and
>> their packages). All the external software previously made available
>> (and more) is made available at http://www.stats.ox.ac.uk/pub/Rtools .
>>
>> The toolchain has support for OpenMP and pthreads: however OpenMP
>> support is not enabled by default in R (it is too slow to be much use).
>> If you do make use of it in your packages, be aware that you will need
>> to ship the appropriate pthreads DLL(s).
>>
>> It is expected that there will be several further minor updates prior to
>> the release of 2.15.0 in ca 4 months, but this step is the major one.
>>
>
>
> --
> Brian D. Ripley,                  [hidden email]
> Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
> University of Oxford,             Tel:  [phone] (self)
> 1 South Parks Road,                     [phone] (PA)
> Oxford OX1 3TG, UK                Fax:  [phone]
>
> ______________________________________________
> [hidden email] mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

[Uwe Ligges-3]

On 18.01.2012 01:09, Dan Tenenbaum wrote:

> Hello,
>
> On Mon, Jan 9, 2012 at 12:28 AM, Prof Brian Ripley
> <[hidden email]>  wrote:
>> 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.
>>
>
> 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).

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?

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

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

>> (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.
>
> 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 29/11/2011 07:56, Prof Brian Ripley wrote:
>>>
>>> An updated toolchain is now being used for Windows' builds of R-devel:
>>> details are in the R-admin manual and at
>>> http://www.murdoch-sutherland.com/Rtools/ and
>>> http://www.stats.ox.ac.uk/pub/Rtools/
>>>
>>> Both 32- and 64-bit parts of the toolchain use v2.0.1 of the Mingw-w64
>>> project's runtime and a beta of gcc 4.5.4: the Mingw.org project's
>>> builds are no longer used. This should mean that code which compiles for
>>> 64-bit Windows also compiles for 32-bit Windows, and v.v. unless code
>>> makes (incorrect but common) assumptions that pointers fit into longs.
>>>
>>> A very few packages will need modifications because they contain
>>> declarations which clash with the headers in this toolchain: where we
>>> are aware of problems the maintainers have been informed.
>>>
>>> At DLL level different Windows' toolchains should be compatible: at C
>>> level they mostly are but at C++ level they are pretty much incompatible
>>> (so that for example GDAL has to be re-compiled for every toolchain: and
>>> Rcpp users need to be careful to use only one toolchain for Rcpp and
>>> their packages). All the external software previously made available
>>> (and more) is made available at http://www.stats.ox.ac.uk/pub/Rtools .
>>>
>>> The toolchain has support for OpenMP and pthreads: however OpenMP
>>> support is not enabled by default in R (it is too slow to be much use).
>>> If you do make use of it in your packages, be aware that you will need
>>> to ship the appropriate pthreads DLL(s).
>>>
>>> It is expected that there will be several further minor updates prior to
>>> the release of 2.15.0 in ca 4 months, but this step is the major one.
>>>
>>
>>
>> --
>> Brian D. Ripley,                  [hidden email]
>> Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
>> University of Oxford,             Tel:  [phone] (self)
>> 1 South Parks Road,                     [phone] (PA)
>> Oxford OX1 3TG, UK                Fax:  [phone]
>>
>> ______________________________________________
>> [hidden email] mailing list
>> https://stat.ethz.ch/mailman/listinfo/r-devel
>
> ______________________________________________
> [hidden email] mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

[Duncan Murdoch-2]

On 12-01-17 7:09 PM, Dan Tenenbaum wrote:

> Hello,
>
> On Mon, Jan 9, 2012 at 12:28 AM, Prof Brian Ripley
> <[hidden email]>  wrote:
>> 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.
>>
>
> 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.

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

>
> 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".
>
>> (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.
>
> 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 29/11/2011 07:56, Prof Brian Ripley wrote:
>>>
>>> An updated toolchain is now being used for Windows' builds of R-devel:
>>> details are in the R-admin manual and at
>>> http://www.murdoch-sutherland.com/Rtools/ and
>>> http://www.stats.ox.ac.uk/pub/Rtools/
>>>
>>> Both 32- and 64-bit parts of the toolchain use v2.0.1 of the Mingw-w64
>>> project's runtime and a beta of gcc 4.5.4: the Mingw.org project's
>>> builds are no longer used. This should mean that code which compiles for
>>> 64-bit Windows also compiles for 32-bit Windows, and v.v. unless code
>>> makes (incorrect but common) assumptions that pointers fit into longs.
>>>
>>> A very few packages will need modifications because they contain
>>> declarations which clash with the headers in this toolchain: where we
>>> are aware of problems the maintainers have been informed.
>>>
>>> At DLL level different Windows' toolchains should be compatible: at C
>>> level they mostly are but at C++ level they are pretty much incompatible
>>> (so that for example GDAL has to be re-compiled for every toolchain: and
>>> Rcpp users need to be careful to use only one toolchain for Rcpp and
>>> their packages). All the external software previously made available
>>> (and more) is made available at http://www.stats.ox.ac.uk/pub/Rtools .
>>>
>>> The toolchain has support for OpenMP and pthreads: however OpenMP
>>> support is not enabled by default in R (it is too slow to be much use).
>>> If you do make use of it in your packages, be aware that you will need
>>> to ship the appropriate pthreads DLL(s).
>>>
>>> It is expected that there will be several further minor updates prior to
>>> the release of 2.15.0 in ca 4 months, but this step is the major one.
>>>
>>
>>
>> --
>> Brian D. Ripley,                  [hidden email]
>> Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
>> University of Oxford,             Tel:  [phone] (self)
>> 1 South Parks Road,                     [phone] (PA)
>> Oxford OX1 3TG, UK                Fax:  [phone]
>>
>> ______________________________________________
>> [hidden email] mailing list
>> https://stat.ethz.ch/mailman/listinfo/r-devel
>
> ______________________________________________
> [hidden email] mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

[Dan Tenenbaum]

Hi Uwe,

2012/1/18 Uwe Ligges <[hidden email]>:

>
>
> On 18.01.2012 01:09, Dan Tenenbaum wrote:
>>
>> Hello,
>>
>> On Mon, Jan 9, 2012 at 12:28 AM, Prof Brian Ripley
>> <[hidden email]>  wrote:
>>>
>>> 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.
>>>
>>
>> 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).
>
>
> 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?
>

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?

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

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

>
> Uwe Ligges
>
>
>
>
>
>>> (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.
>>
>>
>> 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 29/11/2011 07:56, Prof Brian Ripley wrote:
>>>>
>>>>
>>>> An updated toolchain is now being used for Windows' builds of R-devel:
>>>> details are in the R-admin manual and at
>>>> http://www.murdoch-sutherland.com/Rtools/ and
>>>> http://www.stats.ox.ac.uk/pub/Rtools/
>>>>
>>>> Both 32- and 64-bit parts of the toolchain use v2.0.1 of the Mingw-w64
>>>> project's runtime and a beta of gcc 4.5.4: the Mingw.org project's
>>>> builds are no longer used. This should mean that code which compiles for
>>>> 64-bit Windows also compiles for 32-bit Windows, and v.v. unless code
>>>> makes (incorrect but common) assumptions that pointers fit into longs.
>>>>
>>>> A very few packages will need modifications because they contain
>>>> declarations which clash with the headers in this toolchain: where we
>>>> are aware of problems the maintainers have been informed.
>>>>
>>>> At DLL level different Windows' toolchains should be compatible: at C
>>>> level they mostly are but at C++ level they are pretty much incompatible
>>>> (so that for example GDAL has to be re-compiled for every toolchain: and
>>>> Rcpp users need to be careful to use only one toolchain for Rcpp and
>>>> their packages). All the external software previously made available
>>>> (and more) is made available at http://www.stats.ox.ac.uk/pub/Rtools .
>>>>
>>>> The toolchain has support for OpenMP and pthreads: however OpenMP
>>>> support is not enabled by default in R (it is too slow to be much use).
>>>> If you do make use of it in your packages, be aware that you will need
>>>> to ship the appropriate pthreads DLL(s).
>>>>
>>>> It is expected that there will be several further minor updates prior to
>>>> the release of 2.15.0 in ca 4 months, but this step is the major one.
>>>>
>>>
>>>
>>> --
>>> Brian D. Ripley,                  [hidden email]
>>> Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
>>> University of Oxford,             Tel:  [phone] (self)
>>> 1 South Parks Road,                     [phone] (PA)
>>> Oxford OX1 3TG, UK                Fax:  [phone]
>>>
>>> ______________________________________________
>>> [hidden email] mailing list
>>> https://stat.ethz.ch/mailman/listinfo/r-devel
>>
>>
>> ______________________________________________
>> [hidden email] mailing list
>> https://stat.ethz.ch/mailman/listinfo/r-devel

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

[Uwe Ligges-3]

For the records: This rsync infelicity has been solved in the meantime.

Uwe Ligges

On 19.01.2012 02:03, Dan Tenenbaum wrote:

> Hi Uwe,
>
> 2012/1/18 Uwe Ligges<[hidden email]>:
>>
>>
>> On 18.01.2012 01:09, Dan Tenenbaum wrote:
>>>
>>> Hello,
>>>
>>> On Mon, Jan 9, 2012 at 12:28 AM, Prof Brian Ripley
>>> <[hidden email]>    wrote:
>>>>
>>>> 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.
>>>>
>>>
>>> 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).
>>
>>
>> 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?
>>
>
>
> 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?
>
>
>>
>>
>>
>>> 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".
>>
>>
>>
>> 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.
>
>
> 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
>
>
>
>
>>
>> Uwe Ligges
>>
>>
>>
>>
>>
>>>> (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.
>>>
>>>
>>> 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 29/11/2011 07:56, Prof Brian Ripley wrote:
>>>>>
>>>>>
>>>>> An updated toolchain is now being used for Windows' builds of R-devel:
>>>>> details are in the R-admin manual and at
>>>>> http://www.murdoch-sutherland.com/Rtools/ and
>>>>> http://www.stats.ox.ac.uk/pub/Rtools/
>>>>>
>>>>> Both 32- and 64-bit parts of the toolchain use v2.0.1 of the Mingw-w64
>>>>> project's runtime and a beta of gcc 4.5.4: the Mingw.org project's
>>>>> builds are no longer used. This should mean that code which compiles for
>>>>> 64-bit Windows also compiles for 32-bit Windows, and v.v. unless code
>>>>> makes (incorrect but common) assumptions that pointers fit into longs.
>>>>>
>>>>> A very few packages will need modifications because they contain
>>>>> declarations which clash with the headers in this toolchain: where we
>>>>> are aware of problems the maintainers have been informed.
>>>>>
>>>>> At DLL level different Windows' toolchains should be compatible: at C
>>>>> level they mostly are but at C++ level they are pretty much incompatible
>>>>> (so that for example GDAL has to be re-compiled for every toolchain: and
>>>>> Rcpp users need to be careful to use only one toolchain for Rcpp and
>>>>> their packages). All the external software previously made available
>>>>> (and more) is made available at http://www.stats.ox.ac.uk/pub/Rtools .
>>>>>
>>>>> The toolchain has support for OpenMP and pthreads: however OpenMP
>>>>> support is not enabled by default in R (it is too slow to be much use).
>>>>> If you do make use of it in your packages, be aware that you will need
>>>>> to ship the appropriate pthreads DLL(s).
>>>>>
>>>>> It is expected that there will be several further minor updates prior to
>>>>> the release of 2.15.0 in ca 4 months, but this step is the major one.
>>>>>
>>>>
>>>>
>>>> --
>>>> Brian D. Ripley,                  [hidden email]
>>>> Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
>>>> University of Oxford,             Tel:  [phone] (self)
>>>> 1 South Parks Road,                     [phone] (PA)
>>>> Oxford OX1 3TG, UK                Fax:  [phone]
>>>>
>>>> ______________________________________________
>>>> [hidden email] mailing list
>>>> https://stat.ethz.ch/mailman/listinfo/r-devel
>>>
>>>
>>> ______________________________________________
>>> [hidden email] mailing list
>>> https://stat.ethz.ch/mailman/listinfo/r-devel
>
> ______________________________________________
> [hidden email] mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

[Dan Tenenbaum]

2012/1/19 Uwe Ligges <[hidden email]>:
> For the records: This rsync infelicity has been solved in the meantime.

I can confirm that it works; just downloaded r58140.
Thanks!
Dan

>
> Uwe Ligges
>
>
> On 19.01.2012 02:03, Dan Tenenbaum wrote:
>>
>> Hi Uwe,
>>
>> 2012/1/18 Uwe Ligges<[hidden email]>:
>>>
>>>
>>>
>>> On 18.01.2012 01:09, Dan Tenenbaum wrote:
>>>>
>>>>
>>>> Hello,
>>>>
>>>> On Mon, Jan 9, 2012 at 12:28 AM, Prof Brian Ripley
>>>> <[hidden email]>    wrote:
>>>>>
>>>>>
>>>>> 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.
>>>>>
>>>>
>>>> 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).
>>>
>>>
>>>
>>> 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?
>>>
>>
>>
>> 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?
>>
>>
>>>
>>>
>>>
>>>> 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".
>>>
>>>
>>>
>>>
>>> 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.
>>
>>
>>
>> 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
>>
>>
>>
>>
>>>
>>> Uwe Ligges
>>>
>>>
>>>
>>>
>>>
>>>>> (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.
>>>>
>>>>
>>>>
>>>> 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 29/11/2011 07:56, Prof Brian Ripley wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> An updated toolchain is now being used for Windows' builds of R-devel:
>>>>>> details are in the R-admin manual and at
>>>>>> http://www.murdoch-sutherland.com/Rtools/ and
>>>>>> http://www.stats.ox.ac.uk/pub/Rtools/
>>>>>>
>>>>>> Both 32- and 64-bit parts of the toolchain use v2.0.1 of the Mingw-w64
>>>>>> project's runtime and a beta of gcc 4.5.4: the Mingw.org project's
>>>>>> builds are no longer used. This should mean that code which compiles
>>>>>> for
>>>>>> 64-bit Windows also compiles for 32-bit Windows, and v.v. unless code
>>>>>> makes (incorrect but common) assumptions that pointers fit into longs.
>>>>>>
>>>>>> A very few packages will need modifications because they contain
>>>>>> declarations which clash with the headers in this toolchain: where we
>>>>>> are aware of problems the maintainers have been informed.
>>>>>>
>>>>>> At DLL level different Windows' toolchains should be compatible: at C
>>>>>> level they mostly are but at C++ level they are pretty much
>>>>>> incompatible
>>>>>> (so that for example GDAL has to be re-compiled for every toolchain:
>>>>>> and
>>>>>> Rcpp users need to be careful to use only one toolchain for Rcpp and
>>>>>> their packages). All the external software previously made available
>>>>>> (and more) is made available at http://www.stats.ox.ac.uk/pub/Rtools .
>>>>>>
>>>>>> The toolchain has support for OpenMP and pthreads: however OpenMP
>>>>>> support is not enabled by default in R (it is too slow to be much
>>>>>> use).
>>>>>> If you do make use of it in your packages, be aware that you will need
>>>>>> to ship the appropriate pthreads DLL(s).
>>>>>>
>>>>>> It is expected that there will be several further minor updates prior
>>>>>> to
>>>>>> the release of 2.15.0 in ca 4 months, but this step is the major one.
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Brian D. Ripley,                  [hidden email]
>>>>> Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
>>>>> University of Oxford,             Tel:  [phone] (self)
>>>>> 1 South Parks Road,                     [phone] (PA)
>>>>> Oxford OX1 3TG, UK                Fax:  [phone]
>>>>>
>>>>> ______________________________________________
>>>>> [hidden email] mailing list
>>>>> https://stat.ethz.ch/mailman/listinfo/r-devel
>>>>
>>>>
>>>>
>>>> ______________________________________________
>>>> [hidden email] mailing list
>>>> https://stat.ethz.ch/mailman/listinfo/r-devel
>>
>>
>> ______________________________________________
>> [hidden email] mailing list
>> https://stat.ethz.ch/mailman/listinfo/r-devel

______________________________________________
[hidden email] mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel