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