[Mesa-users] Problem installing MESA

[Warrick Ball]

Hi Maddie,

Don't forget to keep including the `mesa-users` list in your replies.  If solve your issue, future users will then be able to find the solution too.

Also, thanks for attaching the screenshot.  Though we prefer users to copy text into the email, the screenshot does contain a relevant message:

     PGPLOT /xw: cannot connect to X server [/private/tmp/com.apple.launchd.fqf10pt1f6/org.xquartz:0]

I've had a brief look at this and it looks like a Mac-specific issue, so hopefully some of the MESA+Mac users will have ideas how to resolve it.  I'll offer a few thoughts anyway but probably can't help any further.

It looks like you've just opened a new terminal, so it's worth checking that the MESA SDK and `$MESA_DIR` variable are set (though I expect they are because `./rn` is at least starting).

I know the XQuartz X-windows infrastructure is a prerequisite on Macs, listed here:

     http://user.astro.wisc.edu/~townsend/static.php?ref=mesasdk#Prerequisites_2

so you might want to try re-installing it.

If you happen to be connecting to the machine with `ssh` you need to pass the `-X` flag to the `ssh` command (i.e. replace `ssh` with `ssh -X` when you connect) for it to pass the X window information from the remote computer to the one you've logged in from.

Finally, one old `mesa-users` message mentions that Anaconda might be interfering with the X windows system, though I couldn't find a description of such an issue, nor a solution.  If possible, try to start a terminal *without* Anaconda and see if that helps.

Good luck!

Regards,
Warrick



___________

Warrick Ball
Senior Research Software Engineer
University of Birmingham
W.H.Ball at bham.ac.uk

On Wed, 13 Mar 2024, Maddie Loupien wrote:

> [IMAGE]
> 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.
> 
> 
> Hi,
> I have join every files that you asked for, but I don’t find the error by myself…
> Thank you for your help.
> Regards,
> Maddie
> 
> > Le 13 mars 2024 à 03:26, Warrick Ball <W.H.Ball at bham.ac.uk> a écrit :
> >
> > Hi Maddie,
> >
> > Could you attach your inlists, please?  The main thing is to check that the inlist does at least have
> >
> >    pgstar_flag = .true.
> >
> > in the `&star_job` section.
> >
> > Also, have a look at the *start* of the output for any messages about not being able to connect to an X window or something.
> >
> > If you like, when you run MESA, you can send to output to a file with
> >
> >    $ ./rn > out.txt
> >
> > (where `$` represents your terminal prompt).  Then, if `out.txt` isn't too big, you can send it in your reply, too.
> >
> > Incidentally, if you'd like to send the output to a file *and* show it on screen as usual while MESA runs, you can use
> >
> >    $ ./rn | tee out.txt
> >
> > where `tee` is a small command that sends the output to both the file and the terminal.  (I've never used a UNIX-like system that didn't already have `tee` installed but I suppose it's possible.)
> >
> > 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 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.
> >> 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
> >> [IMAGE]
> >> > 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
> >> >>
> 
> 
>