[Mesa-users] problem with compiling/linking of adapted subroutine
Lynn Buchele
Lynn.Buchele at ist.ac.at
Tue Sep 30 12:19:17 UTC 2025
Hi Gertjan,
When changing something at the module level (rather than in run_star_extras), you'll typically need to run both ./mk and ./export in the module directory (in this case $MESA_DIR/star). Then make sure to do a ./clean; ./mk in your working directory.
Best,
Lynn
________________________________
From: Mesa-users <mesa-users-bounces at lists.mesastar.org> on behalf of Gerrit Jan Savonije via Mesa-users <mesa-users at lists.mesastar.org>
Sent: Tuesday, September 30, 2025 1:21:37 PM
To: mesa-users at lists.mesastar.org
Subject: [Mesa-users] problem with compiling/linking of adapted subroutine
[EXTERNAL EMAIL - USE CAUTION when clicking links or attachments]
Hi all,
When using version mesa-24.08.1 it proves impossible to insert an
adapted version of the subroutine pulse_osc.f90 in module star. After
command ./mk in star/private it compiles correctly and the new
<pulse_osc.o> and <pulse_osc.mod> show up in star/make. But mesa keeps
using the original version of the subroutine pulse_osc.f90 when starting
a run in my user directory.
After the command in my working directory:
gerritjan at sav:~/proj/Mwork$ ./mk
the response is:
gfortran -fopenmp -o ../star run_star_extras.o run_star.o run.o
-L/mnt/sda5/Fortran/MESA/mesa-24.08.1/lib -lstar -lgyre_mesa -lgyre
-lionization -latm -lcolors -lturb -lstar_data -lnet -leos -lkap -lrates
-lneu -lchem -linterp_2d -linterp_1d -lnum -lauto_diff -lforum -lmtx
-lconst -lmath -lutils `mesasdk_crmath_link` `mesasdk_lapack95_link`
`mesasdk_lapack_link` `mesasdk_blas_link` `mesasdk_hdf5_link`
`mesasdk_pgplot_link` -lz
/mnt/sda5/Fortran/MESA/mesasdk/bin/../lib/gcc/x86_64-pc-linux-gnu/13.3.0/../../../../x86_64-pc-linux-gnu/bin/ld:
warning: atm_support.o: requires executable stack (because the
.note.GNU-stack section is executable)
After ./clean the response is:
gfortran -Wno-uninitialized -fno-range-check -fmax-errors=7
-fdiagnostics-color -fprotect-parens -fno-sign-zero -fbacktrace -ggdb
-finit-real=snan -fopenmp -fbounds-check -Wuninitialized -Warray-bounds
-ggdb -ffree-form -ffree-line-length-none -x f95-cpp-input -std=f2008
-Wno-error=tabs -I/mnt/sda5/Fortran/MESA/mesa-24.08.1/include -I../src
-c ../src/run_star_extras.f90
gfortran -Wno-uninitialized -fno-range-check -fmax-errors=7
-fdiagnostics-color -fprotect-parens -fno-sign-zero -fbacktrace -ggdb
-finit-real=snan -fopenmp -fbounds-check -Wuninitialized -Warray-bounds
-ggdb -ffree-form -ffree-line-length-none -x f95-cpp-input -std=f2008
-Wno-error=tabs -I/mnt/sda5/Fortran/MESA/mesa-24.08.1/include -I../src
-c /mnt/sda5/Fortran/MESA/mesa-24.08.1/star/job/run_star.f90
gfortran -Wno-uninitialized -fno-range-check -fmax-errors=7
-fdiagnostics-color -fprotect-parens -fno-sign-zero -fbacktrace -ggdb
-finit-real=snan -fopenmp -fbounds-check -Wuninitialized -Warray-bounds
-ggdb -ffree-form -ffree-line-length-none -x f95-cpp-input -std=f2008
-Wno-error=tabs -I/mnt/sda5/Fortran/MESA/mesa-24.08.1/include -I../src
-c ../src/run.f90
I never had problems like this and don't remember the normal response
to ./mk The command ./rn in the work directory starts a new run of the
code but not with the adapted subroutine!
I do not use the atmosphere option but is the problem perhaps related to
: (requires executable stack (because the .note.GNU-stack section is
executable) in the above text??
Regards,
Gertjan Savonije
_______________________________________________
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/20250930/bce67531/attachment.htm>
More information about the Mesa-users
mailing list