LAM/MPI problem

I installed LAM/MPI-7.1.1 on our 4-way Opteron workstation with following environment variables: FC=pgf90, F77=pgf77 CC=pgcc CXX=pgCC. Then I tried to compile a program with mpif77, but I got the following error message:
chem@amd4p:/package/chem/vasp/vasp.4.6.26/vasp.4.6> make -f makefile.linux_pgi_opt
./preprocess <base.F | /usr/bin/cpp -P -C -traditional >base.f90 -DMPI -DHOST=“LinuxIFC” -DIFC -Dkind8 -DNGZhalf -DCACHE_SIZE=4000 -DPGF90 -Davoidalloc -DMPI_BLOCK=500
mpif77 -Mfree -O3 -c base.f90
pgf90: LICENSE MANAGER PROBLEM: No such feature exists
Feature: pgf90
License path: /opt/pgi/license.dat:license.dat
FLEXlm error: -5,357. System Error: 2 “No such file or directory”
For further information, refer to the FLEXlm End User Manual,
available at “”.
mpif77: No such file or directory
make: *** [base.o] Error 2

I think my PGI compiler has a valid license file, since I can use pgf90/pgf77 to compile some test fortran program without such error message.

In addition, I did the same thing on another Opteron cluster successfully, so something must be missing on my 4-way Opteron workstation.
Any idea?


Is the pgf90 that mpif77 invokes the same as the one you use from the command line? What’s the output of “pgf90 -V” and “mpif77 -V”? If they are different versions then it’s possible that license file is not valid for the pgf90 that mpif77 invokes.

A second possiblity is that the mpif77 script is using a different license file than the one you use with pgf90. What is the output of “echo $LM_LICENSE_FILE”? You output shows that mpif77 is using “/opt/pgi/license.dat”.

  • Mat

Thanks your reply. I chceked the versions of my pgf90 and pgf77,
they are the same:

chem@amd4p:/package/chem/vasp/vasp.4.6.26/vasp.4.6> pgf77 -V

pgf77 5.2-4
Copyright 1989-2000, The Portland Group, Inc. All Rights Reserved.
Copyright 2000-2004, STMicroelectronics, Inc. All Rights Reserved.
chem@amd4p:/package/chem/vasp/vasp.4.6.26/vasp.4.6> pgf90 -V

pgf90 5.2-4
Copyright 1989-2000, The Portland Group, Inc. All Rights Reserved.
Copyright 2000-2004, STMicroelectronics, Inc. All Rights Reserved.

The license file is the one for PGI:
chem@amd4p:/package/chem/vasp/vasp.4.6.26/vasp.4.6> echo $LM_LICENSE_FILE

Here is the content of the file:

SERVER amd4p 00e08161c8ac 7496
DAEMON pgroupd /opt/pgi/linux86-64/5.2/bin/pgroupd
FEATURE pghpf-linux86 pgroupd 5.200 31-dec-0 1 CB4890B17A30582CF69D
VENDOR_STRING=507001:4 HOSTID=00e08161c8ac ck=186
FEATURE pgf90-linux86 pgroupd 5.200 31-dec-0 1 AB782031F8776B57FD46
VENDOR_STRING=507001:4 HOSTID=00e08161c8ac ck=29
FEATURE pgf77-linux86 pgroupd 5.200 31-dec-0 1 9B689021B439174720CF
VENDOR_STRING=507001:4 HOSTID=00e08161c8ac ck=188
FEATURE pgcc-linux86 pgroupd 5.200 31-dec-0 1 CBA820C19935B09CC309
VENDOR_STRING=507001:4 HOSTID=00e08161c8ac ck=14
FEATURE pgcpp-linux86 pgroupd 5.200 31-dec-0 1 7BA80071263EC9090156
VENDOR_STRING=507001:4 HOSTID=00e08161c8ac ck=244
FEATURE pghpf-linux86-64 pgroupd 5.200 31-dec-0 1
9B2830E1987C088BBEC1 VENDOR_STRING=507001:4
HOSTID=00e08161c8ac ck=23
FEATURE pgf90-linux86-64 pgroupd 5.200 31-dec-0 1
9B68E041AD3AF0684E5B VENDOR_STRING=507001:4
HOSTID=00e08161c8ac ck=28
FEATURE pgf77-linux86-64 pgroupd 5.200 31-dec-0 1
HOSTID=00e08161c8ac ck=121
FEATURE pgcc-linux86-64 pgroupd 5.200 31-dec-0 1 1B2830A1E7B1439129E3
VENDOR_STRING=507001:4 HOSTID=00e08161c8ac ck=163
FEATURE pgcpp-linux86-64 pgroupd 5.200 31-dec-0 1
8B2820D14747FB42C7A5 VENDOR_STRING=507001:4
HOSTID=00e08161c8ac ck=53
FEATURE pgprof pgroupd 5.200 31-dec-0 1 DB68F0616C43BF195AF1
VENDOR_STRING=507001:4 HOSTID=00e08161c8ac ck=57
FEATURE pgdbg pgroupd 5.200 31-dec-0 1 EB28D08138C8176528A0
VENDOR_STRING=507001:4:ws HOSTID=00e08161c8ac ck=219
FEATURE pgdbg-linux86-64 pgroupd 5.200 31-dec-0 1
7B48F0218D664D69C79A VENDOR_STRING=507001:4:ws
HOSTID=00e08161c8ac ck=251

What’s the output of “mpif77 -V -dryrun”? (not pgf77) mpif77 is a script which comes with your MPI installation that has been configured to use pgf90 as it’s compiler. I’m wondering if the pgf90 that mpif77 is using is different than the one your using from the command line. This might be causing the license error since your license may not be valid for this other installation.