On Fri, 23 Aug 2019, Smith, Barry F. via petsc-users wrote: > bsmith@es:~$ ldd /usr/lib/libparmetis.so.3.1 > linux-vdso.so.1 => (0x00007fff9115e000) > libmpi.so.1 => /usr/lib/libmpi.so.1 (0x00007faf95f87000) > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007faf95c81000) > libmetis.so.3.1 => /usr/lib/libmetis.so.3.1 (0x00007faf95a34000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007faf9566b000) > libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007faf95468000) > libhwloc.so.5 => /usr/lib/x86_64-linux-gnu/libhwloc.so.5 > (0x00007faf95228000) > libltdl.so.7 => /usr/lib/x86_64-linux-gnu/libltdl.so.7 > (0x00007faf9501e000) > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 > (0x00007faf94e00000) > /lib64/ld-linux-x86-64.so.2 (0x00007faf9654e000) > libnuma.so.1 => > /soft/com/packages/pgi/19.3/linux86-64/19.3/lib/libnuma.so.1 > (0x00007faf94bf5000) > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007faf949f1000) > > You have something in /usr/lib referring to something in > /soft/com/packages/pgi/ ??
Must be due to LD_LIBRARY_PATH. Checking back the original issue: LD_LIBRARY_PATH=/home/lailai/nonroot/mpi/mpich/3.3-intel19/lib:/opt/intel/lib/intel64:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib: Ok - all this stuff in LD_LIBRARY_PATH is the trigger of the original issue. Satish
