[Mesa-users] SPAM: Problem installing MESA

[Maddie Loupien]

Hi,
Thank you that work I have end the installation, but now I don’t understand why I can’t see the graph when I run ./rn in the tutorial. Maybe I have miss something. I have put the files of what I get when I run the program and the building.log file. 
I don’t know if you can help me but thanks for the first answer!
Regards,
Maddie

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Capture d?e?cran 2024-03-12 a? 17.30.52.png
Type: image/png
Size: 470205 bytes
Desc: not available
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20240312/f2250fa7/attachment.png>
-------------- next part --------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: build.log
Type: application/octet-stream
Size: 62953 bytes
Desc: not available
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20240312/f2250fa7/attachment.obj>
-------------- next part --------------


> Le 12 mars 2024 à 16:01, Warrick Ball <W.H.Ball at bham.ac.uk> a écrit :
> 
> Hi Maddie,
> 
> I'm not familiar with Macs but there are a few lines in the `build.log` that look suspicious.  The log says that `$MESA_DIR` has been set to
> 
>    /Users/maddieloupien/Desktop/mesa
> 
> but the modules are being built in locations like
> 
>    /Users/maddieloupien/desktop/MESA_DIR/const
> 
> Is it possible that you've unpacked MESA in
> 
>    /Users/maddieloupien/desktop/MESA_DIR
> 
> but set `MESA_DIR` to a different directory?  If so, try setting the environment variable `MESA_DIR` to where you've unpacked MESA, for which something like this would work in bash:
> 
>   export MESA_DIR=/Users/maddieloupien/desktop/MESA_DIR
> 
> Then I'd suggest navigating to `$MESA_DIR` and running `./clean` and then `./install`.  (I'm guessing at the correct path here...)
> 
> I also noticed your `$PATH` variable puts some Anaconda paths before the MESA SDK.  If you're initialising the MESA SDK in your bash profile, you may want to make sure you initialise it after Anaconda.  I'm not familiar with Anaconda either but I would worry that you might end up using some programs from that distribution rather than the MESA SDK.  I don't think this is an issue right now though: the gfortran details at the start of the log indicate that you've got the MESA SDK version.  But this might change if you at some point install gfortran in Anaconda.
> 
> I'm not sure if this is related to the warnings about duplicate libraries.
> 
> Regards,
> Warrick
> 
> 
> 
> 
> ___________
> 
> Warrick Ball
> Senior Research Software Engineer
> University of Birmingham
> W.H.Ball at bham.ac.uk
> 
> On Tue, 12 Mar 2024, Maddie Loupien via Mesa-users wrote:
> 
>> CAUTION: This email originated from outside the organisation. Do not click links or open attachments unless you recognise the sender and know the content is safe.
>> There is attach my build.log file. Hope it can help resolving my problem.
>> Regards,
>> Maddie
>> _______________________________________________
>> mesa-users at lists.mesastar.org
>> https://lists.mesastar.org/mailman/listinfo/mesa-users
>>