CRAN Package Check Results for Package scs

Last updated on 2025-03-22 08:53:28 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 3.2.4 7.92 20.79 28.71 WARN
r-devel-linux-x86_64-debian-gcc 3.2.4 8.39 16.68 25.07 WARN
r-devel-linux-x86_64-fedora-clang 3.2.4 46.36 WARN
r-devel-linux-x86_64-fedora-gcc 3.2.4 56.50 WARN
r-devel-macos-arm64 3.2.4 22.00 OK
r-devel-macos-x86_64 3.2.4 45.00 OK
r-devel-windows-x86_64 3.2.4 30.00 46.00 76.00 OK
r-patched-linux-x86_64 3.2.4 11.68 20.29 31.97 WARN
r-release-linux-x86_64 3.2.4 11.31 19.74 31.05 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 32.00 45.00 77.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 31.00 47.00 78.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: 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