package:installation:macos []

This is an old revision of the document!

Installation of CPPAW on MacOS

Someone should verify that this description is complete and correct. Then this fixme can be removed.

Xcode

MacOS has the compiler “gfortran” and the libraries “LAPACK” and “BLAS” installed already as system libraries. Important is to install “Xcode” from the Appstore. (Sign the license after opening it from the application folder.) Then install the “Command-Line tools” of Xcode. (Check the web for installation instructions).

Homebrew

I am installing Linux programs using homebrew. If you do not have it already, follow the installation instruction on its web page. Then install the following libraries.

brew install fftw  --with-fortran
brew install openmpi
brew install grace

PAW

Unpack the PAW distribution into a directory, which I will name PAWDIR in the following.
add the directory PAWDIR/bin/osx_gfortran_accellerate to your PATH variable in your ~/.profile
Create a file ''parms.osx_gfortran_accelerate'' in PAWDIR
Check the values of the parameters FFTDIR, FFTHEADER, MPIDIR, and MPIDIR in parms.osx_gfortran_accelerate. Most likely, you will need to adjust the version numbers of the codes.
execute in PAWDIR
```
     autoconf
     configure --with-parmfile=parms.osx_gfortran_accelerate
     make all 
```
“autoconf” uses the file “configure.ac” to construct the “configure” file. You can skip this step, if a configure file is already present. After the “configure” command, you should get some information that ends with done!—configuration completed successfully!. If not, inspect the error messages and fix them. The “make” command may take a very long time, if you set up the code for the first time.
Codesign: When you try to remotely execute unsigned code under macos, it will ask you for permission. This is painful when you run parallel code. Therefore it is advisable to sign the parallel executables. This is a fairly complicated procedure, which you need to look up. ( This section could be expanded.)
Increase the stack size and the core-dump size by including the following commands in your ~/.profile
```
    ulimit -s 65532
    ulimit -c unlimited 
```