The OSnet recently switched to the SS12 compiler. This tickled
a latent bug in the link-editor by which undefined symbols are
placed in the ELF symbol sort section:
6752728 link-editor can enter UNDEF symbols in symbol sort sections
Under 6752728, the link-editor was fixed, and the check_rtime script
run by nightly builds was modified to better diagnose the issue.
If your build system is running an OS that predates the integration
of 6752728 (went back on Monday Sept 29), but use the current tools
from the ON gate, then you will see the following errors in your build:
==== Check ELF runtime attributes ====
./usr/lib/libl.so.1: .SUNW_dynsymsort: unexpected UNDEF symbol
(link-editor error): yyfnd
./usr/lib/libl.so.1: .SUNW_dynsymsort: unexpected UNDEF symbol
(link-editor error): yyleng
./usr/lib/libl.so.1: .SUNW_dynsymsort: unexpected UNDEF symbol
(link-editor error): yylsp
./usr/lib/libl.so.1: .SUNW_dynsymsort: unexpected UNDEF symbol
(link-editor error): yyolsp
./usr/lib/libl.so.1: .SUNW_dynsymsort: unexpected UNDEF symbol
(link-editor error): yyout
./usr/lib/libl.so.1: .SUNW_dynsymsort: unexpected UNDEF symbol
(link-editor error): yyprevious
./usr/lib/libl.so.1: .SUNW_dynsymsort: unexpected UNDEF symbol
(link-editor error): yywleng
./usr/lib/sparcv9/libl.so.1: .SUNW_dynsymsort: unexpected UNDEF symbol
(link-editor error): yyfnd
./usr/lib/sparcv9/libl.so.1: .SUNW_dynsymsort: unexpected UNDEF symbol
(link-editor error): yyleng
./usr/lib/sparcv9/libl.so.1: .SUNW_dynsymsort: unexpected UNDEF symbol
(link-editor error): yylsp
./usr/lib/sparcv9/libl.so.1: .SUNW_dynsymsort: unexpected UNDEF symbol
(link-editor error): yyolsp
./usr/lib/sparcv9/libl.so.1: .SUNW_dynsymsort: unexpected UNDEF symbol
(link-editor error): yyout
./usr/lib/sparcv9/libl.so.1: .SUNW_dynsymsort: unexpected UNDEF symbol
(link-editor error): yyprevious
./usr/lib/sparcv9/libl.so.1: .SUNW_dynsymsort: unexpected UNDEF symbol
(link-editor error): yywleng
This is as expected. The objects were built by a linker that does not
have the fix, and check_rtime is properly reporting the issue.
The solution is to upgrade the build system. However, these errors are
relatively benign, and will not prevent your objects from working properly.
There is therefore no need to rush an upgrade for this reason alone.
- Ali
