Last updated on 2020-08-07 01:50:20 CEST.
| Package | NOTE | OK |
|---|---|---|
| allelic | 8 | 4 |
Current CRAN status: NOTE: 8, OK: 4
Version: 0.1
Check: compiled code
Result: NOTE
File 'allelic/libs/allelic.so':
Found 'stderr', possibly from 'stderr' (C)
Object: 'newallelic.o'
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.
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, r-release-linux-x86_64
Version: 0.1
Check: compiled code
Result: NOTE
File ‘allelic/libs/allelic.so’:
Found ‘stderr’, possibly from ‘stderr’ (C)
Object: ‘newallelic.o’
File ‘allelic/libs/allelic.so’:
Found no calls to: ‘R_registerRoutines’, ‘R_useDynamicSymbols’
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.
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
Version: 0.1
Check: compiled code
Result: NOTE
File ‘allelic/libs/allelic.so’:
Found ‘___stderrp’, possibly from ‘stderr’ (C)
Object: ‘newallelic.o’
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.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
Flavors: r-release-macos-x86_64, r-oldrel-macos-x86_64