[mesa-users] Errors showing up during installing MESA

Sanskriti Das dassanskriti at gmail.com
Mon Jun 6 09:39:20 EDT 2016


Hello, I would like to let all of you know that the problem was regarding
the commands of set up of environmental variables (i.e. I had to use
commands other than what is shown in MESA website) and an error in one of
the .c files which are compiled during installation. I have corrected all
those things. At last, it has shown MESA has been installed successfully. I
have tried a test run with all default values and it is working as
expected.

Thanks a lot for your support.

I have one more question regarding the output files. The profile<model
no.>.data files have huge no. of (~90) columns some of which are redundant,
and most of which I don't need. From the control.default and
star_job.default files it was not clean to me how to restrict certain
variables which only will be written in the output. May anyone please sort
this out ?

Regards,
Sanskriti

On Sat, Jun 4, 2016 at 3:57 AM, Willie Strickland <cwskas at gmail.com> wrote:

> You can determine which shell you are running by typing
>
>         echo $SHELL
>
> from the terminal window.
>
> Then follow the instructions from this link which are pertinent to your
> shell
>
>         http://mesa.sourceforge.net/prereqs.html#toc-1-7
>
> Willie
>
>
> > On Jun 3, 2016, at 4:10 PM, Sanskriti Das <dassanskriti at gmail.com>
> wrote:
> >
> > Set. But it shows the same error.
> >
> > On Sat, Jun 4, 2016 at 2:24 AM, Robert Farmer <rjfarmer at asu.edu> wrote:
> > makefile:1: /star/work_standard_makefile: No such file or directory
> > make: *** No rule to make target `/star/work_standard_makefile'.  Stop.
> >
> > You've not set the MESA_DIR variable to points to the MESA folder.
> >
> > For setting environment variables have a look here:
> > http://osxdaily.com/2015/07/28/set-enviornment-variables-mac-os-x/
> >
> > Rob
> >
> > On Fri, Jun 3, 2016 at 1:52 PM, Sanskriti Das <dassanskriti at gmail.com>
> wrote:
> > One more question. While trying to compile, the process is getting
> stopped with a message like this-
> >
> > "
> > makefile:1: /star/work_standard_makefile: No such file or directory
> > make: *** No rule to make target `/star/work_standard_makefile'.  Stop.
> >
> > FAILED
> > "
> >
> > It is true that no such file exists and no rule has been imposed to
> target anything. But it is not clear from the MESA website what I should do
> here.
> >
> > The .mk and makefile descriptions themselves did not help.
> >
> > Thanks,
> >
> > Regards,
> > Sanskriti
> >
> > On Sat, Jun 4, 2016 at 2:14 AM, Sanskriti Das <dassanskriti at gmail.com>
> wrote:
> > I am using bash
> >
> > On Sat, Jun 4, 2016 at 2:11 AM, Robert Farmer <rjfarmer at asu.edu> wrote:
> > > But it is showing 'Permission denied'.
> >
> > What command? what file? Does either of the ~/.cshrc or ~/.profile
> exist? Are you using bash or csh?
> >
> > Rob
> >
> > On Fri, Jun 3, 2016 at 1:39 PM, Sanskriti Das <dassanskriti at gmail.com>
> wrote:
> > But it is showing 'Permission denied'.
> >
> > On Sat, Jun 4, 2016 at 2:04 AM, Robert Farmer <rjfarmer at asu.edu> wrote:
> > log.c: In function 'log_rn':
> > log.c:102:20: warning: division by zero [-Wdiv-by-zero]
> >         return (x-x)/0;                      /* log(-x) = Nan    */
> >
> > That is only a warning and can be safely ignored.
> >
> > >putting the commands in a shell startup script
> >
> > So depending on what terminal you use, there is a special file that gets
> executed when ever you load a new terminal window, if you are using a csh
> terminal its ~/.cshrc and a bash terminal its ~/.profile . So if you put
> the commands for setting the mesa_dir, mesasdk_path and also the source
> mesasdk_init.sh into one of those files then whenever you load a terminal
> they will be set for you.
> >
> > Rob
> >
> >
> >
> >
> >
> > On Fri, Jun 3, 2016 at 1:28 PM, Sanskriti Das <dassanskriti at gmail.com>
> wrote:
> > Thanks a lot for reminding of the sdk setup. I had done that earlier
> too, but probably there was some error in setting the environment variable.
> This time I tried with a different command of setting, and it worked!
> >
> > By the way, I am not familiar with these terms, so may I be explained
> what it actually means by "putting the commands in a shell startup script"
> ? In that case, it would save me from setting up sdk every time I open a
> new terminal.
> >
> > Although it is showing that *MESA installation was successful* it has
> shown some warnings like-
> > "
> > log.c: In function 'log_rn':
> > log.c:102:20: warning: division by zero [-Wdiv-by-zero]
> >         return (x-x)/0;                      /* log(-x) = Nan    */
> > " as well. I have checked the file log.c , it seems this won't hamper
> the actual run if parameter values are properly set. Am I right?
> >
> > Thanks,
> >
> > Regards,
> > Sanskriti
> >
> > On Sat, Jun 4, 2016 at 1:34 AM, Sanskriti Das <dassanskriti at gmail.com>
> wrote:
> > It is 64 bit system.
> >
> > On Sat, Jun 4, 2016 at 1:03 AM, Aaron Dotter <aaron.dotter at gmail.com>
> wrote:
> > (Please reply also to mesa-users.)
> >
> > Based on your first email it seems that you are running a 32-bit OS
> (i686).  Can you confirm this?
> >
> > If you are, then you need to install a 64-bit OS in order to use MESA.
> After that things should work properly once you have the SDK set up and
> sourced properly.
> >
> > Aaron
> >
> > On Fri, Jun 3, 2016 at 3:29 PM, Sanskriti Das <dassanskriti at gmail.com>
> wrote:
> > This is a 64 bit (6-Core Intel Xeon) machine.
> >
> > On Fri, Jun 3, 2016 at 11:33 PM, Chris Mankovich <cmankovich at ucsc.edu>
> wrote:
> > MESA does support 32-bit OS anymore so you would have to install it on a
> computer running a 64-bit OS.
> >
> > does NOT!
> >
> > On Fri, Jun 3, 2016 at 10:59 AM, Aaron Dotter <aaron.dotter at gmail.com>
> wrote:
> > Hi,
> >
> > It looks like you may have the wrong version of the MESA SDK for your OS
> (32-bit vs. 64-bit).  Some of the output says
> >
> > i686-apple-darwin11-llvm-gcc-4.2: ../private/mod_klu.F90: Fortran
> compiler not installed on this system
> >
> > i686 suggests a 32-bit OS but you say that you're trying to install the
> x86_64 compiler.  Try this to check:
> >
> >
> https://www.chiefarchitect.com/support/article/KB-01230/determining-if-your-computer-is-32-bit-or-64-bit.html
> >
> > MESA does support 32-bit OS anymore so you would have to install it on a
> computer running a 64-bit OS.
> >
> > I hope this helps!
> >
> > Aaron
> >
> >
> >
> ------------------------------------------------------------------------------
> > What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> > patterns at an interface-level. Reveals which users, apps, and protocols
> are
> > consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> > J-Flow, sFlow and other flows. Make informed decisions using capacity
> > planning reports.
> https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
> > _______________________________________________
> > mesa-users mailing list
> > mesa-users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/mesa-users
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> > patterns at an interface-level. Reveals which users, apps, and protocols
> are
> > consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> > J-Flow, sFlow and other flows. Make informed decisions using capacity
> > planning reports.
> https://ad.doubleclick.net/ddm/clk/305295220;132659582;e_______________________________________________
> > mesa-users mailing list
> > mesa-users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/mesa-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20160606/82ea12e2/attachment.html>


More information about the Mesa-users mailing list