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

incremental flag-day in sun4u cpumem-diagnosis

Date: Mon, 21 Nov 2005 16:08:37 -0800
From: Danek Duvall <danek dot duvall at sun dot com>
To: onnv-gate at onnv dot eng dot sun dot com
Subject: incremental flag-day in sun4u cpumem-diagnosis

The putback for

    PSARC 2005/465 FMA for UltraSPARC-T1 CPU/Memory
    6278369 enhance C-based diagnosis engine for Niagara CPU diagnosis
    6336193 FRU FMRI for cpu fault is not in hc: scheme format

introduced a flag-day for incremental builders.  The putback moved

    usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cpumem-diagnosis.conf

to

    usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cpumem-diagnosis.conf

If a build had already been done in that directory, then a read-only copy
of ../../sun4/cpumem-diagnosis/cpumem-diagnosis.conf (copied at build-time)
will exist in the sun4u directory.  If this file is not removed, then a
bringover will include these lines:

     rename from: usr/src/cmd/fm/modules/sun4/cpumem-diagnosis/cpumem-diagnosis.conf
              to: usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cpumem-diagnosis.conf
     bringover: Can't rename to "usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cpumem-diagnosis.conf"; it exists  (Error 2051)

     bringover warning: files with errors: 1

     bringover: Can't rename to "usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cpumem-diagnosis.conf"; it exists  (Error 2051)

If you ignore this, the build will still succeed, but this one file will
not be correct in the proto area (and hence the BFU archives and packages).
Simply removing the file before the bringover (or running a clobber build)
will resolve the issue.

Danek