>
> Now that I think about it some more, I think I can do the following:
>
> 1. In the DESCRIPTION file, remove "SystemRequirements: C++11". I believe
> this field is used only for R CMD check, not for actually installing
> packages. CRAN only runs R CMD check on r-oldrel, r-release, and r-devel,
On Mon, Feb 6, 2023 at 6:44 PM Duncan Murdoch
wrote:
> On 06/02/2023 3:46 p.m., Winston Chang wrote:
> > I recently submitted a package to CRAN with "SystemRequirements: C++11".
> > This raises the following NOTE on R-devel, and I was asked to fix and
> >
I recently submitted a package to CRAN with "SystemRequirements: C++11".
This raises the following NOTE on R-devel, and I was asked to fix and
resubmit:
* checking C++ specification ... NOTE
Specified C++11: please update to current default of C++17
If I understand correctly, I have two
It looks like hacSIM imports pegas, which imports adegenet, which imports dplyr.
-Winston
On Fri, May 17, 2019 at 11:04 AM Jarrett Phillips
wrote:
>
> Hello,
>
> On submitting an update of my R package (HACSim), checks fail on
> r-release-windows-ix86+x86_64
>
On Sat, Mar 30, 2019 at 5:06 PM Gábor Csárdi wrote:
> I think this is temporary and will go away once R-devel is built with
> this:
> https://github.com/wch/r-source/commit/9542c3215a8f8cfee4a313b6c2fd03320e38e1de
>
>
Before that commit (76285), I was getting a different error when I
submitted a
On Windows I have a package that builds just fine with any recent version
of Rtools. But on win-builder it fails because the version of GNU make on
that machine does not support if-else syntax. Support for this syntax was
added in GNU make 3.81, which was released in 2006. The version of Rtools
on
