Install failed, "zlib not available" on macOS Mojave

[tshu-w]

Description

• Platform information (e.g. Ubuntu Linux 16.04): macOS Mojave 10.14
• OS architecture (e.g. amd64):amd64
• pyenv version: 1.2.7
• Python version: 3.7.0 & 2.7.15
• C Compiler information (e.g. gcc 7.3): Apple LLVM version 10.0.0 (clang-1000.11.45.2)
• Please attach verbose build log as gist

see Homebrew/homebrew-core#29176 (comment)

Temporary workaround:

CFLAGS="-I$(xcrun --show-sdk-path)/usr/include" pyenv install ...

[joshfriend]

I just upgraded to Mojave and had the same problem. The commandline tools headers package fixed it, but it feels like a hack

[DC-ing]

I have the same problem, but I can solve it after watch wiki

[benmezger]

Solved it by running: sudo installer -pkg /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg -target /

[codezakh]

Apparently this is happening because Xcode Command Line tools no longer installs needed headers in /include. You have to run a separate command to install the needed headers.

See https://developer.apple.com/documentation/xcode_release_notes/xcode_10_release_notes.

The command line tools will search the SDK for system headers by default. However, some software may fail to build correctly against the SDK and require macOS headers to be installed in the base system under /usr/include. If you are the maintainer of such software, we encourage you to update your project to work with the SDK or file a bug report for issues that are preventing you from doing so. As a workaround, an extra package is provided which will install the headers to the base system. In a future release, this package will no longer be provided. You can find this package at:
/Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg

To make sure that you're using the intended version of the command line tools, run xcode-select -s or xcode select -s /Library/Developer/CommandLineTools after installing.

[joshfriend]

I've added this to the suggested build environment and common build problems wiki pages for now until a better solution is found

[qianxiaowei]

I'm now working on Mojave, and followed the solution provided by @thetylerwolf , and it works.

I'm running OS X Sierra and the above didn't help for me. Found this solution here: https://medium.com/@pimterry/setting-up-pyenv-on-os-x-with-homebrew-56c7541fd331
and it did work.

CFLAGS="-I$(brew --prefix readline)/include -I$(brew --prefix openssl)/include -I$(xcrun --show-sdk-path)/usr/include" \
LDFLAGS="-L$(brew --prefix readline)/lib -L$(brew --prefix openssl)/lib" \
PYTHON_CONFIGURE_OPTS=--enable-unicode=ucs2 \
pyenv install -v 3.6.0

[chenguanda]

I'm now working on Mojave too, followed the solution provded by @Voleking, I fixed the error of zlib, but not openssl ,

ERROR: The Python ssl extension was not compiled. Missing the OpenSSL lib?

I fix it by run the following command

CFLAGS="-I$(brew --prefix openssl)/include" LDFLAGS="-L$(brew --prefix openssl)/lib" pyenv install 3.6.0

[zanderzhng]

I didn't have CLT installed in my Mojave so I couldn't install the headers pkg.
@qianxiaowei 's code worked for me, but I'm wondering if following commands would be enough. below code are enough.

CFLAGS="-I$(xcrun --show-sdk-path)/usr/include" pyenv install -v 3.7.0

[ssbarnea]

Indeed, the wiki page is misleading as it contains commands that would not work with current released versions of Mojave and xcode 10 but the simple command above works perfects.

Please fix this so we don't need to manually hack CFLAGS to amke it work.

[joshfriend]

@ssbarnea you are always welcome to edit the wiki if you think it is incorrect.