- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi everyone,
I am using 64bit desktop. I have recently installed ifort, Intel composerXE12 on ubuntu 11.04. just after installing, in the next step i have given the following command...
source /opt/intel/composerxe-2011.5.220/bin/compilervars.sh intel64
Everything work smoothly with the ifort command until I open a new terminal because It doesn't recognize the "ifort"anymore and gives "ifort: command not found". In order to recognize the "ifort"again i need to write the command I wrote above, and this goes for any new terminal I open.
I had tried with the intel64 and ia32 options for the compilervars.sh,compilervars_arch.sh,ifortvars.sh but nothing seems to work
Any suggestion about this problem I will appreciate it.
Thanks.
Jorge
Link Copied
10 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
put that whole 'source ...' command in a file ~/.bashrc
ron
ron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
wow, so simple and it works...
Thanks ron!!Jorge
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I do have same problem now... I am quite new ....
could you please tell me how to do this...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I do have the same problem..
Could you please let me know how to do this... I am quite new and I dont understand...
Thank you in advance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
the "compilervars.[sh|csh]" scripts set all necessary environment variables for your shell in order to use the Intel Compiler and Libraries right away. You do so by "sourcing" this script, which is updating your current shell's environment (instead of spawning a sub-shell). It is done in a way that all sub-shells you create henceforth (manually or indirectly) inherit the same environment variables. Thus you can consistently continue to use the Intel Compiler and Libraries in the same terminal; unless you terminate the shell where you sourced the "compilervars.[sh|csh]" scripts (e.g. closing the terminal).
Opening another terminal starts with a new shell without the environment variables set for Intel Compiler and Libraries.
The original question was how to automatize this and not manually sourcing all the time. The best way is to do the sourcing in the start-up scripts of your shell (e.g. .bashrc) - please see the manual of your shell.
For Bourne shell alikes you'd do
$ source/bin/compilervars.sh
...for C shell alikes this
$ source/bin/compilervars.csh
I hope this helps you.
Best regards,
Georg Zitzlsberger
the "compilervars.[sh|csh]" scripts set all necessary environment variables for your shell in order to use the Intel Compiler and Libraries right away. You do so by "sourcing" this script, which is updating your current shell's environment (instead of spawning a sub-shell). It is done in a way that all sub-shells you create henceforth (manually or indirectly) inherit the same environment variables. Thus you can consistently continue to use the Intel Compiler and Libraries in the same terminal; unless you terminate the shell where you sourced the "compilervars.[sh|csh]" scripts (e.g. closing the terminal).
Opening another terminal starts with a new shell without the environment variables set for Intel Compiler and Libraries.
The original question was how to automatize this and not manually sourcing all the time. The best way is to do the sourcing in the start-up scripts of your shell (e.g. .bashrc) - please see the manual of your shell.
For Bourne shell alikes you'd do
$ source
...for C shell alikes this
$ source
I hope this helps you.
Best regards,
Georg Zitzlsberger
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I have followed as you said.... but, same is the result....
Is there any problem with UBUNTU-12.04 ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
we don't support Ubuntu* 12.04 with the current Intel Composer XE 2011 version. Only Ubuntu* 10.04 & 11.04 are supported.
Ubuntu* 12.04 will be first supported with the next major version (Intel Composer XE 2013) for which we're currently running a BETA program:
http://software.intel.com/en-us/forums/showthread.php?t=104796
Best regards,
Georg Zitzlsberger
we don't support Ubuntu* 12.04 with the current Intel Composer XE 2011 version. Only Ubuntu* 10.04 & 11.04 are supported.
Ubuntu* 12.04 will be first supported with the next major version (Intel Composer XE 2013) for which we're currently running a BETA program:
http://software.intel.com/en-us/forums/showthread.php?t=104796
Best regards,
Georg Zitzlsberger
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
can I atleast install previous versions?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You're certainly entitled to try, with no guarantee of success or of full compatibility testing by Intel. Not knowing the details of Ubuntu 12, a possible issue is that g++ 4.7 compatibility is first supported by icpc in that beta version, yet that issue doesn't normally stop ifort from working.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We've already discovered that Ubuntu 12.04 puts gnu/stubs-32.h in a non-standard location and this causes problems for the Intel compilers. I agree with Tim that older versions are unlikely to work any better.

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