[Mesa-users] Installation version v7503 eos_def.mod error

Charlie Sharpe charliesharpe2101 at gmail.com
Thu Aug 5 14:28:08 UTC 2021


Hi Rob,

After looking at the make_o_ne_wd test_suite where a 10M_sol mass star is
modelled from birth to WD, I think what I was missing in my inlists
was overshooting as this seems to allow for c-burn to get moving. Thank you
so much for the suggestion, I will continue playing around and let you know
if I have any further questions.

Thanks again,

Charlie

On Thu, Aug 5, 2021 at 9:21 PM Rob Farmer <robert.j.farmer37 at gmail.com>
wrote:

> >Perhaps my r15140 inlist could be improved to allow the code to progress
> through carbon burning to further stages or even death.
>
> We would need to see the inlists and it would also help if you make some
> plots like a kippenhan to see what is going on. 15140 can certainly go
> beyond carbon burning, so the first place would be to look in the
> test_suite at some of the high mass test cases.
>
> Rob
>
> On Thu, 5 Aug 2021 at 12:26, Charlie Sharpe via Mesa-users <
> mesa-users at lists.mesastar.org> wrote:
>
>> Warrick,
>>
>> I also see a lot of people online suggest uninstalling Xcode then
>> reinstalling with `xcode-select --install`. I did try this a few times and
>> it did not help annoyingly. Here is the build.log from running ./clean;./install
>> |& tee build.log. The gfortran -v gives me version gives gcc version
>> 4.9.3, however this makes sense as I am trying to run with the SDK that was
>> newest at the time (20150210) as opposed to the newest now. I do think it
>> is a Mac-specific issue but no suggestions that I have found on google have
>> been able to help me so far.
>>
>> Rob,
>>
>> That sounds like it might be the only option. The main goal I am trying
>> to achieve is to run MIST, which requires r7503, in the hopes of modelling
>> high mass stars (greater than 2M_solar) from birth to death. The current
>> 15140 version seems to get quite unhappy once carbon burning is reached as
>> the time-steps drop drastically and the code is unable to progress
>> significantly even if left to run for hours/days. Perhaps my r15140 inlist
>> could be improved to allow the code to progress through carbon burning to
>> further stages or even death. Is there anything else you would suggest
>> looking at that could perhaps help me model the evolution of high mass
>> stars for the latest MESA version, or any versions later than 7503?
>>
>> Regards,
>> Charlie
>>
>> On Thu, Aug 5, 2021 at 8:11 PM Warrick Ball <W.H.Ball at bham.ac.uk> wrote:
>>
>>> Hi,
>>>
>>> First, that's a different error to the one you originally reported, so
>>> could you perhaps do `./clean` and *then* `./install |& tee build.log`?
>>> Just to be sure, please also check that `gfortran -v` gives version 10.2 or
>>> so, which is what I think the latest SDK has.
>>>
>>> If this error message (not finding `stdio.h`) does persist, could you go
>>> through the SDK initialisation again?  If it *still* persists, then this
>>> also looks like a Mac-specific issue.  Some cursory Googling suggests it
>>> should be resolved by running `xcode-select --install` but I'm not familiar
>>> enough with the SDK to know if that'll help in this situation.
>>>
>>> Cheers,
>>> Warrick
>>>
>>>
>>> ___________
>>>
>>> Warrick Ball
>>> Postdoc, School of Physics and Astronomy
>>> University of Birmingham, Edgbaston, Birmingham B15 2TT
>>> W.H.Ball at bham.ac.uk
>>> +44 (0)121 414 4552
>>>
>>> On Thu, 5 Aug 2021, charliesharpe2101 at gmail.com wrote:
>>>
>>> > Ahh yes, so sorry, I was looking in the wrong directory. Here is the
>>> correct build.log.
>>> >
>>> > On Thu, Aug 5, 2021 at 8:00 PM Warrick Ball <W.H.Ball at bham.ac.uk>
>>> wrote:
>>> >       Hi Charlie,
>>> >
>>> >       This `build.log` is for r15140.  We need to see the `build.log`
>>> for 7503, which had the problem.
>>> >
>>> >       Cheers,
>>> >       Warrick
>>> >
>>> >       ___________
>>> >
>>> >       Warrick Ball
>>> >       Postdoc, School of Physics and Astronomy
>>> >       University of Birmingham, Edgbaston, Birmingham B15 2TT
>>> >       W.H.Ball at bham.ac.uk
>>> >       +44 (0)121 414 4552
>>> >
>>> >       On Thu, 5 Aug 2021, charliesharpe2101 at gmail.com wrote:
>>> >
>>> >       > Hi Warrack,
>>> >       > Completely understandable. I just realized I didn't send my
>>> previous response to the mailing list so I might do that.
>>> >       >
>>> >       > Here is the build.log when I run ./install |& tee build.log.
>>> >       >
>>> >       > Regards,
>>> >       > Charlie
>>> >       >
>>> >       > On Thu, Aug 5, 2021 at 7:52 PM Warrick Ball <
>>> W.H.Ball at bham.ac.uk> wrote:
>>> >       >       Hi Charlie,
>>> >       >
>>> >       >       I can't help with with the Mac-related SDK issues but
>>> hopefully someone else can chip in.  Sorry!
>>> >       >
>>> >       >       I still invite you to try building with `./install |&
>>> tee build.log` to see if we can work through the compiler errors.  I would
>>> try this myself but haven't much time at the moment.
>>> >       >
>>> >       >       Cheers,
>>> >       >       Warrick
>>> >       >
>>> >       >
>>> >       >
>>> >       >       ___________
>>> >       >
>>> >       >       Warrick Ball
>>> >       >       Postdoc, School of Physics and Astronomy
>>> >       >       University of Birmingham, Edgbaston, Birmingham B15 2TT
>>> >       >       W.H.Ball at bham.ac.uk
>>> >       >       +44 (0)121 414 4552
>>> >       >
>>> >       >       On Thu, 5 Aug 2021, charliesharpe2101 at gmail.com wrote:
>>> >       >
>>> >       >       > Hi Warrack,
>>> >       >       > Thanks for the reply! I had a similar suspicion that
>>> the latest SDK wouldn't work so I did as you said, and downloaded the SDK
>>> that was latest at the time which was 20150210. However, when I do this, I
>>> run into the following
>>> >       error
>>> >       >       >
>>> >       >       > configure: error: in
>>> `/Users/charliesharpe/Desktop/Honours_work/MESA/mesa-r7503/crlibm/crlibm':
>>> >       >       >
>>> >       >       > configure: error: C compiler cannot create executables
>>> >       >       >
>>> >       >       > See `config.log' for more details.
>>> >       >       >
>>> >       >       > make: *** [build] Error 77
>>> >       >       >
>>> >       >       > make: *** No targets specified and no makefile found.
>>> Stop.
>>> >       >       >
>>> >       >       >
>>> >       >       >
>>> /Users/charliesharpe/Desktop/Honours_work/MESA/mesa-r7503/crlibm/crlibm
>>> >       >       >
>>> >       >       > ./build_and_test FAILED
>>> >       >       >
>>> >       >       >
>>> >       >       >
>>> >       >       >
>>> /Users/charliesharpe/Desktop/Honours_work/MESA/mesa-r7503/crlibm
>>> >       >       >
>>> >       >       > ./build_and_test FAILED
>>> >       >       >
>>> >       >       >
>>> >       >       > I saw that some people who had similar issues were
>>> able to resolve them by reinstalling Xcode as well as the prerequisites,
>>> etc. However, I have done this multiple times and to no avail. I have
>>> attached the config.log file to
>>> >       this
>>> >       >       thread. I have
>>> >       >       > tried with different SDK's and still no luck. I
>>> believe it has something to do with installation of headers as on 10.14,
>>> one would use
>>> >       >       >
>>> >       >       >
>>> >       >       > open
>>> /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg
>>> >       >       >
>>> >       >       >
>>> >       >       > to install the headers. However, this no longer works
>>> on 10.15 (Catalina) and I am unsure as to what the new way to do this is.
>>> >       >       >
>>> >       >       >
>>> >       >       > What could be the cause of this issue?
>>> >       >       >
>>> >       >       >
>>> >       >       > Regards,
>>> >       >       >
>>> >       >       > Charlie
>>> >       >       >
>>> >       >       >
>>> >       >       > On Thu, Aug 5, 2021 at 7:30 PM Warrick Ball <
>>> W.H.Ball at bham.ac.uk> wrote:
>>> >       >       >       Hi Charlie,
>>> >       >       >
>>> >       >       >       I doubt you'll manage to build r7503 with the
>>> latest SDK without having to tweak some code to accommodate some changes to
>>> default gfortran behaviour in the ~6½ years since r7503 was released.  Have
>>> a look at the relevant
>>> >       part of
>>> >       >       the FAQ:
>>> >       >       >
>>> >       >       >
>>> https://docs.mesastar.org/en/r15140/faq.html#installing-older-versions-of-mesa
>>> >       >       >
>>> >       >       >       which has a link to the older versions of the
>>> SDK.  r7503 was released 27 Mar 2015, so try whichever was the latest SDK
>>> on that date.
>>> >       >       >
>>> >       >       >       It's hard to make sense of the error message on
>>> its own.  I guess the install script wasn't set up to record a `build.log`
>>> back then back you can replicate most of it by going to your r7503
>>> directory and running
>>> >       >       >
>>> >       >       >            $ ./clean
>>> >       >       >            $ ./install |& tee build.log
>>> >       >       >
>>> >       >       >       which should create a `build.log` file that you
>>> can email to the user list.
>>> >       >       >
>>> >       >       >       Cheers,
>>> >       >       >       Warrick
>>> >       >       >
>>> >       >       >       ___________
>>> >       >       >
>>> >       >       >       Warrick Ball
>>> >       >       >       Postdoc, School of Physics and Astronomy
>>> >       >       >       University of Birmingham, Edgbaston, Birmingham
>>> B15 2TT
>>> >       >       >       W.H.Ball at bham.ac.uk
>>> >       >       >       +44 (0)121 414 4552
>>> >       >       >
>>> >       >       >       On Thu, 5 Aug 2021,
>>> mesa-users at lists.mesastar.org wrote:
>>> >       >       >
>>> >       >       >       > Hello,
>>> >       >       >       > I am trying to install v7503 (currently have
>>> v15140 installed with the most recent SDK). When I run ./clean;./install in
>>> $MESA_DER, I get an error message saying
>>> >       >       >       >
>>> >       >       >       > gfortran -fno-range-check -fmax-errors=100
>>> -fprotect-parens -fno-sign-zero -fopenmp  -I../../../include -Wunused-value
>>> -W -Wno-compare-reals -Wno-unused-parameter -fimplicit-none   -O2 -c
>>> -ffree-form -x f95-cpp-input
>>> >       >       -I../../private -c
>>> >       >       >       > ../src/eval_eosPT.f
>>> >       >       >       >
>>> >       >       >       > ../src/eval_eosPT.f:25:7:
>>> >       >       >       >
>>> >       >       >       >
>>> >       >       >       >    25 |   use eos_def
>>> >       >       >       >
>>> >       >       >       >       |       1
>>> >       >       >       >
>>> >       >       >       > Fatal Error: Cannot open module file
>>> 'eos_def.mod' for reading at (1): No such file or directory
>>> >       >       >       >
>>> >       >       >       > compilation terminated.
>>> >       >       >       >
>>> >       >       >       > make: *** [eval_eosPT.o] Error 1
>>> >       >       >       >
>>> >       >       >       > There seems to be an eos_def.mod file in
>>> $MESA_DIR/eos/make and one in $MESA_DIR/eos/eosDT_builder/make. I would
>>> attach the build.log file but one was not created so here is the output if
>>> I run uname -a; gfortran -v;
>>> >       echo
>>> >       >       $MESASDK_ROOT;
>>> >       >       >       echo $PATH;
>>> >       >       >       > echo $MESA_DIR. Any idea what the issue could
>>> be?
>>> >       >       >       >
>>> >       >       >       > (base) charliesharpe at Charlies-MacBook-Pro
>>> mesa-r7503 % uname -a;
>>> >       >       >       >
>>> >       >       >       > gfortran -v;
>>> >       >       >       >
>>> >       >       >       > echo $MESASDK_ROOT;
>>> >       >       >       >
>>> >       >       >       > echo $PATH;
>>> >       >       >       >
>>> >       >       >       > echo $MESA_DIR
>>> >       >       >       >
>>> >       >       >       > Darwin Charlies-MacBook-Pro.local 19.6.0
>>> Darwin Kernel Version 19.6.0: Mon Apr 12 20:57:45 PDT 2021;
>>> root:xnu-6153.141.28.1~1/RELEASE_X86_64 x86_64
>>> >       >       >       >
>>> >       >       >       > Using built-in specs.
>>> >       >       >       >
>>> >       >       >       >
>>> COLLECT_GCC=/Applications/mesasdk/bin/gfortran.exec
>>> >       >       >       >
>>> >       >       >       >
>>> COLLECT_LTO_WRAPPER=/Applications/mesasdk/bin/../libexec/gcc/x86_64-apple-darwin20.3.0/10.2.0/lto-wrapper
>>> >       >       >       >
>>> >       >       >       > Target: x86_64-apple-darwin20.3.0
>>> >       >       >       >
>>> >       >       >       > Configured with:
>>> /opt/sdk2-tmp/build/gcc/configure CC=clang CXX=clang++
>>> --build=x86_64-apple-darwin20.3.0 --host=x86_64-apple-darwin20.3.0
>>> --target=x86_64-apple-darwin20.3.0 --prefix=/opt/sdk2-tmp/mesasdk
>>> >       >       >       --with-gmp=/opt/sdk2-tmp/mesasdk
>>> >       >       >       > --with-mpfr=/opt/sdk2-tmp/mesasdk
>>> --with-mpc=/opt/sdk2-tmp/mesasdk --enable-languages=c,c++,fortran
>>> --disable-multilib --disable-nls --disable-libsanitizer
>>> --with-sysroot=/opt/sdk2-tmp/mesasdk/sysroot
>>> >       >       >       >
>>> >       >       >       > Thread model: posix
>>> >       >       >       >
>>> >       >       >       > Supported LTO compression algorithms: zlib
>>> >       >       >       >
>>> >       >       >       > gcc version 10.2.0 (GCC)
>>> >       >       >       >
>>> >       >       >       > /Applications/mesasdk
>>> >       >       >       >
>>> >       >       >       >
>>> /Applications/mesasdk/bin:/opt/local/bin:/opt/local/sbin:/opt/miniconda3/bin:/Users/charliesharpe/miniconda3/condabin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Library/Apple/usr/bin
>>> >       >       >       >
>>> >       >       >       >
>>> /Users/charliesharpe/Desktop/Honours_work/MESA/mesa-r7503
>>> >       >       >       >
>>> >       >       >       > (base) charliesharpe at Charlies-MacBook-Pro
>>> mesa-r7503 %
>>> >       >       >       >
>>> >       >       >       >
>>> >       >       >       >
>>> >       >       >
>>> >       >       >
>>> >       >       >
>>> >       >
>>> >       >
>>> >       >
>>> >
>>> >
>>> >
>>
>> _______________________________________________
>> mesa-users at lists.mesastar.org
>> https://lists.mesastar.org/mailman/listinfo/mesa-users
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20210806/8afff94b/attachment.htm>


More information about the Mesa-users mailing list