>Number:         30645
>Category:       pkg
>Synopsis:       zlib versions confused on MacOS X 10.2.8
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jul 01 01:12:00 +0000 2005
>Originator:     John D. Baker
>Release:        Mac OS X 10.2.8
>Organization:
>Environment:
Darwin pm7500.technoskunk.fur 6.8 Darwin Kernel Version 6.8: Wed Sep 10 15:20:55 PDT 2003; root:xnu/xnu-344.49.obj~2/RELEASE_PPC  Power Macintosh powerpc

>Description:
Packages which depend on zlib (libz.dylib) are getting confused between
the version supplied with the system (1.1.3 on MacOS X 10.2.x) and the
version explicitly built as a dependency through pkgsrc (1.2.2).

See pkg/30625 for an example of build failure.

Also, when installing archivers/unzip-5.52nb1, the following was
observed:

[...]
===> Registering installation for unzip-5.52nb1
unzip-5.52nb1 requires installed package zlib-1.2.2
===> Returning to build of mng-1.0.9
warning:  different zlib version (expected 1.1.3, using 1.2.2)
[...]


There may be other examples, but these are the first two I've seen.
>How-To-Repeat:
On Mac OS X 10.2.8

cd .../pkgsrc/graphics/libwmf
bmake

cd .../pkgsrc/archivers/unzip
bmake install
>Fix:
Don't know how to do this, but is it possible to change the search
order for include files, so /usr/pkg/include/zlib.h is found before
/usr/include/zlib.h?

The linker seems to be doing the right thing, but the compiler/preprocesor
is picking up the system-supplied header file instead of the pkgsrc-
installed one, or in the case of libwmf, it's picking both of them up and
complaining.

MacOS X 10.3.9 and later appear not to have this problem (but the machine
in question can't run anything later than 10.2.8).