Chromium upstream has forked zlib due to some security issue; I don't have access to the upstream bug. http://src.chromium.org/viewvc/chrome?view=rev&revision=151720 They have introduced some incompatible changes, causing the following error when building with system zlib. /spdy/spdy_proxy_client_socket.o net/spdy/spdy_proxy_client_socket.cc net/spdy/spdy_framer.cc:669:20: error: ‘Z_CLASS_STANDARD’ was not declared in this scope net/spdy/spdy_framer.cc:675:18: error: ‘Z_CLASS_COOKIE’ was not declared in this scope net/spdy/spdy_framer.cc:678:23: error: ‘Z_CLASS_HUFFMAN_ONLY’ was not declared in this scope net/spdy/spdy_framer.cc: In function ‘void net::WriteZ(const StringPiece&, net::ZDataClass, z_stream*)’: net/spdy/spdy_framer.cc:690:12: error: ‘z_stream’ has no member named ‘clas’ net/spdy/spdy_framer.cc:701:8: error: ‘z_stream’ has no member named ‘clas’ net/spdy/spdy_framer.cc: In member function ‘void net::SpdyFramer::WriteHeaderBlockToZ(const SpdyHeaderBlock*, z_stream*) const’: net/spdy/spdy_framer.cc:811:6: error: ‘z_stream’ has no member named ‘clas’
(In reply to comment #0) > Chromium upstream has forked zlib due to some security issue; I don't have > access to the upstream bug. > > http://src.chromium.org/viewvc/chrome?view=rev&revision=151720 > > They have introduced some incompatible changes, causing the following error > when building with system zlib. I do have access to that bug, and indeed upstream has made API changes which means we have to see what upstream zlib does. This may take a longer time to get fixed properly.
We use system zlib in chromium-24.0.1305.3.
