[mesa-users] Trouble With Work Directory - HELP Please!
jwschwab at berkeley.edu
Wed Oct 3 13:03:18 EDT 2012
Set MESA_DIR to be the full path to your mesa directory (as Bill does in the README). That is use
That would also solve your earlier path troubles to 'standard_run_star_extras.inc' also.
On Oct 3, 2012, at 9:44 AM, José Pedro Pinto Vieira wrote:
> I was trying to follow the "how to use MESA star" instructions but got stuck in the making of the work directory and I'm afraid it may be due to some "loose end" in the version I got... To begin with, there was no README file there, but Cristina Rodriguez (from the mailing list) who was kind enought to get me one (since I'm not sure of what is going wrong, I'm attaching a copy of this README just in case there is something there that is no longer correct). After editing "makefile" and "inlist_project" and doing ./mk there was an error which seemed to be due to a problem with the path to 'standard_run_star_extras.inc' in 'src/run_star_extras.f' (the error disappeared once I put in the complete path). Now I'm getting a different error message, shown below.
> [jvieira at supernova mesa_work]$ ./mk
> gfortran -fno-range-check -fopenmp -fbounds-check -Wuninitialized -Warray-bounds -g -ffree-form -x f95-cpp-input -I~/disk1/mesa/include -I/home/jvieira/disk1/mesasdk/include -c ../src/run_star_extras.f
> use star_lib
> Fatal Error: Can't open module file 'star_lib.mod' for reading at (1): No such file or directory
> make: *** [run_star_extras.o] Error 1
> There seems to be a problem with star_lib? What should I do?
> Help is very appreciated.
> Best regards,
> José Pedro
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> mesa-users mailing list
> mesa-users at lists.sourceforge.net
More information about the Mesa-users