rJava

CRAN incoming feasibility

Maintainer: ‘Simon Urbanek <Simon.Urbanek@r-project.org>’

Package installs .java files.
Package has FOSS license, installs .class/.jar but has no 'java' directory.

whether package can be installed

Installation failed.
See ‘/home/hornik/tmp/R.check/r-devel-clang/Work/PKGS/rJava.Rcheck/00install.out’ for details.

CRAN incoming feasibility

Maintainer: ‘Simon Urbanek <Simon.Urbanek@r-project.org>’

Package installs .java files.
Package has FOSS license, installs .class/.jar but has no 'java' directory.

R code for possible problems

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)

compiled code

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’

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.

include directives in Makefiles

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'.

top-level files

Non-standard file/directory found at top level:
  ‘jri’

R code for possible problems

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)

compiled code

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’

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.

include directives in Makefiles

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'.

top-level files

Non-standard file/directory found at top level:
  ‘jri’

R code for possible problems

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)

compiled code

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’

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.

include directives in Makefiles

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'.

top-level files

Non-standard file/directory found at top level:
  ‘jri’

R code for possible problems

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)

compiled code

Note: information on .o files is not available
File ‘/Volumes/Builds/packages/sonoma-arm64/results/4.6/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.

include directives in Makefiles

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'.

R code for possible problems

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)

compiled code

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)

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.

include directives in Makefiles

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'.

whether package can be installed

Installation failed.
See ‘/Volumes/Builds/packages/big-sur-arm64/results/4.4/rJava.Rcheck/00install.out’ for details.

R code for possible problems

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)

compiled code

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.

for GNU extensions in Makefiles

GNU make is a SystemRequirements.

include directives in Makefiles

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'.

R code for possible problems

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)

compiled code

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.

for GNU extensions in Makefiles

GNU make is a SystemRequirements.

include directives in Makefiles

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'.

R code for possible problems

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)

compiled code

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’

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.

include directives in Makefiles

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'.

top-level files

Non-standard file/directory found at top level:
  ‘jri’

R code for possible problems

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)

compiled code

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’

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.

include directives in Makefiles

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'.

top-level files

Non-standard file/directory found at top level:
  ‘jri’

whether package can be installed

Installation failed.
See ‘/Volumes/Builds/packages/big-sur-arm64/results/4.5/rJava.Rcheck/00install.out’ for details.

R code for possible problems

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)

compiled code

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)

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.

include directives in Makefiles

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'.

R code for possible problems

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)

compiled code

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)

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.

include directives in Makefiles

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'.