Kenneth, Yes, the correct path is in both LD_LIBRARY_PATH and in LIBRARY_PATH.
Attached you can find the outputs of $ LD_DEBUG=all mpifort multitask_mpi.f90 on two different servers that have the same minimal OS but one works and the other fails. The only difference is the CPU architecture but that should not be a concern. Also I have used the same easyconfigs. The easyblocks in the working server come from the develop branch, while on the failing server they are from 3.4.1 The strange thing is that in the failing system it looks for a symbol (vfprintf) that is not even mentioned in the working system. But that's all I can see from that output. -- Davide Vanzo, PhD Application Developer Adjunct Assistant Professor of Chemical and Biomolecular Engineering Advanced Computing Center for Research and Education (ACCRE) Vanderbilt University - Hill Center 201 (615)-875-9137 www.accre.vanderbilt.edu On 2017-11-20 13:15:14-06:00 Kenneth Hoste wrote: Hi Davide, On 20/11/2017 16:06, Vanzo, Davide wrote: Hello EasyBuilders! I have started building the foss-2016b toolchain on a new server and I am stumbling against an error that I have never seen before and for which I cannot pinpoint the cause. When I try to compile a fortran source with mpifort (or mpif90), I get the error you see below. The thing I do not understand is why the linker searches for /usr/lib64/libgfortran.so (which does not exist for obvious reasons) instead of the equivalent library built by EasyBuild with GCCcore-5.4.0 (which exists). The LD_LIBRARY_PATH env var contains the path to the GCCcore directory where libgfortran.so is actually located. Why is ld ignoring this path? Any suggestion? I think ld(.gold) actually checks $LIBRARY_PATH when linking binaries, while $LD_LIBRARY_PATH is checked at runtime. But I assume $LIBRARY_PATH also includes the location to libgfortran.so provide by GCCcore? Do you get any useful output when running "LD_DEBUG=1 mpifort multitask_mpi.f90" (see http://www.bnikolic.co.uk/blog/linux-ld-debug.html<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.bnikolic.co.uk%2Fblog%2Flinux-ld-debug.html&data=02%7C01%7Cdavide.vanzo%40vanderbilt.edu%7C8d702dfec3f9483274df08d5304b0597%7Cba5a7f39e3be4ab3b45067fa80faecad%7C0%7C0%7C636468021133946943&sdata=eGc9RbcsbQlbsxg0mNsrmzxhibtv7ZznYIL3hq%2FsoNw%3D&reserved=0>)? regards, Kenneth
