Last updated on 2024-10-11 15:50:32 CEST.
Flavor | Version | Tinstall | Tcheck | Ttotal | Status | Flags |
---|---|---|---|---|---|---|
r-devel-linux-x86_64-debian-clang | 0.6-5 | 6.95 | 30.26 | 37.21 | WARN | |
r-devel-linux-x86_64-debian-gcc | 0.6-5 | 5.54 | 21.85 | 27.39 | WARN | |
r-devel-linux-x86_64-fedora-clang | 0.6-5 | 61.47 | WARN | |||
r-devel-linux-x86_64-fedora-gcc | 0.6-5 | 57.59 | WARN | |||
r-devel-windows-x86_64 | 0.6-5 | 19.00 | 52.00 | 71.00 | NOTE | |
r-patched-linux-x86_64 | 0.6-5 | 6.12 | 28.18 | 34.30 | WARN | |
r-release-linux-x86_64 | 0.6-5 | 6.16 | 28.10 | 34.26 | WARN | |
r-release-macos-arm64 | 0.6-5 | 12.00 | ERROR | |||
r-release-macos-x86_64 | 0.6-5 | 41.00 | WARN | |||
r-release-windows-x86_64 | 0.6-5 | 19.00 | 50.00 | 69.00 | NOTE | |
r-oldrel-macos-arm64 | 0.6-5 | 29.00 | WARN | |||
r-oldrel-macos-x86_64 | 0.6-5 | 52.00 | WARN | |||
r-oldrel-windows-x86_64 | 0.6-5 | 18.00 | 52.00 | 70.00 | NOTE |
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-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
Version: 0.6-5
Check: for GNU extensions in Makefiles
Result: NOTE
GNU make is a SystemRequirements.
Flavors: 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-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: 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.
Flavor: r-devel-windows-x86_64
Version: 0.6-5
Check: compiled code
Result: WARN
File ‘JavaGD/libs/JavaGD.so’:
Found ‘__sprintf_chk’, 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-patched-linux-x86_64, r-release-linux-x86_64
Version: 0.6-5
Check: whether package can be installed
Result: ERROR
Installation failed.
Flavor: r-release-macos-arm64
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-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64