On 14 December 2017 at 03:04, brodie gaslam via R-package-devel wrote:
| This leads me to think that it is (maybe) possible that this is an issue with
the latest version of the check tool?
Which is what I tried to explain to Inaki when he first filed on as an Rcpp
issue ticket: Sometimes you nee
These are not check errors, but indeed a bug in the check tool:
https://github.com/wch/r-source/commit/c063350799e2209afe1c5b23915ee7b9a1606652#diff-4882a8c8e173bda109ed98da485e1428R8640
It has been fixed, so next R-devel build should be fine.
Gabor
On Thu, Dec 14, 2017 at 2:04 AM, brodie gaslam
--- Begin Message ---
I too am seeing the same failure in my package. It does not contain any
#pragma directives, and it doesn't have any dependencies to other compiled
packages.
Poking around through the CRAN checks I've found other packages with C compiled
code displaying the same error on th
On 14 December 2017 at 00:58, Iñaki Úcar wrote:
| Hi all,
|
| Three days ago, Patrick Perry posted the following on R-devel:
|
| 2017-12-11 16:32 GMT+01:00 Patrick Perry :
| > A recent change to r-devel causes an R CMD check warning when a C file
| > includes a "#pragma GCC diagnostic ignored" p
Hi all,
Three days ago, Patrick Perry posted the following on R-devel:
2017-12-11 16:32 GMT+01:00 Patrick Perry :
> A recent change to r-devel causes an R CMD check warning when a C file
> includes a "#pragma GCC diagnostic ignored" pragma:
> https://github.com/wch/r-source/commit/b76c8fd355a0f5b
This confusion was caused by the CRAN team, who wrote you (Meabh
McCurdy) a message about adding missing copyright holders that should
have gone to the maintainer of anotehr submission.
Our apologies.
Best,
Uwe Ligges
On 12.12.2017 16:06, Dirk Eddelbuettel wrote:
On 12 December 2017 at 1
