CRAN Package Check Results for Package rJava

Last updated on 2018-05-22 13:46:46 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.9-9 46.12 44.71 90.83 WARN
r-devel-linux-x86_64-debian-gcc 0.9-9 35.23 35.39 70.62 WARN
r-devel-linux-x86_64-fedora-clang 0.9-9 65.46 NOTE
r-devel-linux-x86_64-fedora-gcc 0.9-9 62.56 NOTE
r-devel-windows-ix86+x86_64 0.9-9 89.00 66.00 155.00 WARN
r-patched-linux-x86_64 0.9-9 44.52 41.30 85.82 WARN
r-patched-solaris-x86 0.9-9 86.90 NOTE
r-release-linux-x86_64 0.9-9 43.87 40.48 84.35 WARN
r-release-windows-ix86+x86_64 0.9-9 90.00 62.00 152.00 WARN
r-release-osx-x86_64 0.9-9 WARN
r-oldrel-windows-ix86+x86_64 0.9-9 104.00 72.00 176.00 WARN
r-oldrel-osx-x86_64 0.9-9 NOTE

Additional issues

rchk valgrind

Check Details

Version: 0.9-9
Check: whether package can be installed
Result: WARN
    Found the following significant warnings:
     Warning: The javah tool is planned to be removed in the next major
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-osx-x86_64

Version: 0.9-9
Check: top-level files
Result: NOTE
    Non-standard files/directories found at top level:
     ‘getsp.class’ ‘getsp.java’ ‘install-sh’ ‘jri’ ‘version’
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.9-9
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-ix86+x86_64, r-patched-linux-x86_64, r-patched-solaris-x86, r-release-linux-x86_64, r-release-windows-ix86+x86_64, r-release-osx-x86_64, r-oldrel-windows-ix86+x86_64, r-oldrel-osx-x86_64

Version: 0.9-9
Check: for GNU extensions in Makefiles
Result: NOTE
    GNU make is a SystemRequirements.
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-ix86+x86_64, r-patched-linux-x86_64, r-patched-solaris-x86, r-release-linux-x86_64, r-release-windows-ix86+x86_64, r-release-osx-x86_64, r-oldrel-windows-ix86+x86_64, r-oldrel-osx-x86_64

Version: 0.9-9
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-ix86+x86_64, r-patched-linux-x86_64, r-patched-solaris-x86, r-release-linux-x86_64, r-release-windows-ix86+x86_64, r-release-osx-x86_64

Version: 0.9-9
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: ‘R_CStackLimit’, ‘R_CStackStart’,
     ‘R_GlobalContext’
    File ‘rJava/libs/rJava.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. 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.
Flavor: r-devel-linux-x86_64-debian-clang

Version: 0.9-9
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: ‘R_CStackLimit’, ‘R_CStackStart’,
     ‘R_GlobalContext’
    File ‘rJava/libs/rJava.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. 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.
Flavor: r-devel-linux-x86_64-debian-gcc

Version: 0.9-9
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: ‘R_CStackLimit’, ‘R_CStackStart’,
     ‘R_GlobalContext’
    File ‘rJava/libs/rJava.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. 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.
Flavor: r-devel-linux-x86_64-fedora-clang

Version: 0.9-9
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: ‘R_CStackLimit’, ‘R_CStackStart’,
     ‘R_GlobalContext’
    File ‘rJava/libs/rJava.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. 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.
Flavor: r-devel-linux-x86_64-fedora-gcc

Version: 0.9-9
Check: whether package can be installed
Result: WARN
    Found the following significant warnings:
     jri.h:21:20: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
     jri.c:308:27: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
     jri_glue.c:24:15: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
Flavors: r-devel-windows-ix86+x86_64, r-release-windows-ix86+x86_64, r-oldrel-windows-ix86+x86_64

Version: 0.9-9
Check: compiled code
Result: NOTE
    Note: information on .o files for i386 is not available
    Note: information on .o files for x64 is not available
    File 'd:/Rcompile/CRANpkg/lib/3.6/rJava/libs/i386/rJava.dll':
     Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
    File 'd:/Rcompile/CRANpkg/lib/3.6/rJava/libs/x64/rJava.dll':
     Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
    File 'rJava/libs/i386/rJava.dll':
     Found non-API call to R: 'R_GlobalContext'
    File 'rJava/libs/x64/rJava.dll':
     Found non-API call to R: 'R_GlobalContext'
    
    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. 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-devel-windows-ix86+x86_64

Version: 0.9-9
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: ‘R_CStackLimit’, ‘R_CStackStart’,
     ‘R_GlobalContext’
    File ‘rJava/libs/rJava.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. 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.
Flavor: r-patched-linux-x86_64

Version: 0.9-9
Check: compiled code
Result: NOTE
    Note: information on .o files is not available
    File ‘/home/ripley/R/Lib32/rJava/libs/rJava.so’:
     Found ‘exit’, possibly from ‘exit’ (C)
    File ‘rJava/libs/rJava.so’:
     Found non-API call to R: ‘R_GlobalContext’
    
    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. 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-patched-solaris-x86

Version: 0.9-9
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: ‘R_CStackLimit’, ‘R_CStackStart’,
     ‘R_GlobalContext’
    File ‘rJava/libs/rJava.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. 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.
Flavor: r-release-linux-x86_64

Version: 0.9-9
Check: compiled code
Result: NOTE
    Note: information on .o files for i386 is not available
    Note: information on .o files for x64 is not available
    File 'd:/Rcompile/CRANpkg/lib/3.5/rJava/libs/i386/rJava.dll':
     Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
    File 'd:/Rcompile/CRANpkg/lib/3.5/rJava/libs/x64/rJava.dll':
     Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
    File 'rJava/libs/i386/rJava.dll':
     Found non-API call to R: 'R_GlobalContext'
    File 'rJava/libs/x64/rJava.dll':
     Found non-API call to R: 'R_GlobalContext'
    
    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. 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-release-windows-ix86+x86_64

Version: 0.9-9
Check: compiled code
Result: NOTE
    Note: information on .o files is not available
    File ‘/Volumes/SSD-Data/Builds/R-dev-web/QA/Simon/packages/el-capitan-x86_64/results/3.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 call to R: ‘R_GlobalContext’
    
    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. 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-release-osx-x86_64

Version: 0.9-9
Check: compiled code
Result: NOTE
    Note: information on .o files for i386 is not available
    Note: information on .o files for x64 is not available
    File 'd:/Rcompile/CRANpkg/lib/3.4/rJava/libs/i386/rJava.dll':
     Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
    File 'd:/Rcompile/CRANpkg/lib/3.4/rJava/libs/x64/rJava.dll':
     Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
    File 'rJava/libs/i386/rJava.dll':
     Found non-API call to R: 'R_GlobalContext'
    File 'rJava/libs/x64/rJava.dll':
     Found non-API call to R: 'R_GlobalContext'
    
    Compiled code should not call entry points which might terminate R nor
    write to stdout/stderr instead of to the console, nor the system RNG.
    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-ix86+x86_64

Version: 0.9-9
Check: compiled code
Result: NOTE
    Note: information on .o files is not available
    File ‘/Volumes/SSD-Data/Builds/R-dev-web/QA/Simon/packages/el-capitan-x86_64/results/3.4/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 call to R: ‘R_GlobalContext’
    
    Compiled code should not call entry points which might terminate R nor
    write to stdout/stderr instead of to the console, nor the system RNG.
    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-osx-x86_64