Last updated on 2025-05-01 08:52:30 CEST.
| Flavor | Version | Tinstall | Tcheck | Ttotal | Status | Flags |
|---|---|---|---|---|---|---|
| r-devel-linux-x86_64-debian-clang | 2.1.1 | 25.80 | 173.49 | 199.29 | WARN | |
| r-devel-linux-x86_64-debian-gcc | 2.1.1 | 21.56 | 100.23 | 121.79 | WARN | |
| r-devel-linux-x86_64-fedora-clang | 2.1.1 | 341.91 | WARN | |||
| r-devel-linux-x86_64-fedora-gcc | 2.1.1 | 344.28 | WARN | |||
| r-devel-windows-x86_64 | 2.1.1 | 33.00 | 179.00 | 212.00 | WARN | |
| r-patched-linux-x86_64 | 2.1.1 | 24.91 | 161.03 | 185.94 | WARN | |
| r-release-linux-x86_64 | WARN | |||||
| r-release-macos-arm64 | 2.1.1 | 91.00 | WARN | |||
| r-release-macos-x86_64 | 2.1.1 | 238.00 | WARN | |||
| r-release-windows-x86_64 | 2.1.1 | 34.00 | 181.00 | 215.00 | WARN | |
| r-oldrel-macos-arm64 | 2.1.1 | 75.00 | OK | |||
| r-oldrel-macos-x86_64 | 2.1.1 | 290.00 | OK | |||
| r-oldrel-windows-x86_64 | 2.1.1 | 38.00 | 226.00 | 264.00 | OK |
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-devel-linux-x86_64-debian-gcc, r-patched-linux-x86_64, r-release-linux-x86_64
Version: 2.1.1
Check: compiled code
Result: WARN
File ‘cubature/libs/cubature.so’:
Found ‘__sprintf_chk’, possibly from ‘sprintf’ (C)
Object: ‘Cuba/libcuba.a’
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 ‘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-fedora-clang, r-devel-linux-x86_64-fedora-gcc
Version: 2.1.1
Check: compiled code
Result: WARN
File 'cubature/libs/x64/cubature.dll':
Found 'exit', possibly from 'exit' (C), 'stop' (Fortran)
Objects: 'Cuba/libcuba.a', 'cubature-1.0.4/libcubature.a'
Found 'puts', possibly from 'printf' (C), 'puts' (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-windows-x86_64, r-release-windows-x86_64
Version: 2.1.1
Check: compiled code
Result: WARN
File ‘cubature/libs/cubature.so’:
Found ‘___sprintf_chk’, possibly from ‘sprintf’ (C)
Object: ‘Cuba/libcuba.a’
Found ‘___stderrp’, possibly from ‘stderr’ (C)
Object: ‘cubature-1.0.4/libcubature.a’
Found ‘___stdoutp’, possibly from ‘stdout’ (C)
Object: ‘Cuba/libcuba.a’
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’
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
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.