1 sccscheck(1)                     User Commands                    sccscheck(1)
   2 
   3 
   4 
   5 NAME
   6        sccscheck -
   7 
   8 SYNOPSIS
   9        sccscheck filename
  10 
  11 DESCRIPTION
  12        The standard solaris make(1) is SCCS-aware, automatically checking out
  13        files if they are out of date with respect to the SCCS file; however,
  14        this is of little value in the context of teamware and of no value if a
  15        non-SCCS SCM system is used, and can lead to hard-to-diagnose build
  16        failures  in the presence of recursive parallel make.  The sccscheck
  17        script is used from the OS/Net Makefile.master file as a substitute for
  18        make(1)'s default handling of SCCS files; it generates errors preceded
  19        by "sccscheck: error", and warnings preceded by "sccscheck: warning".
  20 
  21        By default an out-of-date source file is treated as a non-event, and
  22        the build continues onward; in most cases this will avoid unnecessary
  23        rebuilds of other targets depending on the out-of-date source file.
  24 
  25 ENVIRONMENT
  26        If set to a non-empty string, SCCSCHECK_WARN will cause sccscheck to
  27        emit a verbose warning when an out-of-date source file is encountered;
  28        the build will continue but the resulting build logs will be large.
  29 
  30        If set to a non-empty string, SCCSCHECK_FAIL will cause sccscheck to
  31        treat out-of-date source files as an error rather than a warning.
  32 
  33        If both are set, behavior will be as if only SCCSCHECK_FAIL is set.
  34 
  35 
  36 
  37 
  38 
  39 
  40                                  7 April 2006                     sccscheck(1)

   1 sccscheck(1ONBLD)             illumos Build Tools            sccscheck(1ONBLD)
   2 
   3 
   4 
   5 NAME
   6        sccscheck -
   7 
   8 SYNOPSIS
   9        sccscheck filename
  10 
  11 DESCRIPTION
  12        The standard solaris make(1) is SCCS-aware, automatically checking out
  13        files if they are out of date with respect to the SCCS file; however,
  14        this is of little value in the context of teamware and of no value if a
  15        non-SCCS SCM system is used, and can lead to hard-to-diagnose build
  16        failures  in the presence of recursive parallel make.  The sccscheck
  17        script is used from the OS/Net Makefile.master file as a substitute for
  18        make(1)'s default handling of SCCS files; it generates errors preceded
  19        by "sccscheck: error", and warnings preceded by "sccscheck: warning".
  20 
  21        By default an out-of-date source file is treated as a non-event, and
  22        the build continues onward; in most cases this will avoid unnecessary
  23        rebuilds of other targets depending on the out-of-date source file.
  24 
  25 ENVIRONMENT
  26        If set to a non-empty string, SCCSCHECK_WARN will cause sccscheck to
  27        emit a verbose warning when an out-of-date source file is encountered;
  28        the build will continue but the resulting build logs will be large.
  29 
  30        If set to a non-empty string, SCCSCHECK_FAIL will cause sccscheck to
  31        treat out-of-date source files as an error rather than a warning.
  32 
  33        If both are set, behavior will be as if only SCCSCHECK_FAIL is set.
  34 
  35 
  36 
  37 
  38 
  39 
  40                                  7 April 2006                sccscheck(1ONBLD)