CRAN Package Check Results for Package cubature

Last updated on 2025-05-07 03:50:57 CEST.

Flavor	Version	T_install	T_check	T_total	Status
r-devel-linux-x86_64-debian-clang	2.1.1	26.26	174.28	200.54	WARN
r-devel-linux-x86_64-debian-gcc	2.1.2	21.81	99.11	120.92	OK
r-devel-linux-x86_64-fedora-clang	2.1.2			9.24	ERROR
r-devel-linux-x86_64-fedora-gcc	2.1.2			8.00	ERROR
r-devel-windows-x86_64	2.1.2	34.00	191.00	225.00	OK
r-patched-linux-x86_64	2.1.1	26.68	160.51	187.19	WARN
r-release-linux-x86_64	2.1.1	24.22	164.02	188.24	WARN
r-release-macos-arm64	2.1.2			146.00	OK
r-release-macos-x86_64	2.1.2			255.00	OK
r-release-windows-x86_64	2.1.2	33.00	187.00	220.00	OK
r-oldrel-macos-arm64	2.1.2			131.00	NOTE
r-oldrel-macos-x86_64	2.1.2			266.00	NOTE
r-oldrel-windows-x86_64	2.1.1	43.00	234.00	277.00	OK

Check Details

Version: 2.1.1
Check: compiled code
Result: WARN File ‘cubature/libs/cubature.so’: Found ‘exit’, possibly from ‘exit’ (C) Objects: ‘Cuba/libcuba.a’, ‘cubature-1.0.4/libcubature.a’ Found ‘puts’, possibly from ‘printf’ (C), ‘puts’ (C) Object: ‘Cuba/libcuba.a’ Found ‘sprintf’, possibly from ‘sprintf’ (C) Object: ‘Cuba/libcuba.a’ Found ‘stderr’, possibly from ‘stderr’ (C) Object: ‘cubature-1.0.4/libcubature.a’ Found ‘stdout’, possibly from ‘stdout’ (C) Object: ‘Cuba/libcuba.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-patched-linux-x86_64, r-release-linux-x86_64

Version: 2.1.2
Check: whether package can be installed
Result: ERROR Installation failed. Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

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