Last updated on 2025-04-12 20:52:22 CEST.
Package | WARN | NOTE | OK |
---|---|---|---|
ASSISTant | 14 | ||
bcaboot | 14 | ||
cubature | 7 | 7 | |
deconvolveR | 11 | 3 | |
distcomp | 7 | 7 | |
ECOSolveR | 14 | ||
homomorpheR | 14 | ||
locfdr | 14 | ||
sglr | 2 | 13 | |
sp23design | 15 |
Current CRAN status: OK: 14
Current CRAN status: OK: 14
Current CRAN status: WARN: 7, OK: 7
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
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.
Flavor: r-devel-linux-x86_64-fedora-gcc
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-devel-macos-arm64, r-devel-macos-x86_64
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.
Flavor: r-devel-windows-x86_64
Current CRAN status: NOTE: 11, OK: 3
Version: 1.2-1
Check: Rd files
Result: NOTE
checkRd: (-1) deconv.Rd:85: Lost braces; missing escapes or markup?
85 | \code{tg}, std. error of \eqn{g}, \eqn{G} (the cdf of {g}),
| ^
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-gcc, r-devel-macos-arm64, r-devel-macos-x86_64, r-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64
Current CRAN status: NOTE: 7, OK: 7
Version: 1.3-3
Check: compiled code
Result: NOTE
File ‘distcomp/libs/distcomp.so’:
Found non-API call to R: ‘NAMED’
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-gcc, r-devel-macos-arm64, r-devel-macos-x86_64, r-patched-linux-x86_64
Version: 1.3-3
Check: compiled code
Result: NOTE
File 'distcomp/libs/x64/distcomp.dll':
Found non-API call to R: 'NAMED'
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
Current CRAN status: NOTE: 14
Version: 0.5.5
Check: compiled code
Result: NOTE
File ‘ECOSolveR/libs/ECOSolveR.so’:
Found ‘printf’, possibly from ‘printf’ (C)
Objects: ‘ecos/libecos.a’, ‘ecos/libecos_bb.a’
Found ‘putchar’, possibly from ‘putchar’ (C)
Objects: ‘ecos/libecos.a’, ‘ecos/libecos_bb.a’
Found ‘puts’, possibly from ‘printf’ (C), ‘puts’ (C)
Objects: ‘ecos/libecos.a’, ‘ecos/libecos_bb.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
Version: 0.5.5
Check: compiled code
Result: NOTE
File ‘ECOSolveR/libs/ECOSolveR.so’:
Found ‘__printf_chk’, possibly from ‘printf’ (C)
Objects: ‘ecos/libecos.a’, ‘ecos/libecos_bb.a’
Found ‘printf’, possibly from ‘printf’ (C)
Objects: ‘ecos/libecos.a’, ‘ecos/libecos_bb.a’
Found ‘putchar’, possibly from ‘putchar’ (C)
Objects: ‘ecos/libecos.a’, ‘ecos/libecos_bb.a’
Found ‘puts’, possibly from ‘printf’ (C), ‘puts’ (C)
Objects: ‘ecos/libecos.a’, ‘ecos/libecos_bb.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.
Flavor: r-devel-linux-x86_64-fedora-gcc
Version: 0.5.5
Check: compiled code
Result: NOTE
File ‘ECOSolveR/libs/ECOSolveR.so’:
Found ‘_printf’, possibly from ‘printf’ (C)
Objects: ‘ecos/libecos.a’, ‘ecos/libecos_bb.a’
Found ‘_putchar’, possibly from ‘putchar’ (C)
Objects: ‘ecos/libecos.a’, ‘ecos/libecos_bb.a’
Found ‘_puts’, possibly from ‘printf’ (C), ‘puts’ (C)
Objects: ‘ecos/libecos.a’, ‘ecos/libecos_bb.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-macos-arm64, r-devel-macos-x86_64
Version: 0.5.5
Check: compiled code
Result: NOTE
File 'ECOSolveR/libs/x64/ECOSolveR.dll':
Found 'putchar', possibly from 'putchar' (C)
Objects: 'ecos/libecos.a', 'ecos/libecos_bb.a'
Found 'puts', possibly from 'printf' (C), 'puts' (C)
Objects: 'ecos/libecos.a', 'ecos/libecos_bb.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.
Flavor: r-devel-windows-x86_64
Version: 0.5.5
Check: for GNU extensions in Makefiles
Result: NOTE
GNU make is a SystemRequirements.
Flavors: r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64
Current CRAN status: OK: 14
Current CRAN status: OK: 14
Current CRAN status: NOTE: 2, OK: 13
Version: 0.8
Check: dependencies in R code
Result: NOTE
Namespace in Imports field not imported from: ‘rlang’
All declared Imports should be used.
Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc
Current CRAN status: OK: 15
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.
Health stats visible at Monitor.