-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
undefined reference to symbol 'MPI_Rsend' and error adding symbols: DSO missing from command line #34
Comments
To help debug this, you can run the make file with
make VERBOSE=1
to see the command that is sent to the compiler. But it looks like it’s missing the mpi library when linking the final executables.
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: sun51027 ***@***.***>
Sent: Friday, June 30, 2023 2:49:13 AM
To: ORNL-Fusion/PARVMEC ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [EXTERNAL] [ORNL-Fusion/PARVMEC] undefined reference to symbol 'MPI_Rsend' and error adding symbols: DSO missing from command line (Issue #34)
Hi
I have problems with "make" files.
I follow the guide in Stellarator-Tools, and cmake runs well.
While when compiling ("make"), error occurred:
/usr/bin/ld: /home/linshih/Library/scalapack/build/lib/libscalapack.a(BI_Rsend.c.o): undefined reference to symbol 'MPI_Rsend'
/home/linshih/Library/openmpi-4.1.5/lib/libmpi.so: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
_deps/parvmec-build/CMakeFiles/xvmec.dir/build.make:106: recipe for target '_deps/parvmec-build/xvmec' failed
make[2]: *** [_deps/parvmec-build/xvmec] Error 1
CMakeFiles/Makefile2:929: recipe for target '_deps/parvmec-build/CMakeFiles/xvmec.dir/all' failed
make[1]: *** [_deps/parvmec-build/CMakeFiles/xvmec.dir/all] Error 2
Makefile:145: recipe for target 'all' failed
make: *** [all] Error 2.
Does it matter with my environment setting?
I've downloaded latest version SCALAPACK and OpenMPI and point them into correct paths, so cmake runs well. But I still don't understand what I should do to deal with this.
Thanks!
—
Reply to this email directly, view it on GitHub<https://urldefense.us/v2/url?u=https-3A__github.com_ORNL-2DFusion_PARVMEC_issues_34&d=DwMCaQ&c=v4IIwRuZAmwupIjowmMWUmLasxPEgYsgNI-O7C4ViYc&r=jHzqd7h8AUyesPAQHKZPYGMox50RMWt0Xdplk3LbqH8&m=sU9qeKDNGWlIW5Rl4uD8EjaXXvX9_J79BYAxeiimL1pyAreYaydTAtvjrl-TfSN5&s=6QKf-irONVGb3vJyREtyUt7EvkFmgeix1FSBrtxSdkU&e=>, or unsubscribe<https://urldefense.us/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ADAPYD7ZIBSZNPIJD26CGMLXNZZGTANCNFSM6AAAAAAZZN3NKI&d=DwMCaQ&c=v4IIwRuZAmwupIjowmMWUmLasxPEgYsgNI-O7C4ViYc&r=jHzqd7h8AUyesPAQHKZPYGMox50RMWt0Xdplk3LbqH8&m=sU9qeKDNGWlIW5Rl4uD8EjaXXvX9_J79BYAxeiimL1pyAreYaydTAtvjrl-TfSN5&s=tv2cx_wrpGpfYTkXFblcCEOTeJcDnudlL5FlA58pd9E&e=>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Hi I tried make VERBOSE=1
Is it possible that the gfortran or other lib like mpi too old so it fails? |
I think the problem is the order that the MPI and Scalapack libraries are being linked. In the
to
and see if that fixes things. |
Thank you so much! This fixed DSO missing problem, and passed "Linking Fortran executable xvmec" .
Does this relate to my environment setting? |
No that's just a coding error on my part. What compiler, version of that compiler, and platform are you trying to build on? |
Compiler: I use the server of our instituite, it is ubuntu:
Other information Thank you! |
The error that you’re seeing is only in one of the test utilities and is not needed for compiling just VMEC if you run
make help
You can get a list of targets you can build
make xvmec
will build just the VMEC tool and it’s associated dependencies and should avoid the problem until I can up load a fix.
Mark
On Jul 2, 2023, at 4:09 AM, sun51027 ***@***.******@***.***>> wrote:
Compiler:
The Fortran compiler identification is GNU 5.4.0
I use the server of our instituite, it is ubuntu:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.7 LTS
Release: 16.04
Other information
Found OpenMP_C: -fopenmp (found version "4.0")
Found OpenMP_CXX: -fopenmp (found version "4.0")
Found OpenMP_Fortran: -fopenmp (found version "4.0")
Found OpenMP: TRUE (found version "4.0")
Found NetCDF: /usr/lib/x86_64-linux-gnu/libnetcdf.so (found version "4.4.0")
Found SCALAPACK: /home/linshih/Library/scalapack/build/lib/libscalapack.a
Found MPI_C: /home/linshih/Library/openmpi-4.1.5/lib/libmpi.so (found version "3.1")
Found MPI_CXX: /home/linshih/Library/openmpi-4.1.5/lib/libmpi.so (found version "3.1")
Found MPI_Fortran: /home/linshih/Library/openmpi-4.1.5/lib/libmpi_usempif08.so (found version "3.1")
Found MPI: TRUE (found version "3.1")
Thank you!
—
Reply to this email directly, view it on GitHub<https://urldefense.us/v2/url?u=https-3A__github.com_ORNL-2DFusion_PARVMEC_issues_34-23issuecomment-2D1616435214&d=DwMCaQ&c=v4IIwRuZAmwupIjowmMWUmLasxPEgYsgNI-O7C4ViYc&r=jHzqd7h8AUyesPAQHKZPYGMox50RMWt0Xdplk3LbqH8&m=IkI8i7wPRpYH1MFhjTL8s0J8SOCUynxNZNuwZ3WWidiI1a2oyWb-u-UhVE77lW4O&s=xMYqQeviEynYo2IKnasNDLpaLdxvysoF5qld1IM9gXQ&e=>, or unsubscribe<https://urldefense.us/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ADAPYD3OWAWCANQC2FGTNCTXOEUEFANCNFSM6AAAAAAZZN3NKI&d=DwMCaQ&c=v4IIwRuZAmwupIjowmMWUmLasxPEgYsgNI-O7C4ViYc&r=jHzqd7h8AUyesPAQHKZPYGMox50RMWt0Xdplk3LbqH8&m=IkI8i7wPRpYH1MFhjTL8s0J8SOCUynxNZNuwZ3WWidiI1a2oyWb-u-UhVE77lW4O&s=GUdnWDVvNXT20mimnevRvym_46-s5vYeZyOiAr0W8XA&e=>.
You are receiving this because you commented.Message ID: ***@***.***>
|
I would also like to have a test run, so if test utilities are able to run, this may help me a lot. |
Hi
I have problems with "make" files.
I follow the guide in Stellarator-Tools, and cmake runs well.
While when compiling ("make"), error occurred:
Does it matter with my environment setting?
I've downloaded latest version SCALAPACK and OpenMPI and point them into correct paths, so cmake runs well. But I still don't understand what I should do to deal with this.
Thanks!
The text was updated successfully, but these errors were encountered: