- 13 8月, 2012 1 次提交
-
-
由 Mark Adler 提交于
This patch allows zlib to compile cleanly with the -Wcast-qual gcc warning enabled, but only if ZLIB_CONST is defined, which adds const to next_in and msg in z_stream and in the in_func prototype. A --const option is added to ./configure which adds -DZLIB_CONST to the compile flags, and adds -Wcast-qual to the compile flags when ZLIBGCCWARN is set in the environment.
-
- 09 7月, 2012 3 次提交
-
-
由 Mark Adler 提交于
-
由 Mark Adler 提交于
-
由 Birunthan Mohanathas 提交于
-
- 07 7月, 2012 2 次提交
-
-
由 Thomas Roß 提交于
-
由 Thomas Roß 提交于
-
- 10 6月, 2012 4 次提交
-
-
由 Mark Adler 提交于
There were two problems before that this fixes. One was that the check for the compiler error return code preceded the determination of the compiler and its options. The other was that the checks for compiler and library characteristics could be fooled if the error options were set to reject K&R-style C. configure now aborts if the compiler produces a hard error on K&R-style C. In addition, aborts of configure are now consistent, and remove any temporary files.
-
由 Mark Adler 提交于
-
由 Mark Adler 提交于
-
由 Mark Adler 提交于
The original change was to always use /usr/bin/libtool on Darwin, in order to avoid using a GNU libtool installed by the user in the path ahead of Apple's libtool. However someone might install a more recent Apple libtool ahead of /usr/bin/libtool. This commit checks to see if libtool is Apple, and uses /usr/bin/libtool if it isn't.
-
- 04 6月, 2012 2 次提交
-
-
由 Mark Adler 提交于
-
由 Mark Adler 提交于
More than a decade later, Microsoft C does not support the C99 standard. It's good that _snprintf has a different name, since it does not guarantee that the result is null terminated, as does snprintf. However where _snprintf is used under Microsoft C, the destination string is assured to be long enough, so this will not be a problem. This occurs in two places, both in gzlib.c. Where sprintf functionality is needed by gzprintf, vsnprintf is used in the case of Microsoft C.
-
- 03 6月, 2012 1 次提交
-
-
由 Mark Adler 提交于
-
- 27 5月, 2012 1 次提交
-
-
由 Mark Adler 提交于
-
- 23 5月, 2012 1 次提交
-
-
由 Mark Adler 提交于
-
- 21 5月, 2012 1 次提交
-
-
由 Mark Adler 提交于
-
- 18 5月, 2012 1 次提交
-
-
由 Mark Adler 提交于
-
- 04 5月, 2012 1 次提交
-
-
由 Mark Adler 提交于
-
- 03 5月, 2012 4 次提交
-
-
由 Mark Adler 提交于
This avoids warnings in OpenBSD that apparently can't be turned off whenever you link strcpy, strcat, or sprintf. When snprintf isn't available, the use of the "unsafe" string functions has always in fact been safe, since the lengths are all checked before those functions are called. We do not use strlcpy or strlcat, since they are not (yet) found on all systems. snprintf on the other hand is part of the C standard library and is very common.
-
由 Mark Adler 提交于
-
由 Mark Adler 提交于
-
由 Mark Adler 提交于
-
- 02 5月, 2012 1 次提交
-
-
由 Mark Adler 提交于
-
- 30 4月, 2012 4 次提交
-
-
由 Daniel Snider 提交于
-
由 Mark Adler 提交于
-
由 Mark Adler 提交于
-
由 Mark Adler 提交于
crc_table is made using a four-byte integer (when that can be determined). However get_crc_table() returned a pointer to an unsigned long, which could be eight bytes. This fixes that by creating a new z_crc_t type for the crc_table. This type is also used for the BYFOUR crc calculations that depend on a four-byte type. The four-byte type can now be determined by ./configure, which also solves a problem where ./configure --solo would never use BYFOUR. No the Z_U4 #define indicates that four- byte integer was found either by ./configure or by zconf.h.
-
- 23 4月, 2012 3 次提交
-
-
由 Mark Adler 提交于
-
由 Mark Adler 提交于
-
由 Mark Adler 提交于
-
- 01 4月, 2012 1 次提交
-
-
由 Mark Adler 提交于
-
- 27 3月, 2012 1 次提交
-
-
由 jK 提交于
-
- 23 3月, 2012 1 次提交
-
-
由 Birunthan Mohanathas 提交于
-
- 19 3月, 2012 4 次提交
-
-
由 Mark Adler 提交于
The conversion to multi-byte will be locale-specific, but it's better than nothing and is only to provide more information in the error message returned by gz_error(). The conversion has no effect on what's opened.
-
由 Mark Adler 提交于
-
由 Peter Kuemmel 提交于
-
由 Mark Adler 提交于
Also need to #include <stddef.h> for zlib.h, and need to workaround the inability to use wide characters in constructed error messages with zlib's interface.
-
- 18 3月, 2012 3 次提交
-
-
由 Mark Adler 提交于
-
由 Peter Kuemmel 提交于
-
由 Peter Kuemmel 提交于
-