topic Re: oneAPI command line in Intel® Fortran Compiler

oneAPI command line

Rodrigues__Pedro — Tue, 16 Feb 2021 12:45:21 GMT

I started command line from oneAPI prompt and ifort and icl aren't on the path.

Is this an issue(bug)?

Re: oneAPI command line

mecej4 — Tue, 16 Feb 2021 12:59:35 GMT

Which packages did you install? Did you install just the base OneAPI toolkit, or did you also install the HPC toolkit? Open the Windows Programs and Features control panel. Do you see the OneAPI compilers listed in it?

Re: oneAPI command line

Rodrigues__Pedro — Tue, 16 Feb 2021 13:36:37 GMT

Yes. I have both installed

Re: oneAPI command line

Ron_Green — Tue, 16 Feb 2021 15:28:42 GMT

What about 'icx' and 'dpcpp' are those found? Just try

icx -V

dpcpp -V

and also try

ifx -V

You can try to uninstall the HPC Toolkit and try to re-install it.

Re: oneAPI command line

Rodrigues__Pedro — Tue, 16 Feb 2021 16:55:48 GMT

nothing. also mpiexec isn't found. It seems that nothing is set. nor the compiler nor mpi or mkl

Re: oneAPI command line

Steve_Lionel — Tue, 16 Feb 2021 17:42:23 GMT

I am unsure what you mean by "started command line from oneAPI prompt". What exactly did you do? Which OS is this?

If you simply started a command prompt session, then this is expected behavior. In order to get the compilers added to the executables path, you have to invoke the compiler's setvars script. The Windows install adds a shortcut to the Start menu to do this, or you can call setvars.bat yourself. I'll also comment that on Windows, if you're using Powershell instead of cmd.exe, this won't work. See Solved: ifort not recognized as an internal or external command - Intel Community for more info.

Re: oneAPI command line

Rodrigues__Pedro — Tue, 16 Feb 2021 18:00:36 GMT

I am on WIN10 with VS2019. I used the oneAPI command line shortcut added after the installation. I also called setvars.bat and nothing.

Re: oneAPI command line

Rodrigues__Pedro — Tue, 16 Feb 2021 18:12:37 GMT

I suppose that setvar script doesn't have the lines to add:

- ifort;

- icl;

- mpiexec;

- MPI library path(.lib and .dll);

- MKL library path (.lib and .dll);

how can I change the script to add these?

Re: oneAPI command line

Steve_Lionel — Tue, 16 Feb 2021 20:44:00 GMT

You don't need to modify setvars.bat.

Please show a screenshot of the command prompt window from the start where it opens and when you type "ifort".

Re: oneAPI command line

Rodrigues__Pedro — Tue, 16 Feb 2021 21:09:28 GMT

see the image attached

Re: oneAPI command line

Steve_Lionel — Tue, 16 Feb 2021 23:04:32 GMT

Thanks for the image. The problem here is the error about "findstr", that is aborting the setvars. As best as I can tell, this is coming from some component other than the compiler calling a sys_check.bat file which invokes Python to do a "findstr". I see that some of the oneAPI components require that Python be installed (the compiler does not.)

See if installing the latest Python (from python.org) resolves this. If not, perhaps one of the Intel support people will pick this up.

Re: oneAPI command line

Rodrigues__Pedro — Wed, 17 Feb 2021 00:36:35 GMT

I have Python. Os this a VS2019 conflict?

Re: oneAPI command line

Steve_Lionel — Wed, 17 Feb 2021 01:32:09 GMT

Nothing to do with VS2019. Let me suggest this. Run the oneAPI Base installer again. When it lets you select which components are installed, uncheck all but "Intel Distribution for GDB", let it finish and see what happens when you try again.

One of the Base components is giving an error in its setup, but it isn't a component I have installed so I can't tell which one it is. It isn't the compiler, that much I can tell you.

If you have support, open a ticket at Online Service Center Otherwise, hope that one of the support reps picks up on this and helps you.

Re: oneAPI command line

Rodrigues__Pedro — Wed, 17 Feb 2021 14:42:48 GMT

Got the same: see attached file.

Re: oneAPI command line

mecej4 — Wed, 17 Feb 2021 15:04:55 GMT

findstr is a standard Windows command utility. If it cannot be found, the implication is that an earlier step in the installer script (or other batch scripts that the installer script called) corrupted %PATH% and, as a result, the findstr command is no longer accessible.

Re: oneAPI command line

Ron_Green — Wed, 17 Feb 2021 15:20:19 GMT

on that command window, do this and send us the output

echo %PATH%

the PATH environment variable is of fixed number of characters. If you have a LOT of installed software it's quite possible the character limit was exceeded. You mentioned some possible conflict with older versions of PSXE. How many PSXE versions do you have installed? Could you remove some apps? But first let's see that PATH. We suspect it may be over the character limit and it's truncated, missing some key paths.

Re: oneAPI command line

Rodrigues__Pedro — Wed, 17 Feb 2021 15:26:04 GMT

attached the $PATH to the file

Re: oneAPI command line

Rodrigues__Pedro — Thu, 18 Feb 2021 15:11:15 GMT

I don't have any more PSXE installed. What is missing on the PATH var?

Re: oneAPI command line

Steve_Lionel — Thu, 18 Feb 2021 15:53:44 GMT

You're missing "C:\Windows\system32;C:\Windows;C:\Windows\System32" at a minimum. Windows\System32 is where findstr is located, and missing those will cause a lot of problems.

The inclusion of ' ' in your path is troubling - it should be removed. Do you know how to edit system environment variables?

After removing that, reboot and try again.

Re: oneAPI command line

Rodrigues__Pedro — Thu, 18 Feb 2021 16:38:16 GMT

Windows GUI (ENV vars) doesn't show all the path. The oneAPI path is loaded at command and has a lot more keys. So, I don't know how where to change it outside the oneAPI prompt. Can you help?