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: CTF build changes

Date: Wed, 13 Sep 2006 20:15:26 +0100
From: John Levon <john.levon at sun dot com>
To: on-all at sun dot com, onnv-gate at onnv dot eng dot sun dot com
Subject: Flag day: CTF build changes


With the putback of:

6415645 cpu_t hack isn't working as expected

ctfconvert performs a sanity check on the contents of the kernel type cpu_t (in
particular, that the last member before cpu_m is "cpu_m_pad", as described in
the inline comment). If you try using this or later versions of ctfconvert on a
workspace without the corresponding kernel changes, you will see a build error
such as:

ERROR: ctfconvert: last cpu_t member before cpu_m is cpu_physid; it must be
cpu_m_pad.

To avoid this problem, you can either use the -t option to nightly to use the
tools within the workspace, or use:

export CTFCONVERT_PERMISSIVE=1

in the environment to disable the error checking. The consequences of not
performing this check can lead to incorrect CTF, so caveat emptor.

Apologies for any inconvenience this may cause.

regards,
john