CRAN Package Check Results for Package RAppArmor

Last updated on 2017-03-27 03:50:00.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 2.0.2 1.68 17.79 19.46 NOTE
r-devel-linux-x86_64-debian-gcc 2.0.2 1.38 17.89 19.28 NOTE
r-devel-linux-x86_64-fedora-clang 2.0.2 34.43 NOTE --no-stop-on-test-error
r-devel-linux-x86_64-fedora-gcc 2.0.2 33.49 NOTE --no-stop-on-test-error
r-patched-linux-x86_64 2.0.2 1.39 17.71 19.11 NOTE
r-release-linux-x86_64 2.0.2 1.32 13.32 14.64 OK
r-release-osx-x86_64-mavericks 2.0.2 ERROR

Check Details

Version: 2.0.2
Check: compiled code
Result: NOTE
    File ‘RAppArmor/libs/RAppArmor.so’:
     Found no calls to: ‘R_registerRoutines’, ‘R_useDynamicSymbols’
    
    It is good practice to register native routines and to disable symbol
    search.
    
    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: 2.0.2
Flags: --no-stop-on-test-error
Check: compiled code
Result: NOTE
    File ‘RAppArmor/libs/RAppArmor.so’:
     Found no calls to: ‘R_registerRoutines’, ‘R_useDynamicSymbols’
    
    It is good practice to register native routines and to disable symbol
    search.
    
    See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

Version: 2.0.2
Check: whether package can be installed
Result: ERROR
    Installation failed.
Flavor: r-release-osx-x86_64-mavericks