Last updated on 2024-07-02 15:50:49 CEST.
| Flavor | Version | Tinstall | Tcheck | Ttotal | Status | Flags |
|---|---|---|---|---|---|---|
| r-devel-linux-x86_64-debian-clang | 2.0.0 | 35.97 | 108.69 | 144.66 | NOTE | |
| r-devel-linux-x86_64-debian-gcc | 2.0.0 | 33.83 | 75.00 | 108.83 | NOTE | |
| r-devel-linux-x86_64-fedora-clang | 2.0.0 | 197.36 | NOTE | |||
| r-devel-linux-x86_64-fedora-gcc | 2.0.0 | 199.09 | NOTE | |||
| r-devel-windows-x86_64 | 2.0.0 | 37.00 | 87.00 | 124.00 | NOTE | |
| r-patched-linux-x86_64 | 2.0.0 | 26.96 | 102.70 | 129.66 | OK | |
| r-release-linux-x86_64 | 2.0.0 | 28.07 | 105.83 | 133.90 | OK | |
| r-release-macos-arm64 | 2.0.0 | 51.00 | OK | |||
| r-release-macos-x86_64 | 2.0.0 | 90.00 | OK | |||
| r-release-windows-x86_64 | 2.0.0 | 38.00 | 87.00 | 125.00 | OK | |
| r-oldrel-macos-arm64 | 2.0.0 | 70.00 | OK | |||
| r-oldrel-macos-x86_64 | 2.0.0 | 169.00 | OK | |||
| r-oldrel-windows-x86_64 | 2.0.0 | 47.00 | 108.00 | 155.00 | OK |
Version: 2.0.0
Check: compiled code
Result: NOTE
File ‘RFCCA/libs/RFCCA.so’:
Found non-API call to R: ‘STRING_PTR’
Compiled code should not call non-API entry points in R.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
See section ‘Moving into C API compliance’ in the ‘Writing R
Extensions’ manual for issues with use of non-API entry points.
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc
Version: 2.0.0
Check: compiled code
Result: NOTE
File ‘RFCCA/libs/RFCCA.so’:
Found non-API call to R: ‘STRING_PTR’
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.
Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc
Version: 2.0.0
Check: compiled code
Result: NOTE
File 'RFCCA/libs/x64/RFCCA.dll':
Found non-API call to R: 'STRING_PTR'
Compiled code should not call non-API entry points in R.
See 'Writing portable packages' in the 'Writing R Extensions' manual.
See section 'Moving into C API compliance' in the 'Writing R
Extensions' manual for issues with use of non-API entry points.
Flavor: r-devel-windows-x86_64