CRAN Package Check Results for Package rlibkriging

Last updated on 2025-06-15 03:49:30 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.9-1 264.74 241.29 506.03 NOTE
r-devel-linux-x86_64-debian-gcc 0.9-1 210.12 153.55 363.67 NOTE
r-devel-linux-x86_64-fedora-clang 0.9-1 1018.73 NOTE
r-devel-linux-x86_64-fedora-gcc 0.9-1 994.65 NOTE
r-devel-windows-x86_64 0.9-1 380.00 268.00 648.00 NOTE
r-patched-linux-x86_64 0.9-1 299.85 220.39 520.24 NOTE
r-release-linux-x86_64 0.9-1 302.28 219.91 522.19 NOTE
r-release-macos-arm64 0.9-1 217.00 NOTE
r-release-macos-x86_64 0.9-1 382.00 NOTE
r-release-windows-x86_64 0.9-1 386.00 284.00 670.00 NOTE
r-oldrel-macos-arm64 0.9-1 185.00 NOTE
r-oldrel-macos-x86_64 0.9-1 364.00 NOTE
r-oldrel-windows-x86_64 0.9-1 454.00 366.00 820.00 NOTE

Additional issues

noSuggests

Check Details

Version: 0.9-1
Check: compiled code
Result: NOTE File ‘rlibkriging/libs/rlibkriging.so’: Found ‘_ZSt4cerr’, possibly from ‘std::cerr’ (C++) Objects: ‘../inst/lib/libKriging.a’, ‘libK/build/src/lib/libKriging.a’ Found ‘_ZSt4cout’, possibly from ‘std::cout’ (C++) Objects: ‘../inst/lib/libKriging.a’, ‘libK/build/src/lib/libKriging.a’ Compiled code should not call entry points which might terminate R nor write to stdout/stderr instead of to the console, nor use Fortran I/O nor system RNGs nor [v]sprintf. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-gcc, r-patched-linux-x86_64, r-release-linux-x86_64

Version: 0.9-1
Check: compiled code
Result: NOTE File ‘rlibkriging/libs/rlibkriging.so’: Found ‘_ZNSt3__14cerrE’, possibly from ‘std::cerr’ (C++) Objects: ‘../inst/lib/libKriging.a’, ‘libK/build/src/lib/libKriging.a’ Found ‘_ZNSt3__14coutE’, possibly from ‘std::cout’ (C++) Objects: ‘../inst/lib/libKriging.a’, ‘libK/build/src/lib/libKriging.a’ Compiled code should not call entry points which might terminate R nor write to stdout/stderr instead of to the console, nor use Fortran I/O nor system RNGs nor [v]sprintf. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. Flavor: r-devel-linux-x86_64-fedora-clang

Version: 0.9-1
Check: compiled code
Result: NOTE File 'rlibkriging/libs/x64/rlibkriging.dll': Found '_ZSt4cerr', possibly from 'std::cerr' (C++) Objects: '../inst/lib/libKriging.a', 'libK/build/src/lib/libKriging.a' Found '_ZSt4cout', possibly from 'std::cout' (C++) Objects: '../inst/lib/libKriging.a', 'libK/build/src/lib/libKriging.a' Compiled code should not call entry points which might terminate R nor write to stdout/stderr instead of to the console, nor use Fortran I/O nor system RNGs nor [v]sprintf. See 'Writing portable packages' in the 'Writing R Extensions' manual. Flavors: r-devel-windows-x86_64, r-release-windows-x86_64

Version: 0.9-1
Check: compiled code
Result: NOTE File ‘rlibkriging/libs/rlibkriging.so’: Found ‘__ZNSt3__14cerrE’, possibly from ‘std::cerr’ (C++) Objects: ‘../inst/lib/libKriging.a’, ‘libK/build/src/lib/libKriging.a’ Found ‘__ZNSt3__14coutE’, possibly from ‘std::cout’ (C++) Objects: ‘../inst/lib/libKriging.a’, ‘libK/build/src/lib/libKriging.a’ Compiled code should not call entry points which might terminate R nor write to stdout/stderr instead of to the console, nor use Fortran I/O nor system RNGs nor [v]sprintf. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. Flavors: r-release-macos-arm64, r-release-macos-x86_64

Version: 0.9-1
Check: installed package size
Result: NOTE installed size is 71.3Mb sub-directories of 1Mb or more: include 7.3Mb lib 37.3Mb libs 26.2Mb Flavors: r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64

Version: 0.9-1
Check: for GNU extensions in Makefiles
Result: NOTE GNU make is a SystemRequirements. Flavors: r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64