CRAN Package Check Results for Package RNetCDF

Last updated on 2024-06-29 01:50:14 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 2.9-2 NOTE
r-devel-linux-x86_64-debian-gcc 2.9-2 15.13 36.77 51.90 NOTE
r-devel-linux-x86_64-fedora-clang 2.9-2 89.25 NOTE
r-devel-linux-x86_64-fedora-gcc 2.9-2 87.82 NOTE
r-devel-windows-x86_64 2.9-2 104.00 177.00 281.00 NOTE
r-patched-linux-x86_64 2.9-2 18.43 46.77 65.20 OK
r-release-linux-x86_64 2.9-2 17.49 46.75 64.24 OK
r-release-macos-arm64 2.9-2 46.00 NOTE
r-release-macos-x86_64 2.9-2 73.00 NOTE
r-release-windows-x86_64 2.9-2 104.00 183.00 287.00 NOTE
r-oldrel-macos-arm64 2.9-2 66.00 NOTE
r-oldrel-macos-x86_64 2.9-2 117.00 NOTE
r-oldrel-windows-x86_64 2.9-2 141.00 207.00 348.00 NOTE

Check Details

Version: 2.9-2
Check: compiled code
Result: NOTE File ‘RNetCDF/libs/RNetCDF.so’: Found non-API call to R: ‘Rf_findVarInFrame3’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. Flavor: r-devel-linux-x86_64-debian-clang

Version: 2.9-2
Check: compiled code
Result: NOTE File ‘RNetCDF/libs/RNetCDF.so’: Found non-API call to R: ‘Rf_findVarInFrame3’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. See section ‘Moving into C API compliance’ in the ‘Writing R Extensions’ manual for issues with use of non-API entry points. Flavors: r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

Version: 2.9-2
Check: installed package size
Result: NOTE installed size is 16.5Mb sub-directories of 1Mb or more: libs 16.2Mb Flavors: r-devel-windows-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64

Version: 2.9-2
Check: compiled code
Result: NOTE File 'RNetCDF/libs/x64/RNetCDF.dll': Found non-API call to R: 'Rf_findVarInFrame3' Compiled code should not call non-API entry points in R. See 'Writing portable packages' in the 'Writing R Extensions' manual. See section 'Moving into C API compliance' in the 'Writing R Extensions' manual for issues with use of non-API entry points. Flavor: r-devel-windows-x86_64

Version: 2.9-2
Check: package dependencies
Result: NOTE Packages which this enhances but not available for checking: 'pbdMPI', 'Rmpi' Flavors: r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64

Version: 2.9-2
Check: Rd cross-references
Result: NOTE Packages unavailable to check Rd xrefs: ‘pbdMPI’, ‘Rmpi’ Flavors: r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64