Build failed: undefined reference to _gfortran_transfer_real_write during linking #1946
Unanswered
Astrogirlanajli
asked this question in
Q&A
Replies: 2 comments
-
|
I think you are on the right track, this looks like a compiler mismatch. It looks like it's pulling in gcc@13 libraries from the OS and as you said gcc in spack-stack is 11. First question: why gcc@11 for spack-stack? gcc@13 works fine and is actually preferred and better supported. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thank you for the reply. I remember that some of the dependencies required for installing MPAS-JEDI do not support gcc@13, so I switched to gcc@11.5.0. I will try rebuilding the stack using a single compiler and check whether the error still persists. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I'm using spack-stack for first time, I'm trying to install the MPAS-JEDI bundle using spack-stack on Ubuntu (WSL) . The configuration step with cmake ../code completes successfully, but the build fails during the make stage with a linking error involving libgfortran from the ESMF library. The error occurs during the final linking stage. The relevant part of the error message is:
I am wondering if this issue could be related to the presence of multiple GCC compilers on my system (gcc@13 as the default and gcc@11 used by spack-stack). I also attempted to install the shared ESMF package (esmf@8.5.0+shared), but during runtime, the build still seems to reference the static library.
I have been trying to resolve this issue for about a week, but have not been able to identify the correct solution. I would greatly appreciate any guidance on how to proceed.
Thank you for your help.
Beta Was this translation helpful? Give feedback.
All reactions