I have a gripe with the Sun linker and am wondering if anyone knows of a
workaround. We build our shared libraries with -Bsymbolic. Yes, we
understand the semantics of -Bsymbolic and we still want them.
Unfortunately, even though we've asked for this behavior, the linker
emits pseudo-error messages such as the following (names anonymized):

Undefined first referenced
symbol in file
fclose xxxxx.o
fscanf yyyyy.o
getenv zzzzz.o
void __Crun::register_exit_code(void(*)()extern"C") aaaaaaaaaa.o
void operator delete(void*) aaaaaaaaaa.o
ld: warning: Symbol referencing errors

This is annoying because (a) the presence of these non-error errors can
confuse developers or release engineers looking through a logfile and
(b) this nannyish over-verbosity smacks of Windows[*]. So - do any
linker experts know how to say "give me what I want without warning me
that you're giving me what I want"?
[*] Personally I just hate when you quit a Windows install and even
after asking if you're sure it prints a message to the effect of
"warning, your install did not complete successfully". Or when you quit
Remote Desktop and it gives a warning to the effect that "you're not
going to lose any data; everything will be just the same when you
reconnect". I prefer to think of my relationship with Solaris as being a
little more mature.

Thanks,
HT