Last updated on 2026-04-26 03:50:04 CEST.
| Package | NOTE | OK |
|---|---|---|
| pbivnorm | 4 | 8 |
| polywog | 1 | 11 |
Current CRAN status: NOTE: 4, OK: 8
Version: 0.6.0
Check: CRAN incoming feasibility
Result: NOTE
Maintainer: ‘Brenton Kenkel <brenton.kenkel@gmail.com>’
No Authors@R field in DESCRIPTION.
Please add one, modifying
Authors@R: c(person(given = c("Fortran", "code", "by", "Alan", "Genz.", "R", "code", "by", "Brenton"),
family = "Kenkel",
role = "aut"),
person(given = c("based", "on", "Adelchi", "Azzalini's", "'mnormt'"),
family = "package.",
role = "aut"),
person(given = "Brenton",
family = "Kenkel",
role = "cre",
email = "brenton.kenkel@gmail.com"))
as necessary.
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc
Version: 0.6.0
Check: compiled code
Result: NOTE
File ‘pbivnorm/libs/pbivnorm.so’:
Found no calls to: ‘R_registerRoutines’, ‘R_useDynamicSymbols’
It is good practice to register native routines and to disable symbol
search.
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
Current CRAN status: NOTE: 1, OK: 11
Version: 0.4-2
Check: compiled code
Result: NOTE
File ‘polywog/libs/polywog.so’:
Found non-API call to R: ‘R_UnboundValue’
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-release-macos-x86_64