ifort: error #10052: could not checkout FLEXlm license

[yanyiaaa]

Hello：

Due to domain name resolution failure I can not reply to your company mail, so published a request for help, put the problem before and after the code below. Looking forward to your reply.

(base) tust212@tust212-Precision-7920-Tower:~/qe-7.3$ ./configure CC=mpiicc F77=mpiifort CXX=mpiicpc F90=mpiifort

configure: success

(base) tust212@tust212-Precision-7920-Tower:~/qe-7.3$ make all

test -d bin || mkdir bin

( cd UtilXlib ; make TLDEPS= all || exit 1 )

make[1]: 进入目录“/home/tust212/qe-7.3/UtilXlib”

ifort -O3 -g -cpp -D__FFTW -I/home/tust212/qe-7.3//external/devxlib/src -I. -I/home/tust212/qe-7.3//include -I. -c parallel_include.f90

Error: A license for FCompL is not available (-76,61026,2).

License file(s) used were (in this order):

1. Trusted Storage

** 2. /home/tust212/vasp/opt/intel/composer_xe_2015.0.090/bin/intel64/../../Licenses

** 3. /home/tust212/Licenses

** 4. /opt/intel/licenses

** 5. /Users/Shared/Library/Application Support/Intel/Licenses

**6./home/tust212/vasp/opt/intel/composer_xe_2015.0.090/bin/intel64/*.lic

Please visit http://software.intel.com/sites/support/ if you require technical assistance.

ifort: error #10052: could not checkout FLEXlm license

../make.inc:16: recipe for target 'parallel_include.o' failed

make[1]: *** [parallel_include.o] Error 1

make[1]: 离开目录“/home/tust212/qe-7.3/UtilXlib”

Makefile:209: recipe for target 'libutil' failed

make: *** [libutil] Error 1

[Vipin_S_Intel]

Hi Yan, we have sent you a private message and asked for some confidential information. Please check your community inbox and share the details with us via private message.

[Vipin_S_Intel]

Hi Yan, we have sent you a private message. Kindly check your community inbox.

[Vipin_S_Intel]

Hi Yan, could you please share the below details for further investigation: 

1. Are you using Intel® Software License Manager?
2. Exact name of the Intel® product with an update number and its build version.

[Vipin_S_Intel]

Hi Yan, unfortunately, we were unable to hear back from you. 

If you have any further queries, please post a new question, as this thread will no longer be monitored by Intel®.