OpenSolaris

1. Community: OS/Net (ON)
   1. Blogs
   2. Development Process
   3. Developer's Reference
      1. Introduction
      2. Prerequisites
      3. The Source Tree, part 1
      4. The Source Tree, part 2
      5. Building OpenSolaris
      6. Installing and Testing OpenSolaris
      7. Integration Procedure
      8. Best Practices and Requirements
      9. Glossary
   4. Discussions
   5. Installation (from source) Quickstart
      1. Annotated nightly(1) Mail Example
   6. Currently Known Issues
   7. CRT
      1. Advocates & Sponsors
      2. Becoming a CRT Advocate
      3. Charter
      4. RTI nits to avoid
      5. Sponsor Tasks
      6. Becoming a Sponsor
   8. Schedule
   9. ONNV Flag Days, Heads Ups, and Project Integration History
      1. All
      2. Builds 91-95
      3. Builds 86-90
      4. Builds 81-85
      5. Builds 76-80
      6. Builds 71-75
      7. Builds 66-70
      8. Builds 61-65
      9. Builds 56-60
      10. Builds 51-55
      11. Builds 46-50
      12. Builds 41-45
      13. Builds 36-40
      14. Builds 31-35
      15. Builds 26-30
      16. Builds 21-25
   10. Leaders
   11. Observers
   12. Putback Logs
   13. Developing Solaris
       1. Quality Death Spiral
   14. wx
   15. findunref and unreferenced files
   16. Bourne/Korn Shell Coding Conventions

Flag day: sccscheck, bringovercheck, and ctfmerge failures (the

Date: Fri, 14 Apr 2006 11:59:38 -0400
From: Bill Sommerfeld <sommerfeld at sun dot com>
To: on-all at sun dot com, onnv-gate at onnv dot eng dot sun dot com
Subject: Flag day: sccscheck, bringovercheck, and ctfmerge failures (the

There is an additional wrinkle to this flag day which I failed to
adequately describe yesterday.  While you can easily cross this flag day
with either an incremental build OR checked-out sources in your
workspace, you cannot cross it with an incremental build AND checked-out
sources.

If you attempt this, dmake will abort with an error resembling:

dmake: Fatal error: ../../common/inet/ip/ip_rts.c is writable so it
cannot be sccs gotten

There are several ways around this, including:

 - A full clobber build via nightly, which will delete .make.state
files.

 - Check the file in and run a full or selective incremental build.

 - Selective "make clobber" and deletion of ".make.state" files in any
build directories referencing the source file.

Once you are across this flag day you can resume incremental builds with
checked out source files.

Background
----------

Pre-flag-day .make.state files include an assumed "sccs get" rule for
every source file.  This flag day changes the command for sccs checkouts
to "sccscheck", and dmake assumes the change in command requires the new
command to be run, but refuses to let it run if the source file is
writable.  You can either cause dmake to forget about the change by
deleting the .make.state files, or let it run once with all source files
read-only, which will update the .make.state files.

					- Bill