Last updated on 2025-07-26 07:50:28 CEST.
Flavor | Version | Tinstall | Tcheck | Ttotal | Status | Flags |
---|---|---|---|---|---|---|
r-devel-linux-x86_64-debian-clang | 0.4.2 | 140.08 | 51.11 | 191.19 | NOTE | |
r-devel-linux-x86_64-debian-gcc | 0.4.2 | 107.94 | 38.02 | 145.96 | NOTE | |
r-devel-linux-x86_64-fedora-clang | 0.4.2 | 321.01 | NOTE | |||
r-devel-linux-x86_64-fedora-gcc | 0.4.2 | 351.80 | NOTE | |||
r-devel-windows-x86_64 | 0.4.2 | 51.00 | 110.00 | 161.00 | NOTE | |
r-patched-linux-x86_64 | 0.4.2 | 157.33 | 47.40 | 204.73 | NOTE | |
r-release-linux-x86_64 | 0.4.2 | 157.21 | 47.40 | 204.61 | NOTE | |
r-release-macos-arm64 | 0.4.2 | 74.00 | NOTE | |||
r-release-macos-x86_64 | 0.4.2 | 146.00 | NOTE | |||
r-release-windows-x86_64 | 0.4.2 | 45.00 | 102.00 | 147.00 | NOTE | |
r-oldrel-macos-arm64 | 0.4.2 | 82.00 | OK | |||
r-oldrel-macos-x86_64 | 0.4.2 | 116.00 | OK | |||
r-oldrel-windows-x86_64 | 0.4.2 | 49.00 | 130.00 | 179.00 | OK |
Version: 0.4.2
Check: compiled code
Result: NOTE
File ‘nanoparquet/libs/nanoparquet.so’:
Found non-API call to R: ‘DATAPTR’
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-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64
Version: 0.4.2
Check: compiled code
Result: NOTE
File 'nanoparquet/libs/x64/nanoparquet.dll':
Found non-API call to R: 'DATAPTR'
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-windows-x86_64, r-release-windows-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.