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 for sun4v and Netra T1 users

Date: Thu, 15 Sep 2005 16:41:43 -0600
From: "Mark J. Nelson" <Mark dot J dot Nelson at Sun dot COM>
To: on-all at Sun dot COM, onnv-gate at onnv dot eng dot sun dot com
Subject: Flag Day for sun4v and Netra T1 users

If you use Niagara (sun4v) machines, or any of the following platforms:

> SUNW,Ultra-1-Engine
> SUNW,UltraAX-MP
> SUNW,UltraAX-e
> SUNW,UltraAX-e2
> SUNW,UltraSPARC-IIi-Engine
> SUNW,UltraSPARC-IIi-cEngine
> SUNW,UltraSPARCengine_CP-20
> SUNW,UltraSPARCengine_CP-40
> SUNW,UltraSPARCengine_CP-60
> SUNW,UltraSPARCengine_CP-80

...then you SHOULD READ THIS NOTE.  Otherwise, do what you like.



Executive summary: DO NOT USE SOS10-built bits on the aforementioned 
platforms.



Due to an unfortunate combination of

	6323803 compiler bug causes __*mul64 failure; svc.configd dies

and

	6324631 sparc hwmuldiv support should be in libc

and missing platform library links on the aforementioned machines, those 
platforms are essentially unusable with onnv archives built after the 
putback of

	6316914 changes in ON needed for Vulcan (SunStudio 10) compiler switch

on Wednesday, September 7.

How do you tell if you're affected?  You'll see the following error 
message on boot:

> Executing last command: boot                                          
> Boot device: /pci@1f,0/pci@1,1/scsi@2/disk@0,0:b  File and args: 
> SunOS Release 5.11 Version onnv-clone.1-7920321 64-bit
> Copyright 1983-2005 Sun Microsystems, Inc.  All rights reserved.
> Use is subject to license terms.
> DEBUG enabled
> misc/forthdebug (497677 bytes) loaded
> svc.configd: Fatal error: invalid integer "10" in field "id"
> svc.configd: Fatal error: invalid integer "10" in field "id"
> svc.configd: Fatal error: invalid integer "10" in field "id"

What should you do?  Either bfu to the onnv_23 archives, or override the 
following settings from usr/src/Makefile.master in your build environment:

> # Base directory where compilers are loaded.
> # Defined here so it can be overridden by developer.
> #
> SPRO_ROOT=		$(BUILD_TOOLS)/SUNWspro
> SPRO_VROOT=		$(SPRO_ROOT)/SOS10
> GNU_ROOT=		$(SFW_ROOT)


...in particular, set SPRO_VROOT to reference SOS8 instead of SOS10.

When will the madness stop?  Watch for a putback of

	6324631 sparc hwmuldiv support should be in libc

sometime before the close of build 24 (Monday night, Pacific time). 
Once that makes it into the onnv nightly (or your workspace), you'll be 
able to use the resulting archives.  You'll get another note when that 
happens.

Many, many thanks to Jonathan Adams for his work root causing this 
failure, and driving resolution on both the compiler and ON sides.

--Mark