Right now, it's possbile to link against a shared library that
requires a symbol from anothe shared library, and not get any
missing symbol warnings during link phase. This has bit me
on the butt more than once, especially with libraries with
promiscuous symbol reference in other libraries (ie: libraries
that know too much about each other).
You can also, I think, inadvertently create a shared library that
requires nonexistent symbols and not get any warnings until run-time.
Which (I think) amounts to the same problem, because the library
requiring a symbol from another library should have been linked
against that library to create a DT_NEEDED entry. I think.
There's a linker option to use when building libraries that
eliminates this problem. In my opinion, it should be the default, but
it's not, because that's not how Solaris does it or some crap like
- David A. Holland | (please continue to send non-list mail to
dhol...@cs.utoronto.ca | dhol...@hcs.harvard.edu. yes, I moved.)
To Unsubscribe: send mail to majo...@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message