#39523: zlib doesn't build when clang is the default compiler (/usr/bin/cc) -----------------------+-------------------------- Reporter: daniel@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: haspatch Port: zlib | -----------------------+-------------------------- Changes (by ryandesign@…): * keywords: => haspatch * cc: landonf@… (added) Old description:
When Clang is used as the default compiler (i.e., /usr/bin/cc) then the zlib configure script may fail to properly detect that the compiler is "gcc"-like. This in turn causes the configure script to follow a slightly different code path which then fails to properly compute the shared library extension on Darwin.
This is effectively the same problem as: http://trac.macports.org/ticket/28656 but when the compiler path doesn't include clang in it.
The attached patch (also submitted upstream to zlib maintainers) fixes the problem by patching the configure script.
New description: When Clang is used as the default compiler (i.e., /usr/bin/cc) then the zlib configure script may fail to properly detect that the compiler is "gcc"-like. This in turn causes the configure script to follow a slightly different code path which then fails to properly compute the shared library extension on Darwin. This is effectively the same problem as: #28656 but when the compiler path doesn't include clang in it. The attached patch (also submitted upstream to zlib maintainers) fixes the problem by patching the configure script. -- Comment: There should be no circumstance in MacPorts when $CC is /usr/bin/cc. See UsingTheRightCompiler for why. Are you encountering an actual issue with this port in MacPorts? If so, could you describe it or show the error you get? Are we perhaps in some way forgetting to tell the zlib configure script to use $CC? -- Ticket URL: <https://trac.macports.org/ticket/39523#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X