diff options
| author | Mark Adler <madler@alumni.caltech.edu> | 2011-09-11 11:04:49 -0700 |
|---|---|---|
| committer | Mark Adler <madler@alumni.caltech.edu> | 2011-09-11 11:04:49 -0700 |
| commit | 10daf0d4d7815447799d555d04d30325836e1d44 (patch) | |
| tree | 75579fbe11e42dc3197acca53f5f887ac3808b57 /FAQ | |
| parent | 9712272c78b9d9c93746d9c8e156a3728c65ca72 (diff) | |
| download | zlib-10daf0d4d7815447799d555d04d30325836e1d44.tar.gz zlib-10daf0d4d7815447799d555d04d30325836e1d44.tar.bz2 zlib-10daf0d4d7815447799d555d04d30325836e1d44.zip | |
zlib 1.2.5.1v1.2.5.1
Diffstat (limited to 'FAQ')
| -rw-r--r-- | FAQ | 8 |
1 files changed, 5 insertions, 3 deletions
| @@ -84,8 +84,10 @@ The lastest zlib FAQ is at http://zlib.net/zlib_faq.html | |||
| 84 | 84 | ||
| 85 | 13. How can I make a Unix shared library? | 85 | 13. How can I make a Unix shared library? |
| 86 | 86 | ||
| 87 | make clean | 87 | By default a shared (and a static) library is built for Unix. So: |
| 88 | ./configure -s | 88 | |
| 89 | make distclean | ||
| 90 | ./configure | ||
| 89 | make | 91 | make |
| 90 | 92 | ||
| 91 | 14. How do I install a shared zlib library on Unix? | 93 | 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 | |||
| 325 | correctly points to the zlib specification in RFC 1950 for the "deflate" | 327 | correctly points to the zlib specification in RFC 1950 for the "deflate" |
| 326 | transfer encoding, there have been reports of servers and browsers that | 328 | transfer encoding, there have been reports of servers and browsers that |
| 327 | incorrectly produce or expect raw deflate data per the deflate | 329 | incorrectly produce or expect raw deflate data per the deflate |
| 328 | specficiation in RFC 1951, most notably Microsoft. So even though the | 330 | specification in RFC 1951, most notably Microsoft. So even though the |
| 329 | "deflate" transfer encoding using the zlib format would be the more | 331 | "deflate" transfer encoding using the zlib format would be the more |
| 330 | efficient approach (and in fact exactly what the zlib format was designed | 332 | efficient approach (and in fact exactly what the zlib format was designed |
| 331 | for), using the "gzip" transfer encoding is probably more reliable due to | 333 | for), using the "gzip" transfer encoding is probably more reliable due to |