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 96-100
      3. Builds 91-95
      4. Builds 86-90
      5. Builds 81-85
      6. Builds 76-80
      7. Builds 71-75
      8. Builds 66-70
      9. Builds 61-65
      10. Builds 56-60
      11. Builds 51-55
      12. Builds 46-50
      13. Builds 41-45
      14. Builds 36-40
      15. Builds 31-35
      16. Builds 26-30
      17. 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

Heads up: extended ldd(1) functionality - check_rtime affected.

Date: Sun, 1 Jun 2008 21:37:56 -0700 (PDT)
From: Rod Evans <Rod.Evans at sun dot com>
To: onnv-gate at onnv dot sfbay dot sun dot com
Subject: Heads up: extended ldd(1) functionality - check_rtime affected.

The integration of:

 6686343 ldd(1) - unused search path diagnosis should be enabled

represents a minor flag day for OSNet developers.

This version of ldd/ld.so.1 reveals unused search paths that might be
specified via LD_LIBRARY_PATH or by individual object runpaths.  This
validation was developed primarily to catch users who use excessive
LD_LIBRARY_PATH settings (many associated to slow responding, or
non-existent NFS paths).  However, the same logic catches unused
runpath settings (encoded within objects using ld(1) -R).

Prior to this putback, the OSNet build was purged of 99% of unnecessary
runpaths, see:

 6683064: check_rtime could do with some spring cleaning,

which was integrated in build snv_90.  This cleanup was required because
ldd(1) -rU is used as part of the OSNet check_rtime() processing, which
in turn is used by nightly with the -A option.  However, a couple of
new unused runpath users have crept in since 6683064 was integrated,
thus the putback of 6686343 has some addition cleanup.

If you have new OSNet components that have unused runpath components, or
you install these new bits and build a environment that is pre-6683064,
(pre-snv_90), and exercise check_rtime, or ldd -U, then you'll see
diagnostics of the form:

 unused search path=/xxx/lib  (RUNPATH/RPATH from file /lib/libyyy.so.1)

If a runpath is determined to be unused by an object to find its
dependencies, then the runpath should be removed.  The runpath
serves no purpose and adds unnecessary runtime search overhead.

--
Rod.