Message: 1
Date: Mon, 26 Oct 2020 15:18:45 -0500
From: Kelvin Li via Openmp-dev <openmp-dev@lists.llvm.org>
To: openmp-dev@lists.llvm.org
Subject: [Openmp-dev] undefined symbol: ompt_start_tool
Message-ID:
<OFF5259549.0EC65D66-ON8525860D.006EC181-8525860D.006F94A6@notes.na.collabserv.com>Content-Type: text/plain; charset=“utf-8”
Has anyone encounter the following error? I am wondering if it is
something to do with how I build libomp.so.$ LD_LIBRARY_PATH=/home/kli/clang-install/lib mpirun -np 1 ./a.out
a.out: symbol lookup error: /home/kli/clang-install/lib/libomp.so:
undefined symbol: ompt_start_toolPrimary job terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
mpirun detected that one or more processes exited with non-zero status,
thus causing
the job to be terminated. The first process to do so was:Process name: [[14546,1],0]
Exit code: 127But it works without mpirun.
$ LD_LIBRARY_PATH=/home/kli/clang-install/lib ./a.out
0
1
2
3Kelvin
Are you confident that /homie/kli/clang-install/lib is the same on all of the nodes used by the MPI program?
And that it contains the same version of libomp.so everywhere?
Perhaps you should also set an envirable to have the OpenMP runtime print its version, something like this
$ KMP_VERSION=1 ./a.out
LLVM OMP version: 5.0.20140926
LLVM OMP library type: performance
LLVM OMP link type: dynamic
LLVM OMP build time: no_timestamp
LLVM OMP build compiler: Clang 12.0
LLVM OMP alternative compiler support: yes
LLVM OMP API version: 5.0 (201611)
LLVM OMP dynamic error checking: no
LLVM OMP thread affinity support: no