CRAN Package Check Results for Package scs

Last updated on 2025-04-02 20:52:16 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 3.2.4 8.09 20.48 28.57 WARN
r-devel-linux-x86_64-debian-gcc 3.2.4 8.55 16.55 25.10 WARN
r-devel-linux-x86_64-fedora-clang 3.2.4 46.81 WARN
r-devel-linux-x86_64-fedora-gcc 3.2.4 51.71 WARN
r-devel-macos-arm64 3.2.4 22.00 WARN
r-devel-macos-x86_64 3.2.4 45.00 OK
r-devel-windows-x86_64 3.2.4 33.00 0.00 33.00 FAIL
r-patched-linux-x86_64 3.2.4 11.09 20.17 31.26 WARN
r-release-linux-x86_64 3.2.4 11.06 20.14 31.20 NOTE
r-release-macos-arm64 3.2.4 28.00 NOTE
r-release-macos-x86_64 3.2.4 34.00 NOTE
r-release-windows-x86_64 3.2.4 31.00 47.00 78.00 NOTE
r-oldrel-macos-arm64 3.2.4 NOTE
r-oldrel-macos-x86_64 3.2.4 30.00 NOTE
r-oldrel-windows-x86_64 3.2.4 33.00 47.00 80.00 NOTE

Check Details

Version: 3.2.4
Check: compiled code
Result: WARN File ‘scs/libs/scs.so’: Found ‘printf’, possibly from ‘printf’ (C) Object: ‘scs/out/libscsdir.a’ Found ‘putchar’, possibly from ‘putchar’ (C) Object: ‘scs/out/libscsdir.a’ Found ‘puts’, possibly from ‘printf’ (C), ‘puts’ (C) Object: ‘scs/out/libscsdir.a’ Found ‘sprintf’, possibly from ‘sprintf’ (C) Object: ‘scs/out/libscsdir.a’ 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-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-patched-linux-x86_64

Version: 3.2.4
Check: compiled code
Result: WARN File ‘scs/libs/scs.so’: Found ‘__printf_chk’, possibly from ‘printf’ (C) Object: ‘scs/out/libscsdir.a’ Found ‘__sprintf_chk’, possibly from ‘sprintf’ (C) Object: ‘scs/out/libscsdir.a’ 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. Flavor: r-devel-linux-x86_64-fedora-clang

Version: 3.2.4
Check: compiled code
Result: WARN File ‘scs/libs/scs.so’: Found ‘__printf_chk’, possibly from ‘printf’ (C) Object: ‘scs/out/libscsdir.a’ Found ‘__sprintf_chk’, possibly from ‘sprintf’ (C) Object: ‘scs/out/libscsdir.a’ Found ‘putchar’, possibly from ‘putchar’ (C) Object: ‘scs/out/libscsdir.a’ Found ‘puts’, possibly from ‘printf’ (C), ‘puts’ (C) Object: ‘scs/out/libscsdir.a’ 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. Flavor: r-devel-linux-x86_64-fedora-gcc

Version: 3.2.4
Check: compiled code
Result: WARN File ‘scs/libs/scs.so’: Found ‘___sprintf_chk’, possibly from ‘sprintf’ (C) Object: ‘scs/out/libscsdir.a’ Found ‘_printf’, possibly from ‘printf’ (C) Object: ‘scs/out/libscsdir.a’ Found ‘_putchar’, possibly from ‘putchar’ (C) Object: ‘scs/out/libscsdir.a’ Found ‘_puts’, possibly from ‘printf’ (C), ‘puts’ (C) Object: ‘scs/out/libscsdir.a’ Found ‘_sprintf’, possibly from ‘sprintf’ (C) Object: ‘scs/out/libscsdir.a’ 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. Flavor: r-devel-macos-arm64

Version: 3.2.4
Check: compiled code
Result: NOTE File 'scs/libs/x64/scs.dll': Found 'putchar', possibly from 'putchar' (C) Object: 'scs/out/libscsdir.a' Found 'puts', possibly from 'printf' (C), 'puts' (C) Object: 'scs/out/libscsdir.a' 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. Flavor: r-devel-windows-x86_64

Version: 3.2.4
Check: PDF version of manual
Result: FAIL Check process probably crashed or hung up for 20 minutes ... killed Most likely this happened in the example checks (?), if not, ignore the following last lines of example output: [1] 0 $info$lin_sys_time [1] 0.0077 $info$cone_time [1] 0.0096 $info$accel_time [1] 0 > > > > ### * <FOOTER> > ### > cleanEx() > options(digits = 7L) > base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n") Time elapsed: 0.17 0 0.18 NA NA > grDevices::dev.off() null device 1 > ### > ### Local variables: *** > ### mode: outline-minor *** > ### outline-regexp: "\\(> \\)?### [*]+" *** > ### End: *** > quit('no') ======== End of example output (where/before crash/hang up occured ?) ======== Flavor: r-devel-windows-x86_64

Version: 3.2.4
Check: for GNU extensions in Makefiles
Result: NOTE GNU make is a SystemRequirements. Flavors: 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

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.
Health stats visible at Monitor.