symbol lookup error

[zhais]

Hello,

After running

./simfactory/bin/sim create-run helloworld \ --parfile arrangements/CactusExamples/HelloWorld/par/HelloWorld.par

‌

I got the error:

*/simulations/helloword/SIMFACTORY/exe/cactus_sim -L 3 */simulations/output-0000/HelloWorld.par

*/simulations/helloworld/SIMFACTORY/exe/cactus_sim: symbol lookup error : */simulations/helloworld/SIMFACTORY/exe/cactus_sim: undefined symbol : ompi_mpi_op_null

I have no idea why.

‌

Thanks in advance,

ashley

‌

‌

[Roland Haas]

Hello Ahsley,

this looks a bit like an issue with setting up correct search path for the libraries to me. This error is typically a link time (not runtime) error if one forgets to link in the OpenMPI library. Since you apparently could link, my first guess would be that the OpenMPI library that is used at runtime is not the same as used during compilation.

You should check the following:

• run ldd /simulations/helloword/SIMFACTORY/exe/cactus_sim | grep mpi to find out which OpenMPI library is used at runtime
• check that path reported there against the directory used at link time in the -L option. If you do not know where to find them then look at the file configs/sim/bindings/Configuration/Capabilities/make.MPI.defn which contains an entry MPI_LIB_DIRS which is the one you are looking for

Other than that, it would b good if you could provide more details:

1. the complete stdout and stderr output of the attempted run, since you are using create-run you will have to do something like ./simfactory/bin/sim create-run helloworld &>helloworld.log --parfile arrangements/CactusExamples/HelloWorld/par/HelloWorld.par then attach helloworld.log
2. which system is this happening on? Your laptop? A public cluster? The Einstein Toolkit tutorial server at https://etkhub.ndslabs.org ?
3. please provide the OptionList and RunScript files used, you can find them in configs/sim under those names
4. provide the full output of ldd /simulations/helloword/SIMFACTORY/exe/cactus_sim

Yours,
Roland

[Roland Haas]

No response for more than 4 months, issue seems to be local setup and not a but in the ET.