- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I completed installing the parallel studio xe 2016.1.056 for linux on my centos 7.
For using ifort command, I implemented the following commands,
#./opt/intel/bin/ifortvars.sh intel64
#./opt/intel/bin/compilervars.sh intel64.
But still I get "ifort: command not found" when I use ifort command.
What is the problem? Please help me...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re the commands in #1: There is a missing space between '.' and '/' at the beginning. That changes the functionality of the "source" shell feature considerably. Furthermore, the sourcing should be done in the normal shell window that you use for development, not in an 'su' shell.
The instructions in the release notes spell all this out clearly. Be sure to follow them to the letter, or beware that changing the instructions should be done only if you are confident of the effects of those changes.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You should need only one of those commands. Can you show the value of the "path" environment variable after the command? Are you running ifort from the same terminal window in which you "sourced" ifortvars.sh?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re the commands in #1: There is a missing space between '.' and '/' at the beginning. That changes the functionality of the "source" shell feature considerably. Furthermore, the sourcing should be done in the normal shell window that you use for development, not in an 'su' shell.
The instructions in the release notes spell all this out clearly. Be sure to follow them to the letter, or beware that changing the instructions should be done only if you are confident of the effects of those changes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just in case, the intended "dot space" shell command is shorthand for "source", a completely different meaning from ./ which means file system root. Attempting the shorthand notation has been known to produce bugs in documentation as well as in user invocations.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
mecej4 wrote:
Re the commands in #1: There is a missing space between '.' and '/' at the beginning. That changes the functionality of the "source" shell feature considerably. Furthermore, the sourcing should be done in the normal shell window that you use for development, not in an 'su' shell.
The instructions in the release notes spell all this out clearly. Be sure to follow them to the letter, or beware that changing the instructions should be done only if you are confident of the effects of those changes.
I just resolved the problem. you are right. Thank you very much!! have a nice Christmas!!

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page