[Users] Installing on OSX10.12

[Ian Hinder]

On 20 Dec 2016, at 23:56, Guy <guy.pitman at bigpond.com> wrote:

> Hi Ian,
> 
> I deleted the Cactus directory and re- downloaded using Homebrew. After running ./simfactory/bin/sim setup --optionlist=osx-homebrew.cfg --runscript generic-mpi.run
> I checked the simfactory/mdb/optionlists/osx-homebrew.cfg which had the following lines
> 
> 
> CPP = cpp-6
> FPP = cpp-6
> CC  = gcc-6
> CXX = g++-6
> F90 = gfortran-6
> 
> CPPFLAGS =
> FPPFLAGS = -traditional
> CFLAGS   = -g -std=c11
> CXXFLAGS = -g -std=c++14
> F90FLAGS = -g -m128bit-long-double -fcray-pointer -ffixed-line-length-none
> 
> LDFLAGS = -lgfortran
> 
> (see attached)
> 
> I did not edit anything
> 
> I ran ./simfactory/bin/sim build --mdbkey make 'make -j2' --thornlist=manifest/einsteintoolkit.th
> 
> 
> and got the following output
> 
> <Einsteintoolkit_build.rtf>
> <osx-homebrew.cfg>
> <Guy-Pitman.local.ini>
> <defs.local.ini>
> 
> Thanks and Regards

Dear Guy,

This is extremely helpful, thanks very much!  The first error that you are getting is

/var/folders/1z/c34gnlxn24s77twgl7kwjvbw0000gq/T//cccA3AqQ.s:27:suffix or operands invalid for `movq'

while compiling fortran code.  After a bit of googling, I came across this:

https://github.com/Homebrew/legacy-homebrew/issues/45258

This seems to be related to the version of the assembler "as" that is being used.  Can you post the output of

	as -v	

as well as 

	which as

so we can see which assembler is being used?  

This person in that bug report found that there was some conflict related to also having MacPorts installed.  Maybe gfortran or one of its libraries is being picked up from the wrong place, or an incompatible assembler is being found?  Do you have anything from macports installed, e.g. in /opt/local?  If so, then you could temporarily remove it by moving /opt/local to /opt/local-tmp and trying the ET build again.  You don't need to check out the code or run sim setup again, you can just rm -rf configs/sim and rerun the build command.

I'm not very familiar with homebrew, but apparently there is a "brew doctor" command which can diagnose potential problems with the homebrew installation. Can you try running that?

Since you have checked out the ET fresh, and are using the standard files without any changes, we need to work out what is different between your system and Roland's, where he tested it.  It is likely a difference with other installed software which is being picked up accidentally (e.g. other homebrew packages, other software in /usr/local, or something from macports in /opt/local).  Unfortunately, with so many different options for installing software, and different versions available, it is really hard to provide something which works out of the box for every possible system configuration.

-- 
Ian Hinder
http://members.aei.mpg.de/ianhin