新用户求助：MacOS 10.13.3无法安装Plone 5.0.8

Hey there, let’s tackle this Plone installation hurdle together. Older macOS versions like 10.13.3 can have quirky dependency conflicts with the Unified Installer, especially when mixing system Python and Homebrew packages. Here’s a structured approach to get your site up and running:

1. Clean Up Residual Files & Avoid Python Conflicts #

First, let’s clear out any leftover files from previous attempts and make sure system Python takes priority over Homebrew’s:

• Kill any stray Plone processes (if they exist):

  ps aux | grep plone
  kill <PID_NUMBER>  # Replace <PID_NUMBER> with the process ID from the output
  

• Delete the installer’s build cache to start fresh:

  rm -rf ./buildout-cache
  

• Unlink Homebrew’s Python 2.7 to prevent it from overriding the system version:

  brew unlink python@2
  

2. Ensure Full Dependencies Are Installed & Configured #

Even with Xcode and command line tools installed, older macOS needs explicit setup for libraries Plone relies on:

• Verify your Xcode command line tools path is correct:

  xcode-select -p
  

  If the output isn’t /Applications/Xcode.app/Contents/Developer, set it with:

  sudo xcode-select -s /Applications/Xcode.app/Contents/Developer
  

• Install critical libraries via Homebrew:

  brew install openssl readline zlib
  

• Set environment variables so the installer can find these libraries (run these in your terminal before installing, or add them to ~/.bash_profile/~/.zshrc for persistence):

  export LDFLAGS="-L/usr/local/opt/openssl/lib -L/usr/local/opt/zlib/lib"
  export CPPFLAGS="-I/usr/local/opt/openssl/include -I/usr/local/opt/zlib/include"
  export PATH="/usr/local/opt/readline/bin:$PATH"
  

3. Run the Installer Correctly #

Skip using sudo unless you’re installing to a system directory—most users should install in their home folder to avoid permission issues:

• First, run the preflight check without sudo to validate dependencies:

  ./preflight
  

  This will tell you exactly what’s missing if anything.
• If preflight passes, run the installer with verbose logging to catch any errors in detail:

  ./install.sh --verbose --target ~/Plone
  

  The --target ~/Plone flag installs Plone in your home directory, which is safer and easier to manage.

4. Troubleshoot Persistent Python/Compiler Errors #

If you still hit issues like clang failures or SSL errors:

• Upgrade the system’s pip to the latest compatible version:

  sudo easy_install --upgrade pip
  

• Install virtualenv and run the installer inside an isolated environment (this avoids system Python conflicts):

  sudo pip install virtualenv
  virtualenv --python=/usr/bin/python2.7 plone-env
  source plone-env/bin/activate
  ./install.sh --target ~/Plone
  

5. Common Error Fixes #

• Clang exit status 1: Double-check your LDFLAGS and CPPFLAGS are set correctly—this usually means the compiler can’t find a required library.
• SSL-related errors: Ensure the openssl environment variables are active, and that Homebrew’s openssl is installed (the system’s default openssl is often outdated for Plone 5.0.8).

内容的提问来源于stack exchange，提问作者Felipe Lukavei