[Mesa-users] ./build_and_test FAILED on macOS High Sierra 10.13.1

[RICHARD H D TOWNSEND]

> On Feb 22, 2018, at 9:20 AM, Brian Jackson <bjackson at boisestate.edu> wrote:
> 
> All,
> I think I figured out how to fix the problem (although I'm not sure
> why it's a problem in the first place).
> 
> It turns out that, even though I inserted "source
> $MESASDK_ROOT/bin/mesasdk_init.sh" into my .bash_profile, I still
> ended up with the gfortran upon start-up. That is, immediately after
> opening a terminal window, I do:
> 
> zarkon:~ bjackson2$ which gfortran
> /usr/local/bin/gfortran
> 
> The only way to get it to point to the right fortran was for me to
> directly source mesasdk_init.sh:
> zarkon:~ bjackson2$ source $MESASDK_ROOT/bin/mesasdk_init.sh
> zarkon:~ bjackson2$ which gfortran
> /Applications/mesasdk/bin/gfortran
> 
> BUT if I put "source $MESASDK_ROOT/bin/mesasdk_init.sh" as the very
> last line in .bash_profile, then the file is properly sourced and
> gfortran points where it's supposed to.
> 
> I don't seem to have anything else in my .bash_profile that would
> negate mesasdk_init.sh (everything else is just an export or alias
> command), so I'm not sure why I ran into the issue, but implementing
> this approach allows me to compile MESA.
> 

If you're modifying the PATH environment variable in your .bash_profile file, you could be placing /usr/local/bin ahead of the MESA SDK in the search order. Hence, /usr/local/bin/gfortran is found as the 'gfortran' command, rather than /Applications/mesasdk/bin/gfortran.

cheers,

Rich


> Thanks,
> Brian
> 
> On Wed, Feb 21, 2018 at 5:50 PM, Brian Jackson <bjackson at boisestate.edu> wrote:
>> zarkon:~ bjackson2$ otool -L $MESA_DIR/num/test/tester
>> /Users/bjackson/research/mesa/mesa_10108/num/test/tester:
>>    /Applications/mesasdk/lib/liblapack.dylib (compatibility version
>> 0.0.0, current version 0.0.0)
>>    /Applications/mesasdk/lib/libxblas.dylib (compatibility version
>> 0.0.0, current version 0.0.0)
>>    /Applications/mesasdk/lib/libblas.dylib (compatibility version
>> 0.0.0, current version 0.0.0)
>>    /Applications/mesasdk/lib/libgfortran.4.dylib (compatibility
>> version 5.0.0, current version 5.0.0)
>>    /Applications/mesasdk/lib/libgomp.1.dylib (compatibility version
>> 2.0.0, current version 2.0.0)
>>    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
>> version 1252.0.0)
>>    /Applications/mesasdk/lib/libgcc_s.1.dylib (compatibility version
>> 1.0.0, current version 1.0.0)
>>    /Applications/mesasdk/lib/libquadmath.0.dylib (compatibility
>> version 1.0.0, current version 1.0.0)
>> 
>> Thanks,
>> Brian
>> 
>> On Wed, Feb 21, 2018 at 4:34 PM, RICHARD H D TOWNSEND
>> <townsend at astro.wisc.edu> wrote:
>>> Hi Brian --
>>> 
>>> Can you post the output from
>>> 
>>> otool -L $MESA_DIR/num/test/tester
>>> 
>>> cheers,
>>> 
>>> Rich
>>> 
>>>> On Feb 21, 2018, at 3:26 PM, Brian Jackson <bjackson at boisestate.edu> wrote:
>>>> 
>>>> Apologies. Answers below:
>>>> 
>>>>> do you have the latest xcode - version 9.2 (9C40b) ?
>>>>> 
>>>>> did you run
>>>>> 
>>>>> % xcode-select --install
>>>>> 
>>>>> after installing xcode?
>>>> 
>>>> Yes, I did.
>>>> 
>>>>> what do these commands show
>>>>> 
>>>>> % uname -a
>>>> 
>>>> Darwin zarkon.boisestate.edu 17.2.0 Darwin Kernel Version 17.2.0: Fri
>>>> Sep 29 18:27:05 PDT 2017; root:xnu-4570.20.62~3/RELEASE_X86_64 x86_64
>>>> 
>>>>> % gfortran -v
>>>> 
>>>> Using built-in specs.
>>>> COLLECT_GCC=/Applications/mesasdk/bin/gfortran.exec
>>>> COLLECT_LTO_WRAPPER=/Applications/mesasdk/libexec/gcc/x86_64-apple-darwin17.3.0/7.2.0/lto-wrapper
>>>> Target: x86_64-apple-darwin17.3.0
>>>> Configured with: /Users/townsend/devel/mesasdk-src/gcc/configure
>>>> CC='gcc -D_FORTIFY_SOURCE=0' --build=x86_64-apple-darwin17.3.0
>>>> --prefix=/Applications/mesasdk --with-gmp=/Applications/mesasdk
>>>> --with-mpfr=/Applications/mesasdk --with-mpc=/Applications/mesasdk
>>>> --enable-languages=c,c++,fortran --disable-multilib --disable-nls
>>>> --disable-libsanitizer
>>>> Thread model: posix
>>>> gcc version 7.2.0 (GCC)
>>>> 
>>>>> % echo $MESASDK_ROOT
>>>> 
>>>> /Applications/mesasdk
>>>> 
>>>>> % echo $PATH
>>>> 
>>>> /Applications/mesasdk/bin:/Users/bjackson/anaconda2/bin:/Users/bjackson/research/py_mesa_reader/:/anaconda/bin:/usr/local/bin:/Users/bjackson/research/pylib:/Users/bjackson/anaconda/bin:/Applications/mesasdk/bin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/usr/local/git/bin:/usr/local/MacGPG1/bin:/Library/TeX/texbin
>>>> 
>>>> ---
>>>> 
>>>> I tried very hard to follow the instructions for asking for help on
>>>> the Troubleshooting website. I wonder if it would be worthwhile
>>>> including the requests for gfortran version, path, etc. on that list?
>>>> 
>>>> Many thanks,
>>>> Brian Jackson
>>>> _______________________________________________
>>>> mesa-users at lists.mesastar.org
>>>> https://lists.mesastar.org/mailman/listinfo/mesa-users
>>>> 
>>> 
> _______________________________________________
> mesa-users at lists.mesastar.org
> https://lists.mesastar.org/mailman/listinfo/mesa-users
>