Last updated on 2025-04-13 14:50:28 CEST.
Flavor | Version | Tinstall | Tcheck | Ttotal | Status | Flags |
---|---|---|---|---|---|---|
r-devel-linux-x86_64-debian-clang | 0.1.6 | 71.88 | 19.75 | 91.63 | WARN | |
r-devel-linux-x86_64-debian-gcc | 0.1.7 | 58.44 | 20.51 | 78.95 | OK | |
r-devel-linux-x86_64-fedora-gcc | 0.1.7 | 164.84 | OK | |||
r-devel-macos-arm64 | 0.1.7 | 41.00 | OK | |||
r-devel-macos-x86_64 | 0.1.7 | 101.00 | OK | |||
r-devel-windows-x86_64 | 0.1.6 | 76.00 | 61.00 | 137.00 | NOTE | |
r-patched-linux-x86_64 | 0.1.7 | 74.72 | 24.12 | 98.84 | OK | |
r-release-linux-x86_64 | 0.1.7 | 74.24 | 23.96 | 98.20 | OK | |
r-release-macos-arm64 | 0.1.7 | 47.00 | OK | |||
r-release-macos-x86_64 | 0.1.7 | 82.00 | OK | |||
r-release-windows-x86_64 | 0.1.7 | 59.00 | 78.00 | 137.00 | OK | |
r-oldrel-macos-arm64 | 0.1.7 | 50.00 | OK | |||
r-oldrel-macos-x86_64 | 0.1.7 | 84.00 | OK | |||
r-oldrel-windows-x86_64 | 0.1.6 | 83.00 | 66.00 | 149.00 | OK |
Version: 0.1.6
Check: compiled code
Result: WARN
File ‘arcpbf/libs/arcpbf.so’:
Found ‘_exit’, possibly from ‘_exit’ (C)
Object: ‘rust/target/release/libarcpbf.a’
Found ‘abort’, possibly from ‘abort’ (C)
Object: ‘rust/target/release/libarcpbf.a’
Found ‘exit’, possibly from ‘exit’ (C)
Object: ‘rust/target/release/libarcpbf.a’
File ‘arcpbf/libs/arcpbf.so’:
Found non-API calls to R: ‘BODY’, ‘CLOENV’, ‘DATAPTR’, ‘ENCLOS’,
‘FORMALS’
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.
Compiled code should not call non-API entry points in R.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
Flavor: r-devel-linux-x86_64-debian-clang
Version: 0.1.6
Check: compiled code
Result: NOTE
File 'arcpbf/libs/x64/arcpbf.dll':
Found non-API calls to R: 'BODY', 'CLOENV', 'DATAPTR', 'ENCLOS',
'FORMALS'
Compiled code should not call non-API entry points in R.
See 'Writing portable packages' in the 'Writing R Extensions' manual,
and section 'Moving into C API compliance' for issues with the use of
non-API entry points.
Flavor: r-devel-windows-x86_64