Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

Problems installing Intel Fortran version 16

jayb
Beginner
1,156 Views

I am having several problems installing Intel Fortran version 16 from a user account (not root), using an offline license file.  

First problem occurs at the end of installation.  Some final steps require root privileges:

Finalizing product configuration...
--------------------------------------------------------------------------------
mkdir: cannot create directory `/home/documentation_2016': Permission denied
ln: creating symbolic link `/home/documentation_2016/en/clck': No such file or directory
mkdir: cannot create directory `/home/samples_2016': Permission denied
ln: creating symbolic link `/home/samples_2016/en/clck': No such file or directory
mkdir: cannot create directory `/home/documentation_2016': Permission denied
ln: creating symbolic link `/home/documentation_2016/en/itac': No such file or directory
mkdir: cannot create directory `/home/samples_2016': Permission denied
ln: creating symbolic link `/home/samples_2016/en/itac': No such file or directory

------------------------------------------------------------------------------------------------------

After that, the ifort command cannot find the license file:

[braun@sequoia ~]$ ifort --version

Error: A license for Comp-FL is not available now (-15,570,115).

A connection to the license server could not be made.  You should
make sure that your license daemon process is running: both an
lmgrd process and an INTEL process should be running
if your license limits you to a specified number of licenses in use
at a time.  Also, check to see if the wrong port@host or the wrong
license file is being used, or if the port or hostname in the license
file has changed.

License file(s) used were (in this order):
    1.  Trusted Storage
**  2.  /home/braun/COM_L__xxxx_xxxx-xxxxxxxx.lic <original content edited>
**  3.  /home/braun/intel/compilers_and_libraries_2016.0.109/linux/bin/intel64/../../Licenses
**  4.  /home/braun/Licenses
**  5.  /opt/intel/licenses
**  6.  /Users/Shared/Library/Application Support/Intel/Licenses
**  7.  /home/braun/intel/compilers_and_libraries_2016.0.109/linux/bin/intel64/*.lic

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

ifort: error #10052: could not checkout FLEXlm license

-------------------------------------------------------------------------------------------------------

I am using the new license file sent by Intel:

[braun@sequoia ~]$ pwd
/home/braun
[braun@sequoia ~]$ ls *.lic
COM_L__xxxx_xxxx-xxxxxxxx.lic <original content edited>

Contents of license file:

<original content removed>

---------------------------------------------------------------------------------------

The environment variable is set (is this still the right name?)

export INTEL_LICENSE_FILE=/home/braun/COM_L__xxxx_xxxx-xxxxxxxx.lic  <original content edited>

-------------------------------------------------------------------------------------

Finally, will the license file only work on the server named sequoia?  I have a 5-seat floating license using offline license files.

Jay

0 Kudos
6 Replies
Kevin_D_Intel
Employee
1,156 Views

I captured the sensitive details about your license and removed those details from your post. Best not to share those in the post itself but rather through private communication if necessary.

I reproduced the mkdir/symbolic link errors with the non-root installation. Those should have been made relative to the default installation directory, in your case /home/braun/intel/. I will report this to our Installation Developers (and update the internal tracking id below) and keep you updated on what I hear.

You can work around these link errors by using the Customize installation option and adding one-level to the target installation directory, i.e., set the installation directory to something like: /home/braun/intel/intel2

Regarding the license issues, the installation (sans the mkdir/ln errors) successfully used your floating license in an offline-mode as expected. The error received when invoking ifort relates to not having the license server running to manage the floating license actual usage. Yes, the server license is keyed to run on the server named sequoia. You need to install the Intel License Manager software on sequoia to manage the license in order to use the compiler and product libraries/features.

(Internal tracking id: DPD200375503)

(Resolution Update on 12/04/2015): This defect is fixed in the Intel® Parallel Studio XE 2016 Update 1 Release (PSXE 2016.1.056 / CnL 2016.1.150 - Linux)

0 Kudos
taisei_i_
Beginner
1,156 Views

I installed Intel Parallel Studio XE Cluster Edition for Linux in order to compile Fortran.

I think the installation was successful.

But when I tried to compile program made with emacs, an error occured.

--------------------------------------------------------------------------------------------------------------

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

License file(s) used were (in this order):
    1.  Trusted Storage
**  2.  /home/itoh/intel/compilers_and_libraries_2016.1.150/linux/bin/intel64/../../Licenses
**  3.  /home/itoh/Licenses
**  4.  /opt/intel/licenses
**  5.  /Users/Shared/Library/Application Support/Intel/Licenses
**  6.  /home/itoh/intel/compilers_and_libraries_2016.1.150/linux/bin/intel64/*.lic

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

ifort: error #10052: could not checkout FLEXlm license

--------------------------------------------------------------------------------------------------------------

I am not very knowledgeable about programming, so please teach me what I should do.

0 Kudos
Kevin_D_Intel
Employee
1,156 Views

It appears you installed into your /home/itoh area so I expect you suffered from the same issues as the original poster.

Unfortunately the defect that I noted earlier has not yet been fixed.

To install into your /home/itoh area, I advise that you uninstall the current PSXE 2016 you have and then re-install to employ the suggested work around in my post #2 of adding one-level to the target installation directory. In your case, when doing a re-installation, use a custom directory of: /home/itoh/intel/intel2

Let me know whether this helps.

0 Kudos
jayb
Beginner
1,156 Views

Kevin,

I recently installed update 1 in my original manner, with an off-line license file, and it seemed to work.  There were also some (very) minor differences in the prompts and responses, but all went well, i.e., I installed under /home/<user>/ without customizing the installation.  

I will be installing again on another computer next week, so I can verify that this is the case.

Jay

 

 

 

0 Kudos
Kevin_D_Intel
Employee
1,156 Views

Jay - Thank you for the update. I’m glad to hear about your success. The “2016.1.150” string in the details from the other user’s post indicates they too installed PSXE 2016 Update 1. There’s no indication from Development regarding a fix so I pinged them for current status. Keep us posted on how your subsequent installation goes.

0 Kudos
Kevin_D_Intel
Employee
1,156 Views

@Jay - Development confirmed the underlying defect with the installation noted in your original post was fixed in PSXE 2016 Update 1; they apologize for failing to update the internal tracking id. You should be good for your planned installations next week. Thank you for reporting that defect.

@taisei - Your issue must involve a matter different than what Jay reported. I am not really that familiar with using emacs so perhaps there’s a relation there, or it could be a license issue of some sort. We could test both if you try the compiler outside of emacs. To do that, source the psxevars.sh under your installation (should be located under: /home/itoh/intel/parallel_studio_xe_2016.1.056) and then run the compiler using the ifort -V command. That should display the compiler banner unless there is an underlying license issue in which case you will see an error like that in your earlier post.

0 Kudos
Reply