Absolutely; this is a complicated and frustrating procedure, and we
owe Jeoren and all our gratitude!
Avi
On Tue, Apr 28, 2020 at 3:37 PM Gabriel Becker wrote:
>
> Huge thanks to you (Jeroen) and R-core for doing this.
>
> I wasn't involved with this directly but I know it was a pretty
Huge thanks to you (Jeroen) and R-core for doing this.
I wasn't involved with this directly but I know it was a pretty seriously
heavy list so well done all around!
~G
On Tue, Apr 28, 2020, 11:04 AM Hervé Pagès wrote:
> Thanks Jeroen!
>
> > On Tue, Apr 7, 2020 at 6:07 PM Kevin Ushey
Thanks Jeroen!
On Tue, Apr 7, 2020 at 6:07 PM Kevin Ushey wrote:
Regardless, I would like to thank R core, CRAN, and Jeroen for all of
the time that has gone into creating and validating this new
toolchain. This is arduous work at an especially arduous time, so I'd
like to voice my
Hevré told me that people from Bioconductor and possibly others are
keeping an eye on this thread so it would be good to post a note here
too.
As of version 4.0.0, the official R for Windows and binary packages
provided via CRAN are built with gcc-8.3.0 from rtools40, as shown in
the CRAN check
That's great to see, although I suspect it's still a speculative
change and could be backed out if any non-trivial issues were
encountered.
Regardless, I would like to thank R core, CRAN, and Jeroen for all of
the time that has gone into creating and validating this new
toolchain. This is arduous
There appears to have been some progress on this matter:
-Note that @command{g++} 4.9.x (as used for @R{} on Windows up to 3.6.x)
+Note that @command{g++} 4.9.x (as used on Windows prior to @R{} 4.0.0)
See SVN commit r78169 titled 'anticipate change in Windows toolchain', or the
mirrored git
Jeroen,
Sorry, I was unclear. I'm not arguing against switching tot the new windows
tool chain. Without being involved or knowing the details of any
remaining difficulties, I am de facto for that.
I was specifically responding to the prospect of R packages moving to
directly rely on c++17 this
On Mon, Apr 6, 2020 at 9:39 AM Gabriel Becker wrote:
>
> Hi Kevin,
>
> On Wed, Apr 1, 2020 at 9:36 PM Kevin Ushey wrote:
>
> > Hello,
> >
> > FWIW, I'm excited at the prospect at seeing a new toolchain for
> > Windows, since it would imply support for C++17 and so it would become
> > easier for
On Mon, Apr 6, 2020 at 9:15 AM Prof Brian Ripley wrote:
>
> On 02/04/2020 05:35, Kevin Ushey wrote:
> > Hello,
> >
> > Has a decision been made yet as to whether R 4.0.0 on Windows is going
> > to be built using the new gcc8 toolchain (described at
> >
Hi Kevin,
On Wed, Apr 1, 2020 at 9:36 PM Kevin Ushey wrote:
> Hello,
>
> FWIW, I'm excited at the prospect at seeing a new toolchain for
> Windows, since it would imply support for C++17 and so it would become
> easier for CRAN packages to depend on the newer C++ standard.
>
One thing to keep
On 02/04/2020 05:35, Kevin Ushey wrote:
Hello,
Has a decision been made yet as to whether R 4.0.0 on Windows is going
to be built using the new gcc8 toolchain (described at
https://cran.r-project.org/bin/windows/testing/rtools40.html)?
Short answer: 'no'.
From the sidelines, I can see that
Also related to this, I tried looking in the archives and couldn't find a
previous discussion, was gcc 8.1 chosen over gcc 9 because mingw-w64 does
not support v9 yet? It looks like 9 is the first version that makes C++17
support non-experimental
https://gcc.gnu.org/gcc-9/changes.html
Regards,
Hello,
Has a decision been made yet as to whether R 4.0.0 on Windows is going
to be built using the new gcc8 toolchain (described at
https://cran.r-project.org/bin/windows/testing/rtools40.html)?
>From the sidelines, I can see that the toolchain is being used to
build and test packages on CRAN;
13 matches
Mail list logo
