Comment #4 on issue 31545 by John.Cunningham.Bowler: update libpng to 1.4
http://code.google.com/p/chromium/issues/detail?id=31545
You will face the same issue that you face with libjpeg.so.62 vs
libjpeg.so.7.
Chromium (the browser) compiles fine against libpng 1.4.0 once the use of
the png
NULL macros has been fixed (see attached patch), however libpng12.so.12 and
libpng14.so.14 can be installed in parallel and are *not* ABI compatible.
(No
surprise there I hope.)
This really is a system builder issue - if someone is building systems and
distributing binaries it is up to the distributor to ensure everything gets
built
against the same core libraries or that the core libraries have symbol
versioning.
(Symbol versioning allows you to use two different ABI versions in the same
program.)
Including your own copies of the libraries is not just distributing
bloatware; it
forces you to track all the security issues and re-issue both binary and
source PDQ
when an issue is discovered. You will probably find that you end up
loading the
shared library too anyway: last time I tried I could not persuade ld.so to
link back
against symbols in the main program without major work.
BTW libpng1.2 is fully supported - it gets any security fixes. The main
point of
1.4 is to allow changes that can't be made without an ABI change, in
particular the
use of non-Western European text in the values of keyword comments.
Attachments:
chromium-4.0.251.0-libpng-1.4.patch 2.0 KB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
