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: 6488141 ld(1) should detect attempt to reference 0-length

Date: Wed, 29 Nov 2006 14:56:12 -0700
From: Ali Bahrami <Ali.Bahrami at Sun dot COM>
To: on-all at Sun dot COM, onnv-gate at onnv dot eng dot sun dot com
Subject: Flag Day: 6488141 ld(1) should detect attempt to reference 0-length

The integration of

	6488141 ld(1) should detect attempt to reference 0-length .bss section

represents a flag day if all three of the following conditions are true:

	- You are building on X86 (not sparc),
	- You are using build 54 or newer of Solaris
	  on your build host, and
	- You are building a workspace based on build 53 or
	  older.

You may safely ignore this message otherwise.

In the failure case, your build will fail with an error like:

	ld: fatal: symbol `intr_thread_cnt' in file debug32/interrupt.o:
		section [4] .data: size 0: symbol (address 0, size 4) lies
		outside of containing section
	ld: fatal: File processing errors. No output written to debug32/unix.o

This error comes when compiling usr/src/uts/i86pc/ml/interrupt.s. Note
that interrupt.s has had this error for a long time --- what has changed
is that the build 54 or new linker properly catches the error instead of
quietly generating a bad output file. The flaw is in code that only appears
in debug builds.

To avoid this situation, you can take either of the following measures:

	- Use a build host running Nevada build 53 or older

	- Update your workspace to get a newer copy of
	  usr/src/uts/i86pc/ml/interrupt.s The fix is a one-liner
	  that appears on line 527, replacing:

		DGDEF(intr_thread_cnt)

	  with
		DGDEF(intr_thread_cnt)
		.4byte  0
		
- Ali