From 10daf0d4d7815447799d555d04d30325836e1d44 Mon Sep 17 00:00:00 2001 From: Mark Adler Date: Sun, 11 Sep 2011 11:04:49 -0700 Subject: zlib 1.2.5.1 --- FAQ | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'FAQ') diff --git a/FAQ b/FAQ index 1a22750..03676dd 100644 --- a/FAQ +++ b/FAQ @@ -84,8 +84,10 @@ The lastest zlib FAQ is at http://zlib.net/zlib_faq.html 13. How can I make a Unix shared library? - make clean - ./configure -s + By default a shared (and a static) library is built for Unix. So: + + make distclean + ./configure make 14. How do I install a shared zlib library on Unix? @@ -325,7 +327,7 @@ The lastest zlib FAQ is at http://zlib.net/zlib_faq.html correctly points to the zlib specification in RFC 1950 for the "deflate" transfer encoding, there have been reports of servers and browsers that incorrectly produce or expect raw deflate data per the deflate - specficiation in RFC 1951, most notably Microsoft. So even though the + specification in RFC 1951, most notably Microsoft. So even though the "deflate" transfer encoding using the zlib format would be the more efficient approach (and in fact exactly what the zlib format was designed for), using the "gzip" transfer encoding is probably more reliable due to -- cgit v1.2.3-55-g6feb