CRAN Package Check Results for Package eaf

Last updated on 2024-02-23 05:07:18 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 2.5 NOTE
r-devel-linux-x86_64-debian-gcc 2.5 16.57 76.81 93.38 NOTE
r-devel-linux-x86_64-fedora-clang 2.5 150.21 NOTE
r-devel-linux-x86_64-fedora-gcc 2.5 153.09 NOTE
r-devel-windows-x86_64 2.5 48.00 111.00 159.00 NOTE
r-patched-linux-x86_64 2.5 22.95 97.37 120.32 NOTE
r-release-linux-x86_64 2.5 19.50 98.39 117.89 NOTE
r-release-macos-arm64 2.5 61.00 NOTE
r-release-macos-x86_64 2.5 130.00 NOTE
r-release-windows-x86_64 2.5 64.00 130.00 194.00 NOTE
r-oldrel-macos-arm64 2.5 60.00 NOTE
r-oldrel-windows-x86_64 2.5 57.00 120.00 177.00 NOTE

Check Details

Version: 2.5
Check: for GNU extensions in Makefiles
Result: NOTE GNU make is a SystemRequirements. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64, r-oldrel-macos-arm64, r-oldrel-windows-x86_64

Version: 2.5
Check: installed package size
Result: NOTE installed size is 6.0Mb sub-directories of 1Mb or more: bin 3.1Mb extdata 1.7Mb Flavors: r-devel-windows-x86_64, r-release-windows-x86_64, r-oldrel-windows-x86_64

Version: 2.5
Check: compiled code
Result: NOTE File ‘eaf/libs/eaf.so’: Found ‘___stderrp’, possibly from ‘stderr’ (C) Objects: ‘eaf/io.o’, ‘mo-tools/hv.o’ Found ‘___stdoutp’, possibly from ‘stdout’ (C) Object: ‘eaf/io.o’ 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: 2.5
Check: compiled code
Result: NOTE File ‘eaf/libs/eaf.so’: Found ‘___stderrp’, possibly from ‘stderr’ (C) Objects: ‘eaf/io.o’, ‘mo-tools/hv.o’ Found ‘___stdoutp’, possibly from ‘stdout’ (C) Object: ‘eaf/io.o’ 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. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. Flavor: r-oldrel-macos-arm64