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

Ifort cannot be accessed from regular command line Windows 10

Feng__Jesse
New Contributor I
269 Views

Following the instructions from some other threads I could find, here is my system path exported with set path > path.txt. I organized the entries a bit for ease of reading. From what I can see, there should be no problem for my command line to recognize ifort, but my cmd is saying ifort is not a recognized internal or external command. Any suggestions would be greatly appreciated!

Path=

C:\Program Files (x86)\Intel\oneAPI\tbb\latest\redist\intel64\vc_mt\;

C:\Program Files (x86)\Intel\oneAPI\tbb\latest\redist\ia32\vc_mt\;

C:\Program Files (x86)\Intel\oneAPI\compiler\latest\windows\redist\intel64_win\compiler;

C:\Program Files (x86)\Intel\oneAPI\compiler\latest\windows\redist\ia32_win\compiler;

C:\Program Files (x86)\Common Files\Intel\Shared Libraries\intel64\;

C:\Program Files (x86)\Common Files\Intel\Shared Libraries\intel64\bin\;

C:\Program Files (x86)\Common Files\Intel\Shared Libraries\intel64\libfabric\bin\;

C:\Program Files (x86)\Common Files\Intel\Shared Libraries\intel64\libfabric\bin\utils\;

C:\Program Files (x86)\Common Files\Intel\Shared Libraries\;

C:\Program Files\Microsoft MPI\Bin\;

C:\Program Files\Java\jre1.8.0_60\bin;C:\Python27\;

C:\Python27\Scripts;C:\SIMULIA\Commands;

C:\MSC.Software\Patran_x64\20170\bin;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;

C:\Program Files (x86)\Intel\iCLS Client\;

C:\Program Files\Intel\iCLS Client\;

C:\Windows\system32;

C:\Windows;

C:\Windows\System32\Wbem;

C:\Windows\System32\WindowsPowerShell\v1.0\;

C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;

C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\;

C:\WINDOWS\system32;

C:\WINDOWS;

C:\WINDOWS\System32\Wbem;

C:\WINDOWS\System32\WindowsPowerShell\v1.0\;

C:\Python27;C:\Intel\DAL_1.9.9588.110\;

C:\WINDOWS\System32\OpenSSH\;

C:\DREAM3D_SDK\Cmake\bin;

C:\Program Files\Git\cmd;

C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;

C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;

C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2016.4.246\windows\bin;

C:\Program Files\MATLAB\R2020b\runtime\win64;

C:\Program Files\MATLAB\R2020b\bin;

C:\Program Files\MATLAB\R2019a\runtime\win64;

C:\Program Files\MATLAB\R2019a\bin;

C:\Program Files\Intel\WiFi\bin\;

C:\Program Files\Common Files\Intel\WirelessCommon\;

C:\Program Files\dotnet\;

C:\Users\zf1005.AD\AppData\Local\Microsoft\WindowsApps;

C:\Users\zf1005.AD\.dotnet\tools

PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC

Path_backup=

C:\Program Files\Microsoft MPI\Bin\;

C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;

C:\Program Files (x86)\Intel\iCLS Client\;

C:\Program Files\Intel\iCLS Client\;

C:\WINDOWS\system32;

C:\WINDOWS;

C:\WINDOWS\System32\Wbem;

C:\WINDOWS\System32\WindowsPowerShell\v1.0\;

C:\Program Files\Intel\WiFi\bin\;

C:\Program Files\Common Files\Intel\WirelessCommon\;

C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;

C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;

C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;

C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;

C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;

C:\SIMULIA\Abaqus\Commands;

C:\Program Files\MATLAB\R2018a\runtime\win64;

C:\Program Files\MATLAB\R2018a\bin

0 Kudos
1 Solution
mecej4
Black Belt
231 Views

Here is one problem: the PATH that you reported above does not contain the directory that contains the compiler driver, ifort.exe:

 

 

C:\Program Files (x86)\Intel\oneAPI\compiler\latest\windows\bin\intel64

 

 

The PATH as reported above shows a bit of clutter -- several versions of Matlab, SQL Server, etc., are included, which you could possibly remove from %PATH% and retry. Depending on the version of Windows and the build tools that you use, having %PATH% longer than a certain limit may cause problems.

A few things to try:

  • Try adding the path that I showed above to %PATH%
  • Look at the startup batch file c:\Program Files (x86)\Intel\oneAPI\setvars.bat
  • See if the following command, issued in a OneAPI command window, produces meaningful output:

 

 

set | findstr -i fort

 

 

View solution in original post

6 Replies
mecej4
Black Belt
232 Views

Here is one problem: the PATH that you reported above does not contain the directory that contains the compiler driver, ifort.exe:

 

 

C:\Program Files (x86)\Intel\oneAPI\compiler\latest\windows\bin\intel64

 

 

The PATH as reported above shows a bit of clutter -- several versions of Matlab, SQL Server, etc., are included, which you could possibly remove from %PATH% and retry. Depending on the version of Windows and the build tools that you use, having %PATH% longer than a certain limit may cause problems.

A few things to try:

  • Try adding the path that I showed above to %PATH%
  • Look at the startup batch file c:\Program Files (x86)\Intel\oneAPI\setvars.bat
  • See if the following command, issued in a OneAPI command window, produces meaningful output:

 

 

set | findstr -i fort

 

 

Feng__Jesse
New Contributor I
137 Views

Sorry, I have been busy, but adding the path you suggested worked. Thanks!

Devorah_H_Intel
Moderator
141 Views

Do you have oneAPI specific cmd shortcuts in Start Menu? Intel oneAPI command prompt for Intel 64 for Visual Studio 2022 located in 

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Intel oneAPI 2023 

Feng__Jesse
New Contributor I
138 Views

I do have the oneAPI CMDs. For x32 and x64. My machine uses x64.

Devorah_H_Intel
Moderator
132 Views

Those shortcuts run  "C:\Program Files (x86)\Intel\oneAPI\setvars.bat" intel64 vs2022"  for you.

Feng__Jesse
New Contributor I
130 Views

Yes that is correct. I  have been running Abaqus via the oneAPI cmds because of this. But the response above solved the issue. My normal system cmd can now recognize ifort. Thanks!

Reply