[Zlib-devel] zlib 1.2.4.3 for your perusal

[John Bowler]

From: Alon Bar-Lev [mailto:alon.barlev at gmail.com] 
>Either the ./configure && make produces the correct output or we need
>to keep using the Makefile.gcc.

We?  The problem arose because ./configure *did* 'work' on zlib-1.2.3 and zlib-1.2.4, however .4 started building the shared library when the obvious bug of the spurious -lc in the Makefile was fixed...  That's what I fixed.

There's nothing in the system to *stop* the library being built on MinGW/MSYS with the configure route, so it will get used - hence my "we?" question.

If the correct fix is to *never* build MinGW with configure then that's easy to fix too (with Mark's version of my original fix):

	echo "Use win32/Makefile.gcc to build MinGW, configure builds are not supported"
	exit 1;;

What about Cygwin?  As I said, it has the same problems (the .def is not used, the .rc is not used, the output names are not libz.a and cygz.dll/libz.dll.a, though the shared library build is disabled.)

Since I'm new to this I don't know what the official names are, but what I see is the following list:

Cygwin:	/bin/cygz.dll+/lib/libz.dll.a (DLL+implib), /lib/libz.a
		/bin/mgwz.dll+/lib/mingw/libz.dll.a (DLL+implib for MinGW), /lib/mingw/libz.a
MinGW:	'system32'\zlib1.dll+/lib/libzdll.a (DLL+implib), /lib/libz.a
VS:		'system32'\zlib1.dll+'libdir'\zdll.lib (DLL+implib), 'libdir'\zlib.lib

Correct?

John Bowler <jbowler at acm.org>