I had the same this week. Yes, you should answer these are false negative results.
KR, David De : R-package-devel <r-package-devel-boun...@r-project.org> de la part de Pepijn de Vries <pepijn.devr...@outlook.com> Date : vendredi, 10 janvier 2025 � 18:00 � : Ivan Krylov via R-package-devel <r-package-devel@r-project.org> Objet : [R-pkg-devel] gcc-san check warns for non-portable flags Dear fellow package developers, There were multiple issues with a package I maintain: @CRAN: <https://cran.r-project.org/package=adfExplorer> @source: <https://github.com/pepijn-devries/adfExplorer/>. As far as I can tell all issues listed @CRAN were fixed in the latest version (available from GitHub and R-Universe). However, when submitting to CRAN, the special gcc san check complains about non-portable flags (see below). I cannot reproduce this warning myself. As far as I can tell, I don't set these flags myself (neither in the configure script nor in makevars.in). I suspect that these flags are set by the machine that performs the checks. How do I pass this check? Or should I report it to CRAN as a false negative result? Many thanks for your help. Kind regards, Pepijn > Flavor: r-devel-windows-x86_64, r-devel-linux-x86_64-debian-special-clang-san > Check: *, Result: OK > > Flavor: r-devel-linux-x86_64-debian-special-gcc-san > Check: compilation flags used, Result: WARNING > Compilation used the following non-portable flag(s): > '-Wno-deprecated-declarations' '-Wno-ignored-attributes' > '-Wno-stringop-truncation' > including flag(s) suppressing warnings ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel [[alternative HTML version deleted]]
______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
