[Mesa-users] Help regarding NuDocker and mesa old version
Falk Herwig
fherwig at uvic.ca
Fri Aug 19 15:59:24 UTC 2022
Hi Abhijnan,
You should add as you did in your direct message to me that you had troubles compiling mesa in the first place. So if you don’t have mesa compiled correctly in the first place you can’t expect any of the test suite cases to compile.
Yesterday you mailed me:
> Thanks for the reply!It has been fixed.However, it gives the message like following:
> mesa/utils has been built, tested, and exported.
>
> ************************************************
>
> /home/user/mesa/crlibm
> building crlibm package.
>
> gzip: crlibm-1.0beta4_unzip.tar.gz has 1 other link -- unchanged
> tar: crlibm-1.0beta4_unzip.tar: Cannot open: No such file or directory
> tar: Error is not recoverable: exiting now
> mv: cannot stat 'crlibm-1.0beta4': No such file or directory
> ./build_and_test_parallel: line 43: cd: crlibm: No such file or directory
> make: ../makefile_crlibm: No such file or directory
> make: *** No rule to make target '../makefile_crlibm'. Stop.
> make: *** No targets specified and no makefile found. Stop.
>
> /home/user/mesa/crlibm
> ./build_and_test FAILED
>
>
> /home/user/mesa/crlibm
> ./build_and_test FAILED
Now, fortunately since we are now in the NuDocker system we can exclude any system/OS differences. It looks from the above to me as if you are not having a complete source tree. I looks as if the entire crlib dir is missing. Here is what the content of my r9575 source tree looks like:
user at mesa-r9575:~/mesa/crlibm$ pwd
/home/user/mesa/crlibm
user at mesa-r9575:~/mesa/crlibm$ ls
README ck crlibm-1.0beta4.tar.gz i1 makefile_crlibm test
build_and_test clean crlibm_private.c i1p mk
build_and_test_mic_native crlibm de_Dinechin_et_at_2007.pdf install private
build_and_test_parallel crlibm-1.0beta3.pdf export make public
It looks your r9575 source tree is corrupted, maybe from previous compilation or whatever. I suggest you download and unpack a fresh r97575 an place that in the same location you are mounting as mesa source into your Docker instance and start with a fresh compile of mesa itself before moving on to a test-suite case.
If you unpack the r9575 zip archive it will have the crlib dir with the source tar.gz archive:
atlas:tmp $ ls mesa-r9575/crlibm
README clean export makefile_crlibm
build_and_test crlibm-1.0beta3.pdf i1 mk
build_and_test_mic_native crlibm-1.0beta4.tar.gz i1p private/
build_and_test_parallel crlibm_private.c install public/
ck de_Dinechin_et_at_2007.pdf make/ test/
atlas:tmp $
then doing inside ~/mesa the usual ./install command will give the usual:
************************************************
************************************************
************************************************
MESA installation was successful
************************************************
************************************************
************************************************
user at mesa-r9575:~/mesa$
Then you can move on to your specific test-suite case, and it has to work:
user at mesa-r9575:~/mesa/binary/test_suite/double_bh$ ./mk
gfortran -Wno-uninitialized -fno-range-check -fmax-errors=12 -fprotect-parens -fno-sign-zero -fbacktrace -ggdb -finit-real=snan -fopenmp -fbounds-check -Wuninitialized -Warray-bounds -ffree-form -x f95-cpp-input -I../../../../include -c ../src/run_star_extras.f
gfortran -Wno-uninitialized -fno-range-check -fmax-errors=12 -fprotect-parens -fno-sign-zero -fbacktrace -ggdb -finit-real=snan -fopenmp -fbounds-check -Wuninitialized -Warray-bounds -ffree-form -x f95-cpp-input -I../../../../include -c ../src/run_binary_extras.f
gfortran -Wno-uninitialized -fno-range-check -fmax-errors=12 -fprotect-parens -fno-sign-zero -fbacktrace -ggdb -finit-real=snan -fopenmp -fbounds-check -Wuninitialized -Warray-bounds -ffree-form -x f95-cpp-input -I../../../../include -c ../../../../binary/job/run_binary.f
gfortran -Wno-uninitialized -fno-range-check -fmax-errors=12 -fprotect-parens -fno-sign-zero -fbacktrace -ggdb -finit-real=snan -fopenmp -fbounds-check -Wuninitialized -Warray-bounds -ffree-form -x f95-cpp-input -I../../../../include -c ../src/binary_run.f
gfortran -fopenmp -o ../binary run_star_extras.o run_binary_extras.o run_binary.o binary_run.o -L../../../../lib -lbinary -lstar -lionization -latm -lcolors -lmlt -lnet -leos -lkap -lrates -lneu -lchem -linterp_2d -linterp_1d -lnum -lf2crlibm -lcrlibm -lmtx -lconst -lutils -lmesaklu `mesasdk_lapack_link` `mesasdk_blas_link` `mesasdk_pgplot_link` -lz
user at mesa-r9575:~/mesa/binary/test_suite/double_bh$ ./rn
DATE: 2022-08-19
TIME: 15:56:50
read inlist_project
read inlist_extra
version_number 9575
new_rotation_flag T
new_surface_rotation_v 0 5.0000000000000000D+01 5.9612211423488179D-06
Good luck,
Falk
> On Aug 19, 2022, at 4:24 AM, ABHIJNAN KAR 20064 <abhijnank20 at iiserbpr.ac.in> wrote:
>
> Hi Mesa Users,
> I am running a mesa old version of r9575 and I have to reproduce the results of a paper.I have successfully installed NuDocker.I have to run the inlists in test_suite of binary module using NuDocker.So, the problem i am encountering is that during ./mk command in test_suite of binary module in mesa-r9575 it is showing error as follows:
> gfortran -Wno-uninitialized -fno-range-check -fmax-errors=12 -fprotect-parens -fno-sign-zero -fbacktrace -ggdb -finit-real=snan -fopenmp -fbounds-check -Wuninitialized -Warray-bounds -ffree-form -x f95-cpp-input -I../../../../include -c ../src/run_star_extras.f
> ../src/run_star_extras.f:25:10:
>
> use star_lib
> 1
> Fatal Error: Can't open module file 'star_lib.mod' for reading at (1): No such file or directory
> compilation terminated.
> ../../../../binary/work_standard_makefile_binary:33: recipe for target 'run_star_extras.o' failed
> make: *** [run_star_extras.o] Error 1
>
> FAILED
> What to do next?
> Regards,
> Abhijnan Kar(He/his/him)
> BS-MS,IISER Berhampur
>
>
>
>
>
>
> _______________________________________________
> 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/20220819/0dbbc3be/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1367 bytes
Desc: not available
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20220819/0dbbc3be/attachment.bin>
More information about the Mesa-users
mailing list