gt; > From: "Kasper Daniel Hansen"
> > To: "Dan Tenenbaum"
> > Cc: "bioc-devel"
> > Sent: Thursday, March 31, 2016 5:52:36 PM
> > Subject: Re: [Bioc-devel] new Windows toolchain for R-3.3.0
>
> > There are tons of errors with affxpars
need a VM.
Dan
- Original Message -
> From: "Kasper Daniel Hansen"
> To: "Dan Tenenbaum"
> Cc: "bioc-devel"
> Sent: Thursday, March 31, 2016 5:52:36 PM
> Subject: Re: [Bioc-devel] new Windows toolchain for R-3.3.0
> There are tons o
There are tons of errors with affxparser (as mentioned on the toolchain
setup documentation). However, (almost) all of them seems to be errors in
header files included with mingq. The first one is pasted below, and the
error (seems to be) in the minwindef.h header file. Given that this is a
new
Hello all,
R is planning to use a new Windows toolchain (known as Rtools33) for the
soon-to-be-released R-3.3.0.
This toolchain will use gcc/g++ 4.9.3 (an upgrade from 4.6.3).
We expect CRAN packages for Windows using this toolchain in a few days.
We are currently building the devel branch of B
An update on this: for the time being, the R folks have decided to roll back to
a toolchain based once more on gcc 4.6.3.
They plan for the new (gcc 4.9.2-based) toolchain to be available in
conjunction with R 3.2.1 sometime later this year.
More information is here:
http://lists.r-forge.r-pro
A quick update: Sounds like there is a strong possibility that the toolchain
will be rolled back to use the older gcc and avoid all these issues.
Alternatively, some of the issues may be fixed in the next few days.
So, please do NOT make any changes to your packages in response to these issues
Hi all,
This is relevant (and possibly quite important) to all package maintainers
whose packages contain C or C++ code, or depend on one that does.
A new toolchain is available for building R and R packages on Windows. This
toolchain uses gcc 4.9.2 whereas the old one used gcc 4.6.3.
Another
