@evan: why can't you get the fix too? if i move back to system-libs, it's
fine, so the
problem is on your side.
--
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
Comment #9 on issue 38073 by ev...@chromium.org:
third_party/libxml/xmlIO.c:1132: warning: implicit declaration of
function 'gzopen64' on newer systems
http://code.google.com/p/chromium/issues/detail?id=38073
Oh, maybe our copy is of the bad one? I will investigate again.
Comment #10 on issue 38073 by ev...@chromium.org:
third_party/libxml/xmlIO.c:1132: warning: implicit declaration of
function 'gzopen64' on newer systems
http://code.google.com/p/chromium/issues/detail?id=38073
Our copy of zlib is fine (no mention of gzopen64).
I am now pretty sure the problem is just the bad system zlib on lucid, but
I've been
wrong a bunch of times now so I am not positive. :)
There's not much i can do. Your in-source libxml expects an old zlib
(1.2.3, released
in 2005).
Debian/Ubuntu have 1.2.3.3 (also old) + a few x64 patches.
Upstream merged them in 1.2.3.4, then released .5 up to .9 and now 1.2.4
(14 Mar
2010) with tons of changes compared to your old in-source 1.2.3: see
http://zlib.net/ChangeLog.txt
as a desperate measure (as i get lots of complains from jaunty x64 users),
i can try
to move to in-source zlib for intrepid and jaunty :(
How does the in-source libxml depend on that older zlib? (I still don't
understand,
sorry!)