|
|
Heads Up: PSARC 2006/526 can cause harmless ".SUNW_ldynsym has invalid
Date: Mon, 25 Sep 2006 21:02:52 -0600
From: Ali Bahrami <Ali.Bahrami at sun dot com>
To: onnv-gate at onnv dot eng dot sun dot com, on-all at sun dot com
Subject: Heads Up: PSARC 2006/526 can cause harmless ".SUNW_ldynsym has invalid
Last Tuesday (Sept 19th), I integrated:
PSARC 2006/526 SHT_SUNW_LDYNSYM - default local symbol addition
4934427 runtime linker should load up static symbol names visible to dladdr()
to the Nevada gate. This change introduces a new ELF section type into
Solaris sharable objects and dynamic executables named ".SUNW_ldynsym".
The purpose of this new section is to make local function symbols available
in contexts where only the dynsym symbol table is available (either the
file is stripped, or the process is examining itself via dladdr(3C)).
This change does not require you to adjust your workspace or environment.
As such, we did not feel that a "Heads Up" message was warranted.
However, some people have encountered warnings of the form:
ld: warning: file /ws/onnv-clone/proto/root_sparc/lib/libc.so: section
.SUNW_ldynsym has invalid type 0x6ffffff3
These warnings are harmless and may be safely ignored. They occur if you
are using a system with an older (non-ldynsym aware) version of the linker,
but are feeding it sharable objects that contain .SUNW_ldynsym sections.
The most likely way to trigger this is when you're using ws, or otherwise
setting your environment up to pull libraries from the gate machine, or
another proto area that's been built with the new linker.
To eliminate the warnings, you can do one of the following:
- Pull your sharable objects from a proto area that
predates Tuesday the 19th.
- BFU from any Nevada nightly build that includes
the changes from Tuesday the 19th.
- Install build 50 once it is available (not for a couple
of weeks yet).
- Ali
|