Skip to content

Known installation issues

Jump to bottom
Antonio Villarreal edited this page Mar 1, 2019 · 16 revisions
  1. If you are having issues with GSL versions linking, please try the following during the configuration step:
./configure CFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib"
  1. If you move or delete the source directory after installing CCL, some functions may fail. The source directory contains files needed by CLASS (which is contained within CCL) at run-time.
  2. If you are planning to compile your own file that calls CCL, then you should add the following to your .bashrc:
export LD_LIBRARY_PATH=/path/to/where/ccl/is/installed/lib:$LD_LIBRARY_PATH
  1. In some Mac systems, the angpow installation script might fail on the first run with the message
CMake Error: The source directory "CCL/angpow" does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.

If this happens, try running it a second time.

  1. In some Mac systems, depending on the XCode version of the C/C++ compiler, you can get a compilation error. For a proposed solution, see here.

  2. If using a sudo make install for the C library and attempting to install the developer Python library, it may be necessary to include a sudo for your chosen Python installation.

  3. If you are building CCL using a conda environment, be mindful of the known issues documented here.

  4. For some Mac installs, headers for homebrew have been moved, resulting in an error of fatal error: 'stdio.h' file not found while attempting to install CLASS. This can be resolved with the command: sudo installer -pkg /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg -target /, which will install all the required headers into /usr/include.

Clone this wiki locally