Last updated on 2025-04-19 06:50:01 CEST.
| Package | ERROR | WARN | NOTE | OK |
|---|---|---|---|---|
| audio | 13 | |||
| aws.iam | 13 | |||
| aws.kms | 13 | |||
| aws.s3 | 13 | |||
| base64enc | 10 | 3 | ||
| Cairo | 13 | |||
| emdist | 10 | 3 | ||
| fastmatch | 10 | 3 | ||
| FastRWeb | 13 | |||
| fasttime | 13 | |||
| iotools | 13 | |||
| iplots | 3 | 4 | 6 | |
| JavaGD | 10 | 3 | ||
| jpeg | 13 | |||
| OpenCL | 11 | |||
| PKI | 7 | 6 | ||
| png | 13 | |||
| proj4 | 3 | 10 | ||
| rJava | 1 | 12 | ||
| RJDBC | 10 | 3 | ||
| RSclient | 11 | 2 | ||
| Rserve | 4 | 9 | ||
| scagnostics | 1 | 10 | 2 | |
| tiff | 2 | 11 | ||
| uuid | 1 | 12 | ||
| venneuler | 1 | 12 |
Current CRAN status: NOTE: 13
Version: 0.1-11
Check: Rd files
Result: NOTE
checkRd: (-1) audioSample.Rd:20: Lost braces in \itemize; meant \describe ?
checkRd: (-1) audioSample.Rd:21: Lost braces in \itemize; meant \describe ?
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-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, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64
Version: 0.1-11
Check: compiled code
Result: NOTE
File ‘audio/libs/audio.so’:
Found non-API calls to R: ‘EXTPTR_PTR’, ‘R_checkActivity’
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
Version: 0.1-11
Check: compiled code
Result: NOTE
File 'audio/libs/x64/audio.dll':
Found non-API call to R: 'EXTPTR_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-windows-x86_64, r-release-windows-x86_64
Version: 0.1-11
Check: compiled code
Result: NOTE
File ‘audio/libs/audio.so’:
Found non-API call to R: ‘EXTPTR_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-release-macos-arm64, r-release-macos-x86_64
Current CRAN status: OK: 13
Current CRAN status: OK: 13
Current CRAN status: OK: 13
Current CRAN status: NOTE: 10, OK: 3
Version: 0.1-3
Check: compiled code
Result: NOTE
File ‘base64enc/libs/base64enc.so’:
Found non-API call to R: ‘SETLENGTH’
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-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64
Version: 0.1-3
Check: compiled code
Result: NOTE
File ‘base64enc/libs/base64enc.so’:
Found non-API call to R: ‘SETLENGTH’
File ‘base64enc/libs/base64enc.so’:
Found no calls to: ‘R_registerRoutines’, ‘R_useDynamicSymbols’
Compiled code should not call non-API entry points in R.
It is good practice to register native routines and to disable symbol
search.
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: 0.1-3
Check: compiled code
Result: NOTE
File 'base64enc/libs/x64/base64enc.dll':
Found non-API call to R: 'SETLENGTH'
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
Current CRAN status: NOTE: 13
Version: 1.6-2
Check: top-level files
Result: NOTE
possible bashism in configure.ac line 36 (should be 'b = a'):
if test "xx$CAIRO_LIBS" == "xx"; then
possible bashism in configure.ac line 129 (should be 'b = a'):
if test "xx${CAIRO_LIBS}" == "xx"; then
possible bashism in configure.ac line 130 (should be 'b = a'):
if test $uses_ats == "yes"; then
possible bashism in configure.ac line 214 (test -a/-o):
if test -z "${FCI}" -a -e "${pre}/include/fontconfig/fontconfig.h"; then
possible bashism in configure.ac line 218 (test -a/-o):
if test -z "${FTI}" -a -e "${pre}/include/freetype2/freetype/freetype.h"; then
possible bashism in configure.ac line 227 (test -a/-o):
if test -z "${FCI}" -a -z "${FTI}"; then
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
Version: 1.6-2
Check: compiled code
Result: NOTE
File ‘Cairo/libs/Cairo.so’:
Found non-API calls to R: ‘EXTPTR_PTR’, ‘Rf_GetOption’, ‘Rf_gsetVar’
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: 1.6-2
Check: compiled code
Result: NOTE
File 'Cairo/libs/x64/Cairo.dll':
Found non-API calls to R: 'EXTPTR_PTR', 'Rf_gsetVar'
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
Version: 1.6-2
Check: installed package size
Result: NOTE
installed size is 63.7Mb
sub-directories of 1Mb or more:
libs 63.6Mb
Flavors: r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64
Current CRAN status: NOTE: 10, OK: 3
Version: 0.3-3
Check: DESCRIPTION meta-information
Result: NOTE
License stub is invalid DCF.
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, r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64
Version: 0.3-3
Check: DESCRIPTION meta-information
Result: NOTE
Licence stub is invalid DCF.
Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc
Current CRAN status: NOTE: 10, OK: 3
Version: 1.1-6
Check: compiled code
Result: NOTE
File ‘fastmatch/libs/fastmatch.so’:
Found non-API calls to R: ‘DATAPTR’, ‘EXTPTR_PTR’, ‘NAMED’, ‘OBJECT’,
‘SETLENGTH’, ‘SET_NAMED’, ‘STRING_PTR’, ‘VECTOR_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-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: 1.1-6
Check: compiled code
Result: NOTE
File 'fastmatch/libs/x64/fastmatch.dll':
Found non-API calls to R: 'DATAPTR', 'EXTPTR_PTR', 'NAMED', 'OBJECT',
'SETLENGTH', 'SET_NAMED', 'STRING_PTR', 'VECTOR_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-windows-x86_64, r-release-windows-x86_64
Current CRAN status: NOTE: 13
Version: 1.2-1
Check: R code for possible problems
Result: NOTE
.run: no visible binding for global variable ‘init’
.run: no visible global function definition for ‘init’
.run: no visible binding for global variable ‘run’
Undefined global functions or variables:
init run
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-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, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64
Version: 1.2-1
Check: Rd cross-references
Result: NOTE
Found the following Rd file(s) with Rd \link{} targets missing package
anchors:
WebPlot.Rd: Cairo
Please provide package anchors for all Rd \link{} targets not in the
package itself and the base packages.
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-windows-x86_64
Version: 1.2-1
Check: compiled code
Result: NOTE
Note: information on .o files is not available
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, r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64
Version: 1.2-1
Check: compiled code
Result: NOTE
Note: information on .o files is not available
File ‘FastRWeb/libs/null.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
Version: 1.2-1
Check: installed package size
Result: NOTE
installed size is 5.3Mb
sub-directories of 1Mb or more:
Rcgi 2.6Mb
cgi-bin 2.5Mb
Flavor: r-oldrel-windows-x86_64
Current CRAN status: OK: 13
Current CRAN status: NOTE: 13
Version: 0.3-5
Check: compiled code
Result: NOTE
File ‘iotools/libs/iotools.so’:
Found non-API calls to R: ‘DATAPTR’, ‘NAMED’, ‘R_GetConnection’,
‘R_ReadConnection’, ‘R_WriteConnection’, ‘SETLENGTH’, ‘SET_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-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64
Version: 0.3-5
Check: compiled code
Result: NOTE
File ‘iotools/libs/iotools.so’:
Found non-API calls to R: ‘DATAPTR’, ‘NAMED’, ‘R_GetConnection’,
‘R_ReadConnection’, ‘R_WriteConnection’, ‘SETLENGTH’, ‘SET_NAMED’
File ‘iotools/libs/iotools.so’:
Found no calls to: ‘R_registerRoutines’, ‘R_useDynamicSymbols’
Compiled code should not call non-API entry points in R.
It is good practice to register native routines and to disable symbol
search.
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: 0.3-5
Check: compiled code
Result: NOTE
File 'iotools/libs/x64/iotools.dll':
Found non-API calls to R: 'DATAPTR', 'NAMED', 'R_GetConnection',
'R_ReadConnection', 'R_WriteConnection', 'SETLENGTH', 'SET_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-windows-x86_64, r-release-windows-x86_64
Version: 0.3-5
Check: compiled code
Result: NOTE
File ‘iotools/libs/iotools.so’:
Found non-API calls to R: ‘R_GetConnection’, ‘R_ReadConnection’,
‘R_WriteConnection’
Compiled code should not call non-API entry points in R.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
Flavors: r-oldrel-macos-arm64, r-oldrel-macos-x86_64
Version: 0.3-5
Check: compiled code
Result: NOTE
File 'iotools/libs/x64/iotools.dll':
Found non-API calls to R: 'R_GetConnection', 'R_ReadConnection',
'R_WriteConnection'
Compiled code should not call non-API entry points in R.
See 'Writing portable packages' in the 'Writing R Extensions' manual.
Flavor: r-oldrel-windows-x86_64
Current CRAN status: ERROR: 3, NOTE: 4, OK: 6
Version: 1.1-8
Check: whether package can be installed
Result: ERROR
Installation failed.
Flavors: r-devel-windows-x86_64, r-release-windows-x86_64, r-oldrel-windows-x86_64
Version: 1.1-8
Flags: --install=fake
Check: R code for possible problems
Result: NOTE
.get.plot.obj: no visible binding for global variable ‘.iplots’
.iDebug: no visible binding for global variable ‘.iplots.fw’
.iobj.color: no visible binding for global variable ‘.iplot.current’
.iobj.opt: no visible binding for global variable ‘.iplot.current’
.iplot.get.by.pm: no visible binding for global variable ‘.iplots’
.iplot.getPar: no visible binding for global variable ‘.iplot.current’
.iplot.iBar: no visible binding for global variable ‘.iplots.fw’
.iplot.iBox: no visible binding for global variable ‘.iplots.fw’
.iplot.iHammock: no visible binding for global variable ‘.iplots.fw’
.iplot.iHist: no visible binding for global variable ‘.iplots.fw’
.iplot.iMap: no visible binding for global variable ‘.iplots.fw’
.iplot.iMosaic: no visible binding for global variable ‘.iplots.fw’
.iplot.iPCP: no visible binding for global variable ‘.iplots.fw’
.iplot.iPlot: no visible binding for global variable ‘.iplots.fw’
.iplot.new: no visible binding for '<<-' assignment to ‘.iplots’
.iplot.new: no visible binding for global variable ‘.iplots’
.iplot.new: no visible binding for '<<-' assignment to ‘.iplot.current’
.iplot.new: no visible binding for '<<-' assignment to ‘.iplot.curid’
.iplot.opt: no visible binding for global variable ‘.iplots.fw’
.iplot.opt: no visible binding for global variable ‘.iplots’
.iset.save: no visible binding for '<<-' assignment to ‘.isets’
.iset.save: no visible binding for global variable ‘.isets’
.iset.save: no visible binding for global variable ‘.iplots’
.iset.save: no visible binding for global variable ‘.iplot.curid’
.iset.save: no visible binding for global variable ‘.iplot.current’
.ivar.check.length: no visible binding for global variable ‘.iplots.fw’
ievent.wait: no visible binding for global variable ‘.restricted.el’
ievent.wait: no visible binding for global variable ‘.iplots.fw’
iplot.backend: no visible binding for global variable ‘.iplots.fw’
iplot.cur: no visible binding for global variable ‘.iplot.curid’
iplot.data: no visible binding for global variable ‘.iplot.current’
iplot.data: no visible binding for global variable ‘.iplots.fw’
iplot.list: no visible binding for global variable ‘.iplots’
iplot.location: no visible binding for global variable ‘.iplots’
iplot.next: no visible binding for global variable ‘.iplots’
iplot.off: no visible binding for global variable ‘.iplots’
iplot.off: no visible binding for '<<-' assignment to ‘.iplots’
iplot.off: no visible binding for '<<-' assignment to ‘.iplot.current’
iplot.off: no visible binding for '<<-' assignment to ‘.iplot.curid’
iplot.opt: no visible binding for global variable ‘.iplots’
iplot.prev: no visible binding for global variable ‘.iplots’
iplot.resetZoom: no visible binding for global variable
‘.iplot.current’
iplot.rotate: no visible binding for global variable ‘.iplot.current’
iplot.set: no visible binding for global variable ‘.iplots’
iplot.set: no visible binding for '<<-' assignment to ‘.iplot.current’
iplot.set: no visible binding for '<<-' assignment to ‘.iplot.curid’
iplot.setExtendedQuery: no visible binding for global variable
‘.iplot.curid’
iplot.setExtendedQuery: no visible binding for global variable
‘.iplots.fw’
iplot.size: no visible binding for global variable ‘.iplots’
iplot.zoomIn: no visible binding for global variable ‘.iplot.current’
iplot.zoomOut: no visible binding for global variable ‘.iplot.current’
iset: no visible binding for global variable ‘.iplots.fw’
iset.brush: no visible binding for global variable ‘.iplots.fw’
iset.brush: no visible binding for global variable ‘.iplot.current’
iset.cur: no visible binding for global variable ‘.iplots.fw’
iset.list: no visible binding for global variable ‘.iplots.fw’
iset.new: no visible binding for global variable ‘.iplots.fw’
iset.new: no visible binding for '<<-' assignment to ‘.iplots’
iset.new: no visible binding for '<<-' assignment to ‘.iplot.current’
iset.new: no visible binding for '<<-' assignment to ‘.iplot.curid’
iset.next: no visible binding for global variable ‘.iplots.fw’
iset.prev: no visible binding for global variable ‘.iplots.fw’
iset.rm: no visible binding for global variable ‘.iplots.fw’
iset.rm: no visible binding for global variable ‘.isets’
iset.rm: no visible binding for '<<-' assignment to ‘.isets’
iset.rm: no visible binding for '<<-' assignment to ‘.iplots’
iset.rm: no visible binding for '<<-' assignment to ‘.iplot.curid’
iset.rm: no visible binding for '<<-' assignment to ‘.iplot.current’
iset.sel.changed: no visible binding for global variable
‘.iset.selection’
iset.sel.changed: no visible binding for '<<-' assignment to
‘.iset.selection’
iset.select: no visible binding for global variable ‘.iplots.fw’
iset.selectAll: no visible binding for global variable ‘.iplots.fw’
iset.selectNone: no visible binding for global variable ‘.iplots.fw’
iset.selected: no visible binding for global variable ‘.iplots.fw’
iset.set: no visible binding for global variable ‘.iplots.fw’
iset.set: no visible binding for '<<-' assignment to ‘.iplots’
iset.set: no visible binding for global variable ‘.isets’
iset.set: no visible binding for '<<-' assignment to ‘.iplot.curid’
iset.set: no visible binding for '<<-' assignment to ‘.iplot.current’
iset.updateVars: no visible binding for global variable ‘.iplots.fw’
isets: no visible binding for global variable ‘.iplots.fw’
ivar.data: no visible binding for global variable ‘.iplots.fw’
ivar.new: no visible binding for global variable ‘.iplots.fw’
ivar.new.map: no visible binding for global variable ‘.iplots.fw’
ivar.update: no visible binding for global variable ‘.iplots.fw’
Undefined global functions or variables:
.iplot.curid .iplot.current .iplots .iplots.fw .iset.selection .isets
.restricted.el
Flavors: r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64
Current CRAN status: WARN: 10, NOTE: 3
Version: 0.6-5
Check: include directives in Makefiles
Result: NOTE
Found the following Makefile(s) with an include directive with a pathname using R_HOME:
src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives. However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME. This option can be specified
multiple times to include multiple Makefiles. Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.
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-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, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64
Version: 0.6-5
Check: compiled code
Result: WARN
File ‘JavaGD/libs/JavaGD.so’:
Found ‘__vsprintf_chk’, possibly from ‘vsprintf’ (C)
Object: ‘jGDtalk.o’
File ‘JavaGD/libs/JavaGD.so’:
Found non-API call to R: ‘Rf_gsetVar’
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.
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-linux-x86_64-debian-clang
Version: 0.6-5
Check: compiled code
Result: WARN
File ‘JavaGD/libs/JavaGD.so’:
Found ‘__sprintf_chk’, possibly from ‘sprintf’ (C)
Object: ‘jGDtalk.o’
File ‘JavaGD/libs/JavaGD.so’:
Found non-API call to R: ‘Rf_gsetVar’
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.
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-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
Version: 0.6-5
Check: compiled code
Result: NOTE
File 'JavaGD/libs/x64/JavaGD.dll':
Found non-API call to R: 'Rf_gsetVar'
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
Version: 0.6-5
Check: compiled code
Result: WARN
File ‘JavaGD/libs/JavaGD.so’:
Found ‘_sprintf’, possibly from ‘sprintf’ (C)
Object: ‘jGDtalk.o’
File ‘JavaGD/libs/JavaGD.so’:
Found non-API call to R: ‘Rf_gsetVar’
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.
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-release-macos-arm64, r-release-macos-x86_64
Version: 0.6-5
Check: for GNU extensions in Makefiles
Result: NOTE
GNU make is a SystemRequirements.
Flavors: r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64
Version: 0.6-5
Check: compiled code
Result: WARN
File ‘JavaGD/libs/JavaGD.so’:
Found ‘_sprintf’, possibly from ‘sprintf’ (C)
Object: ‘jGDtalk.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 nor [v]sprintf.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
Flavors: r-oldrel-macos-arm64, r-oldrel-macos-x86_64
Current CRAN status: OK: 13
Current CRAN status: NOTE: 11
Version: 0.2-10
Check: DESCRIPTION meta-information
Result: NOTE
License stub is invalid DCF.
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, r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64
Version: 0.2-10
Check: compiled code
Result: NOTE
File ‘OpenCL/libs/R_OpenCL.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.2-10
Check: tests
Result: NOTE
Running ‘buffer.R’ [0s/1s]
Comparing ‘buffer.Rout’ to ‘buffer.Rout.save’ ...5,10d4
< >
< > if (!length(oclPlatforms())) {
< + cat("== Cannot run tests as there is no platform")
< + q("no")
< + }
< >
Running ‘kernel.R’ [3s/5s]
Comparing ‘kernel.Rout’ to ‘kernel.Rout.save’ ...5,10d4
< >
< > if (!length(oclPlatforms())) {
< + cat("== Cannot run tests as there is no platform")
< + q("no")
< + }
< >
Flavors: r-devel-linux-x86_64-debian-clang, r-release-linux-x86_64
Version: 0.2-10
Check: tests
Result: NOTE
Running ‘buffer.R’ [0s/1s]
Comparing ‘buffer.Rout’ to ‘buffer.Rout.save’ ...5,10d4
< >
< > if (!length(oclPlatforms())) {
< + cat("== Cannot run tests as there is no platform")
< + q("no")
< + }
< >
Running ‘kernel.R’ [2s/3s]
Comparing ‘kernel.Rout’ to ‘kernel.Rout.save’ ...5,10d4
< >
< > if (!length(oclPlatforms())) {
< + cat("== Cannot run tests as there is no platform")
< + q("no")
< + }
< >
Flavor: r-devel-linux-x86_64-debian-gcc
Version: 0.2-10
Check: DESCRIPTION meta-information
Result: NOTE
Licence stub is invalid DCF.
Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc
Version: 0.2-10
Check: tests
Result: NOTE
Running ‘buffer.R’
Comparing ‘buffer.Rout’ to ‘buffer.Rout.save’ ...5,10d4
< >
< > if (!length(oclPlatforms())) {
< + cat("== Cannot run tests as there is no platform")
< + q("no")
< + }
< >
Running ‘kernel.R’
Comparing ‘kernel.Rout’ to ‘kernel.Rout.save’ ...5,10d4
< >
< > if (!length(oclPlatforms())) {
< + cat("== Cannot run tests as there is no platform")
< + q("no")
< + }
< >
Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc
Version: 0.2-10
Check: tests
Result: NOTE
Running ‘buffer.R’ [0s/0s]
Comparing ‘buffer.Rout’ to ‘buffer.Rout.save’ ...5,10d4
< >
< > if (!length(oclPlatforms())) {
< + cat("== Cannot run tests as there is no platform")
< + q("no")
< + }
< >
Running ‘kernel.R’ [3s/5s]
Comparing ‘kernel.Rout’ to ‘kernel.Rout.save’ ...5,10d4
< >
< > if (!length(oclPlatforms())) {
< + cat("== Cannot run tests as there is no platform")
< + q("no")
< + }
< >
Flavor: r-patched-linux-x86_64
Version: 0.2-10
Check: tests
Result: NOTE
Running ‘buffer.R’ [0s/0s]
Comparing ‘buffer.Rout’ to ‘buffer.Rout.save’ ...5,10d4
< >
< > if (!length(oclPlatforms())) {
< + cat("== Cannot run tests as there is no platform")
< + q("no")
< + }
< >
77c71
< OpenCL buffer, 16 elements of type single
---
> OpenCL buffer, 16 elements of type double
79c73
< [9] 3.316625 3.464102 3.605551 3.741657 3.872983 4.000000 4.123106 4.242640
---
> [9] 3.316625 3.464102 3.605551 3.741657 3.872983 4.000000 4.123106 4.242641
Running ‘kernel.R’ [0s/0s]
Comparing ‘kernel.Rout’ to ‘kernel.Rout.save’ ...5,10d4
< >
< > if (!length(oclPlatforms())) {
< + cat("== Cannot run tests as there is no platform")
< + q("no")
< + }
< >
29c23
< OpenCL buffer, 16 elements of type single
---
> OpenCL buffer, 16 elements of type double
32,35c26,27
< OpenCL buffer, 16 elements of type single
< [1] 1.00000 4.00000 9.00000 16.00000 25.00000 36.00001 48.99999
< [8] 63.99999 81.00000 100.00000 121.00002 144.00000 169.00000 196.00003
< [15] 225.00003 256.00000
---
> OpenCL buffer, 16 elements of type double
> [1] 1 4 9 16 25 36 49 64 81 100 121 144 169 196 225 256
42c34
< OpenCL buffer, 16 elements of type single
---
> OpenCL buffer, 16 elements of type double
Flavor: r-release-macos-arm64
Version: 0.2-10
Check: tests
Result: NOTE
Running ‘buffer.R’ [0s/0s]
Comparing ‘buffer.Rout’ to ‘buffer.Rout.save’ ...5,10d4
< >
< > if (!length(oclPlatforms())) {
< + cat("== Cannot run tests as there is no platform")
< + q("no")
< + }
< >
77c71
< OpenCL buffer, 16 elements of type single
---
> OpenCL buffer, 16 elements of type double
79c73
< [9] 3.316625 3.464102 3.605551 3.741657 3.872983 4.000000 4.123106 4.242640
---
> [9] 3.316625 3.464102 3.605551 3.741657 3.872983 4.000000 4.123106 4.242641
Running ‘kernel.R’ [0s/1s]
Comparing ‘kernel.Rout’ to ‘kernel.Rout.save’ ...5,10d4
< >
< > if (!length(oclPlatforms())) {
< + cat("== Cannot run tests as there is no platform")
< + q("no")
< + }
< >
29c23
< OpenCL buffer, 16 elements of type single
---
> OpenCL buffer, 16 elements of type double
32,35c26,27
< OpenCL buffer, 16 elements of type single
< [1] 1.00000 4.00000 9.00000 16.00000 25.00000 36.00001 48.99999
< [8] 63.99999 81.00000 100.00000 121.00002 144.00000 169.00000 196.00003
< [15] 225.00003 256.00000
---
> OpenCL buffer, 16 elements of type double
> [1] 1 4 9 16 25 36 49 64 81 100 121 144 169 196 225 256
42c34
< OpenCL buffer, 16 elements of type single
---
> OpenCL buffer, 16 elements of type double
Flavor: r-release-macos-x86_64
Version: 0.2-10
Check: for GNU extensions in Makefiles
Result: NOTE
GNU make is a SystemRequirements.
Flavors: r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64
Current CRAN status: NOTE: 7, OK: 6
Version: 0.1-14
Check: top-level files
Result: NOTE
possible bashism in configure.ac line 39 (test -a/-o):
if test x"${PKG_CPPFLAGS}" = x -a x"${PKG_LIBS}" = x -a x"$PKGCONFIG" != x; then
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
Version: 0.1-14
Check: installed package size
Result: NOTE
installed size is 5.3Mb
sub-directories of 1Mb or more:
libs 5.1Mb
Flavor: r-oldrel-windows-x86_64
Current CRAN status: OK: 13
Current CRAN status: NOTE: 3, OK: 10
Version: 1.0-15
Check: installed package size
Result: NOTE
installed size is 12.8Mb
sub-directories of 1Mb or more:
libs 12.8Mb
Flavors: r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64
Current CRAN status: ERROR: 1, NOTE: 12
Version: 1.0-11
Check: top-level files
Result: NOTE
Non-standard file/directory found at top level:
‘jri’
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
Version: 1.0-11
Check: R code for possible problems
Result: NOTE
Found the following possibly unsafe calls:
File ‘rJava/R/import.R’:
unlockBinding(IMPORTER, env = env)
assignInNamespace(IMPORTER, importer, envir = env)
File ‘rJava/R/jinit.R’:
unlockBinding(x, .env)
unlockBinding(x, pe)
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-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, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64
Version: 1.0-11
Check: include directives in Makefiles
Result: NOTE
Found the following Makefile(s) with an include directive with a pathname using R_HOME:
jri/src/Makefile.win
jri/src/win32/Makefile
src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives. However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME. This option can be specified
multiple times to include multiple Makefiles. Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.
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-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, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64
Version: 1.0-11
Check: compiled code
Result: NOTE
Note: information on .o files is not available
File ‘/home/hornik/tmp/R.check/r-devel-clang/Work/build/Packages/rJava/libs/rJava.so’:
Found ‘_exit’, possibly from ‘_exit’ (C)
Found ‘stderr’, possibly from ‘stderr’ (C)
Found ‘stdout’, possibly from ‘stdout’ (C)
File ‘rJava/libs/rJava.so’:
Found non-API calls to R: ‘EXTPTR_PROT’, ‘EXTPTR_PTR’,
‘R_CStackLimit’, ‘R_CStackStart’
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
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-linux-x86_64-debian-clang
Version: 1.0-11
Check: compiled code
Result: NOTE
Note: information on .o files is not available
File ‘/home/hornik/tmp/R.check/r-devel-gcc/Work/build/Packages/rJava/libs/rJava.so’:
Found ‘_exit’, possibly from ‘_exit’ (C)
Found ‘stderr’, possibly from ‘stderr’ (C)
Found ‘stdout’, possibly from ‘stdout’ (C)
File ‘rJava/libs/rJava.so’:
Found non-API calls to R: ‘EXTPTR_PROT’, ‘EXTPTR_PTR’,
‘R_CStackLimit’, ‘R_CStackStart’
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
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-linux-x86_64-debian-gcc
Version: 1.0-11
Check: compiled code
Result: NOTE
Note: information on .o files is not available
File ‘/data/gannet/ripley/R/packages/tests-clang/rJava.Rcheck/rJava/libs/rJava.so’:
Found ‘_exit’, possibly from ‘_exit’ (C)
Found ‘stderr’, possibly from ‘stderr’ (C)
Found ‘stdout’, possibly from ‘stdout’ (C)
File ‘rJava/libs/rJava.so’:
Found non-API calls to R: ‘EXTPTR_PROT’, ‘EXTPTR_PTR’,
‘R_CStackLimit’, ‘R_CStackStart’
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
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-linux-x86_64-fedora-clang
Version: 1.0-11
Check: compiled code
Result: NOTE
Note: information on .o files is not available
File ‘/data/gannet/ripley/R/packages/tests-devel/rJava.Rcheck/rJava/libs/rJava.so’:
Found ‘_exit’, possibly from ‘_exit’ (C)
Found ‘stderr’, possibly from ‘stderr’ (C)
Found ‘stdout’, possibly from ‘stdout’ (C)
File ‘rJava/libs/rJava.so’:
Found non-API calls to R: ‘EXTPTR_PROT’, ‘EXTPTR_PTR’,
‘R_CStackLimit’, ‘R_CStackStart’
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
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-linux-x86_64-fedora-gcc
Version: 1.0-11
Check: compiled code
Result: NOTE
Note: information on .o files for x64 is not available
File 'd:/Rcompile/CRANpkg/lib/4.6/rJava/libs/x64/rJava.dll':
Found '_exit', possibly from '_exit' (C)
Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
File 'rJava/libs/x64/rJava.dll':
Found non-API calls to R: 'EXTPTR_PROT', 'EXTPTR_PTR'
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
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
Version: 1.0-11
Check: examples
Result: ERROR
Running examples in 'rJava-Ex.R' failed
The error most likely occurred in:
> ### Name: J
> ### Title: High level API for accessing Java
> ### Aliases: J
> ### Keywords: interface
>
> ### ** Examples
>
> ## Don't show:
> .jinit()
[1] 0
> ## End(Don't show)
>
> if (!nzchar(Sys.getenv("NOAWT"))) {
+ f <- new(J("java.awt.Frame"), "Hello")
+ f$setVisible(TRUE)
+ }
Error in .jcall("RJavaTools", "Ljava/lang/Object;", "newInstance", class, :
java.awt.HeadlessException:
The application does not have desktop access,
but this program performed an operation which requires it.
Calls: new -> new -> .J -> .jcall -> .jcheck
Execution halted
Flavor: r-devel-windows-x86_64
Version: 1.0-11
Check: compiled code
Result: NOTE
Note: information on .o files is not available
File ‘/home/hornik/tmp/R.check/r-patched-gcc/Work/build/Packages/rJava/libs/rJava.so’:
Found ‘_exit’, possibly from ‘_exit’ (C)
Found ‘stderr’, possibly from ‘stderr’ (C)
Found ‘stdout’, possibly from ‘stdout’ (C)
File ‘rJava/libs/rJava.so’:
Found non-API calls to R: ‘EXTPTR_PROT’, ‘EXTPTR_PTR’,
‘R_CStackLimit’, ‘R_CStackStart’
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
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-patched-linux-x86_64
Version: 1.0-11
Check: compiled code
Result: NOTE
Note: information on .o files is not available
File ‘/home/hornik/tmp/R.check/r-release-gcc/Work/build/Packages/rJava/libs/rJava.so’:
Found ‘_exit’, possibly from ‘_exit’ (C)
Found ‘stderr’, possibly from ‘stderr’ (C)
Found ‘stdout’, possibly from ‘stdout’ (C)
File ‘rJava/libs/rJava.so’:
Found non-API calls to R: ‘EXTPTR_PROT’, ‘EXTPTR_PTR’,
‘R_CStackLimit’, ‘R_CStackStart’
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
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-linux-x86_64
Version: 1.0-11
Check: compiled code
Result: NOTE
Note: information on .o files is not available
File ‘/Volumes/Builds/packages/big-sur-arm64/results/4.5/rJava.Rcheck/rJava/libs/rJava.so’:
Found ‘___stderrp’, possibly from ‘stderr’ (C)
Found ‘___stdoutp’, possibly from ‘stdout’ (C)
File ‘rJava/libs/rJava.so’:
Found non-API calls to R: ‘EXTPTR_PROT’, ‘EXTPTR_PTR’
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
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-arm64
Version: 1.0-11
Check: compiled code
Result: NOTE
Note: information on .o files is not available
File ‘/Volumes/Builds/packages/big-sur-x86_64/results/4.5/rJava.Rcheck/rJava/libs/rJava.so’:
Found ‘___stderrp’, possibly from ‘stderr’ (C)
Found ‘___stdoutp’, possibly from ‘stdout’ (C)
File ‘rJava/libs/rJava.so’:
Found non-API calls to R: ‘EXTPTR_PROT’, ‘EXTPTR_PTR’
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
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
Version: 1.0-11
Check: compiled code
Result: NOTE
Note: information on .o files for x64 is not available
File 'd:/Rcompile/CRANpkg/lib/4.5/rJava/libs/x64/rJava.dll':
Found '_exit', possibly from '_exit' (C)
Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
File 'rJava/libs/x64/rJava.dll':
Found non-API calls to R: 'EXTPTR_PROT', 'EXTPTR_PTR'
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
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-windows-x86_64
Version: 1.0-11
Check: for GNU extensions in Makefiles
Result: NOTE
GNU make is a SystemRequirements.
Flavors: r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64
Version: 1.0-11
Check: compiled code
Result: NOTE
Note: information on .o files is not available
File ‘/Volumes/Builds/packages/big-sur-arm64/results/4.4/rJava.Rcheck/rJava/libs/rJava.so’:
Found ‘___stderrp’, possibly from ‘stderr’ (C)
Found ‘___stdoutp’, possibly from ‘stdout’ (C)
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
Flavor: r-oldrel-macos-arm64
Version: 1.0-11
Check: compiled code
Result: NOTE
Note: information on .o files is not available
File ‘/Volumes/Builds/packages/big-sur-x86_64/results/4.4/rJava.Rcheck/rJava/libs/rJava.so’:
Found ‘___stderrp’, possibly from ‘stderr’ (C)
Found ‘___stdoutp’, possibly from ‘stdout’ (C)
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
Flavor: r-oldrel-macos-x86_64
Version: 1.0-11
Check: compiled code
Result: NOTE
Note: information on .o files for x64 is not available
File 'd:/Rcompile/CRANpkg/lib/4.4/rJava/libs/x64/rJava.dll':
Found '_exit', possibly from '_exit' (C)
Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
See 'Writing portable packages' in the 'Writing R Extensions' manual.
Flavor: r-oldrel-windows-x86_64
Current CRAN status: NOTE: 10, OK: 3
Version: 0.2-10
Check: DESCRIPTION meta-information
Result: NOTE
License stub is invalid DCF.
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, r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64
Version: 0.2-10
Check: DESCRIPTION meta-information
Result: NOTE
Licence stub is invalid DCF.
Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc
Current CRAN status: NOTE: 11, OK: 2
Version: 0.7-10
Check: compiled code
Result: NOTE
File ‘RSclient/libs/RSclient.so’:
Found non-API calls to R: ‘BODY’, ‘EXTPTR_PTR’, ‘FORMALS’
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.7-10
Check: compiled code
Result: NOTE
File 'RSclient/libs/x64/RSclient.dll':
Found non-API calls to R: 'BODY', 'EXTPTR_PTR', 'FORMALS'
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
Version: 0.7-10
Check: installed package size
Result: NOTE
installed size is 5.2Mb
sub-directories of 1Mb or more:
libs 5.1Mb
Flavor: r-oldrel-windows-x86_64
Current CRAN status: WARN: 4, NOTE: 9
Version: 1.8-15
Check: compiled code
Result: NOTE
Note: information on .o files is not available
File ‘/home/hornik/tmp/R.check/r-devel-clang/Work/build/Packages/Rserve/libs/Rserve.so’:
Found ‘exit’, possibly from ‘exit’ (C)
Found ‘rand’, possibly from ‘rand’ (C)
Found ‘random’, possibly from ‘random’ (C)
Found ‘srandom’, possibly from ‘srandom’ (C)
Found ‘stderr’, possibly from ‘stderr’ (C)
File ‘Rserve/libs/Rserve.so’:
Found non-API calls to R: ‘BODY’, ‘FORMALS’, ‘R_Consolefile’,
‘R_Outputfile’, ‘R_TempDir’, ‘R_Visible’, ‘R_curErrorBuf’,
‘ptr_R_Busy’, ‘ptr_R_ClearerrConsole’, ‘ptr_R_FlushConsole’,
‘ptr_R_ReadConsole’, ‘ptr_R_ResetConsole’, ‘ptr_R_ShowMessage’,
‘ptr_R_WriteConsole’, ‘ptr_R_WriteConsoleEx’
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
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-linux-x86_64-debian-clang
Version: 1.8-15
Check: compiled code
Result: NOTE
Note: information on .o files is not available
File ‘/home/hornik/tmp/R.check/r-devel-gcc/Work/build/Packages/Rserve/libs/Rserve.so’:
Found ‘exit’, possibly from ‘exit’ (C)
Found ‘rand’, possibly from ‘rand’ (C)
Found ‘random’, possibly from ‘random’ (C)
Found ‘srandom’, possibly from ‘srandom’ (C)
Found ‘stderr’, possibly from ‘stderr’ (C)
File ‘Rserve/libs/Rserve.so’:
Found non-API calls to R: ‘BODY’, ‘FORMALS’, ‘R_Consolefile’,
‘R_Outputfile’, ‘R_TempDir’, ‘R_Visible’, ‘R_curErrorBuf’,
‘ptr_R_Busy’, ‘ptr_R_ClearerrConsole’, ‘ptr_R_FlushConsole’,
‘ptr_R_ReadConsole’, ‘ptr_R_ResetConsole’, ‘ptr_R_ShowMessage’,
‘ptr_R_WriteConsole’, ‘ptr_R_WriteConsoleEx’
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
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-linux-x86_64-debian-gcc
Version: 1.8-15
Check: compiled code
Result: NOTE
Note: information on .o files is not available
File ‘/data/gannet/ripley/R/packages/tests-clang/Rserve.Rcheck/Rserve/libs/Rserve.so’:
Found ‘exit’, possibly from ‘exit’ (C)
Found ‘rand’, possibly from ‘rand’ (C), ‘rand’ (Fortran)
Found ‘random’, possibly from ‘random’ (C)
Found ‘srandom’, possibly from ‘srandom’ (C)
Found ‘stderr’, possibly from ‘stderr’ (C)
File ‘Rserve/libs/Rserve.so’:
Found non-API calls to R: ‘BODY’, ‘FORMALS’, ‘R_Consolefile’,
‘R_Outputfile’, ‘R_TempDir’, ‘R_Visible’, ‘R_curErrorBuf’,
‘ptr_R_Busy’, ‘ptr_R_ClearerrConsole’, ‘ptr_R_FlushConsole’,
‘ptr_R_ReadConsole’, ‘ptr_R_ResetConsole’, ‘ptr_R_ShowMessage’,
‘ptr_R_WriteConsole’, ‘ptr_R_WriteConsoleEx’
File ‘Rserve/libs/Rserve.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 nor [v]sprintf. The detected symbols are linked into
the code but might come from libraries and not actually be called.
Compiled code should not call non-API entry points in R.
It is good practice to register native routines and to disable symbol
search.
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-linux-x86_64-fedora-clang
Version: 1.8-15
Check: compiled code
Result: NOTE
Note: information on .o files is not available
File ‘/data/gannet/ripley/R/packages/tests-devel/Rserve.Rcheck/Rserve/libs/Rserve.so’:
Found ‘exit’, possibly from ‘exit’ (C)
Found ‘rand’, possibly from ‘rand’ (C)
Found ‘random’, possibly from ‘random’ (C)
Found ‘srandom’, possibly from ‘srandom’ (C)
Found ‘stderr’, possibly from ‘stderr’ (C)
File ‘Rserve/libs/Rserve.so’:
Found non-API calls to R: ‘BODY’, ‘FORMALS’, ‘R_Consolefile’,
‘R_Outputfile’, ‘R_TempDir’, ‘R_Visible’, ‘R_curErrorBuf’,
‘ptr_R_Busy’, ‘ptr_R_ClearerrConsole’, ‘ptr_R_FlushConsole’,
‘ptr_R_ReadConsole’, ‘ptr_R_ResetConsole’, ‘ptr_R_ShowMessage’,
‘ptr_R_WriteConsole’, ‘ptr_R_WriteConsoleEx’
File ‘Rserve/libs/Rserve.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 nor [v]sprintf. The detected symbols are linked into
the code but might come from libraries and not actually be called.
Compiled code should not call non-API entry points in R.
It is good practice to register native routines and to disable symbol
search.
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-linux-x86_64-fedora-gcc
Version: 1.8-15
Check: compiled code
Result: NOTE
Note: information on .o files for x64 is not available
File 'd:/Rcompile/CRANpkg/lib/4.6/Rserve/libs/x64/Rserve.dll':
Found '_exit', possibly from '_exit' (C)
Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
Found 'exit', possibly from 'exit' (C), 'stop' (Fortran)
Found 'rand', possibly from 'rand' (C)
Found 'srand', possibly from 'srand' (C)
File 'Rserve/libs/x64/Rserve.dll':
Found non-API calls to R: 'BODY', 'FORMALS', 'R_Interactive',
'R_Visible', 'R_curErrorBuf', 'Rf_initialize_R', 'setup_Rmainloop'
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
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
Version: 1.8-15
Check: compiled code
Result: NOTE
Note: information on .o files is not available
File ‘/home/hornik/tmp/R.check/r-patched-gcc/Work/build/Packages/Rserve/libs/Rserve.so’:
Found ‘exit’, possibly from ‘exit’ (C)
Found ‘rand’, possibly from ‘rand’ (C)
Found ‘random’, possibly from ‘random’ (C)
Found ‘srandom’, possibly from ‘srandom’ (C)
Found ‘stderr’, possibly from ‘stderr’ (C)
File ‘Rserve/libs/Rserve.so’:
Found non-API calls to R: ‘BODY’, ‘FORMALS’, ‘R_Consolefile’,
‘R_Outputfile’, ‘R_TempDir’, ‘R_Visible’, ‘R_curErrorBuf’,
‘ptr_R_Busy’, ‘ptr_R_ClearerrConsole’, ‘ptr_R_FlushConsole’,
‘ptr_R_ReadConsole’, ‘ptr_R_ResetConsole’, ‘ptr_R_ShowMessage’,
‘ptr_R_WriteConsole’, ‘ptr_R_WriteConsoleEx’
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
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-patched-linux-x86_64
Version: 1.8-15
Check: compiled code
Result: NOTE
Note: information on .o files is not available
File ‘/home/hornik/tmp/R.check/r-release-gcc/Work/build/Packages/Rserve/libs/Rserve.so’:
Found ‘exit’, possibly from ‘exit’ (C)
Found ‘rand’, possibly from ‘rand’ (C)
Found ‘random’, possibly from ‘random’ (C)
Found ‘srandom’, possibly from ‘srandom’ (C)
Found ‘stderr’, possibly from ‘stderr’ (C)
File ‘Rserve/libs/Rserve.so’:
Found non-API calls to R: ‘BODY’, ‘FORMALS’, ‘R_Consolefile’,
‘R_Outputfile’, ‘R_TempDir’, ‘R_Visible’, ‘R_curErrorBuf’,
‘ptr_R_Busy’, ‘ptr_R_ClearerrConsole’, ‘ptr_R_FlushConsole’,
‘ptr_R_ReadConsole’, ‘ptr_R_ResetConsole’, ‘ptr_R_ShowMessage’,
‘ptr_R_WriteConsole’, ‘ptr_R_WriteConsoleEx’
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
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-linux-x86_64
Version: 1.8-15
Check: compiled code
Result: WARN
Note: information on .o files is not available
File ‘/Volumes/Builds/packages/big-sur-arm64/results/4.5/Rserve.Rcheck/Rserve/libs/Rserve.so’:
Found ‘___stderrp’, possibly from ‘stderr’ (C)
Found ‘_abort’, possibly from ‘abort’ (C)
Found ‘_exit’, possibly from ‘exit’ (C)
Found ‘_rand’, possibly from ‘rand’ (C)
Found ‘_random’, possibly from ‘random’ (C)
Found ‘_sprintf’, possibly from ‘sprintf’ (C)
Found ‘_srandom’, possibly from ‘srandom’ (C)
File ‘Rserve/libs/Rserve.so’:
Found non-API calls to R: ‘BODY’, ‘FORMALS’, ‘R_Consolefile’,
‘R_Outputfile’, ‘R_TempDir’, ‘R_Visible’, ‘R_curErrorBuf’,
‘ptr_R_Busy’, ‘ptr_R_ClearerrConsole’, ‘ptr_R_FlushConsole’,
‘ptr_R_ReadConsole’, ‘ptr_R_ResetConsole’, ‘ptr_R_ShowMessage’,
‘ptr_R_WriteConsole’, ‘ptr_R_WriteConsoleEx’
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
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-arm64
Version: 1.8-15
Check: compiled code
Result: WARN
Note: information on .o files is not available
File ‘/Volumes/Builds/packages/big-sur-x86_64/results/4.5/Rserve.Rcheck/Rserve/libs/Rserve.so’:
Found ‘___stderrp’, possibly from ‘stderr’ (C)
Found ‘_abort’, possibly from ‘abort’ (C)
Found ‘_exit’, possibly from ‘exit’ (C)
Found ‘_rand’, possibly from ‘rand’ (C)
Found ‘_random’, possibly from ‘random’ (C)
Found ‘_sprintf’, possibly from ‘sprintf’ (C)
Found ‘_srandom’, possibly from ‘srandom’ (C)
File ‘Rserve/libs/Rserve.so’:
Found non-API calls to R: ‘BODY’, ‘FORMALS’, ‘R_Consolefile’,
‘R_Outputfile’, ‘R_TempDir’, ‘R_Visible’, ‘R_curErrorBuf’,
‘ptr_R_Busy’, ‘ptr_R_ClearerrConsole’, ‘ptr_R_FlushConsole’,
‘ptr_R_ReadConsole’, ‘ptr_R_ResetConsole’, ‘ptr_R_ShowMessage’,
‘ptr_R_WriteConsole’, ‘ptr_R_WriteConsoleEx’
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
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
Version: 1.8-15
Check: compiled code
Result: NOTE
Note: information on .o files for x64 is not available
File 'd:/Rcompile/CRANpkg/lib/4.5/Rserve/libs/x64/Rserve.dll':
Found '_exit', possibly from '_exit' (C)
Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
Found 'exit', possibly from 'exit' (C), 'stop' (Fortran)
Found 'rand', possibly from 'rand' (C)
Found 'srand', possibly from 'srand' (C)
File 'Rserve/libs/x64/Rserve.dll':
Found non-API calls to R: 'BODY', 'FORMALS', 'R_Interactive',
'R_Visible', 'R_curErrorBuf', 'Rf_initialize_R', 'setup_Rmainloop'
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
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-windows-x86_64
Version: 1.8-15
Check: installed package size
Result: NOTE
installed size is 20.0Mb
sub-directories of 1Mb or more:
libs 19.8Mb
Flavors: r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64
Version: 1.8-15
Check: for GNU extensions in Makefiles
Result: NOTE
GNU make is a SystemRequirements.
Flavors: r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64
Version: 1.8-15
Check: compiled code
Result: WARN
Note: information on .o files is not available
File ‘/Volumes/Builds/packages/big-sur-arm64/results/4.4/Rserve.Rcheck/Rserve/libs/Rserve.so’:
Found ‘___stderrp’, possibly from ‘stderr’ (C)
Found ‘_abort’, possibly from ‘abort’ (C)
Found ‘_exit’, possibly from ‘exit’ (C)
Found ‘_rand’, possibly from ‘rand’ (C)
Found ‘_random’, possibly from ‘random’ (C)
Found ‘_sprintf’, possibly from ‘sprintf’ (C)
Found ‘_srandom’, possibly from ‘srandom’ (C)
File ‘Rserve/libs/Rserve.so’:
Found non-API calls to R: ‘R_Consolefile’, ‘R_Outputfile’,
‘R_TempDir’, ‘R_Visible’, ‘getInputHandler’, ‘ptr_R_Busy’,
‘ptr_R_ClearerrConsole’, ‘ptr_R_FlushConsole’, ‘ptr_R_ReadConsole’,
‘ptr_R_ResetConsole’, ‘ptr_R_ShowMessage’, ‘ptr_R_WriteConsole’,
‘ptr_R_WriteConsoleEx’
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
Compiled code should not call non-API entry points in R.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
Flavor: r-oldrel-macos-arm64
Version: 1.8-15
Check: compiled code
Result: WARN
Note: information on .o files is not available
File ‘/Volumes/Builds/packages/big-sur-x86_64/results/4.4/Rserve.Rcheck/Rserve/libs/Rserve.so’:
Found ‘___stderrp’, possibly from ‘stderr’ (C)
Found ‘_abort’, possibly from ‘abort’ (C)
Found ‘_exit’, possibly from ‘exit’ (C)
Found ‘_rand’, possibly from ‘rand’ (C)
Found ‘_random’, possibly from ‘random’ (C)
Found ‘_sprintf’, possibly from ‘sprintf’ (C)
Found ‘_srandom’, possibly from ‘srandom’ (C)
File ‘Rserve/libs/Rserve.so’:
Found non-API calls to R: ‘R_Consolefile’, ‘R_Outputfile’,
‘R_TempDir’, ‘R_Visible’, ‘getInputHandler’, ‘ptr_R_Busy’,
‘ptr_R_ClearerrConsole’, ‘ptr_R_FlushConsole’, ‘ptr_R_ReadConsole’,
‘ptr_R_ResetConsole’, ‘ptr_R_ShowMessage’, ‘ptr_R_WriteConsole’,
‘ptr_R_WriteConsoleEx’
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
Compiled code should not call non-API entry points in R.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
Flavor: r-oldrel-macos-x86_64
Version: 1.8-15
Check: compiled code
Result: NOTE
Note: information on .o files for x64 is not available
File 'd:/Rcompile/CRANpkg/lib/4.4/Rserve/libs/x64/Rserve.dll':
Found '_exit', possibly from '_exit' (C)
Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
Found 'exit', possibly from 'exit' (C), 'stop' (Fortran)
Found 'rand', possibly from 'rand' (C)
Found 'srand', possibly from 'srand' (C)
File 'Rserve/libs/x64/Rserve.dll':
Found non-API calls to R: 'R_Interactive', 'R_Visible',
'Rf_initialize_R', 'setup_Rmainloop'
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. The detected symbols are linked into
the code but might come from libraries and not actually be called.
Compiled code should not call non-API entry points in R.
See 'Writing portable packages' in the 'Writing R Extensions' manual.
Flavor: r-oldrel-windows-x86_64
Current CRAN status: WARN: 1, NOTE: 10, OK: 2
Version: 0.2-6
Check: DESCRIPTION meta-information
Result: NOTE
License stub is invalid DCF.
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, r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64
Version: 0.2-6
Check: DESCRIPTION meta-information
Result: NOTE
Licence stub is invalid DCF.
Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc
Version: 0.2-6
Check: whether startup messages can be suppressed
Result: NOTE
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
It looks like this package (or a package it requires) has a startup
message which cannot be suppressed: see ?packageStartupMessage.
Flavor: r-devel-windows-x86_64
Version: 0.2-6
Check: dependencies in R code
Result: NOTE
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
Flavor: r-devel-windows-x86_64
Version: 0.2-6
Check: S3 generic/method consistency
Result: WARN
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
See section 'Generic functions and methods' in the 'Writing R
Extensions' manual.
Flavor: r-devel-windows-x86_64
Version: 0.2-6
Check: replacement functions
Result: WARN
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
The argument of a replacement function which corresponds to the right
hand side must be named 'value'.
Flavor: r-devel-windows-x86_64
Version: 0.2-6
Check: foreign function calls
Result: NOTE
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
See chapter 'System and foreign language interfaces' in the 'Writing R
Extensions' manual.
Flavor: r-devel-windows-x86_64
Version: 0.2-6
Check: R code for possible problems
Result: NOTE
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
Flavor: r-devel-windows-x86_64
Version: 0.2-6
Check: for missing documentation entries
Result: WARN
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
All user-level objects in a package should have documentation entries.
See chapter 'Writing R documentation files' in the 'Writing R
Extensions' manual.
Flavor: r-devel-windows-x86_64
Version: 0.2-6
Check: for code/documentation mismatches
Result: WARN
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
Flavor: r-devel-windows-x86_64
Version: 0.2-6
Check: Rd \usage sections
Result: NOTE
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
The \usage entries for S3 methods should use the \method markup and not
their full name.
See chapter 'Writing R documentation files' in the 'Writing R
Extensions' manual.
Flavor: r-devel-windows-x86_64
Current CRAN status: NOTE: 2, OK: 11
Version: 0.1-12
Check: installed package size
Result: NOTE
installed size is 5.4Mb
sub-directories of 1Mb or more:
libs 5.3Mb
Flavors: r-oldrel-macos-arm64, r-oldrel-macos-x86_64
Current CRAN status: WARN: 1, OK: 12
Version: 1.2-1
Check: whether package can be installed
Result: WARN
Found the following significant warnings:
randutils.c:60:12: warning: function declaration isn't a prototype [-Wstrict-prototypes]
See 'd:/Rcompile/CRANpkg/local/4.4/uuid.Rcheck/00install.out' for details.
* used C compiler: 'gcc.exe (GCC) 13.2.0'
Flavor: r-oldrel-windows-x86_64
Current CRAN status: WARN: 1, OK: 12
Version: 1.1-4
Check: whether startup messages can be suppressed
Result: NOTE
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
It looks like this package (or a package it requires) has a startup
message which cannot be suppressed: see ?packageStartupMessage.
Flavor: r-devel-windows-x86_64
Version: 1.1-4
Check: dependencies in R code
Result: NOTE
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
Flavor: r-devel-windows-x86_64
Version: 1.1-4
Check: S3 generic/method consistency
Result: WARN
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
See section 'Generic functions and methods' in the 'Writing R
Extensions' manual.
Flavor: r-devel-windows-x86_64
Version: 1.1-4
Check: replacement functions
Result: WARN
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
The argument of a replacement function which corresponds to the right
hand side must be named 'value'.
Flavor: r-devel-windows-x86_64
Version: 1.1-4
Check: foreign function calls
Result: NOTE
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
See chapter 'System and foreign language interfaces' in the 'Writing R
Extensions' manual.
Flavor: r-devel-windows-x86_64
Version: 1.1-4
Check: R code for possible problems
Result: NOTE
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
Flavor: r-devel-windows-x86_64
Version: 1.1-4
Check: for missing documentation entries
Result: WARN
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
All user-level objects in a package should have documentation entries.
See chapter 'Writing R documentation files' in the 'Writing R
Extensions' manual.
Flavor: r-devel-windows-x86_64
Version: 1.1-4
Check: for code/documentation mismatches
Result: WARN
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
Flavor: r-devel-windows-x86_64
Version: 1.1-4
Check: Rd \usage sections
Result: NOTE
OpenJDK 64-Bit Server VM warning: The Windows job object has enabled multiple processor groups (2) but the UseAllWindowsProcessorGroups flag is off. Some processors might not be used.
The \usage entries for S3 methods should use the \method markup and not
their full name.
See chapter 'Writing R documentation files' in the 'Writing R
Extensions' manual.
Flavor: r-devel-windows-x86_64