[Zlib-devel] zlib 1.2.6 released

[Mark Adler]

On Jan 29, 2012, at 3:40 PM, Mark Adler wrote:
> zlib 1.2.6 has been released.

And ... there's already a problem.  io.h needs to be included in gzguts.h for Visual Studio.  If someone could take a look at the macro logic there and suggest adjustments to fix this, I would appreciate it.  Thanks.

Also in the report below are some warnings for the assembler code in contrib/masmx86.  The warning appears to have no correlation whatsoever to the lines that they're pointing to, so some help there would be appreciated as well.

Mark



Begin forwarded message:
> From: DK <dk.273c at gmail.com>
> Date: January 29, 2012 1:58:59 PM PST
> To: zlib at gzip.org
> Subject: Zlib V1.2.6 Warnings with Visual Studio 2010
> 
> Hi,
> 
> Just updated to v1.2.6 in my project.
> 
> When Assembling under VS2010, I get the following warnings in inffas32.asm and match686.asm:
> 
> inffas32.asm(162): warning A5000: @@: label defined but not referenced
> match686.asm(198): warning A5000: @@: label defined but not referenced
> 
> which corresponds to the new statements:
> 
> .FPO (16, 4, 0, 0, 1, 0) and .FPO (9, 4, 0, 0, 1, 0) respectively.
> 
> See: http://msdn.microsoft.com/en-US/library/yctw20z4(v=vs.100).aspx
> 
> Not knowing microprocessor assembler, I am not able to fix this.  I prefer not to have even warnings.
> 
> When Compiling under VS2010, I get the following warnings in gzlib.c, gzread.c ad gzwrite.c:
> 
> 1>  gzlib.c
> 1>gzlib.c(182): warning C4013: 'open' undefined; assuming extern returning int
> 1>gzlib.c(206): warning C4013: '_lseeki64' undefined; assuming extern returning int
> 1>  gzread.c
> 1>gzread.c(32): warning C4013: 'read' undefined; assuming extern returning int
> 1>gzread.c(583): warning C4013: 'close' undefined; assuming extern returning int
> 1>  gzwrite.c
> 1>gzwrite.c(86): warning C4013: 'write' undefined; assuming extern returning int
> 1>gzwrite.c(560): warning C4013: 'close' undefined; assuming extern returning int
> 
> These is fixed by explicitly including "#include <io.h> in these 3 source files. However, this may not be your preferred solution.
> 
> Many thanks for a great library.
> 
> Regards,
> 
> David