-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 30/09/15 09:11 AM, Rich Freeman wrote: > > Suppose apache uses libfoo and libbar. Libfoo switches to > libressl, and libbar sticks with openssl. That is going to > create a mess no matter what you do with isolating their > namespaces, because you're forced to bring it all back together > and not all software is designed to handle that today (especially > when you're not using --as-needed, etc). Flameeyes's blog entry > keeps coming up: > https://blog.flameeyes.eu/2008/06/a-few-risks-i-see-related-to-the-n ew-portage-2-2-preserve-libs-behaviour > > That's almost exactly what i had to deal with a while back with the libjs symbols in firefox vs seamonkey -- firefox was linking to libsomething (sorry dont remember the name), and libsomething was built against seamonkey. firefox's libjs was massively newer than seamonkey though and so libsomething would end up using the libjs symbols from within firefox, which was entirely incompatible (and segfaulting would occur as expected).
The fix in that case was the symver mapping i just described in my reply to hasufell. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlYMDfMACgkQAJxUfCtlWe1OtgD/QvaNGYTqsdbNlMHBkbQ+azrP CBNpHwEsm32j5yztEXgBAKVG30m1U7UEH9h1g5rNE7aq6Kp0bdOEKjKHZm84VXAF =9bT/ -----END PGP SIGNATURE-----
